TDGSS DefaultNegotiatingMechanism Property | Teradata Vantage - DefaultNegotiatingMechanism - 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
Language
English (United States)
Last Update
2023-11-02
dita:mapPath
hjo1628096075471.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
zuy1472246340572
lifecycle
latest
Product Category
Teradata Vantage™

The DefaultNegotiatingMechanism property is used to specify a default mechanism from among the mechanisms with the NegotiationSupported property set to yes. This property is used to determine the default mechanism when both the client and the server support mechanism negotiation.

Any mechanism that has the mechanism property DefaultNegotiatingMechanism set to yes must also have the mechanism property NegotiationSupported set to yes; otherwise, the tdgssconfig executable reports an error.

If both client and server support negotiation, but no common negotiating mechanism exists between them, then the existing DefaultMechanism property is used to select a default mechanism.

Default Property Value

TDGSS sets the value of this property to no for all mechanisms for all platforms (Teradata Vantage and clients).

Valid Settings

Setting Description
yes The mechanism is the default negotiating mechanism.
no The mechanism is not the default negotiating mechanism.

Editing Guidelines

  • You can set the DefaultNegotiatingMechanism property on Teradata Vantage nodes, and Vantage clients.
  • Any mechanism that has the mechanism property DefaultNegotiatingMechanism set to yes must also have the mechanism property NegotiationSupported set to yes, otherwise the tdgssconfig executable reports an error.
  • You can designate a different default mechanism and default negotiating mechanism for each client.