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

(7.0.x) UNDERTOW-1006 - JSESSIONID not trusted by CachedAuthenticatedSessionHandler

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.0.6.GA, 7.0.7.CR1, 7.0.7.GA
    • None
    • None
    • None
    • EAP 7.0.7

    Description

      As described in this forum post and in the following reproducer application when an HttpSesion is created from a secured call without previous provided JSESSIONID, the generated JSESSIONID is not stable and is regenerated by a next secured call.
      This behavior causes calls failures if several parallel calls are fired behind the first one.

      Why the generated JSESSIONID is not trusted whereas it is issued by a secure call without previous JSESSIONID?

      The only workarounds I have found so far are:

      • make an unnecessary secured call in order to stabilize the JSESSIONID before the parallel calls are fired
      • or deactivate ChangeSessionIdOnLogin feature by the use of an undertow servlet extension (introduction of security issue)

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-9706 JSESSIONID not trusted by CachedAuthenticatedSessionHandler

          • 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
          incorporates

          Bug - A problem that impairs or prevents the functions of the product. UNDERTOW-1006 JSESSIONID not trusted by CachedAuthenticatedSessionHandler

          • 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.
          • Resolved
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-8650 (7.0.z) Upgrade undertow from 1.3.27.Final to 1.3.28.Final

          • 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

            People

              sdouglas1@redhat.com Stuart Douglas
              sdouglas1@redhat.com Stuart Douglas
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: