Network Security Policy | Teradata Vantage - 17.20 - Using LDAP Directory Objects in Policies - 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 assign a security policy to Teradata user and profile objects in the directory.

Some Teradata user and profile objects may already exist in the directory as a result of configuring LDAP authorization, as shown in the following diagram.



Teradata Vantage users and profiles must exist in the directory before you can assign security policies to them.

In a multiple system environment, a single tdatSystem object, related authorization structure, and set of security policies applies to all directory users.

In cases where directory users can log on directly to the database, Teradata recommends a single authorization structure for all logons.

For information on creating profile and user objects, see Provisioning Directory Users with Teradata Schema Extensions or Using Native Directory Schema to Provision Directory Users.