TDP builds and passes a parameter list to TDPUAX. The parameter list consists of the following:
When TDPUAX is called during an application logon or connect request, it can be used to:
In a validated logon, the password field of the logon string is optional, and is ignored if present. The userid must be a valid userid with the proper rights granted, as described above. An account string, if it is used, must be valid and will be respected.
When TDP has authenticated the Database userid, the Database requires that both the Logical-host on which TDP resides and the Teradata Database userid both have been granted the right to logon “with null password.”This is accomplished for a particular userid by the SQL GRANT LOGON ON <Logical-host id> TO USERID <userid> WITH NULL PASSWORD or for all userids by the SQL GRANT LOGON ON <Logical-host id> AS DEFAULT WITH NULL PASSWORD.
While Database userids must be defined with a password, the password is ignored when TDP has authenticated the Database userid. Since it is ignored, an expired password will not prevent a logon when TDP has authenticated the Database userid, though it will prevent a logon when TDP has not authenticated that userid, since the password is used.
This exit does not currently support a terminate call, therefore any cleanup after the application ends or abends must be managed by the application.
For an example of coding TDPUAX, refer to the sample TDPUAX that is shipped with TDP.