17.10 - Applying Confidentiality QOP Policy to Teradata Vantage Users - Advanced SQL Engine - Teradata Database

Teradata Vantage™ - Advanced SQL Engine Security Administration

Product
Advanced SQL Engine
Teradata Database
Release Number
17.10
Published
July 2021
Language
English (United States)
Last Update
2022-02-15
dita:mapPath
ppz1593203596223.ditamap
dita:ditavalPath
wrg1590696035526.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.

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
-