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.
- is cloned by
-
ELY-1225 Elytron - Write SASL mechanism implementing class into trace log
-
- Resolved
-
- is incorporated by
-
JBEAP-12265 Upgrade WildFly Elytron to 1.1.0.CR3
-
- Closed
-
-
-
- Closed
-
