16.10 - System Processing of Security Policies - Teradata Database

Teradata Database Security Administration

Teradata Database
Release Number
Release Date
June 2017
Content Type
Publication ID
English (United States)

When a user logs on to Teradata Database, TDGSS checks the <LdapConfig> section of the TdgssUserConfigFile.xml for <Policy> elements. A <Policy> element found in the <LdapConfig> directs TDGSS to a directory object that is the parent of a security policy configuration. TDGSS enforces any applicable policies that it finds in the directory.

If a QOP-related policy or option applies to a session that logs on from a pre-14.10 client, the system does not permit the logon, unless the only applicable policy derives from setting the RequireConfidentiality flag to yes. See Requiring Confidentiality.

The system determines the security policy for a session based upon client settings, such as a client request for confidentiality or integrity, combined with other applicable security policy.

  • In the absence of an applicable QOP or option policy, a request for confidentiality or integrity on the client uses the DEFAULT QOP.
  • If multiple QOP policies apply to the session, the strongest QOP takes precedence.