Neoview User Management and Security Administration Guide (R2.5)
Changes in any of these policy attributes require you to restart NDCS services:
• Allow Down-rev Drivers to Connect
• Log Successful Database Logins
• Log Failed Database Logins
• Abort Database Login if Logging Fails
• Role password Required at Login-Database Users
• Role password Required at Login-Platform Users
NOTE: Although in almost every case, you change a policy by specifying it explicitly in a dialog
or on a command line, HPDM also includes radio buttons labeled Load Default and Load
Most Secure, which let a user reset a group of policies to their default or most secure values.
These options should be used with the utmost care, and if their use affects the value of any policy
indicated here as requiring restart, you must stop and restart all services in order for the change
to take effect.
The full set of actions required to implement any of these policy changes is as follows:
1. A user in the ROLE.SECMGR role alters the security policy, using HPDM or NCI.
2. If the security policy is one of those in the list just presented, the ROLE.SECMGR user uses
HPDM or NCI to stop every NDCS service—“on client disconnect” in HPDM or with
STOPMODE DISCONNECT in NCI—then to start every NDCS service again. When you
stop and restart an NDCS service in this way, all servers associated with the service that are
started and in an Available state are stopped and restarted. Any connected servers are
stopped only after a client disconnects or a session timeout occurs; for example, the HPDM
or NCI session in which you stop and restart the NDCS services is not itself restarted because
it is still connected.
NOTE: If the policy change placed new requirements on a user's credentials—for example,
if the change was to require a power database user such as ROLE.SECMGR to provide a
role password in addition to the individual's password in order to log on--the ROLE.SECMGR
user might encounter an error when logging on to stop and restart the services. In this case,
he or she should try again with credentials that comply with the new policy.
3. The user disconnects from HPDM or NCI, then reconnects to have the new security settings
apply to subsequent HPDM or NCI sessions. HPDM displays a message reminding the user
to take this action.
4. New policy settings will apply to users of other applications only after they disconnect and
reconnect.
40 Post-installation Security Setup Tasks