ADMIN_KEYFILE Keyword

     ADMIN_KEYFILE={keyfile}

This keyword controls access to administrative data maintained by the Data Manager. The keyword specifies a logon key file.

The {keyfile} identifies a data file formatted similarly to an INI file that contains a [user] section. When the second level security is used, any user who tries to access the administrative services must have a line item entry in the [user] section.

Each line item 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 administrative services. If the assignment value is zero, the user cannot have access. 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.

Example:

[user]

User_9faa02b6940e1866e8a574fca50018e7=1 ;John Jones

If PLBWIN is operating in one or both of the security modes, any runtime client that attempts to access the administrative services must match the security requirements. Otherwise, the client program terminates with an appropriate I82 error. This also means that any older runtime clients that do not support encryption will not be allowed to access the administrative services when any security level is used.

Note the following:

1. 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.

2. If logon security is used in conjunction with public key security, it is possible to prevent individual/specific LOGON keys without affecting other users accessing PLBWIN.

3. The public/logon keys are defined by the individuals responsible for controlling the administrative server security requirements.

See Also: SUNDM Keywords, SUNADMIN, MAKEMFD