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-33822: OpenJDK Compatibility with Centrify KCM

Authentication Service ,  

5 June,20 at 02:54 PM

Question: When enabling the Centrify Kerberos in-memory Cache (KCM), the Java OpenJDK application suddenly cannot use SSO and may generate errors. Why does this happen?

For example, after enabling Centrify KCM by setting the following value to "KCM" in the /etc/centrifydc/centrifydc.conf file:

krb5.cache.type: KCM


OpenJDK will fail to use SSO and messages similar to the following may be seen:


WARN ipc.Client: Exception encountered while connecting to the server : javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt)]


Answer: This is expected. The reason is that Centrify DirectControl uses the MIT based implementation of Kerberos, but Java has its own implementation for Kerberos. Java does not use MIT Kerberos libraries, so there currently is no compatibility with Java and Centrify KCM.



 

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.