Back to bug 1044772
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Brian Stansberry | 2013-12-19 16:44:42 UTC | Assignee | brian.stansberry | darran.lofthouse |
| Darran Lofthouse | 2013-12-19 17:56:59 UTC | Status | NEW | ASSIGNED |
| Link ID | JBoss Issue Tracker WFLY-2672 | |||
| Darran Lofthouse | 2014-01-29 12:48:59 UTC | Doc Text | Cause: No trace or debug logging is currently logged for the loading of LDAP groups by the security realms. Consequence: Diagnosing configuration issues for the group loading is very difficult due to the lack of debug logging. Fix: Generous amounts of trace logging for the loading of groups is now logged to the 'org.jboss.as.domain.management.security' category. Result: Trace logging of the group loading can be obtained for the 'org.jboss.as.domain.management.security' category. Note: The logging is very verbose hence the decision to log at trace level rather than debug. |
|
| mark yarborough | 2014-01-29 13:01:24 UTC | CC | myarboro | |
| Darran Lofthouse | 2014-01-29 13:07:08 UTC | Status | ASSIGNED | POST |
| Kabir Khan | 2014-01-31 10:18:18 UTC | Status | POST | MODIFIED |
| CC | kkhan | |||
| Target Milestone | --- | DR0 | ||
| Paul Gier | 2014-02-12 03:34:06 UTC | Status | MODIFIED | ON_QA |
| Target Release | --- | EAP 6.3.0 | ||
| Ondrej Lukas | 2014-03-05 12:54:08 UTC | Status | ON_QA | VERIFIED |
| CC | olukas | |||
| Scott Mumford | 2014-04-28 04:52:22 UTC | CC | smumford | |
| Doc Text | Cause: No trace or debug logging is currently logged for the loading of LDAP groups by the security realms. Consequence: Diagnosing configuration issues for the group loading is very difficult due to the lack of debug logging. Fix: Generous amounts of trace logging for the loading of groups is now logged to the 'org.jboss.as.domain.management.security' category. Result: Trace logging of the group loading can be obtained for the 'org.jboss.as.domain.management.security' category. Note: The logging is very verbose hence the decision to log at trace level rather than debug. | In previous versions of JBoss EAP 6 TRACE and DEBUG logging had not been added to the LDAP interactions within the security realms. This made diagnosing authentication issues where LDAP is in use extremely difficult as no logging was available. Verbose TRACE logging for the loading of groups has been added in this release and is now logged to the <literal>org.jboss.as.domain.management.security</literal> category. This new logging has been limited to the TRACE level due to the verbosity at the DEBUG level. Customers can now use these logs to diagnose LDAP related issues with security realms. | ||
| Doc Type | Bug Fix | Enhancement | ||
| mark yarborough | 2014-06-28 15:24:30 UTC | CC | sgilda | |
| Doc Text | In previous versions of JBoss EAP 6 TRACE and DEBUG logging had not been added to the LDAP interactions within the security realms. This made diagnosing authentication issues where LDAP is in use extremely difficult as no logging was available. | In previous versions of JBoss EAP 6 TRACE and DEBUG logging had not been added to the LDAP interactions within the security realms. This made diagnosing authentication issues where LDAP is in use extremely difficult as no logging was available. | ||
| Doc Text | Verbose TRACE logging for the loading of groups has been added in this release and is now logged to the <literal>org.jboss.as.domain.management.security</literal> category. This new logging has been limited to the TRACE level due to the verbosity at | Verbose TRACE logging for the loading of groups has been added in this release and is now logged to the `org.jboss.as.domain.management.security` category. This new logging has been limited to the TRACE level due to the verbosity at the DEBUG level. | ||
| Doc Text | the DEBUG level. Customers can now use these logs to diagnose LDAP related issues with security realms. | Customers can now use these logs to diagnose LDAP related issues with security realms. | ||
| Status | VERIFIED | CLOSED | ||
| Resolution | --- | CURRENTRELEASE | ||
| Last Closed | 2014-06-28 11:24:30 UTC |
Back to bug 1044772