Security Restrictions/Custom Authentication | Analytics Database (SQL Engine) 17.20 - Security-Related Restrictions - Analytics Database - Teradata Vantage

Teradata Vantageā„¢ - Analytics Database Release Definition - 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
2024-04-05
dita:mapPath
biq1628096019643.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
xvd1618799188927
Product Category
Teradata Vantage

Custom-Authentication Mechanisms

A custom-authentication mechanism is a user-authentication mechanism that is above and beyond the mechanisms that are provided with Analytics Database:
  1. Teradata Method 2
  2. KRB5 (Kerberos authentication)
  3. LDAP
  4. SPNEGO (used for Kerberos authentication for logons from Windows .NET clients)
  5. TDNEGO
  6. JWT

If additional information is required, customers should contact their Teradata representative. Teradata representatives requiring help should contact Teradata Corporate Export Compliance, Law Department.

FIPS Compliance

Analytics Database runs in FIPS-compliant mode. This might impact third-party products libraries that get loaded directly into SQL processes if they use non-FIPS cryptographic functions, such as MD5 hashing.