16.10 - Applying Confidentiality QOP Policy to Directory Principals - Teradata Database

Teradata Database Security Administration

prodname
Teradata Database
vrm_release
16.10
created_date
June 2017
category
Administration
Security
featnum
B035-1100-161K

You can specify a directory principal DN for an LDAP user not mapped to a Teradata user object.

You can specify policy membership for directory principals only if AuthorizationSupported=no for both KRB5 and LDAP.

When using Teradata schema extensions:

dn: cn=default,cn=conf-qops,cn=policy1,cn=tdatrootP,dc=domain1,dc=com
changetype: modify
add: member
member: uid=jdoe,ou=principals,dc=domain1,dc=com
-

When using native directory schema:

dn: cn=default,ou=conf-qops,ou=policy1,ou=tdatrootP,dc=domain1,dc=com
changetype: modify
add: member
member: uid=jdoe,ou=principals,dc=domain1,dc=com
-