.th LOGIN I 4/21/86
.sh "NAME"
login \- sign onto KSOS
.sh "DESCRIPTION"
.s3
The login procedure is used when a user initially signs onto KSOS.
When the user hits the Secure Attention key at a terminal which is not
logged in, the Secure Server Process (SSP) invokes login at that
terminal.
.s3
Login prompts for a user name and password.  Echoing is turned off (if
possible) during the typing of the password, so it will not appear on
the written record of the session.
.s3
After a successful login, the user integrity level is checked.  If it
is system_low, the user and supervisor domain programs specified in the
user access authentication database (user) will be entered.  If there
is no supervisor domain program specified in the database, login will
prompt the user to hit the Secure Attention key.  If the user is not at
system_low integrity, an informative message will be issued and the
user will use the Secure Server Process (SSP) as a command interpreter.
.s3
The user's security level will normally be the default level specified
in the user access authentication database for the given login name.
If this level is higher than the maximum level of the terminal or the
current maximum level of the system, the user's level will be lowered
accordingly and a diagnostic message will be issued.
.sh FILES
.lp 30 25
/sys/dataBases/user     user access authentication database
.lp 30 25
/sys/dataBases/group    group access authentication database
.lp 30 25
/sys/dataBases/terminal terminal profile database
.lp 30 25
/sys/dataBases/system   system profile database
.i0
.i7
.sh "SEE ALSO"
logout(I),
SIP(VIII),
SSP(VIII),
user(V),
group(V),
terminal(V),
system(V)
.sh DIAGNOSTICS
.lp 30 25
"Login denied," if user does not exist or wrong password is given.
.lp 30 25
"Your maximum level is too low to login."
.lp 30 25
"Your integrity level is too high to run an emulator."
.sh NOTES
This procedure is implemented internal to the Secure Server Process,
SSP(VIII).

