• Documentation (Ref Guide, User Guide, etc.), User Experience
    • Hide
      1. Apply attached configuration and deploy attached applications.
      2. Add SSO configuration:
        /subsystem=undertow/application-security-domain=applicationSecurityDomain-UndertowSecurityDomainFormSsoTestCase/setting=single-sign-on:add(domain=localhost,key-store=keyStore-UndertowSecurityDomainFormSsoTestCase,credential-reference={clear-text=secret},key-alias=localhost)
      3. Hit localhost:8080/app1/protected.
      4. Enter userA and passwordA to login form.
      5. GOOD is returned.
      6. Hit localhost:8080/app2/protected.
      7. GOOD should be returned (not a login form).
      Show
      Apply attached configuration and deploy attached applications. Add SSO configuration: /subsystem=undertow/application-security-domain=applicationSecurityDomain-UndertowSecurityDomainFormSsoTestCase/setting=single-sign-on:add(domain=localhost,key-store=keyStore-UndertowSecurityDomainFormSsoTestCase,credential-reference={clear-text=secret},key-alias=localhost) Hit localhost:8080/app1/protected . Enter userA and passwordA to login form. GOOD is returned. Hit localhost:8080/app2/protected . GOOD should be returned (not a login form).

      The operation adding Elytron SSO configuration to Undertow subsystem returns {"outcome" => "success"}. However the SSO does not work without performing reload. It is very confusing for an administrator.

      The reload should not be required, or a response header requiring reload should be returned.

            [JBEAP-9917] Adding Elytron SSO to Undertow should announce reload-required

            Moving verified to closed.

            Michaela Osmerova added a comment - Moving verified to closed.

            Verified for 7.1.0.DR17.

            Ondrej Kotek added a comment - Verified for 7.1.0.DR17.

            rhn-support-dlofthouse, thanks for your feedback. I have updated the summary and description to match the feedback.

            Ondrej Kotek added a comment - rhn-support-dlofthouse , thanks for your feedback. I have updated the summary and description to match the feedback.

            This was triaged as a blocker yesterday because the feature requires a reload however the operation completes without informing the user a reload is required.

            This is not a blocker to eliminate the need for a reload, just to ensure this state is correctly reported to the user performing the configuration.

            Darran Lofthouse added a comment - This was triaged as a blocker yesterday because the feature requires a reload however the operation completes without informing the user a reload is required. This is not a blocker to eliminate the need for a reload, just to ensure this state is correctly reported to the user performing the configuration.

            The priority has been raised because this should be solved in GA (see description and comments).

            rhn-support-dlofthouse, do you still consider this to be solved in GA? Could you set appropriate priority please?

            Ondrej Kotek added a comment - The priority has been raised because this should be solved in GA (see description and comments). rhn-support-dlofthouse , do you still consider this to be solved in GA? Could you set appropriate priority please?

            Paul Ferraro added a comment - - edited

            Why is this a blocker? Requiring a server reload is not a bug, but a usability improvement.

            Paul Ferraro added a comment - - edited Why is this a blocker? Requiring a server reload is not a bug, but a usability improvement.

            Raising to Critical. Hitting this issue leads to very frustrating user experience.

            Ondrej Kotek added a comment - Raising to Critical. Hitting this issue leads to very frustrating user experience.

              pferraro@redhat.com Paul Ferraro
              okotek@redhat.com Ondrej Kotek
              Ondrej Kotek Ondrej Kotek
              Ondrej Kotek Ondrej Kotek
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: