TDGSS MechanismRank Property | Teradata Vantage - MechanismRank - 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 MechanismRank property defines the order of preference in which client applications offer mechanisms for user selection.

Default Property Values

  • TDNEGO = “10”
  • TD2 = “20”
  • JWT = “30”
  • KRB5 = “40”
  • SPNEGO = “65”
  • LDAP = “70”
  • PROXY = “80”

Valid Settings

The value for MechanismRank must be numeric.

Default MechanismRank values are for reference only and need not be in increments of 10. The system ranks values in order from low to high, with the lowest numbers having the highest preference.

Editing Guidelines

  • TDNEGO supports MechanismRank. However, TDNEGO only looks at the mechanism rank of the mechanisms it is trying to negotiate: TD2, ldap, KRB5, and SPNEGO. For all other mechanisms, including TDNEGO itself, MechanismRank is not used.v
  • TDNEGO uses the MechanismRank property to determine the priority order of the mechanisms being negotiated.
  • For TDNEGO, this property can be set independently on the client and Teradata Vantage server. Note: The decision of which mechanism to select is attempted locally at both client and server. If all mechanism ranks are different on client and server, it is the ordering at the system where the decision is made that takes effect.