Directory Schema Requirements for Using ipNetwork Objects - Advanced SQL Engine - Teradata Database

Security Administration

Product
Advanced SQL Engine
Teradata Database
Release Number
17.10
Published
July 2021
Language
English (United States)
Last Update
2022-02-15
dita:mapPath
ppz1593203596223.ditamap
dita:ditavalPath
wrg1590696035526.ditaval
dita:id
B035-1100
lifecycle
previous
Product Category
Teradata Vantageā„¢

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.