16.10 - LegacyUnAuthBehavior - Teradata Database

Teradata Database Utilities

Product
Teradata Database
Release Number
16.10
Published
June 2017
Language
English (United States)
Last Update
2018-04-26
dita:mapPath
zll1480972831047.ditamap
dita:ditavalPath
changebar_rev_16_10_exclude_audience_ie.ditaval

Purpose

Controls whether some unauthenticated user names are logged in the DBC.EventLog table as they were entered or as "Non-existent User".

Field Group

General

Valid Settings

Setting Description
TRUE Preserve legacy Teradata Database behavior to log some unauthenticated user name values to DBC.EventLog.
FALSE Log unauthenticated user name values as the literal "Non-existent User" in the DBC.EventLog table.

Default

FALSE

Changes Take Effect

After the DBS Control record has been written.

Usage Notes

The name information is logged in the UserName and AuthUser columns of DBC.EventLog and in views that are based on this table, such as DBC.LogOnOffV.

In some cases, in Teradata Database releases without the LegacyUnAuthBehavior field, user names that could not be authenticated were nevertheless logged and visible in the DBC.EventLog table. When a user logs in to the database and types a user name and password, a common mistake is to accidentally enter the password in the user name field. Because this would be considered an "unauthenticated user" by the database, legacy behavior can risk having these misplaced passwords logged to the database.

The default setting of FALSE for LegacyUnAuthBehavior prevents these user names from being visible in the log by recording them as "Non-existent User".

Change this field value to TRUE if you want to preserve the legacy behavior, and record some user name values in the log.

Related Topics

  • For more information about Data Dictionary tables and views, see Data Dictionary, B035-1092.