Safeguard Administrator's Manual (G06.24+, H06.03+)
Table Of Contents
- What’s New in This Manual
- About This Manual
- 1 Introduction
- 2 Controlling User Access
- Introduction
- Using SAFECOM to Establish a Local User Community
- Using SAFECOM to Manage User Access to Your System
- Changing the Owner of a User Authentication Record
- Granting a User Temporary Access to Your System
- Requiring Users to Change Their Passwords
- Granting a Grace Period for Changing an Expired Password
- Forcing Immediate Expiration of a User’s Password
- Freezing a User's Ability to Access the System
- Specifying Auditing for a User ID
- Deleting Users
- Deleting Administrative Groups
- Using SAFECOM to Establish a Network of Users
- Using Safeguard With Nodes With Standard Security
- Identifying Network Users
- Granting a Network User Access to Objects on Your System
- Establishing a Community of Network Users
- Changes to the PAID During a User’s Session
- Additional Considerations for Aliases and Groups
- Additional Considerations for ACCESS with Network Specific Subject IDs
- Establishing Default Protection for a User's Disk Files
- Specifying a Default Command Interpreter for a User
- Establishing Guardian Defaults
- Assigning an Alias to a User
- 3 Managing User Groups
- 4 Securing Volumes and Devices
- 5 OBJECTTYPE Control
- 6 Managing Security Groups
- 7 Securing Terminals
- 8 Warning Mode
- 9 Configuration
- Safeguard Attributes
- Configuring User Authentication
- Configuring Password Control
- Configuring Device Control
- Configuring Process Control
- Configuring Disk-File Control
- Configuring Safeguard Auditing
- Configuring a Default Command Interpreter
- Configuring Communication With $CMON
- Configuring Logon Dialog
- Configuring Exclusive Access at Safeguard Terminals
- Configuring Warning Mode
- Configuring Persistence
- Configuring Attributes for Node Specific Subjects in ACLs
- 10 Installation and Management
- Safeguard Components
- Process Considerations for the SMP and SAFECOM
- Safeguard Subsystem Management Commands
- General Installation Procedure
- Installing the Safeguard Software
- Starting the SMP
- Converting to the Safeguard Subsystem
- Updating the Safeguard Software
- Guidelines for Securing the Safeguard Subsystem
- Monitoring the Safeguard Subsystem
- A SAFECOM Command Syntax
- Index
Controlling User Access
Safeguard Administrator’s Manual—523317-013
2-31
Establishing a Community of Network Users
The concept of network groups and local groups does not apply if you define user
aliases as network users. Administrative group names need not be coordinated for
user aliases functioning as network users. Group names are not checked during the
remote validation of a user alias. However, group numbers are checked.
For instance, assume that in the previous example, SALES.FRED at the node \NY has
the user alias Freddie defined as follows. If an alias authentication record for Freddie is
defined with a matching user ID and matching remote passwords at \SF, SALES.FRED
can access objects on \SF from \NY regardless of the group name associated with the
alias Freddie at \SF. Similarly, the user with the alias Freddie at \SF can access
objects on \NY.
System \NY System \SF
Alias : Freddie Alias : Freddie
User Name : SALES.FRED User Name : SOFTWARE.JOE
User ID : 2,0 User ID : 2,0
Remote password: \NY xyz Remote password: \NY xyz
Remote password: \SF asdfg Remote password: \SF asdfg
Figure 2-1. A Community of Network Users
San Francisco
Los Angeles
Dallas
New York
1, 0 ADMIN BOB \NY XYZ
\DA QWERTY
\SF ASDFG
\LA ABC
2, 0 SOFTWARE JOE \SF ASDFG
\LA ABC
2, 1 SOFTWARE JAN \SF ASDFG
\LA ABC
1, 0 ADMIN BOB \NY XYZ
\DA QWERTY
\SF ASDFG
\LA ABC
2, 0 SALES FRED \NY XYZ
\DA QWERTY
2, 1 SALES MARY \NY XYZ
\DA QWERTY
1, 0 ADMIN BOB \NY XYZ
\DA QWERTY
\SF ASDFG
\LA ABC
2, 0 SOFTWARE JOE \SF ASDFG
\LA ABC
2, 1 SOFTWARE JAN \SF ASDFG
\LA ABC
1, 0 ADMIN BOB \NY XYZ
\DA QWERTY
\SF ASDFG
\LA ABC
2, 0 SALES FRED \NY XYZ
\DA QWERTY
2, 1 SALES MARY \NY XYZ
\DA QWERTY
\LA
\SF
\NY
\DA
VST001.vsd