17.10 - Examples: Enable Logging for Clients and Proxies that are Unable to Automatically Support Security Policy - Advanced SQL Engine - Teradata Database

Teradata Vantage™ - Advanced SQL Engine Security Administration

Product
Advanced SQL Engine
Teradata Database
Release Number
17.10
Published
July 2021
Language
English (United States)
Last Update
2022-02-15
dita:mapPath
ppz1593203596223.ditamap
dita:ditavalPath
wrg1590696035526.ditaval
dita:id
zuy1472246340572

Example: Enabling Logging for All

Setting the --secpcynotsupported log flag to all means the gateway logs a message in a gateway log file when an attempt is made to log on using a client or proxy that is unable to automatically support security policy:

gtwcontrol --secpcynotsupported log=all

Example: Enabling Logging for Clients

Setting the --secpcynotsupported log flag to client means the gateway logs a message in a gateway log file when an attempt is made to log on using a client that is unable to support security policy:

gtwcontrol --secpcynotsupported log=client
The gateway does not log a message if a logon attempt uses a proxy that is unable to support security policy, because such a proxy is incapable of telling the gateway when the client does not support security policy.

Example: Enabling Logging for Proxies

Setting the --secpcynotsupported log flag to proxy means the gateway logs a message in a gateway log file when an attempt is made to log on using a proxy that is unable to automatically support security policy:

gtwcontrol --secpcynotsupported log=proxy