go to  ForumEasy.com   
LdapPro
Home » Archive » Message


[Email To Friend][View in Live Context][prev topic « prev post | next post » next topic]
  Error #4: Password is wrong: Pre-authentication information was invalid (24)
 
Subject: Error #4: Password is wrong: Pre-authentication information was invalid (24)
Author: eLDAP
In response to: Error #3: Account is wrong: Client not found in Kerberos database (6)
Posted on: 03/13/2013 12:04:34 AM


javax.security.auth.login.LoginException: Pre-authentication information was invalid (24)
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: You provided a wrong password to login.

 

> On 03/12/2013 11:59:00 PM eLDAP wrote:


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.).




    References:

  •  


     
    Powered by ForumEasy © 2002-2022, All Rights Reserved. | Privacy Policy | Terms of Use
     
    Get your own forum today. It's easy and free.