GssapiTestSuite and Gs2Test fail with com.ibm.security.krb5.KrbException, status code: 9 for IBM JDK ---------------------------------------------------------------------------------------------------- Key: ELY-483 URL: https://issues.jboss.org/browse/ELY-483 Project: WildFly Elytron Issue Type: Bug Affects Versions: 1.1.0.Beta5 Reporter: Ondrej Lukas Labels: ibm-java Test cases initialization from GssapiTestSuite and Gs2Test fail with following exception for IBM JDK: {code} 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:15) at com.ibm.security.auth.module.Krb5LoginModule.j(Krb5LoginModule.java:727) at com.ibm.security.auth.module.Krb5LoginModule.b(Krb5LoginModule.java:307) at com.ibm.security.auth.module.Krb5LoginModule.login(Krb5LoginModule.java:59) 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:507) 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:686) at javax.security.auth.login.LoginContext.invokeCreatorPriv(LoginContext.java:719) at javax.security.auth.login.LoginContext.login(LoginContext.java:593) at org.wildfly.security.sasl.gssapi.JaasUtil.login(JaasUtil.java:71) at org.wildfly.security.sasl.gssapi.JaasUtil.loginClient(JaasUtil.java:53) at org.wildfly.security.sasl.gssapi.JdkClientJdkServer.initialise(JdkClientJdkServer.java:47) ... {code} It is test case issue but it can hide any another functional issue because affected tests are not running with IBM JDK.