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

The following examples show how to apply an option policy (has-policy or no-direct-connect) to an existing tdatUser object in the directory.

Specify the DN of a tdatUser object for:

  • A user that logs on with the TD2 mechanism
  • An LDAP user that is mapped to the tdatUser object.

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=xyz,cn=users,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=xyz,ou=users,ou=system1,ou=tdatrootA,dc=domain1,dc=com