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

add trace logging to the SSO code in undertow

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 7.0.1.CR2, 7.0.1.GA
    • None
    • Undertow
    • None
    • Release Notes
    • Documented as Known Issue
    • EAP 7.0.1

    Description

      Please add trace logging to the SSO code in wildfly/undertow.

      For example, it would be helpful if the sso code logged that it was getting triggered, if re-authentication was happening, etc.

      This is going to be very difficult to support if we do not have this type of information.

      Attachments

        Issue Links

          causes

          Sub-task - The sub-task of the issue JBEAP-4453 Document JBEAP-3998 for RN

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

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) UNDERTOW-711 add trace logging to the SSO code in undertow

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved
          is cloned by

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) UNDERTOW-711 add trace logging to the SSO code in undertow

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-5060 Upgrade Undertow from 1.3.22.Final to 1.3.23.Final

          • 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.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-5152 move trace logging for SSO code in Undertow to use 'SECURITY_LOGGER'

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBEAP-5099 add trace logging to the SSO code in wildfly (undertow)

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Activity

            People

              rhn-support-iweiss Ingo Weiss
              rhn-support-dehort Derek Horton
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 2 days
                  2d
                  Remaining:
                  Time Spent - 1 day Remaining Estimate - 1 day
                  1d
                  Logged:
                  Time Spent - 1 day Remaining Estimate - 1 day
                  1d