Logon Format - Teradata Database

Logons to Teradata Database can take the following forms:

Command line

Graphical User Interface (GUI)

Logon from a mainframe-attached client

Logon through a middle-tier application

Command-Line Logon

Users provide the following information when logging on from a workstation-attached client:

.logmech: Specifies the name of the security mechanism that defines the method by which the user will be authenticated and authorized. If a mechanism is not specified, the logon proceeds using the designated default mechanism.

.logdata: Used only for external authentication. Specifies the username and password, and optionally names an individual username, profile, or role where the logon user has access to multiple user identities, profiles, or roles.

.logon: Must be used for Teradata Database authentication. May be used for external authentication except when the logon requires specification of user=, profile=, or realm= to differentiate among multiple user identities, profiles, or realms.

For either authentication type, .logon specifies the tdpid, username, password, and optional account string information.

Note: The format required for the username and password information varies depending on the user is sign-on method.

For more information on command-line logons, see Security Administration.

GUI Logons

Some Teradata Database client applications provide a logon GUI in the form of dialog boxes. The dialog boxes provide fields and buttons that prompt the user to enter the same logon information shown for command-line logons.

For an example of a GUI logon, see Security Administration.

Logons from Mainframe-Attached Clients

Sessions logged on from mainframe-attached clients do not support network security features, such as security mechanisms, encryption, or directory management of users. Such logons require submittal of only the username, password, tdpid, and optional account string information using the .logon command.

For information on logons from mainframe-attached clients, see Security Administration and Teradata Director Program Reference.

Logons Through Connection Pools

Some users access the database through a middle-tier application. The application must log on to Teradata Database with a database username. The application then sets up a connection pool that allows individual end users access to the database but does not require that the users formally logon. End user privileges are determined by whether or not the application and its end-users are set up for trusted sessions.

For information, see “Authorization of Middle-tier Application Users” on page 158.