Feedback
Did this article resolve your question/issue?

   

Article

Is NTLM authentication supported with Connect for ODBC Teradata driver ?

Information

 
TitleIs NTLM authentication supported with Connect for ODBC Teradata driver ?
URL NameIs-NTLM-authentication-supported-with-Connect-for-ODBC-Teradata-driver
Article Number000185240
EnvironmentProduct: Connect for ODBC Teradata Wire Protocol driver
Version: 7.1
OS: All supported platforms
Database: Teradata
Application: All supported applications
Question/Problem Description

What connection option be used with the Conenct for ODBC Teradata driver to use NTLM authentication ?

Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution

Connect for ODBC Teradata driver supports NTLM authentication. The connection option to be used is called Security Mechanism

Attribute
SecurityMechanism (SECM)

Purpose
The authentication method to be used by the driver for connections to the database.

Valid Values
TD1 | TD2 | ldap | KRB5 | KRB5C | NTLM | NTLMC

Behavior for values NTLM/NTLMC 
If set to NTLM, the driver uses NTLM on Windows clients working with Windows servers if the server is V2R6.0.
If set to NTLMC, the driver uses NTLM Compatibility on Windows clients working with Windows servers if the server is pre-V2R6.0.

Note: Kerberos and NTLM are enabled through the Teradata client. See your Teradata documentation for requirements.

The following options may appear if NTLM or NTLMC is selected:
Authentication UserID: The NTLM user ID.
Realm: The NTLM domain. (The equivalent connection string attribute is AuthenticationDomain.)


 

Workaround
Notes
Last Modified Date2/8/2016 7:54 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.