Combining IdentityMap and IdentitySearch | Teradata Vantage - 17.20 - Using Multiple IdentityMap and IdentitySearch Elements in Combination - Analytics Database - Teradata Vantage

Teradata Vantage™ - Analytics Database Security Administration - 17.20

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-03-07
dita:mapPath
hjo1628096075471.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
zuy1472246340572
Some sites define users in more than one directory subtree, while allowing users to employ a variety of username formats. To meet those diverse needs, you may need to configure a combination of IdentityMap and IdentitySearch elements, according to these guidelines:
  • There is no limit to the number of IdentityMap and IdentitySearch elements you can add to the LDAP configuration.
  • The elements can appear in the TdgssUserConfigFile.xml in any order.
  • LDAP processes the IdentityMap and IdentitySearch elements in the order they appear in the mechanism configuration.
  • LDAP authenticates the user with the first IdentityMap or IdentitySearch element that contains a Match expression that completely consumes the user name (authcid).
  • If no identity map or identity search completely consumes the user name, LDAP attempts the bind with the simple username as it appears in the logon. If the directory cannot resolve the simple username to the user DN, the logon fails.
  • If an identity search does not return exactly one object, the authentication fails.
  • If a user defined in an identity map does not exist in the directory, the authentication fails.
You can also use ${0} which represents the entire user name (authcid).