[jboss-jira] [JBoss JIRA] (ELY-1225) Elytron - Write SASL mechanism implementing class into trace log

[Jan Kalina (JIRA)]

     [ https://issues.jboss.org/browse/ELY-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jan Kalina moved JBEAP-11360 to ELY-1225:
-----------------------------------------

              Project: WildFly Elytron  (was: JBoss Enterprise Application Platform)
                  Key: ELY-1225  (was: JBEAP-11360)
             Workflow: GIT Pull Request workflow   (was: CDW with loose statuses v1)
          Component/s: Authentication Client
                           (was: Security)
    Affects Version/s: 1.1.0.Beta50
                           (was: 7.1.0.DR19)


> 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
>
> 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)