Neoview User Management and Security Administration Guide (R2.5)

A database role has a fully qualified name of the form ROLE.role. Some database roles are
predefined, but a user who has the role ROLE.MGR can define additional roles, as discussed in
“Roles and Role Assignment” (page 22).
Platform User Names and Roles
Certain users log on with personal names associated with special platform roles, similar to database
roles in that they have associated access privileges. Such platform-level users are authenticated
locally and therefore able to perform troubleshooting and maintenance operations whether or
not an external directory server is available.
A platform-user name (also called an “alias” in some Neoview documentation) is a text string
with a maximum of 32 characters, potentially including alphanumeric characters and the special
characters period (.), hyphen (-), and underscore (_). Such a name is case-insensitive in all Neoview
interfaces accessible to customers. (Certain tools used only by HP Support require the name to
be entered in uppercase.)
The valid platform roles are:
• SUPER.SUPER. Logs on with the predefined name “SUPERUSER” or another name defined
by the Security Administrator.
• SUPER. SERVICES. Logs on with the predefined name “HPSUPPORT” or another name
defined by the Security Administrator.
• HP.SDI. Logs on with a name defined by the Security Administrator.
• HP.VTS. Logs on only from the external Virtual TapeServer (VTS) with the predefined name
“VTS”.
• SAP.USER. Logs on with a name defined by the Security Administrator. This role is used
exclusively in relation to the SAP application.
Special Roles for Security Administration
The following Neoview roles represent hybrids of the two main categories of user, in that they
can be assigned only to database users but are associated with system management—specifically
security related system management—and troubleshooting duties:
• ROLE.SECMGR (Security Administrator). Logs on with the predefined name
“SECURITYMGR” or another name defined by a Security Administrator or User Manager,
as described in “Post-installation Security Setup Tasks” (page 33).
• ROLE.MGR (User Manager). Logs on with the predefined name “USERMGR” or another
name defined by a Security Administrator or User Manager, as described in “Post-installation
Security Setup Tasks” (page 33).
Because the tasks specific to these users must sometimes be performed when an external directory
server is unavailable, it is a best practice to define one or more Security Administrators and User
Managers as locally authenticated database users, as described in “Post-installation Security
Setup Tasks” (page 33).
Preconfigured Users and Roles
The Neoview platform installation procedure preconfigures a small set of users and roles, listed
and described in “Predefined Users and Roles ” (page 21).
20 Introduction to Security on the Neoview Platform