17.20 - Applying Confidentiality QOP Policy to Teradata Vantage Users - Analytics Database - Teradata Vantage

Teradata Vantage™ - Analytics Database Security Administration - 17.20

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
2023-03-07
dita:mapPath
hjo1628096075471.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
zuy1472246340572

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.

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
-

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
-