How to configure a Teradata JDBC data source to use LDAP Authentication in Information Designer.
Article ID: KB0079103
Updated On:
| Products | Versions |
|---|---|
| Spotfire Analyst | All versions |
Description
By default in the Information Designer, Teradata data source(template) uses database authentication and not the LDAP Authentication.
Issue/Introduction
How to configure a Teradata JDBC data source to use LDAP Authentication in Information Designer.
Environment
All Supported Operating Systems
Resolution
If you want to use Windows/LDAP authentication inside information designer, add the following parameters in the JDBC URL:
LOGMECH
LOGDATA
Example: jdbc:teradata://DatabaseServerName/LOGMECH=LDAP
About LOGMECH: This is the Logon Mechanism. It determines both the sort of authentication used and the type of encryption to support the connection.
TD2 – Teradata Method 2
KRB5 – Kerberos V5
LDAP – Lightweight Directory Access Protocol
Use a user-defined name in cases where the user-defined methods have been created.
In the case where no LOGMECH is specified, the Teradata JDBC Driver uses the local default mechanism. If this default doesn't exist, the default mechanism, as specified by the Teradata Database, is used.
About LOGDATA: It specifies any additional data needed by a logon mechanism, such as a secure token, Distinguished Name, or a domain/realm name. LOGDATA values are specific to each logon mechanism. LOGDATA is not used with the TD2 mechanism.
Note : TIBCO Spotfire will not use the logged in user name but LDAP credentials provided in the information designer instead of database credentials.
Disclaimer: The parameters mentioned in this knowledge article are external (Teradata) parameters. It is not intended to be used "As Is" in a Production environment. Always test in a Development environment.
LOGMECH
LOGDATA
Example: jdbc:teradata://DatabaseServerName/LOGMECH=LDAP
About LOGMECH: This is the Logon Mechanism. It determines both the sort of authentication used and the type of encryption to support the connection.
TD2 – Teradata Method 2
KRB5 – Kerberos V5
LDAP – Lightweight Directory Access Protocol
Use a user-defined name in cases where the user-defined methods have been created.
In the case where no LOGMECH is specified, the Teradata JDBC Driver uses the local default mechanism. If this default doesn't exist, the default mechanism, as specified by the Teradata Database, is used.
About LOGDATA: It specifies any additional data needed by a logon mechanism, such as a secure token, Distinguished Name, or a domain/realm name. LOGDATA values are specific to each logon mechanism. LOGDATA is not used with the TD2 mechanism.
Note : TIBCO Spotfire will not use the logged in user name but LDAP credentials provided in the information designer instead of database credentials.
Disclaimer: The parameters mentioned in this knowledge article are external (Teradata) parameters. It is not intended to be used "As Is" in a Production environment. Always test in a Development environment.
Additional Information
Feedback
Yes
No
Powered by
