To enable server security, you must configure the Rational
DOORS database server to use secure connections.
Before you begin
Make sure that the server can start in secure mode and accept
connections from clients. Here is a check list to verify secure mode
configuration (this is for guidance only):
- Make sure that the certificate key database is up to date. Make
sure there are no expired certificates. If you are using a different
keystore database, the -keydb parameter can be used to specify it
when starting the Rational DOORS database server and clients.
Note: The
sample certificate store supplied with Rational DOORS 9.4 is now expired.
- Make sure that the server starts with the correct server host
name. If you are running from the command line, set the -serverhostname
parameter, otherwise it is defined by the SERVERHOSTNAME environment
variable (or Registry entry). This host name must be the same host
that runs the Rational DOORS database server.
- Make sure that the server is restarted with secure mode enabled.
From command line, it is enabled by the -secure ON option. In Windows,
if you do not specify it in the command line, it is defined by the
secure registry option. Please note that this registry value is set
to OFF by default. If you do not use the command-line parameters,
you must set this option to ON. This key can be found in this path:
\HKEY_LOCAL_MACHINE\SOFTWARE\Telelogic\DOORS_Server\9.4\Config
If
you are running on 64-bit Windows, the key is in this path:
\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Telelogic\DOORS_Server
\9.4\Config
- Make sure that the clients and interoperation server start with
the correct host name. It must be the same as the Rational DOORS database
server host name (see above). For example, if the Rational DOORS database
server host name is IBMEDSERV, then the client must use IBMEDSERV
in the command line (-data 36700@IBMEDSERV) and in the client's environment
this host name must point to the same host that the Rational DOORS
database server is running. You can modify the operating system’s
hosts file to point to the host for IBMEDSERV. To summarize, the important
points are:
- The Rational DOORS database server must start with the correct
server host name (for example, IBMEDSERV), and in the server environment
this host name has to resolve to the server itself.
- The Rational DOORS client must connect to the server by the same
server host name (for example, specifying the -data 36700@IBMEDSERV
parameter in the shortcut) and again this host name in the client
environment has to resolve to the server’s IP address.
Starting the client
After you start the Rational DOORS database server, connect
the Rational DOORS clients to the Rational DOORS database server and
run as usual.
If Rational DOORS is configured to use the Rational
Directory Server, existing users need to be signed. To do this, start
a Rational DOORS client, log in as the Administrator, and run the
DXL perm signTdsUsers(). You need to run the DXL once
each time you change the Rational DOORS database server.
Setting up a password for dbadmin
After you start the Rational DOORS client, you must set
up a password for dbadmin. Set it using the -p switch, and when you
run dbadmin, you need to enter the password with the -P switch and
the -l switch.
For example, set the password using a command in
this format:
dbadmin.exe -d 36700@IBMEDSERV -keyDB "C:\path\to\key\db.kdb"
-p NewPassword
After you assign the dbadmin password,
specify each request using a command in this format:
dbadmin.exe
-d 36700@IBMEDSERV -keyDB "C:\path\to\key\db.kdb" -P NewPassword -l
Setting up access to modules
You must make sure that sensitive data is protected by setting
up the correct access rights to modules.
When server security is
enabled, clients enforce usual access rights to information in the
database. A user’s access to the database is the same whether the
system is using server security or the classic Rational DOORS security
model.
However, if the client is compromised, for example if
a user gains unauthorized access to the database, as long as the user
has Read access to a module they will have Full access
to the contents of the module.
To guard against this possibility,
make sure that modules that contain sensitive data are protected.
Only allow access to the module if a user needs it. If a user does
not need to access a module, do not set their access to Read.
Set their access to None. That way, even if a user gains unauthorized
access to the database, they will not be able to access the module.
Changing the authentication method
You can change the server security authentication method
using dbadmin. When you change the method, you do not need to restart
the Rational DOORS database server.
For example, to set the method
to user keys, enter:
dbadmin.exe -d 36700@IBMEDSERV
-keyDB C:\path\to\certificate\db\client_authentication.kdb -certName
DBM1 -P samplePassword -sssAuthenticationMode UserKeys
These
are the valid options for the -sssAuthenticationMode switch:
UserKeys
UsernamePassword
UsernamePasswordAndUserKeys