The SPNEGO mechanism supports Kerberos authentication for users that log on to Teradata Vantage from .NET clients, and functions similarly to the KRB5 mechanism.
The SPNEGO mechanism is derived from the KRB5 mechanism, and is therefore subject to the multiple LAN adapter restriction. For further information, see Kerberos Multiple LAN Adapter Restriction.
SPNEGO appears in the TdgssLibraryConfigFile.xml for all installations of Teradata Vantage; however, to change to SPNEGO, you must manually copy the mechanism from the TdgssLibraryConfigFile.xml and add it to the TdgssUserConfigFile.xml (Teradata Vantage). Note, this copy only needs to be done for configuration changes; otherwise, the default configuration can remain in TdgssLibraryConfigFile.xml.
Example: SPNEGO Configuration
If you decide to use SPNEGO with directory authorization, you must add and configure some optional properties not shown in this example. See Option 3: Non-LDAP External Authentication with Directory Authorization.
<!-- 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="" LdapSystemFQDN="" LdapGroupBaseFQDN="" LdapUserBaseFQDN="" LdapClientReferrals="off" LdapClientDeref="never" LdapClientDebug="0" LdapClientRebindAuth="yes" LdapClientRandomDevice="/dev/urandom" LdapClientUseTls="no" LdapServiceFQDN="" LdapServicePasswordProtected="no" LdapServicePassword="" UseLdapConfig="no" /> <MechQop Value="0"> GLOBAL_QOP_1 </MechQop> <NegotiatedMechanism ObjectId="1.2.840.113554.1.2.2"/> </Mechanism>