[jboss-jira] [JBoss JIRA] (ELY-680) No log messages comming from Elytron - kerberos
[
https://issues.jboss.org/browse/ELY-680?page=com.atlassian.jira.plugin.sy...
]
Martin Choma reopened ELY-680:
------------------------------
Verification failed.
Please implement reasonable toString() method on logged Objects.
{code:title-server.log}
09:56:25,124 TRACE [org.wildfly.security] (default task-34) Caching GSSContext
sun.security.jgss.GSSContextImpl@57e9e7a0
09:56:25,135 TRACE [org.wildfly.security] (default task-35) Sending intermediate
challenge: [B@633f813
09:56:25,135 TRACE [org.wildfly.security] (default task-35) Handling
SecurityIdentityCallback: identity =
org.wildfly.security.auth.server.SecurityIdentity@8f4177d
09:56:25,123 TRACE [org.wildfly.security] (default task-34) Using
SpnegoAuthenticationMechanism to authenticate HTTP/localhost.localdomain(a)JBOSS.ORG using
the following mechanisms: [[Lorg.ietf.jgss.Oid;@592e12f5]
{code}
No log messages comming from Elytron - kerberos
-----------------------------------------------
Key: ELY-680
URL: https://issues.jboss.org/browse/ELY-680
Project: WildFly Elytron
Issue Type: Bug
Components: Authentication Mechanisms
Reporter: Martin Choma
Assignee: Jan Kalina
Priority: Critical
Elytron is missing log messages related to kerberos authentication. These log messages
should be added. See JBEAP-6041 for more details.
I consider to be useful to have TRACE log messages at least in:
- SpnegoAuthenticationMechanism
- GSSCredentialSecurityFactory
If there are more classes involved in kerberos authnetication include them as well.
Kerberos issues are very specific. So it is very important to have as much trace
information as possible. Therefore raising priority to Critical.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)