Teradata recommends using alternative columns instead of the LogonSource column, if available. For information about the recommended columns for LogonSource, see "LogonSource Column Fields and Examples."
Possible Values for ClientConnectionType
|1||Client is connected using TCP/IP via the gateway.|
|2||Client is connected from a mainframe via a mainframe-attached host.|
Possible Values for DirUserNetConfidentiality, UnityNetConfidentiality, EffectiveSessionNetConf
When these columns are set to I or C it indicates the level of protection required.
|I||Indicates the level of protection required for Integrity, which is obtained by lookup in the LDAP directory used for security policy. The levels are: Default (D), Low (L), Medium (M), and High (H).|
|C||Indicates the level of protection required for Confidentiality, which is obtained by lookup in the LDAP directory used for security policy. The levels are: Default (D), Low (L), Medium (M), and High (H).|
Possible Values for Event
- Logon failed
This value means a logon failed for reasons other than “Bad User,” “Bad Account,” “Bad Password,” “Bad profile,” “IP restrict,” “Auth failed,” “Bad auth,” or “Secur policy.” Currently, those other reasons are a failure to conform to Logon Rules or an attempt to log on without a password, where the TDP logon exit does not approve the logon.
- Bad user
- Bad account
This value means the user provided an account string during logon time, but that string does not match any of the account names specified for the user in the SQL CREATE USER or MODIFY USER statement.
- Bad password
- Bad profile
The external profile associated with the logon request does not exist. External profiles are stored in the directory server.
- Forced off
This value indicates that the user session was terminated from the Teradata Database console or the PM/API.
- IP restrict
This value indicates the user is not permitted to log on from the IP address used.
- Auth failed
This value indicates an authentication error.
- Bad auth
This value may indicate other authentication errors: bad authentication field, deprecated logons, decryption failure, and so forth.
- Secur policy
This value indicates that a logon attempt failed because of a security policy violation.
Possible Values for LogonRedrive
|' '||Not participating|
|MEMORY NON-FALLBACK RESPONSES||Memory-based Redrive participation|
|NULL or blanks||Session is not participating in Redrive and database restarts will not be transparent to applications and users.|
Possible Values for ProxyLogon
|T||The ProxyLogon column indicates if Unity has logged a user onto a TD2 session using existing credentials, when that user was previously validated on another Teradata Database managed by the same Unity system. When this occurs, ProxyLogon is set to T.|
|F||False indicates the TD2 session logged on or attempted to log on with a valid password.|
Possible Values for RecoverableNetworkProtocol
Possible Values for SecurityPolicy and UnitySecurityPolicy
- No Policy
- Integrity, Default
- Integrity, Low
- Integrity, Medium
- Integrity, High
- Confidentiality, Default
- Confidentiality, Low
- Confidentiality, Medium
- Confidentiality, High
The source table columns for SecurityPolicy (DBC.EventLog.RFU1) and UnitySecurityPolicy (DBC.EventLog.RFU2) are used to provide audit trail information for the security policy.
The source table column for Unity_AuthUser (DBC.EventLog.RFU3) is used to provide the audit trail information for the security policy.
The UserName column returns “Non-existent User” when a user tries to log on with a bad username.