17.20 - Applying an Option Policy to a Teradata Vantage Profile - 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

When you configure option membership by Vantage profile, the corresponding tdatProfile object must already exist in the directory.

Users accessing the database through a middle-tier application are subject to the policies assigned to the application user, instead of policies assigned to them as individuals.

Example using Teradata schema extensions:

dn: cn=has-policy,cn=options,cn=policy1,
 cn=tdatrootP,dc=domain1,dc=com
changetype: modify
add: member
member: cn=profile1,cn=profiles,cn=system1,cn=tdatrootA,dc=domain1,dc=com
-

Example using native directory schema:

dn: cn=no-direct-connect,ou=options,ou=policy1,
 ou=tdatrootP,dc=domain1,dc=com
changetype: modify
add: member
member: cn=profile1,ou=profiles,ou=system1,ou=tdatrootA,dc=domain1,dc=com
-