Centrify

Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-5163: "GSSHeader did not find the right tag" error when connecting via Kerberos SSO using Cloudera

Authentication Service ,  

12 April,16 at 11:11 AM

Applies to:
All versions of Centrify DirectControl on all platforms

Problem:
The following error appears in the log when attempting to load a webpage after Cloudera is configured to use Kerberos SSO:
 
GSSException: Defective token detected (Mechanism level: GSSHeader did not find the right tag)
at ....jgss.GSSHeader.<init>(Unknown Source)

GSSHeader Error in web browser
 
Cause:
During authentication, newer versions of Windows and Internet Explorer attempt to negotiate to use NEGOEX mechanism for authentication.

Unfortunately, there is known issue with Java Runtime which does not support that correctly.  As a result the negotiation process causes Java to fail with the above error.

Cloudera handles that error and fails appropriately.  Following that, Windows/Internet Explorer re-tries the negotiate differently which Java is then able to process.

Solution:
As of this writing, the error can be ignored.
 

Related Articles

 articleKB-6044: How to configure users for automatic Kerberos Credentials for infinite renewal even after users have logged out? articleKB-6050: How to configure a group for automatic Kerberos Credentials for infinite renewal? articleCentrify's Privileged Identity Management Solution for Big Data articleCentrify 17.7 Release Notes article[How-To] Use a zone enabled supergroup to manage HDFS for Cloudera articleKB-6041: How to show current license type in use by adclient articleKB-6040: How to change the license type in use after adclient successful joined to the AD? articleKB-20210: Common Questions Regarding Centrify DirectControl and CoreOS article[How to] Force Kerberos SSH Authentication, and Disable SSH Public Key Authentication