Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-8474

Adding Elytron SSO to Undertow should announce reload-required

    XMLWordPrintable

Details

    • 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).
    • Documentation (Ref Guide, User Guide, etc.), User Experience

    Description

      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.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-9917 Adding Elytron SSO to Undertow should announce reload-required

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: