[
https://issues.jboss.org/browse/WFLY-5719?page=com.atlassian.jira.plugin....
]
Brett Prucha commented on WFLY-5719:
------------------------------------
Ahh that would explain it. I went with option 1 but did find the Kerberos class in the
negotiation module and thought about trying to explicitly include that module but that
didn't seem correct as I figured it should have been loaded by default. Hence why I
concluded a class loading problem. What do I gain by using the Wildfly provided login
module other than being more JVM independent? I can't seem to find any documentation
on it.
Using Kerberos as login module results in LoginException: unable to
find LoginModule class
------------------------------------------------------------------------------------------
Key: WFLY-5719
URL:
https://issues.jboss.org/browse/WFLY-5719
Project: WildFly
Issue Type: Bug
Components: Security
Affects Versions: 9.0.2.Final, 10.0.0.CR4
Environment: Windows Server 2012 R2, Java 8 update 40
Reporter: Brett Prucha
Assignee: Darran Lofthouse
When using <login-module code="Kerberos" flag="required">, the
following exception is thrown:
javax.security.auth.login.LoginException: unable to find LoginModule class:
org.jboss.security.negotiation.KerberosLoginModule
When replacing the login module with the one provided by the JVM:
<login-module code="com.sun.security.auth.module.Krb5LoginModule"
flag="required">
no exception is thrown and authentication works as expected.
The Kerberos login module works in Wildfly 8.2.0. It appears the class loading or
something similar has changed in 9.x onwards to cause this to stop working.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)