TDGSS NegotiationSupported Property | Teradata Vantage - 17.20 - NegotiationSupported - 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

The NegotiationSupported property is Boolean. It signifies that a mechanism is actually a pseudo mechanism that negotiates between the client and the server to find an appropriate mechanism to use. All mechanisms that fit this description have NegotiationSupported set to yes.

The SPNEGO mechanism is no longer considered a negotiating mechanism, because it can only be used for .NET clients that are connecting to Vantage servers using the Kerberos mechanism. Therefore SPNEGO has the NegotiationSupported property set to no.

Default Property Value

TDGSS sets the value of this property to yes for TDNEGO and to no for all other mechanisms in the Vantage server and client configuration files.

Valid Settings

Setting Description
yes The mechanism is a pseudo mechanism that negotiates between the client and the server to find an appropriate mechanism to use; for example, the TDNEGO mechanism is set to yes.
no The mechanism is not a pseudo mechanism that negotiates between the client and the server.

Editing Guidelines

  • This property should never be edited.
  • Any mechanism that has the NegotiationSupported property set to yes must also have at least one NegotiatedMechanism ObjectId set for that mechanism, otherwise an error is reported by the tdgssconfig executable.