GDO-Based IP Access Restriction - Analytics Database - Teradata Vantage

Security Administration

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Analytics Database
Teradata Vantage
Release Number
17.20
Published
June 2022
ft:locale
en-US
ft:lastEdition
2024-04-05
dita:mapPath
hjo1628096075471.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
zuy1472246340572
lifecycle
latest
Product Category
Teradata Vantageā„¢
You can define IP restrictions in:
  • Teradata Vantage, by creating an XML IP document
  • A supported directory, by configuring Teradata schema objects in the directory
    You must use Teradata schema extensions to configure IP filter directory objects. Directories configured without Teradata extensions, as shown in Using Native Directory Schema to Provision Directory Users, cannot use directory-based IP restrictions.

After defining the IP restrictions, you must transfer them to the IP restriction GDO.

The system applies IP restrictions to users based on:
  • Filters that define allowed or denied IP addresses or address ranges.
  • The users assigned to each filter.

The Teradata Vantage gateway screens each database logon and allows or denies the logon according to the IP restrictions in the GDO. If no IP restrictions exist, the database allows logons from any IP address to an authenticated user.