TDGSS MutualAuthentication Property | Teradata Vantage - MutualAuthentication - 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ā„¢

The MutualAuthentication property tells the client whether to request that the server authenticate itself to the client. You can use mutual authentication to avoid man-in-the-middle attacks, which could allow the attacker to divert a network transmission to an unauthenticated third party.

Valid Settings

Setting Description
yes (default) The mechanism supports mutual authentication.
no The mechanism does not support mutual authentication.

Editing Guidelines

  • Edit this property on Vantage clients.
  • You must set MutualAuthentication to yes for KRB5 or SPNEGO.
  • If you want user logons through Unity to behave the same as user logons direct to the database, then the property setting for KRB5 and LDAP should be the same on Unity and on all connected database systems.
  • If you edit the preset value of this property on a mechanism that does not currently support it, TDGSS ignores the edit.
  • Do not modify the TDNEGO setting for this property.