17.20 - QOP Configuration Options - Analytics Database - Teradata Vantage

Teradata Vantage™ - Analytics Database Security Administration - 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
2023-03-07
dita:mapPath
hjo1628096075471.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
zuy1472246340572

You can enable QOP strength options in the TD2, JWT, PROXY, and LDAP mechanisms, to use in enforcing QOP security policy. For information about how QOP strength options are used in QOP security policy, see Network Security Policy.

For users authenticated by Kerberos (KRB5 or SPNEGO mechanism) who enable message encryption or are subject to a confidentiality QOP policy, the system uses the encryption method and strength automatically negotiated by Kerberos. See Message Encryption for Kerberos Authentication.

The following table describes QOP configuration options for each element in the QOP section of the TDGSS configuration file.

Configuration File Element Configuration Options
DEFAULT QOP You can edit the DEFAULT QOP to a different encryption strength.
  • AES-128 (default)
  • AES-192
  • AES-256
  • LOW SECURITY QOP
  • MEDIUM SECURITY QOP
  • HIGH SECURITY QOP
If you plan on configuring QOP security policies, you can:
  • Enable the LOW, MEDIUM, and HIGH SECURITY QOP entries for use in confidentiality and integrity policies.
  • Optionally edit the LOW, MEDIUM, and HIGH SECURITY QOP entries to specify a different encryption strength.