17.20 - Rules for Specifying Users as Policy Members - 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

You can specify the DN of a tdatUser object, or in some cases the DN of a directory principal object, as a member of a policy to apply the policy to the user.

The DN specification requirements depend on how the user is authenticated and authorized, regardless of policy type.

Authentication Mechanism Member Definition
TD2 The DN must be an existing Teradata user object in the directory with a cn that matches a Teradata Vantage user name.
KRB5 (AuthorizationSupported=no) The DN must be an existing Teradata user object in the directory with a cn that matches Kerberos domain user name.
LDAP (AuthorizationSupported=no) The DN must be an existing Teradata user object in the directory with a cn matches the LDAP log on name for the user.
KRB5 or LDAP with (AuthorizationSupported=yes) Must be either:
  • The DN of a Teradata user object
  • The DN of a directory principal

The choice of user object is subject to the following rules:

If the directory principal is mapped to a Teradata user object, use the DN of the Teradata user object for the member attribute.

If the directory principal is not mapped to a Teradata user object, use the DN of the directory principal for the member attribute.

JWT JWT allows a user that has been authenticated to the Identity Provider to do a single sign-on to establish a session with Vantage.