16.10 - Using Native Directory Schema to Create Mechanism Objects - Teradata Database

Teradata Database Security Administration

Product
Teradata Database
Release Number
16.10
Release Date
June 2017
Content Type
Administration
Security
Publication ID
B035-1100-161K
Language
English (United States)
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.