The SPNEGO mechanism supports Kerberos authentication for users that log on to Teradata Vantage from .NET clients, and functions similarly to the KRB5 mechanism.
SPNEGO appears in the TdgssLibraryConfigFile.xml for all installations of Teradata Vantage and Unity; however, to make a configuration change to SPNEGO, you must manually copy the mechanism from the TdgssLibraryConfigFile.xml and add it to the TdgssUserConfigFile.xml (Teradata Vantage) and to the TdgssUnityConfig.xml (Unity). Then follow the instructions in Teradata® Unity™ Installation, Configuration, and Upgrade Guide for Customers, B035-2523 to update the Unity configuration file. Note, this copy only needs to be done for configuration changes; otherwise, the default configuration can remain in TdgssLibraryConfigFile.xml.
Example: SPNEGO Configuration
<!-- SPNEGO for UNIX Teradata servers --> <Mechanism Name="SPNEGO" ObjectId="1.3.6.1.5.5.2" LibraryName="gssp2spnego" Prefix="spnego" InterfaceType="negotiate"> <MechanismProperties AuthenticationSupported="yes" AuthorizationSupported="no" SingleSignOnSupported="yes" DefaultMechanism="no" MechanismEnabled="yes" MechanismRank="65" DelegateCredentials="no" MutualAuthentication="yes" ReplayDetection="yes" OutOfSequenceDetection="yes" ConfidentialityDesired="yes" IntegrityDesired="yes" AnonymousAuthentication="no" DesiredContextTime="" DesiredCredentialTime="" CredentialUsage="0" LdapServerName="" LdapServerPort="389" LdapServerRealm="" LdapSystemFQDN="" LdapBaseFQDN="" LdapGroupBaseFQDN="" LdapUserBaseFQDN="" LdapClientReferrals="off" LdapClientDeref="never" LdapClientDebug="0" LdapClientRebindAuth="yes" LdapClientRandomDevice="/dev/urandom" LdapClientMechanism="SASL/DIGEST-MD5" LdapClientUseTls="no" LdapServiceFQDN="" LdapServicePasswordProtected="no" LdapServicePassword="" LdapClientSaslSecProps="" UseLdapConfig="no" /> <MechQop Value="0"> GLOBAL_QOP_1 </MechQop> <NegotiatedMechanism ObjectId="1.2.840.113554.1.2.2"/> </Mechanism>