ecSecurity and Authentication

To protect data from unauthorized access, Teradata data stores require authentication for access. To access your data, you must configure the connector to pass in your credentials and authenticate the connection. The Simba Teradata ODBC Connector supports a number of methods for authenticating connections:

  • TD2
  • Kerberos (KRB5)
  • LDAP
  • JSON Web Token (JWT)
  • Teradata Negotiating (TDNEGO)
  • Single Sign-On (SSO), including SSO through TDNEGO

Configure authentication for your connection by selecting an authentication mechanism and then specifying the appropriate credentials in the DSN or connection string. In some cases, such as when you use LDAP or KRB5, you do not need to specify any credentials because the connector uses the credentials from the application. For detailed configuration instructions, see Configuring AuthenticationConfiguring Authentication.

When configuring authentication, you have the option of providing Teradata Wallet reference strings instead of specifying your password or additional authentication parameters directly in the connection information. For security reasons, the connector does not allow password values or authentication parameters to be saved in DSNs. You can only save Teradata Wallet reference strings that are mapped to the password or authentication parameters. For more information about the Teradata Wallet utility, see Teradata Wallet.

Related topics