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

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, Unity servers, 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, Unity server, 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.