GRANT LOGON Syntax - Analytics Database - Teradata Vantage

SQL Data Control Language

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-07-11
dita:mapPath
sgu1628111251052.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
dvv1472243528022
lifecycle
latest
Product Category
Teradata Vantageā„¢
GRANT LOGON ON
  { host_id [,...] | ALL }
  { AS DEFAULT | { TO | FROM } user_name [,...] }
  [ WITH NULL PASSWORD ] [;]

Syntax Elements

host_id
A mainframe connection or a workstation network connection that is currently defined to the system by the hardware configuration data. The interface need not be operational.
You can define multiple host IDs per node.
The host ID for the system console is 0. For any other connector, the value for host_id ranges from 1 through 32,767.
ALL
Any source through which a logon is attempted, including the system console.
AS DEFAULT
The current default for the specified host_id set is to be changed, without residual conditions, as defined in this GRANT LOGON statement. A statement with AS DEFAULT has no effect on the access granted to or revoked from particular user names.
A statement that sets the default for a specific host_id takes precedence over a statement that sets the default for ALL client systems.
TO
FROM
The clause that specifies the recipient of the GRANT results.
user_name
One or more user names whose current system logon defaults are to be changed.
  • You cannot specify the name DBC as a user name in a GRANT LOGON statement. A statement that includes this name returns an error message.
  • The product of the number of host IDs times the number of user names cannot exceed 25.
WITH NULL PASSWORD
Permits a logon string that has no password to be accepted from the specified client system community.
The initial default is that all logon requests must include a password. The WITH NULL PASSWORD option, in conjunction with a TDP security exit procedure, negates that default.
This option implies that the user has been authenticated externally and not by the database. See Teradata Vantageā„¢ - Analytics Database Security Administration, B035-1100 for more information.