Applying an Option Policy to a Network Group - Advanced SQL Engine - Teradata Database

Security Administration

Product
Advanced SQL Engine
Teradata Database
Release Number
17.05
17.00
Published
September 2020
Language
English (United States)
Last Update
2021-01-23
dita:mapPath
ied1556235912841.ditamap
dita:ditavalPath
lze1555437562152.ditaval
dita:id
B035-1100
lifecycle
previous
Product Category
Teradata Vantageā„¢

When you configure option membership by network group, the type of network group determines the effects of membership.

  • Internal network group IP addresses are subject to an Option in which the group is a member
  • External network group IP addresses are exempt from an Option in which the group is a member.

For example, when using Teradata schema extensions:

dn: cn=no-direct-connect,cn=options,cn=policy1,
 cn=tdatrootP,dc=domain1,dc=com
changetype: modify
add: member
member: cn=behind-the-firewall,cn=internal-network-groups,cn=policy1,
 cn=tdatrootP,dc=domain1,dc=com

For example, when using native schema extensions:

dn: cn=has-policy,ou=options,ou=policy1,
 ou=tdatrootP,dc=domain1,dc=com
changetype: modify
add: member
member: cn=behind-the-firewall,ou=internal-network-groups,ou=policy1,
 ou=tdatrootP,dc=domain1,dc=com