Applying Confidentiality QOP Policy to Directory Principals - Analytics Database - Teradata Vantage

Security Administration

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
2024-04-05
dita:mapPath
hjo1628096075471.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
zuy1472246340572
lifecycle
latest
Product Category
Teradata Vantageā„¢

You can specify a directory principal DN for an LDAP user not mapped to a Teradata user object.

You can specify policy membership for directory principals only if AuthorizationSupported=no for both KRB5 and LDAP.

Using Teradata schema extensions:

dn: cn=default,cn=conf-qops,cn=policy1,cn=tdatrootP,dc=domain1,dc=com
changetype: modify
add: member
member: uid=jdoe,ou=principals,dc=domain1,dc=com
-

Using native directory schema:

dn: cn=default,ou=conf-qops,ou=policy1,ou=tdatrootP,dc=domain1,dc=com
changetype: modify
add: member
member: uid=jdoe,ou=principals,dc=domain1,dc=com
-