The LOGON program is used by Safeguard software to manage the user authentication process for Safeguard controlled terminals. LOGON can be started by the LOGIN program if the terminal is connecting to the system via dynamic TCP/IP. Otherwise, it is started directly by Safeguard software . The LOGON program displays the "Safeguard 1>" prompt at which the user enters the userid or alias and the password for that userid or alias.
After authentication, the Safeguard TERMINAL record for the terminal where LOGON is running is used to determine what program will be started. If no values are defined in the TERMINAL record or there is no TERMINAL record, the USER record in Safeguard software will be used. If no values are defined in the USER record, the Safeguard global values will be used. If there are no values in the Safeguard globals , the TACL program located in the active system image will be used.
The program that is started is supplied with all of the user's authentication information so the user is not prompted again for the userid or alias and password.
BP-FILE-LOGON-01 LOGON should be secured "UUNU".
BP-OPSYS-LICENSE-01 LOGON must be LICENSED.
BP-OPSYS-OWNER-01 LOGON must be owned by SUPER.SUPER.
BP-OPSYS-FILELOC-01 LOGON must reside in $SYSTEM.SYSnn.
Discovery Questions | Look here: | |
---|---|---|
OPSYS-OWNER-01 | Who owns the LOGON object file? | Fileinfo |
OPSYS-LICENSE-01 | Is the LOGON object file licensed? | Fileinfo |
FILE-POLICY | Who is allowed to execute LOGON on the system? | Policy |
FILE-LOGON-01 I | s the LOGON object file secured correctly? | Fileinfo |
Related Topics
LOGIN
User Management
Safeguard subsystem
TELSERV