Documentation Comments
Use this form to comment on this topic. You can also provide any general observations about the Online Documentation, or request that additional information be added in a future release.
Reality V15.2 Online Documentation (MoTW) Revision 3
Security (m604803+security.htm)
Reality provides a range of security features which enable the database administrator to secure both the database and the host against unauthorised access.
The following security features are provided to secure a Reality database.
The user-id, entered at the 'Logon please:' prompt, is a key element by which access is restricted to a database. Normally, a user-id has an associated password which must be entered in order to gain access. Various other restrictions can be placed on the user to enhance security. The user-id, password and other security restrictions are setup by the administrator using the SSM utility.
A second level of security based on the physical location of the user can be applied. Each location is assigned a Physical Location Identifier (PLId) when connection is attempted, and security restrictions can be determined for a user depending on the PLId. The association between the PLId and security is set up using the SSM utility.
Security facilities are also supported to protect individual accounts and files. These include:
Update and retrieval (u/r) lock codes. These can be assigned to an account or file to prevent users without the appropriate keys being able to access or update the account/file. Update and retrieval lock codes consist of ASCII character strings in attributes 5 and 6 of the account and file definition items. In an account definition items these can be multivalued.
The update/retrieval locking mechanism is based on string matching. A user can only update/retrieve data from a file, if the user's u/r code matches the u/r code of the targeted account/file. This enables an account and its associated files to be fully, or selectively protected from unauthorised access. See Retrieval and Update Lock Codes and Keys for details.
Reality also provides two security facilities which enable the restriction of access to the host system from the Reality environment, on a per-user basis. They are:
System Command Shell Security Level. UNIX or Windows system commands can be run from the Reality environment by invoking a Reality utility such as the SYS command, or some other TCL command created by a user to execute a system command, based on the SYS command definition. Reality provides the facility to restrict the system commands that can be executed by a particular database user. Each user can be set up by the administrator with a particular System Command Prompt Security Level, so that only a specified set of system commands can be executed by that user. See the topic Host Command Shell Security for details.
Caution
On Windows, only DOS-based system commands should be executed using SYS. A Windows-based application will run, but you will be unable to quit. The shell will hang. It order to recover, it will be necessary to kill the application on the Reality server.