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-8814: Non-forwardable Kerberos Ticket is Generated With Trust Delegation Enabled

Authentication Service ,  

13 June,17 at 08:19 PM

Question:
 
A non-forwardable kerberos TGT (Ticket Granting Ticket) is generated on login even when the host machine is trusted for kerberos delegation.

On a windows machine the TGT looks like this:
  
User-added image
  
On a Linux machine, after running the command 
 
# kinit -f
 
the TGT looks like this:
  
User-added image
 
Answer:
  
The user account has the account flag enabled "Account is sensitive and cannot be delegated"
 
User-added image

This prevents the TGT from being forwardable.  The TGT will still be valid for one SSO (Single Sign On) hop, but it will prevent nested SSO hops.

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

Related Articles

 article[TIPS] A Centrify Server Suite Cheat Sheet 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-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? articleKB-6056: How to report the group policy settings that are in effect for the local computer? articleKerberos SSO - Handling Disjointed Active Directory and UNIX DNS namespaces with Centrify articleKB-6038: How to specify the license type to use when joining the server to AD using adjoin? articleKB-1835: How do I enable forwardable kerberos tickets in plink articleKB-4303: How to troubleshoot SSH Single-Sign-On (SSO) and nested SSO?