External Authentication
In some cases the user name in a job script must be authenticated by an agent external to the Teradata Database, such as Kerberos or Active Directory. External authentication is only available for jobs launched from network-attached clients. It requires special setup.
Note: Do not use external authentication to log on with a Teradata PT job script until you understand the associated setup and logon requirements, as shown in Security Administration.
Specify security attributes for external authentication as follows:
Security Attribute |
Description |
Strategy |
UserName |
The name used to log on to the network prior to launching the job script. |
Optional: Note: Do not declare the UserName or UserPassword attributes if you plan to enter user name and password data in LogonMechData. |
UserPassword |
The network password (not the Teradata Database password) associated with the UserName) |
|
TdpId |
Identifies the connection to the Teradata Database |
Optional If you don't specify a TdpId, the system will use the default TdpId, as defined in the Teradata Client clispb.dat. Specify either: TDP6 cs4400S3
|
LogonMech |
The security mechanism that authenticate the user. Similar to the |
Required unless the external authentication mechanism is the default. Choose among the following, depending on authentication method. |
LogonMechData |
Data required by external authentication mechanisms to complete the logon. Similar to the |
Optional LogonMechData contains the user name, password, and in some cases, other information. Entering user credential information in LogonMechData is required for all logons that specify profile=profilename or user=username, to differentiate among multiple applicable profiles or users. Note: Do not declare the LogonMechData attribute if you plan to enter user name and password data in UserName and UserPassword. |