After you install Teradata schema extensions in a supported directory, you can create several objects that can link directory users to Teradata Vantage users, roles, and profiles.
| Object Type | Description | Class |
|---|---|---|
| tdatRootNode | Parent object for all tdatSystem objects. The directory administrator determines the value for cn attribute. | Required |
| tdatSystem | Identifies a Teradata Vantage system or Unity server, where cn=system_name. The tdatSystem object is the parent of the Teradata schema objects that define the LDAP authorization structure and mappings to directory users. The tdatSystem object maybe named for a single system, but multiple systems that use the same authorization structure can specify the same tdatSystem object.
|
Required |
| tdatContainer | tdatContainer objects contain individual Teradata user, role, profile, and IP filter objects. Valid containers are:
|
Required (except as noted) |
| tdatUser | Describes a Vantage user, where cn=user_name. | |
| tdatRole | Describes aVantage role, where cn=role_name. | Optional |
| tdatProfile | Describes a Vantage profile, where cn=profile_name. | |
| tdatIPFilter | Describes a Vantage IP filter, where cn=filter_name. |