Using Native Directory Schema to Create Mechanism Objects - 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
2024-04-05
dita:mapPath
hjo1628096075471.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
zuy1472246340572
lifecycle
latest
Product Category
Teradata Vantage™
dn: cn=td2,ou=mechanisms,ou=policy1,ou=tdatrootP,dc=domain,dc=com
objectClass: groupOfNames
cn: td2
member: ou=mechanisms,ou=policy1,ou=tdatrootP,dc=domain,dc=com

dn: cn=krb5,ou=mechanisms,ou=systems,ou=tdatrootP,dc=domain,dc=com
objectClass: groupOfNames
cn: krb5
member: ou=mechanisms,ou=policy1,ou=tdatrootP,dc=domain,dc=com

dn: cn=ldap,ou=mechanisms,ou=policy1,ou=tdatrootP,dc=domain,dc=com
objectClass: groupOfNames
cn: ldap
member: ou=mechanisms,ou=policy1,ou=tdatrootP,dc=domain1,dc=com

dn: cn=proxy,ou=mechanisms,ou=policy1,ou=tdatrootP,dc=domain1,dc=com
objectClass: groupOfNames
cn: proxy
member: ou=mechanisms,ou=policy1,ou=tdatrootP,dc=domain1,dc=com
The member attribute is required for any object with a GroupOfNames class. The preceding examples use member: ou=mechanisms to allow the mechanism object to exist in the directory prior to being populated with individual member users.