Before a supported directory can authenticate and authorize user access to Teradata Vantage, you must create Teradata schema objects in the DIT, and arrange them in the required hierarchical relationship to other directory objects.
You can place the tdatRootNode object, labeled cn=tdat, anywhere in the hierarchy, but you must locate all child objects exactly as shown in diagram.
where:
| Row | DN | Object Class | Description | Defined by Object Class |
|---|---|---|---|---|
| Top | dc=domain, dc=com | dcObject | Top-level directory object | Standard directory schema |
| Middle | ou=people | organizationalUnit | Directory object that contains individual person objects | |
| ou=groups | organizationalUnit | Directory object that contains user and database objects | ||
| cn=tdat | tdatRootNode | Teradata Root Node object. This is the suggested location for the Root Node object. However, you can locate it elsewhere in the directory.
|
Teradata directory schema extensions | |
| Bottom | cn=systemone | tdatSystem | Directory object that defines Teradata Vantage system 1. | Teradata directory schema extension |
| cn=systemtwo | tdatSystem | Teradata object that defines Teradata Vantage system 2. | ||
| cn=administrators | groupOfNames | Directory object that defines the administrator group. | Standard directory schema | |
| cn=dbas | groupOfNames | Directory object that defines the group dbas. Enter the DN of each directory user in the groupOfNames member attribute, to give them group membership. | ||
| uid=bwq | person | Directory objects that define individual directory users. | ||
| uid=jcm | person |