Error #3: Account is wrong: Client not found in Kerberos database (6)

Subject: Error #3: Account is wrong: Client not found in Kerberos database (6)
Author: eLDAP
In response to: Error #2: Clock skew too great (37).
Posted on: 03/12/2013 11:59:00 PM


javax.security.auth.login.LoginException: Client not found in Kerberos database (6)
at com.sun.security.auth.module.Krb5LoginModule.attemptAuthentication(Krb5LoginModule.java:696)
at com.sun.security.auth.module.Krb5LoginModule.login(Krb5LoginModule.java:542)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
at javax.security.auth.login.LoginContext.login(LoginContext.java:579)

Possible causes include:

If you have service account ldap/test_user@MYREALM.COM defined in KDC, but you login with account ldap/test_user.mycompany.com@MCOMPANY.COM

If you have service account ldap/test_user.mycompany.com@MYREALM.COM defined in KDC, but you login with account ldap/test_user@MCOMPANY.COM

If you have service account ldap/test_user:10389@MYREALM.COM defined in KDC, but you login with account ldap/test_user@MCOMPANY.COM

Note:

If you have service account ldap/test_user:10389@MYREALM.COM defined in KDC, and you login with account ldap/test_user:10389 it will be fine as long as the default realm defined in krb5.ini matches your acoount.

If you have service account ldap/test_user:10389@MYREALM.COM defined in KDC, and you login with empty account <blank> it will be fine as it will use the default currently-logined account instead (this is also the way how SSO works.).

>
> On 03/12/2013 11:56:43 PM eLDAP wrote:

javax.security.auth.login.LoginException: Clock skew too great (37) at com.sun.security.auth.module.Krb5LoginModule.attemptAuthentication(Krb5LoginModule.java:696) at com.sun.security.auth.module.Krb5LoginModule.login(Krb5LoginModule.java:542) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769) at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186) at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680) at javax.security.auth.login.LoginContext.login(LoginContext.java:579)

Cause: Kerberos is a time sensitive protocol. The system time between a client and the server should not differ by more than 5 minutes.

References:

Next Post: Error #4: Password is wrong: Pre-authentication information was invalid (24) eLDAP 03/13/2013 12:04:34 AM
Previous Post: Error #2: Clock skew too great (37). eLDAP 03/12/2013 11:56:43 PM
Next Topic: Schema about attribute eLDAP 01/31/2014 08:32:14 PM
Previous Topic: ktab + kinit + klist -- Kerberos key and ticket cache management tools eLDAP 03/12/2013 11:40:35 PM
Index: by Date
Index: by Topic