Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-23732

[SET](7.4.z) WFLY-16464 - SSO not require restart

    XMLWordPrintable

Details

    • False
    • None
    • False
    • Hide
      1. Deploy secured-web.war
      2. Enable sso on undertow
      3. Change path on sso
      4. Login on http://127.0.0.1:8080/secured-web/user/index.jsp
      5. The path in JSESSIONIDSSO cookie is not changed
      6. Reload/restart server
      7. Login again and the JSESSIONIDSSO is changed
      Show
      Deploy secured-web.war Enable sso on undertow Change path on sso Login on http://127.0.0.1:8080/secured-web/user/index.jsp The path in JSESSIONIDSSO cookie is not changed Reload/restart server Login again and the JSESSIONIDSSO is changed

    Description

      When updated path for single sign-on the path in cookie is same as before even the path attribute show changed path. When reload/restart server the path in cookie is changed to new path. The problem is nothing indicate to reload/restart server as it does in other cases by changing "process-state" status. Only resource description of sso is mentioning the reload by "restart-required" => "all-services". So the server should be showing that it's need to be reloaded/restarted. Other sso attributes probably have same problem but not tested.

      .   

      Attachments

        Issue Links

          clones

          Bug - A problem which impairs or prevents the functions of the product. WFLY-16464 Change of undertow/single-sign-on attributes does not require restart

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JBEAP-23610 SSO not require restart

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Activity

            Public project attachment banner

              context keys: [headless, issue, helper, isAsynchronousRequest, project, action, user]
              current Project key: JBEAP

              People

                thofman Tomas Hofman
                thofman Tomas Hofman
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: