IV06886: CUSTOM GSKIT SECURITY KEY NOT RESPECTED FOR SILENT INSTALL

IBM Tivoli Monitoring 6.2.2 Fix Pack 8 (6.2.2-TIV-ITM-FP0008)
IBM Tivoli Monitoring 6.2.2 Fix Pack 9 (6.2.2-TIV-ITM-FP0009)

APAR status

• Closed as program error.

Error description

• For silent installations, a parameter file is used to specify
  values that the ITM installer uses. The INSTALL_ENCRYPTION_KEY
  parameter is one of those values. When doing a pristine
  install of ITM 6.22.04.00 or later, the INSTALL_ENCRYPTION_KEY
  parameter is ignored in lieu of the default. This interferes
  with secure communications between components.
  
  
  
  RECREATE INSTRUCTIONS:
  1. Create a silent install parameter file and specify an
     INSTALL_ENCRYPTION_KEY value other than the default.
  
  2. Using a 6.22.04.00 or later install image (either a
     pristine install or one created by tacmd exportbundles),
     attempt to do a silent install with the parameter file
     from step 1.
  
  3. Using the 6.22.02.00 install image, do another silent
     install to a different CANDLEHOME using the same parameter
     file.
  
  4. Compare the CANDLEHOME/keyfiles directories from step 2 and
     step 3. They should be the same. However, because of the
     error, they are different.
  

Local fix

• Install using a 6.22.02.00 image and then upgrade to 6.22.04.00
  or later.
  

Problem summary

• The encryption key specified in a silent install response file
  on UNIX/Linux is ignored during silent installation.
  
  
  The encryption key specified in a silent install response file
  on UNIX/Linux is ignored and the internally defined default
  value is used when performing a silent install. This can be seen
  with the following message in logs/candle_installation.log
  runGSkit: Setting encryption key -
  ThisIsMyTestForTestEncryptionKey using gskSetkey class
  

Problem conclusion

• Use the encryption key specified in the silent installation
  response file when performing a silent install. The specified
  key is only used if the keyfiles directory does not exist, which
  is the current behavior.
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
     | fix pack | 6.2.2-TIV-ITM-FP0007
     | fix pack | 6.2.3-TIV-ITM-FP0001
  

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

  OMEG DIST INSTA

• Fixed component ID

  5608A41CI

Applicable component levels

• R622 PSY

     UP