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

1. Checks the location specified by CertificateDir and CertificateFile to determine
whether a certificate exists at that location. If the application did not specify a directory, the
driver checks the user's home directory. If the application did not specify a filename, the
driver assumes the name SYSTEM_NAME.cer, where SYSTEM_NAME consists of the first
five characters of the Neoview platform name.
2. If no certificate for the Neoview platform exists at the expected location and if automatic
download is permitted, the driver downloads the certificate from the Neoview platform to
the location specified by certificateFileActive. If the application did not specify that
attribute, the driver assumes the name SYSTEM_NAMEActive.cer, where SYSTEM_NAME
consists of the first five characters of the Neoview platform name. If automatic download
is prohibited, an error occurs. If automatic download is prohibited, an error occurs.
Password Change at Login
NCI and HPDM provide interfaces that let a platform user or a locally authenticated database
user change his or own password at login if the password is about to expire or has expired but
is within a configured grace period. For more information , see “Changing Your Own Password”
(page 103).
ODBC and JDBC drivers for Release 2.5 do not allow customer applications to change the
password at login. Any ODBC or JDBC application that relies on this feature will require changes
so that users are no longer offered a means of changing their passwords when they log on.
Logging on from an Older Version of a Client
Especially during the initial period of migration to Release 2.5, it is possible for the security policy
to allow older versions of clients to connect to the Neoview platform. Login instructions for users
of those older versions of clients will be the same as earlier releases, except that user names must
be specified as defined in Neoview Release 2.5. Role selection will not be available in most cases,
passwords will not be strongly encrypted, and connections to the Neovew platform will be less
secure than if current version of clients were in use.
For information about the applicable security policies, see “Viewing and Updating the Password
Encryption Policies” (page 41).
148 Secure Login and Role Selection for Neoview Users