ODBC Driver for Teradata allows specification of the authentication mechanism in the connection string and in the ODBC data source configuration.
The authentication mechanism for a connection is determined as follows:
- If an authentication mechanism is specified in the connection string passed to SQLDriverConnect() or SQLBrowseConnect(), then that authentication mechanism is selected. The SQLBrowseConnect() can return a set of authentication mechanisms supported by both the client and the database to allow the application to make a choice.
- If no mechanism is specified in the connection string or if connecting using SQLConnect(), then the driver looks in the ODBC data source configuration. If an authentication mechanism is specified in the DSN settings—in the [Named Data Source] section or the [Default Data Source] section—then that mechanism is selected. The specification in the [Named Data Source] section takes precedence over any specification in the [Default Data Source] section.
- If no mechanism is specified in the connection string or DSN settings, then the selected authentication mechanism is the authentication mechanism configured for TeraGSS on the client, provided that it is supported by the gateway.
- Otherwise, the selected mechanism is the default mechanism configured for TDGSS on the gateway, provided that it is supported by the client.
- Otherwise, the selected mechanism is Teradata 2 if the gateway supports it, or else it is Teradata 1 if the gateway supports it, or else it is the conventional Teradata mechanism.
- If the selected authentication mechanism is not supported by the client and the gateway, then the connection function call (SQLConnect(), SQLDriverConnect(), or SQLBrowseConnect()) fails and returns SQL_ERROR.