[
https://issues.jboss.org/browse/ELY-1225?page=com.atlassian.jira.plugin.s...
]
Jan Kalina edited comment on ELY-1225 at 7/3/17 5:00 AM:
---------------------------------------------------------
PR 1: trace into mechs factories
PR 2: toString of delegating objects
was (Author: honza889):
Second PR: toString of delegating objects
Elytron - Write SASL mechanism implementing class into trace log
----------------------------------------------------------------
Key: ELY-1225
URL:
https://issues.jboss.org/browse/ELY-1225
Project: WildFly Elytron
Issue Type: Bug
Components: Authentication Client
Affects Versions: 1.1.0.Beta50
Reporter: Jan Kalina
Assignee: Jan Kalina
Priority: Critical
Fix For: 1.1.0.Beta51
It's very hard to debug issues when a wrong SASL mechanism implementation is used
(e.g. JDK provided one instead Elytron one). The class name implementing the mechanism
should be logged by Elytron.
One place to cover this could be
{{org.wildfly.security.auth.client.AuthenticationConfiguration.createSaslClient()}}
method, but there are probably more places to look into.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)