Difference between revisions of "UCI~"
| Line 1: | Line 1: | ||
; UCI | ; UCI | ||
| − | : User Class Identification, a computing area. The MGR UCI is typically | + | : User Class Identification, a computing area. The MGR UCI is typically the Manager's account, while VAH or ROU may be Production accounts. The UCI is an older concept represented by a namespace in Cache systems. The UCI in MUMPS systems is similar to the UIC in VMS (User Indentifier Class) where the UIC a way of identifying a combination of users and groups or classes. In a Linux or Unix system, the username and group provides a basic identification system. |
| − | the Manager's account, while VAH or ROU may be Production accounts. | + | |
| + | There are also more complex ways to identify a user or a privilege. In VMS this is called an Access Control List (ACL). | ||
| + | In VMS, an ACL ties the access control with a set of named privileges for each of the capabilities of the operating system. | ||
| + | These privileges may include basic system levle administrative tasks, the ability to start or stop network connections, The ability to mount the tape drives, to print a message on the console, to add memory to your existing running process, and many more. Within Unix or Linux, the ACL ideas come in when a system has implemented the ideas from the NSF's SELinux. | ||
| + | |||
| + | SECURITY KEYS in VistA are very similar to ACLs as they control the ability to perform particular activities, or control access to parts of the system. Depending on the package, SECURITY KEYS are either very broad or extremely narrow in what they control. The FileMan Access Code characters in [[DUZ(0)~|DUZ(0)]] also control access to fields or files. | ||
| + | In recent years, some programs have been using PARAMETERs to provide some of the security aspects of SECURITY KEYs. | ||
Revision as of 16:08, 6 December 2005
- UCI
- User Class Identification, a computing area. The MGR UCI is typically the Manager's account, while VAH or ROU may be Production accounts. The UCI is an older concept represented by a namespace in Cache systems. The UCI in MUMPS systems is similar to the UIC in VMS (User Indentifier Class) where the UIC a way of identifying a combination of users and groups or classes. In a Linux or Unix system, the username and group provides a basic identification system.
There are also more complex ways to identify a user or a privilege. In VMS this is called an Access Control List (ACL). In VMS, an ACL ties the access control with a set of named privileges for each of the capabilities of the operating system. These privileges may include basic system levle administrative tasks, the ability to start or stop network connections, The ability to mount the tape drives, to print a message on the console, to add memory to your existing running process, and many more. Within Unix or Linux, the ACL ideas come in when a system has implemented the ideas from the NSF's SELinux.
SECURITY KEYS in VistA are very similar to ACLs as they control the ability to perform particular activities, or control access to parts of the system. Depending on the package, SECURITY KEYS are either very broad or extremely narrow in what they control. The FileMan Access Code characters in DUZ(0) also control access to fields or files. In recent years, some programs have been using PARAMETERs to provide some of the security aspects of SECURITY KEYs.
Source: VistA User Manual
| This is a Glossary term from the VistA Documentation Library |
