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

Migration of Users from an Earlier Neoview Release
If you upgraded your Neoview platform from a release earlier than 2.5, your platform already
has a set of locally or remotely authenticated database users corresponding to database users
defined on the platform from which you upgraded. You can use the procedures and interfaces
described in this chapter to define additional users or replace one kind of database user with
another.
The migration procedures do not create platform users corresponding to users who existed on
a Neoview release earlier than 2.5, except the minimal set of platform users listed in “User and
Role Names and Associated Functions” (page 19). You can use the procedures and interfaces
described in this chapter to define additional platform users.
Platform users defined on an earlier release can log on to Neoview 2.5 platform command interpreters but
can no longer log on to Neoview clients such as NCI, ODBC, or HPDM. Any platform user who requires
access to Neoview clients must have a new platform account, created as described in “Creating a Platform
User Account” (page 104).
User and Role Management Interfaces
The Neoview platform offers the following interfaces for managing database and platform users
and roles:
• NCI commands to assign names and roles to database and platform users and to manage
passwords for platform-level users. These commands are described in “User Management
Commands” (page 108) and are especially useful if you want to create scripts to add or
modify information for a large number of users.
• HPDM dialogs that provide functions equivalent to the NCI commands. These dialogs are
described in detail in the HPDM Online Help and provide a user-friendly interface for defining
or changing attributes of users singly or in small groups.
• Views for monitoring user-management actions pertaining to database users and
platform-level users, described in “User Management Views” (page 120)
User Management Tasks
This section describes the tasks involved in managing users and roles on Neoview.
You can make user-management changes on any segment of a Neoview platform. Changes are
propagated automatically to other segments.
NOTE: Backup and recovery facilities on Neoview have two implications for role and user
management:
• Making a user-management change during a backup could cause the backup to be inconsistent
with regard to the change: in the event of a recovery, the change might be fully available,
might not be available at all, or might be partially applied. Therefore, you should not perform
any user management actions on the Neoview platform while a backup is in progress.
• If a failure should require recovery of system files that contain information about users, it
is possible for some user-management information to become inconsistent. If security errors
occur after system data recovery, it might be necessary to repeat user management actions
for any affected users. For example, if you added a role and assigned it to users since the
last backup, the role might not be available following recovery, and users having only that
role might therefore be unable to log on. To resolve such a problem, delete each affected
user, add the role again, and then add the users to whom the role should be assigned.
Managing Database Users and Roles
The security infrastructure provides the following HPDM dialogs and NCI commands for user
and role management. Most user-management actions that pertain to database users can be
96 User and Role Management