17.20 - General Rules for Editing the TDGSS Configuration - 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
  • You can individually enable or disable authentication mechanisms, but a logon fails if the operant mechanism for a session is disabled on the client or the database. This is true for both system-selected (default) and user-selected mechanisms.
  • Security requirements may vary among Vantage clients. You may find it useful to configure and enable a different set of mechanisms or define a different default mechanism for different clients.
  • You can designate only one mechanism as the default mechanism. The system automatically uses the default, so users do not need to specify the mechanism at logon.
  • Before you edit the value of a mechanism property, review the editing guidelines for the property. See the topics beginning with Mechanism Properties.
  • Most mechanism properties are editable only on Vantage nodes.
  • On Vantage clients, only the MechanismEnabled and DefaultMechanism properties can be configured.
  • If no mechanism is specified in a user logon, job script, or client application preset, the system uses the first configured DefaultMechanism it finds, in the following order:
    1. Client TdgssUserConfigFile.xml default
    2. Teradata Vantage TdgssUserConfigFile.xml default
  • You must edit certain properties as part of implementing common security administration strategies, for example, directory authentication and authorization.
  • Some optional properties and mechanisms do not appear in the TdgssUserConfigFile.xml. You must manually copy them from the TdgssLibraryConfigFile.xml and add them to the TdgssUserConfigFile.xml before configuring them.