17.10 - Applying Confidentiality QOP Policy to Teradata Vantage Profiles - 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 profile object in the directory.

When users log on to the Vantage through an application that uses pooled sessions, the users are subject to the profile for the application user, not profiles in which the users have membership or to which they are mapped.

When using Teradata schema extensions:

dn: cn=low,cn=conf-qops,cn=policy1,cn=tdatrootP,dc=domain1,dc=com
changetype: modify
add: member
member: cn=profile1,cn=profiles,cn=system1,cn=tdatA,dc=domain1,dc=com

When using native directory schema:

dn: cn=low,cn=conf-qops,cn=policy1,cn=tdatrootP,dc=domain1,dc=com
changetype: modify
add: member
member: cn=profile1,ou=profiles,ou=system1,ou=tdatrootA,dc=domain1,dc=com