-
Bug
-
Resolution: Done
-
Minor
-
3.3.4.Final, 4.0.7.Final
-
None
RemoteKerberosChannelTest fails with IBM jdk 1.8 on login:
Running org.jboss.remoting3.test.RemoteKerberosChannelTest
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 13.038 sec <<< FAILURE!
org.jboss.remoting3.test.RemoteKerberosChannelTest Time elapsed: 13.037 sec <<< ERROR!
javax.security.auth.login.FailedLoginException: Login error: com.ibm.security.krb5.KrbException, status code: 9
message: The client or server has a null key
at com.ibm.security.jgss.i18n.I18NException.throwFailedLoginException(I18NException.java:48)
at com.ibm.security.auth.module.Krb5LoginModule.a(Krb5LoginModule.java:328)
at com.ibm.security.auth.module.Krb5LoginModule.b(Krb5LoginModule.java:227)
at com.ibm.security.auth.module.Krb5LoginModule.login(Krb5LoginModule.java:424)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:495)
at javax.security.auth.login.LoginContext.invoke(LoginContext.java:788)
at javax.security.auth.login.LoginContext.access$000(LoginContext.java:196)
at javax.security.auth.login.LoginContext$5.run(LoginContext.java:721)
at javax.security.auth.login.LoginContext$5.run(LoginContext.java:719)
at java.security.AccessController.doPrivileged(AccessController.java:742)
at javax.security.auth.login.LoginContext.invokeCreatorPriv(LoginContext.java:719)
at javax.security.auth.login.LoginContext.login(LoginContext.java:593)
at org.jboss.remoting3.test.RemoteKerberosChannelTest.login(RemoteKerberosChannelTest.java:187)
at org.jboss.remoting3.test.RemoteKerberosChannelTest.create(RemoteKerberosChannelTest.java:117)
Originally, I caught it with Remoting 3.3.4.Final with EAP productized bits but then also tested clean 3.3 (1) branch and master branch (2) (present in both).
This is a configuration fail so nothing wrong with Remoting yet (minor prio). Maybe it's a jdk issue? I haven't been able to find anything known like that, other jdks are fine.
(1): c33afeb0154427ad0a50d19ec7272b77e39341ff
(2): 3e0cde7c07ae83907194be54ebc6246d9461970a
