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

2 Post-installation Security Setup Tasks
The Neoview platform installation procedure installs and initializes the server-side processes
and stored procedures required for LDAP integration, user and role management, and password
handling. In addition, HP Support runs utilities that perform migration from an earlier release
of Neoview to a release that potentially supports LDAP integration.
NOTE: If you are migrating from an earlier release and do not want users on your new platform
to have the same names as on your old platform, or if the names of some users on your old
platform differed only with the respect to case–for example, if one user had the name
shelbourne_chong and another SHELBOURNE_CHONG—you will need to work with HP
Support to ensure the desired mapping between your existing user names and the names you
will use on the Neoview 2.5 or later platform. Furthermore, if you intend to use an external
directory server for authentication, you will need to configure it, as described in “LDAP Integration
Overview” (page 63) and “LDAP Server Configuration on Neoview” (page 67) before your
database user community migrates.
This chapter describes the post-installation setup tasks you perform to enable secure system
management of your Neoview platform:
• “Obtaining and Installing Client Software” (page 34)
• “Changing Passwords for Predefined Users and Roles” (page 35)
• “Creating New Platform and Power Users” (page 36)
• “Viewing and Updating the Password Quality and Control Policies” (page 44)
• “Viewing and Updating the Password Encryption Policies” (page 41)
• “Enabling Password Expiration Notifications” (page 53)
• “Obtaining and Installing Certificates” (page 56)
Before you perform the tasks described in this chapter, someone must already have completed
the tasks listed for “Platform software installation and migration” in the “Security Administration
Task Map” (page 29).
33