(4)
Assign command groups to the user identity.
(5)
Enable login and/or authority checking for the terminal.
Notice all terminal and user identities are added to TAUTH and PAUTH and assigned command groups
before
login
and/or authority checking are configured. This ensures that the desired command group assignments are in place
before anyone is subject to authority checking on the device. If (5) was done between (1) and (2), then ALL input
requests from the terminal would be restricted until (2) is completed.
3.8.4.2 Administering User Identities
User identities defined with the admin command are used when authority checking is disabled ('n' authority level).
Be aware that the login/password database for 'n' authority is not the same database used for 't' and 'u' authority.
The admin command is documented in the Administration section of 235-700-200,
UNIX
®
System Reference
Manual
.
For 't' and 'u' authority levels person (user) identities are added to the person authority database via the
ADD:PAUTH
input message. The administrator specifies the user name (identity) and a password, which the user
will be forced to change at first login. For example:
ADD:PAUTH:IDENT="userid",PSSWD="userpass"
By default, a user identity has no command groups assigned (it is completely restricted). Because of this, it is
recommended that the administrator assign command groups to the user identity immediately after the identity is
added to the personal authority data base.
The administrator can override a user's password via the
CHG:PAUTH
. The user will be forced to choose a new
password upon his or her next login. For example:
CHG:PAUTH:IDENT="userid",PSSWD="newpass"
ADD:PAUTH
and
CHG:PAUTH
are not printed (echoed) on the ROP in order to keep passwords private.
A user identity is deleted from the person authority data base via the
DEL:PAUTH
input message. For example:
DEL:PAUTH:IDENT="userid"
The administrator can retrieve information about user identities from the person authority data base using the
VFY:PAUTH
input message. The following lists all user identities in the person authority data base:
VFY:PAUTH
The following reports the last login time for a given user identity:
VFY:PAUTH:IDENT="userid"
3.8.4.3 Administering Terminal Identities
The first step in administering terminal identities is to determine the terminal identity names for the terminals
involved. For example, the terminal identity for
/dev/ttyn
is
ttyn
.
A terminal identity is added to the terminal authority data base (TAUTH) via the
ADD:TAUTH
input message:
ADD:TAUTH:TERM="ttyn"
where
ttyn
is replaced with the desired terminal identity.
By default, a terminal identity has no command groups assigned (it is completely restricted). Because of this, it is
recommended that the administrator assign command groups to the terminal identity immediately after the identity is
added to the terminal authority data base.
A terminal identity is deleted from the terminal authority data base via the
DEL:TAUTH
input message. For example:
DEL:TAUTH:TERM="ttyn"
235-105-210
October 1999
Copyright © 1999
Page 28
Summary of Contents for 5ESS-2000
Page 96: ...235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 184: ...235 105 210 October 1999 Copyright 1999 Page 3 ...
Page 300: ...13 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 55 ...
Page 339: ...7 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 13 ...
Page 342: ...235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 359: ...235 105 210 October 1999 Copyright 1999 Page 5 ...
Page 609: ...2 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 12 ...
Page 676: ...235 105 210 October 1999 Copyright 1999 Page 9 ...
Page 792: ...3 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 9 ...
Page 799: ...Figure 11 36 3 1 Cleaning Points 235 105 210 October 1999 Copyright 1999 Page 7 ...
Page 801: ...235 105 210 October 1999 Copyright 1999 Page 9 ...
Page 839: ...2 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 16 ...
Page 999: ...2 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 13 ...
Page 1008: ...Figure 11 55 1 CTSNS DIP Switch Settings 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1011: ...235 105 210 October 1999 Copyright 1999 Page 5 ...
Page 1053: ...235 105 210 October 1999 Copyright 1999 Page 15 ...
Page 1289: ...Figure 15 17 2 AMATPS Data Link 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1292: ...235 105 210 October 1999 Copyright 1999 Page 5 ...
Page 1303: ...9 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1360: ...Figure 15 47 2 Typical SCANS III Link Diagram 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1372: ...235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1374: ...235 105 210 October 1999 Copyright 1999 Page 4 ...
Page 1421: ...Table 1 1 O M Checklist 235 105 210 October 1999 Copyright 1999 Page 3 ...