tdspolicy for a TD2 User - 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™

Users who log on with the TD2 mechanism are not subject to local policy because they are not authenticated or authorized in the directory. When you specify a Vantage username for -u, TDGSS looks in the TdgssUserConfigFile.xml to see if a global policy applies to the user.

Profile-based policies do not apply to users authenticated by TD2.
$ tdspolicy -u td2user –i 141.206.3.173
Querying policy using the following parameters:

       Teradata user: td2user
          IP address: 141.206.3.173

          Mechanisms: td2
Confidentiality QoPs: default

where the Vantage user specified by -u:

  • Can use only the TD2 mechanism to log on.
  • Confidentiality is required, but because a TD2 user is not authenticated or authorized in the directory, QOP strength defaults to the DEFAULT QOP.