Required Directory Teradata Objects | Teradata Vantage - 17.10 - About Required Teradata Objects - Advanced SQL Engine - Teradata Database

Teradata Vantage™ - Advanced SQL Engine Security Administration

Product
Advanced SQL Engine
Teradata Database
Release Number
17.10
Release Date
July 2021
Content Type
Administration
Security
Publication ID
B035-1100-171K
Language
English (United States)

The following table shows the Teradata directory objects required to manage database users, when using only native schema.

Teradata Object Directory Object Type and Description Class
RootNode An organizationalUnit object that describes the parent object for all Teradata System objects.

The ou attribute and its value must be used as the relative distinguished name (RDN).

Required
System An organizationalUnit object that describes the parent object for a set of Teradata objects.

ou=system name

The system name can be a Teradata Vantage system or a Unity server.

The value of the LdapSystemFQDN mechanism property for a system must specify the FQDN of this object.
Container A groupOfNames object. Teradata user, role, or profile objects each require a separate container.
  • ou=users
  • ou=profiles
  • ou=roles
User A groupOfNames object that describes a Vantage user.

cn=a database user name

Optional

Directory users whose database privileges are authorized by the directory have only the privileges of the database objects to which they are mapped.

Role A groupOfNames object that describes a Vantage external role.

cn=a database external role name

Profile A groupOfNames object that describes a Vantagee profile.

cn=a database profile name