HP Archive Backup System for OpenVMS Guide to Operations
HP Archive Backup System for OpenVMS Guide to Operations
HP Archive Backup System for OpenVMS Guide to Operations
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Security<br />
5.2 Access Control<br />
5.2 Access Control<br />
Access control complements the MDMS rights access by granting object-based control over<br />
operations. You can assign up <strong>to</strong> 32 access control entries on any MDMS object, and define the<br />
types of access that the user in the entry is granted. There are seven kinds of access that users can<br />
be granted as shown in the following table:<br />
Table 5–3 Access Control Allowed <strong>Operations</strong><br />
Allowed Access<br />
CONTROL<br />
EXECUTE<br />
DELETE<br />
READ<br />
SET<br />
SHOW<br />
WRITE<br />
Explanation<br />
The user may modify the object’s access control<br />
The user may per<strong>for</strong>m operations on the object<br />
The user may delete the object<br />
The user may per<strong>for</strong>m res<strong>to</strong>re requests using this object (ABS only)<br />
The user may modify the attributes of this object<br />
The user may show this object<br />
The user may per<strong>for</strong>m save requests using this object (ABS only)<br />
You can manipulate access control from MDMSView using the Access tab on an object’s Show<br />
screen. From the DCL, you can use the /ACCESS qualifier. In either case, the user name specification<br />
should include both node name and user name in the <strong>for</strong>mat:<br />
node::username<br />
From either interface, wildcards are supported in both the node and username portions of the<br />
specification. For example:<br />
HOUST%::SMITH* allows users whose name begins with SMITH access from HOUST%<br />
JUNGLE::* allows all users access from node JUNGLE<br />
*::SYSTEM allows all users named SYSTEM from all nodes<br />
SYS001::JAMES allows user JAMES from node SYS001 only<br />
If an access control entry matches a requesting user, only the access that is granted in the entry is<br />
granted <strong>to</strong> the user. Allowances that are not specifically listed are not granted.<br />
Access control checks are optionally per<strong>for</strong>med depending on attributes that you can set in the<br />
domain. The following table explains the settings:<br />
Table 5–4 Domain Access Control Options<br />
Check Access Relaxed Access Explanation<br />
Clear Clear No access control checking is done<br />
Clear Set No access control checking is done<br />
Set Clear Access control is checked; if there<br />
are no access control entries, access<br />
is denied.<br />
5-4 Security
Change language