Applying Confidentiality QOP Policy to Directory Principals - Advanced SQL Engine - Teradata Database

Security Administration

Product
Advanced SQL Engine
Teradata Database
Release Number
17.05
17.00
Published
September 2020
Language
English (United States)
Last Update
2021-01-23
dita:mapPath
ied1556235912841.ditamap
dita:ditavalPath
lze1555437562152.ditaval
dita:id
B035-1100
lifecycle
previous
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.

When 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
-

When 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
-