16.10 - NegotiationSupported - Teradata Database

Teradata Database Security Administration

Product
Teradata Database
Release Number
16.10
Release Date
June 2017
Content Type
Administration
Security
Publication ID
B035-1100-161K
Language
English (United States)

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 will have NegotiationSupported set to yes.

The SPNEGO mechanism is no longer considered a negotiating mechanism, because starting with Teradata Database 15.10 it can only be used for Windows .NET clients that are connecting to Teradata servers using the Kerberos mechanism. Therefore SPNEGO will have 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 Teradata Database server, Unity 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.

Supporting Mechanisms for NegotiationSupported

Mechanisms that are not listed in the table do not support this property. The Property Editable column indicates if the setting for a property may be edited.
Mechanism Property Editable?
TDNEGO Do Not Edit

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.