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

(7.0.z) Provide username in trace logging for sec constraint during logout

    XMLWordPrintable

Details

    • EAP 7.0.2

    Description

      With addition of trace logging for security constraint processing, there is added debug message Logging out user... here is the source. Unfortunatelly this will be translated into the log like this:

      DEBUG [io.undertow.request.security] (default task-4) Logging out user org.wildfly.extension.undertow.security.AccountImpl@36ebcb for HttpServerExchange{ GET /secured-web/logout.jsp request {Connection=[Keep-Alive], Accept-Encoding=[gzip,deflate], Cookie=[JSESSIONID=wLMwH7gyCnqb5ZKcAxcjRF8j7UIuo9FEA38VKe6s.dhcp-10-40-4-199], User-Agent=[Apache-HttpClient/4.5.1 (Java/1.8.0_91)], Host=[127.0.0.1:8080]} response {X-Powered-By=[Undertow/1, JSP/2.3], Server=[JBoss-EAP/7], Content-Type=[text/html;charset=utf-8]}}

      Problem I see here is that there is printed only string of AccountImpl instance, not actual user name that has logout.

      Is it possible to provide username instead in this case instead?

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-5286 (7.1.0) Provide username in trace logging for sec constraint during logout

          • 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
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. UNDERTOW-743 Provide username in trace logging for sec constraint during logout

          • 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-5116 (7.0.z) Upgrade Undertow from 1.3.23.Final to 1.3.24.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.
          • Verified
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-4255 add trace logging to the security constraint processing in wildfly/undertow

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

          Activity

            People

              sdouglas1@redhat.com Stuart Douglas
              jstourac@redhat.com Jan Stourac
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: