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
Managing User Groups
Safeguard Administrator’s Manual—523317-013
3-2
Adding User Groups
Adding User Groups
Any super-group member can add a group definition group unless an OBJECTTYPE
USER access control list exists. If an OBJECTTYPE USER record exists, only users
with CREATE authority on that access control list can use the ADD GROUP command.
Assume that the user ADMIN.DON (user ID 16,24) has C authority on the
OBJECTTYPE USER access control list. To create a group that could be subsequently
activated as an administrative group, ADMIN.DON enters this command:
=ADD GROUP PROG4, NUMBER 144, DESCRIPTION Maintenance &
=programmers for Inventory System
The group name PROG4 and group number 144 meet the syntactical requirements for
administrative group names and numbers. A group name specified in a GROUP
command is case-sensitive. Therefore, an administrative group name must be entered
in uppercase letters.
ADMIN.DON could create another group named ProG4:
=ADD GROUP ProG4, NUMBER 1144, DESCRIPTION Inventory system &
=programmers
Two distinct groups, PROG4 and ProG4, now exist concurrently. But only PROG4 can
serve as an administrative group. The group ProG4 was given the group number 1144
because it is advisable to reserve the group numbers below 256 for administrative
groups. An administrative group must have a group number from 0 to 255.
The group PROG4 is considered a file-sharing group unless a user is added to it with
the ADD USER command. If this occurs so that the group PROG4 is activated as an
administrative group, it can be specified on Safeguard access control lists. Only
administrative groups can appear on Safeguard access control lists. File-sharing
groups cannot appear on access control lists. The group name ProG4 cannot be
specified on access control lists, but it can be used for file-sharing in an OSS
environment.
To verify the results of the commands, use the INFO GROUP command:
=INFO GROUP PROG4, DETAIL
The display shows:
=INFO GROUP ProG4, DETAIL
GROUP NAME NUMBER OWNER LAST-MODIFIED
PROG4 144 16,24 23JUL94, 11:16
AUTO-DELETE = OFF
DESCRIPTION = Maintenance programmers for Inventory System