Users and Roles

There are two categories of users – customer (with four roles: Viewer, Operator, User, and Administrator) and service (with three roles: Service, Advanced Service, and Escalation). A user's role determines their access to GUI functions and SCI methods.

• See the “User Roles" section of the SL4000 Library Guide for role descriptions and authorized GUI functions.

Creating Customer Users

The administrator can use the GUI to create customer users by defining the user ID, password, and role (see the “Add, Modify, or Delete a User" section in the SL4000 Library Guide). Passwords must be at least eight characters long and include a mix of letters (uppercase or lowercase) and numbers.

Creating Service Users

Service users are either automatically generated by the library following the detection of a fault or manually created by the administrator. Service users have a specified role, but a randomly generated user ID and encrypted password (known as a key file). Oracle Services can decrypt the key file to provide the credentials to a field engineer. Service users expire 72 hours after creation and cannot be extended.

When the library detects a fault, it automatically creates a user with the "Service" role and generates an encrypted support bundle (which contains the service key file). You must manually transmit the support bundles to Oracle Service, unless you have configured the library to perform Automated Service Requests (ASR). If the fault requires more than 72 hours to resolve or requires a higher-level service role, the administrator may need to create an additional service user ID through the GUI (see the “Add a Service User" in the SL4000 Library Guide).