PM36497: DBAdmin tool does not connect to DDBS when customer has secure connection using custom certificates.

IBM Rational DOORS version 9.3.0.4

APAR status

• Closed as program error.

Error description

• DBAdmin tool does not connect to DDBS when customer has secure
  connection using custom certificates.
  
  Using customers custom certificates for secure mode, they
  receive the following error when using the dbadmin tool.
  
  C:\Program Files\DOORS 9.3\bin?dbadmin.exe -d
  port@host -u
  03/08/11 16:13:40 (PID 1700): Initialised in secure mode.
  -F- DBADMIN: Unknown operation failed : FATAL EXCEPTION:
  
  DoorsException: GSKit S
  ocInit failed: The secure connection attempt failed.
  
  The received server certificate was invalid.;
  
  ..\general\SecureSocket.cpp(79); v
  9.3.0.1(93268)
  
  ------------------------------------------------------------
  
  C:\Program Files\DOORS 9.3\bin?dbadmin.exe -d
  
  port@host -u
  -keyDB 'C:\path\to\cert' -secure on -certName
  port@host
  03/09/11 10:57:03 (PID 5544): Initialised in secure mode.
  -F- DBADMIN: Unknown operation failed : FATAL EXCEPTION:
  
  DoorsException: GSKit S
  ocInit failed: The secure connection attempt failed.
  
  The received server certificate was invalid.;
  
  ..\general\SecureSocket.cpp(79); v
  9.3.0.1(93268)
  
  Everything works as expected when they use DOORS in non-secure
  mode.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  With a DOORS database running in secure mode, using custom
  certificates - dbadmin fails with "The secure connection
  attempt failed".
  
  The problem was caused because dbadmin failed to use the
  certificate details specified in system variables (the
  registry on Windows).
  

Problem conclusion

• Dbadmin was fixed to use the specified certificate, so that
  the connection with the server can be validated.
  
  The certificate can now also be specified on the
  command-line using these when dbadmin is run:
   -certName
   -keyDB
   -mcs on
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  TLOGIC DOORS

• Fixed component ID

  5724V61DR

Applicable component levels

• R930 PSN

     UP