Using Native Directory Schema to Create Mechanism Objects - Advanced SQL Engine - Teradata Database

Security Administration
Product
Advanced SQL Engine
Teradata Database
Release Number
17.05
17.00
Published
September 2020
Language
English (United States)
Last Update
2021-01-23
dita:mapPath
ied1556235912841.ditamap
dita:ditavalPath
lze1555437562152.ditaval
dita:id
B035-1100
lifecycle
previous
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.