Example: Bad Canonicalization with Identity Mapping - 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
ft:locale
en-US
ft:lastEdition
2024-04-05
dita:mapPath
hjo1628096075471.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
zuy1472246340572
lifecycle
latest
Product Category
Teradata Vantage™

This example illustrates an identity mapping object that transforms a user name of the form user@realm to an appropriate FQDN. The content of the dsMatching-pattern specifies that the user name obtained from the -u option be transformed to an FQDN. The user name is then matched against the expression contained in the dsMatching-regexp attribute. Substitutions are made in the substitution pattern contained in the dsMapped attribute. Then if you run the user name diperm01@testing through this identity mapping rule, the FQDN is uid=diperm01, ou=people, ou=testing, dc=elkwood, dc=example, dc=com.

Before you design or change identity mappings, you should consult the directory and security administrators, since these objects represent closely guarded configuration information that could adversely affect other directory users and potentially compromise directory security.

For further information on identity mappings, consult the Directory Server Administration Guide for the Oracle Directory Server Enterprise Edition. This guide can be found on the following website: http://download.oracle.com.

dn: cn=test mapping,cn=identity mapping,cn=config
objectClass: top
objectClass: nsContainer
objectClass: dsIdentityMapping
objectClass: dsPatternMatching
cn: test mapping
dsMatching-pattern: ${Principal}
dsMappedDN: uid=$1,ou=people,ou=$2,dc=elkwood,dc=example,dc=com
dsMatching-regexp: ([ˆ:]*)@(.*)
The Teradata LDAP authentication does not support DIGEST-MD5. DIGEST-MD5 must not be used. Use SIMPLE binding instead.