README for HP Neoview Release 2.5 (R2.5)

NOTE: The Neoview JDBC Type 4 driver no longer lets you change your password when you
log on. If you are a locally authenticated database user, you can change your password using
NCI or HPDM, as described in the Neoview User Management and Security Administration Guide.
If you are a remotely authenticated database user, your password is managed on an external
directory server; no Neoview client offers an interface for changing it.
Logging on as a Platform User
To log on as a platform user, provide:
• Your username. This is the name by which you are registered on the Neoview platform.
To specify the username, use the connection property user either in the connection string
or in the properties file. The value of this property is a string containing any valid database
user name.
• Your personal password. To specify the password, use the connection property password
either in the connection string or in the properties file.
• Your role password if the security policy at your site requires you to specify both your
individual password and your role password. If you need to specify both the personal
password and the role password, use the form mypassword/rolepassword as the value
of the connection property password, either in the connection string or in the properties
file.
As a platform user, you have only one role and therefore do not need to specify it when you log
on.
NOTE: The Neoview JDBC Type 4 driver no longer lets you change your password when you
log on. However, you can change your password using NCI or HPDM, as described in the Neoview
User Management and Security Administration Guide.
Specifying the Certificate File Location
The Neoview security infrastructure requires that a certificate be installed on each workstation
that connects to a Neoview platform. A system security policy, under the control of your Security
Manager, determines how the certificate is deployed to workstations:
• In some configurations, the JDBC driver automatically downloads a certificate to the
workstation when it first connects to a Neoview platform. Because the same workstation
can connect to multiple Neoview platforms, the driver downloads a unique certificate for
every Neoview platform to which the workstation connects.
• In configurations that do not permit automatic download, the certificate is deployed to your
workstation in accordance with your own corporate security procedures.
In either case, three new JDBC connection properties specify the location of the certificate file:
• certificateDir specifies the directory where the certificate resides. If you do not specify
this attribute, the home directory applies by default.
• certificateFile specifies the file where a new certificate is deployed. This is the location
to which a new certificate must be deployed if automatic download is prohibited. By default,
the filename is SYSTEM_NAME.cer, where SYSTEM_NAME consists of the first five characters
of the Neoview platform name.
• certificateFileActive specifies the filename of the certificate used for connection.
This is the location to which a certificate is automatically downloaded if automatic download
is permitted by the security policy. By default, the filename is SYSTEM_NAMEActive.cer,
where SYSTEM_NAME consists of the first five characters of the Neoview platform name.
When the workstation application attempts to connect for the first time or connects with a
certificate that has expired, the JDBC driver:
16