Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Blocker
    • Resolution: Done
    • Affects Version/s: 1.1.0.Beta53
    • Fix Version/s: 1.1.0.Beta54
    • Component/s: HTTP
    • Labels:
      None

      Description

      Intention on legacy security realm is tracked by JBEAP-8563:

      • If this is the only mechanism enabled then 500 is the correct status code
      • however if a fallback mechanism was also enabled then that mechanism should be able to challenge with a HTTP 401 status code.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  dlofthouse Darran Lofthouse
                  Reporter:
                  dlofthouse Darran Lofthouse
                  Tester:
                  Martin Choma
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: