Troubleshooting Tips
Buffer Size
You may encounter a buffer size related error when connecting to TDV with SSO, check the Exception stack trace. If the source of the exception is “java.io.IOException: FULL head”, you need to configure a larger header buffer size. The default size is 4096.
Follow these steps to modify the setting:
1. Log into Studio as the admin user.
2. Select Administration > Configuration from the Studio menu bar.
3. Locate the two Head Buffer Size configuration parameters:
— HTTP > Header Buffer Size
— HTTPS > Header Buffer Size
4. Increment the value by 4096 until you no longer get the error.
5. Restart the Server.
Authentication Errors
Obtaining a Kerberos Ticket
If the Kerberos ticket is invalid or expired you may encounter an error “Unable to obtain Principal Name for authentication”.
Follow these steps to obtain and cache the Kerberos Ticket Granting Tickets (TGT):
1. Open the Command-line tool as an administrator.
2. Change directory to JDK bin path.
3. Type the following command:
kinit <username@Domain> and give your password.
4. Execute the "klist” command to get the ticket.
Once you have a valid Kerberos ticket, you can login to TDV Studio using the SSO option.
Using File Cache in Linux
In the Linux environment if the default cache setting is KEYRING, you may encounter SSO Authentication errors. Changing it to a File Cache in the configuration file (krb5.conf) will solve the issue. For example,
default_ccache_name = FILE:/tmp/krb5cc_%{uid}
Data Source Authentication Error
Data sources support only JGSS based Negotiate and Kerberos authentication. If you introspect a data source set up with SSPI Kerberos authentication, you get a 401 Authentication Error message.
SSO Authentication Failure
There can be many number of reasons when you get an SSO Authentication error. Running the Kerberos Test utility will help you identify the exact problem. Refer
Kerberos Test Utility for instructions on how to run the utility.