LDAP Mechanism Properties that Support Service Binds - Analytics Database - Teradata Vantage

Security Administration

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Analytics Database
Teradata Vantage
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-11-02
dita:mapPath
hjo1628096075471.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
zuy1472246340572
lifecycle
latest
Product Category
Teradata Vantage™

Evaluate all the LDAP mechanism properties that support service binds. You may need to configure some or all of them when implementing service binds on your system.

Configure the TdgssUserConfigFile.xml on each Teradata Vantage system served by the directory.
Property Setting Property Value Setting
LdapServiceBindRequired Yes/No Sets the requirement for a service bind.
  • A yes value means that TDGSS always performs a service bind.
  • A no value (the default) means that TDGSS performs a service bind only if IdentitySearch elements are present in the configuration.
LdapServiceFQDN Distinguished name Identifies the bindable object in the directory that represents the service identity, that is, a Teradata Vantage system.
LdapServicePassword String Configures a password as the value of this property. This option is needed if your site security policy requires a password for the service FQDN.
LdapServicePasswordFile String (fully qualified file name) Specifies the file that contains a list of encrypted, base64 encoded service passwords, one per line. Allows for changing the LDAP service password without requiring a database restart.
LdapServicePasswordProtected Yes/No Enables encryption for the LDAP service password, if used.
  • Yes (the default) means that TDGSS stores the LdapServicePassword is stored in encrypted form.
  • No means that TDGSS stores the LdapServicePassword in plain text.