|mech_name||Specifies the authentication mechanism.
For Teradata Database authorization:
For directory authorization
|user_credentials||Specifies the username and password for the logon, and must conform to the following rules:
Valid formats for user credentials:
In the .logdata statement for KRB5 and SPNEGO:
Sign-On As using Kerberos authentication (SPNEGO mechanism) is usable only from Windows clients.
In the .logdata statement for LDAP:
In a .logon statement for KRB 5 and SPNEGO:
In a .logon statement for LDAP:
Ensuring Correct Interpretation of UPNs
For the logon diruser,dirpassword, the user specification can be “a@b” or a/b” or “a\b”. Set LdapCredentialIsUPN to interpret the user specification. See LdapCredentialIsUPN.
|authorization_qualifier||Required if the user is authorized by the directory (AuthorizationSupported=yes) and one or more of the following is true:
Individual specifications within the .logdata statement must be separated by white spaces.
Directory user mapped to multiple database users:
If the directory user is mapped to more than one database user, specify the user with the database privileges needed for the session in the form:
The database username can be either an individual database user or EXTUSER.
Directory user mapped to multiple profiles:
Directory offers multiple realms (LDAP authentication only):
Specify the realm as it appears in the directory, normally the fully qualified DNS name of the directory, for example:
The system processes realm information as follows:
|tdpid/||Required. The tdpid identifies the Teradata Database system, Unity server, or host group to which the logon, if successful, connects.|
|, ,||If the logon specifies an account, and the directory username and directory password appear in the .logdata statement, the , , must precede the account specification, with these exceptions:
|"account"||Optional. The account string specification must be enclosed in double quotation marks.
For information on accounts, see Database Administration.