16.10 - Applying Confidentiality QOP Policy to Teradata Users - 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)

The following examples show how to assign membership in a QOP to an existing Teradata user object in the directory. A directory principal mapped to the Teradata user object inherits the QOP policy.

When using Teradata schema extensions:

dn: cn=high,cn=conf-qops,cn=policy1,cn=tdatrootP,dc=domain1,dc=com
changetype: modify
add: member
member: cn=xyz,cn=users,cn=system1,cn=tdatrootA,dc=domain1,dc=com
-

When using native directory schema:

dn: cn=high,ou=conf-qops,ou=policy1,ou=tdatrootP,dc=domain1,dc=com
changetype: modify
add: member
member: cn=xyz,ou=users,ou=system1,ou=tdatrootA,dc=domain1,dc=com
-