TDV supports Kerberos SSO authentication so that Studio designers, developers, and end-users can log on to their operating system and use that authenticated login identity as established by the Kerberos authentication system. User identity and group affiliations that are established and maintained by an associated LDAP server can authorize use of applications, resources, and data provided that the authentication and authorization match.

Use of a Kerberos authentication system for Single Sign-On requires configuration of all components that makes use of the Kerberos authentication provider. If you use Active Cluster, each TDV node of the cluster must have an SPN identifier, and a KeyTab file generated from that SPN.