[ https://issues.jboss.org/browse/WFLY-5719?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on WFLY-5719: ---------------------------------------- Thanks, I see where the problem is. The problem is not that our classloading has changed - the problem is that we have switched which LoginModule is used when 'Kerberos' is specified as the login module. Previously we just mapped to the Sun/Oracle implementation - however now we map to our own module which wraps the JDK supplied implementation after detecting which one is available (IBM is a different fully qualified class name) and also we have a couple of additional configuration options. For the error you are experiencing there are two options really: - 1 - Specify the fully qualified class name of the login module in the security domain configuration. 2 - Add a jboss-deployment-structure.xml to your deployment and also define a dependency on the "org.jboss.security.negotiation" module. Unfortunately the APIs and SPIs around JAAS config do not give us an option to take control of class loading and specifying the classloader when the LoginContext is created directly by an application. -- This message was sent by Atlassian JIRA (v6.4.11#64026)