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

When users log on to 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.

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

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