DM_KEYFILE Keyword
DM_KEYFILE={keyfile}
This keyword controls logon access to data maintained by the server by defining a logon key file.
The {keyfile} identifies a data file formatted similarly to an INI file that contains a [user] section. When this level of security is used, any user that tries to access the server must have an entry in the [user] section of {keyfile}.
Each line in the {keyfile} must be formatted as follows:
[user]
User_{key32}={0|1} ;Comment Optional
The {key32} is a thirty-two (32) digit hexadecimal string that identifies the logon key that can access the server. Each key is also assigned a value of zero (0) or one (1). If the assigned value is zero, server access is denied. If the assignment value is one, access is granted. The assignment values can be changed real-time as needed. A Sunbelt administration program named SUNADMIN is available to generate the {key32} id strings.
File Content Example:
[user]
User_9faa02b6940e1866e8a574fca50018e7=1 ;John Jones
Note the following:
Public key security can be used without logon security. However, be aware that if the public key changes for any reason, all users accessing the administrative services must change to the new public key.
If logon security is used in conjunction with public key security, it is possible to prevent individual logon keys without affecting other users accessing the server.
The public and logon keys are defined by the individuals responsible for controlling the administrative server security requirements.
See Also: SUNDM Keywords, SUNADMIN, MAKEMFD
![]() |