Troubleshooting Kerberos authentication
This section describes errors that can occur when users try to connect to a IXIA TEXTML Server instance that uses Kerberos authentication.
javax.security.auth.login.LoginException: Integrity check on decrypted field failed (31)
Could not log in.
Make sure your login details are correct and that the server is running properly. [javax.security.auth.login.LoginException:Integrity check on decrypted field failed (31).
The username probably includes a mix of uppercase and lowercase letters.
In that case, the network administrator must change the casing of the username so that it is all lowercase. In particular, the network administrator must change the user principal name (UPN) and Security Account Manager (SAM) account in the Active Directory. Users must then change their passwords before trying to connect to the TEXTML Server instance.
javax.security.auth.login.LoginException: Could not load configuration file <filepath>\krb5.ini
javax.security.auth.login.LoginException: Could not load configuration file <filepath>\krb5.ini
(The system cannot find the file specified.)
The user is trying to access a TEXTML Server instance that requires Kerberos authentication. Make sure that the client used to access the TEXTML Server (Administration Console, IXIA CCMS Desktop, etc.) is configured for Kerberos.
javax.security.auth.login.LoginException: Pre-authentication information was invalid (24)
Could not log in.
Make sure your login details are correct and that the server is running properly. [javax.security.auth.login.LoginException: Pre-authentication information was invalid (24)]
The user entered an incorrect password.
javax.security.auth.login.LoginException: Client not found in Kerberos database (6)
Could not log in.
Make sure your login details are correct and that the server is running properly. [javax.security.auth.login.LoginException: Client not found in Kerberos database (6)]
The user entered an incorrect username.
javax.security.auth.login.LoginException: null (68)
Could not log in.
Make sure your login details are correct and that the server is running properly. [javax.security.auth.login.LoginException: null (68)]
- The user did not specify the correct domain when logging in.
- The domain is not specified correctly in the krb5.ini file.
- The krb5.ini file is incorrect.