17.20 - Directory Schema Requirements for Using ipNetwork Objects - 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

Most directory types certified for use with TDGSS contain schema that conforms to IETF RFC 2307. This RFC defines a standard data storage entry for naming services, including the ipNetwork entry and its required attributes.

The ADAM and AD LDS directories do not contain schema to support an ipNetwork entry. If you plan to assign policy by IP address and your directory is ADAM or AD LDS, you must install one of the following to enable use of ipNetwork entries:

  • An IETF RFC 2307-compatible schema for the ipNetwork object from an outside source.
  • The ipNetwork schema extension provided by Teradata, ipnetwork.adam.schema, which is based on the ipNetwork object schema found in Active Directory. The Teradata-provided schema appears in the tdgss/etc directory.