IBM Security Key Lifecycle Manager Version 2.5.0 -- Distributed Platforms Fix Pack 1 README


Abstract

Readme documentation for IBM® Security® Key Lifecycle Manager for Distributed Platforms, Version 2.5.0 Fix Pack 1 including installation-related instructions, prerequisites and corequisites, and a list of fixes.  All IBM Security Key Lifecycle Manager for Distributed Platforms fix packs are cumulative.  This fix pack contains the content of all prior fix packs published to date. 

Fix Pack Publication date : 20 February 2014

Last modified date : 17 February 2014


Contents

Platform support
Download locations
Prerequisites and corequisites
Known issues
Known limitations
Updates to CLI commands

Installation information
Installing the IBM Security Key Lifecycle Manager fix pack
Prior to fix pack installation
Performing the necessary tasks after fix pack installation
List of Fixes and Features
Copyright and trademark information
Document change history


Platform support

IBM Security Key Lifecycle Manager Version 2.5.0 platforms supported

AIX Version 6.1 64-bit

AIX Version 7.1 64-bit

Red Hat Enterprise Linux Version 5 update 4 on x86 64-bit in 32-bit mode

Red Hat Enterprise Linux Version 6 update 3 on x86 64-bit in 32-bit mode

Red Hat Enterprise Linux Version 5 update 4 (System z) on x86 64–bit mode

Red Hat Enterprise Linux Version 6 update 3 (System z) on x86 64–bit mode

SuSE Linux Enterprise Server Version 10 on x86 64–bit

SuSE Linux Enterprise Server Version 11 on x86 64–bit mode

SuSE Linux Enterprise Server Version 11 (System z) on x86 64–bit mode

Sun Server Solaris 10 (SPARC 64–bit in 32-bit mode)

Windows Server 2008 R2 (64-bit in 32-bit mode for all Intel and AMD processors) Standard Edition

Windows Server 2008 R2 (64-bit in 32-bit mode for all Intel and AMD processors) Enterprise Edition

Windows Server 2012 (64-bit in 32-bit mode for all Intel and AMD processors) Standard Edition

IBM Security Key Lifecycle Manager Version 2.5.0 has been certified to run on the following virtual environments. The platform running within the virtual machine must be supported by the virtual platform server and Security Key Lifecycle Manager Version 2.5.0(see "platforms supported" table).

IBM Security Key Lifecycle Manager Version 2.5.0 virtual platforms supported

VMWare ESX/ESXi Server Versions 4.0, 5.0, 5.1 and 5.5

Red Hat Enterprise Virtualization/Kernel-Based Virtual Machine (RHEV/KVM) Version 5.4



Download location

Download IBM Security Key Lifecycle Manager Version 2.5.0 Fix Pack from IBM Fix Central:

  1. Go to IBM Fix Central Home Page, http://www.ibm.com/support/fixcentral/

  2. For the Product Group, select "Security Systems"

  3. For the Product, select "IBM Security Key Lifecycle Manager"

  4. For Installed Version, select your system's appropriate version level, ie. 2.5.0.0

  5. For Platform, select the appropriate platform. Choose "Continue"

  6. At the Identify Fixes page, select the "Browse for Fixes" radio button (default) and choose "Continue".

  7. At the Select Fixes page, choose "Fix Pack 2.5.0-ISS-SKLM-FP0001". Choose "Continue".

  8. You may be prompted to "Sign In".  If you do not have an ID, click on the "register now" link and follow the register steps as appropriate.

  9. At the Download Options page, choose a download method. (default is "Download using Download Director")

  10. Select the associated files and README for Fix Pack 2.5.0-ISS-SKLM-FP0001 and select "Download now".

Platforms updated by this fix pack

Product/Component Name

Platform

File Name

IBM Security Key Lifecycle Manager version 2.5.0 Fix Pack - 2.5.0-ISS-SKLM-FP0001

AIX

2.5.0-ISS-SKLM-FP0001-AIX.tar.gz

IBM Security Key Lifecycle Manager version 2.5.0 Fix Pack - 2.5.0-ISS-SKLM-FP0001

Linux

2.5.0-ISS-SKLM-FP0001-Linux.tar.gz

IBM Security Key Lifecycle Manager version 2.5.0 Fix Pack - 2.5.0-ISS-SKLM-FP0001

Solaris

2.5.0-ISS-SKLM-FP0001-Solaris.tar.gz

IBM Security Key Lifecycle Manager version 2.5.0 Fix Pack - 2.5.0-ISS-SKLM-FP0001

Windows

2.5.0-ISS-SKLM-FP0001-Windows.zip



Prerequisites and corequisites

IBM Security Key Lifecycle Manager Version 2.5.0 GA must be installed.

Known issues

Known limitations

Updates to CLI commands

Installing the IBM Security Key Lifecycle Manager Fix Pack

Prior to fix pack installation

  1. Ensure that IBM Security Key Lifecycle Manager is not being utilized before installing the fix pack. If your facility has a "service maintenance outage" process, consider installing this fix pack during an arranged service outage.

  2. A backup of your IBM Security Key Lifecycle Manager server should be performed prior to installing this fix pack. Follow the steps Backing up critical files in the Administering section of the IBM Security Key Lifecycle Manager Product Manuals.

Backup Websphere Application Server files on Windows platforms

Instruction

Command

Open a command prompt.

Click the Start button, Click Run, type cmd and Click the OK button.

Stop the Websphere Application Server

WAS_HOME\bin\stopServer.bat server1 -username [WAS_ADMIN] -password [WAS_PASSWORD]

Make a temporary directory

mkdir [WAS_BACKUP_DIRECTORY]
example: mkdir c:\wasbackup

Change to the temporary directory

cd c:\wasbackup

Copy the files from the directory where Websphere Application Server files is installed

xcopy /y /e /d %WAS_HOME% c:\wasbackup

Start the Websphere Application Server

%WAS_HOME%\bin\startServer.bat server1

where:
WAS_HOME is the directory where Websphere Application Server is installed
(default:C:\Program Files (x86)\IBM\WebSphere\AppServer).



Backup Websphere Application Server files on AIX, Solaris, and Linux platforms

Instruction

Command

Open a ksh or bash shell.

if your default shell is not ksh or bash, run "exec ksh" or "exec bash".

Stop the Websphere Application Server

$WAS_HOME/bin/stopServer.sh server1 -username [WAS_ADMIN] -password [WAS_PASSWORD]

Make a temporary directory

mkdir [WAS_BACKUP_DIRECTORY]
example: mkdir /tmp/wasbackup

Change to the temporary directory

cd /tmp/wasbackup

Archive the files from the directory where Websphere Application Server is installed

tar -cvf wasbackup.tar $WAS_HOME/*

Start the Websphere Application Server

$WAS_HOME/bin/startServer.sh server1
where:
WAS_HOME is the directory where Websphere Application Server is installed (default: /opt/IBM/WebSphere/AppServer).



Before Fix Pack installation

Instruction

Steps

Make a repository directory

Open a command prompt.Make a repository directory.

  • Windows

    Default repository directory is C:\sklminstall_windowsfp
    mdir C:\sklminstall_windowsfp

  • Unix

    Default repository directory is /sklminstall_linuxfp
    mkdir /sklminstall_linuxfp

Change directory to the directory created.

  • Windows

    cd C:\sklminstall_windowsfp

  • Unix

    cd /sklminstall_linuxfp

Download the SKLM fix pack into the repository directory.

Link to fix pack download table

Extract the downloaded file

  • Windows

    Extract downloaded file 2.5.0-ISS-SKLM-FP0001-Windows.zip

  • Unix

    Extract downloaded file 2.5.0-ISS-SKLM-FP0001-<platform>.tar.gz

Steps for installing Fix Pack for IBM Security Key Lifecycle Manager version 2.5.0 on Windows and Unix platforms in GUI mode

Instruction

Steps

Start Installation Manager in GUI mode

  • Windows

    Open a command window, and change to the Installation_Manager_Home/eclipse directory

    where Installation_Manager_Home refers to the installation root directory for Installation Manager

    (Default path :C:\Program Files (x86)\IBM\Installation Manager\eclipse)

    double-click IBMIM.

  • Unix

    Open a command window, and change to the Installation_Manager_Home/eclipse directory

    where Installation_Manager_Home refers to the installation root directory for Installation Manager

    (Default path :/opt/IBM/InstallationManager/eclipse)

    and run ./IBMIM.

Set up the fix pack repository preference

  1. Select File > Preferences.

  2. In the Preferences > Repositories panel, click Add Repository.

  3. Click Browse and browse to the location of fixpack

  4. Uncheck Search service repository during installation and upgrades option.
    SKLM does not support internet based repositories.

  5. Click OK

  6. Click OK to close the Preferences >Repositories panel.

  7. On the Installation Manager home page, click Update.
    The Installation Manager > Update Packages window opens.

Select the SKLM software package group

  1. Select the base offering, SKLM software package group(IBM Security Key Lifecycle Manager v2.5)

  2. Uncheck Search service repository during installation and upgrades option.
    SKLM does not support internet based repositories.

  3. click Next.

  4. In the Update Packages updates panel
    Select each check box associated with each installed component that you want to update, and click Next.

    • IBM Security Key Lifecycle Manager v2.5

    • IBM Security Key Lifecycle Manager v2.5.0.0(installed)

    • Version 2.5.0.1

Provide credentials for
WAS admin user
(default:wasadmin)
and SKLM admin user
(default:SKLMAdmin)

In the Update Packages Configuration for IBM Security Key Lifecycle Manager v2.5.0.1

  • Enter Username and Password for Application Server Administrator

  • Enter Username and Password for IBM Security Key Lifecycle Manager Application Administrator

  • Click on Validate Credentials button,
    Validation may take few minutes, wait till Next button gets enabled.

  • Click on Next button

Click on Update button

In the Update Packages > Summary panel,
review the software packages that you want to install and click Update. After Installation Manager successfully updates the fix pack for the services that you select, it displays a message.

Steps for installing a fix pack for IBM Security Key Lifecycle Manager version 2.5.0 on Windows and Unix platforms in silent mode

Instruction

Steps

Installation Manager utility to encrypt the passwords for users as required

Open a command window, and change to the Installation_Manager_Home/eclipse/tools directory,
where Installation_Manager_Home refers to the installation root directory for Installation Manager

  • Windows

  • Run the following command to generate an encrypted password:
    imcl.exe encryptString password_to_encrypt

  • Unix

  • Run the following command to generate an encrypted password:
    ./imcl.exe encryptString password_to_encrypt

Make a backup of response file

For example: SKLM_Silent_Update_<platform>_Resp_original.xml

Edit the response file.

  • Windows

  • Edit the silent response file "SKLM_Silent_Update_<platform>_Resp.xml"

    1. Edit the repository location to point to current location of installables
      (Sample:<repository location='C:\sklminstall_windowsfp'/>)

    2. Edit WASAdmin username and password(Password need to be encrypted)
      (Sample:
      <data key='user.WAS_ADMIN_ID,com.ibm.sklm.win32>value='wasadmin'/>
      <data key='user.WAS_ADMIN_PASSWORD,com.ibm.sklm.win32>value='zN39fpCc9SqIryGJM7+02A=='/>)

    3. Edit SKLMAdmin username and password(Password need to be encrypted)
      (Sample:
      <data key='user.SKLM_ADMIN_ID,com.ibm.sklm.win32>value='sklmadmin'/>
      <data key='user.SKLM_ADMIN_PASSWORD,com.ibm.sklm.win32>value='94FrH/Ll220hVIYc9TflNQ=='/>)

  • Unix

  • Edit the silent response file "SKLM_Silent_Update_<platform>_Resp.xml"

    1. Edit the repository location to point to current location of installables
      (Sample for Linux:<repository location='/sklminstall_linuxfp'/>)

    2. Edit WASAdmin username and password(Password need to be encrypted)
      (Sample:
      <data key='user.WAS_ADMIN_ID,com.ibm.sklm.Linux>value='wasadmin'/>
      <data key='user.WAS_ADMIN_PASSWORD,com.ibm.sklm.Linux>value='zN39fpCc9SqIryGJM7+02A=='/>)

    3. Edit SKLMAdmin username and password(Password need to be encrypted)
      (Sample:
      <data key='user.SKLM_ADMIN_ID,com.ibm.sklm.Linux>value='sklmadmin'/>
      <data key='user.SKLM_ADMIN_PASSWORD,com.ibm.sklm.Linux>value='94FrH/Ll220hVIYc9TflNQ=='/>)

Install the fix pack

  • Windows

    1. Open a command window, and change to the Installation_Manager_Home/eclipse/tools directory,
      where Installation_Manager_Home refers to the installation root directory for Installation Manager

    2. Run the following command for your platform to silently install SKLM Fix Pack 1
      imcl -input <Response_File> -silent

      Sample:
      C:\Program Files (x86)\IBM\Installation Manager\eclipse\tools\imcl -input <Response_File> -silent

      where:
      -? Returns this command usage
      Response_File should be the complete path to SKLM_Silent_Update_Win32_Resp.xml

  • Unix

    1. Open a command window, and change to the Installation_Manager_Home/eclipse/tools directory,
      where Installation_Manager_Home refers to the installation root directory for Installation Manager

    2. Run the following command for your platform to silently install SKLM Fix Pack 1
      ./imcl -input <Response_File> -silent


      Sample:
      /opt/IBM/InstallationManager/eclipse/tools/imcl -input <Response_File> -silent

      where:
      -? Returns this command usage
      Response_File should be the complete path to SKLM_Silent_Update_<platform>_Resp.xml

Check logs for fix pack installation success

View the log file output produced for fix pack installation success
Logs are located at <Installation_Manager_Home>/logs/native



  Performing the necessary tasks after fix pack installation.

  1. Verify Installation - Run the wsadmin AdminTask.tklmVersionInfo() command

    Open a shell (ksh or bash)

    Type: cd <WAS_HOME>/bin/

    Type: ./wsadmin.sh -lang jython -username <sklmadminUserID> -password <sklmadminPassword>

    example: ./wsadmin.sh -lang jython -username sklmadmin -password sklmpassword

    At the wsadmin> prompt type: print AdminTask.tklmVersionInfo()

    Windows users:

    Open a command prompt.

    type cd <WAS_HOME>\bin

    type: wsadmin -lang jython -username <sklmadminUserID>-password <sklmadminPassword>

    example: wsadmin.bat -lang jython -username sklmadmin -password sklmpassword

    At the wsadmin> prompt type: print AdminTask.tklmVersionInfo()

    Check the output of the tklmVersionInfo command:

    IBM Security Key Lifecycle Manager Version = 2.5.0.1

    IBM Security Key Lifecycle Manager Build Level = 201402040817

  2. A backup of your IBM Security Key Lifecycle Manager server should be performed after installing this fix pack. Follow the steps Backing up critical files in the Administering section of the IBM Security Key Lifecycle Manager Product Manuals.



Steps for uninstalling fix pack for IBM Security Key Lifecycle Manager version 2.5.0 on Windows and Unix platforms in GUI mode

Instruction

Steps

Start Installation Manager in GUI mode

  • Windows

    Open a command window, and change to the Installation_Manager_Home/eclipse directory

    where Installation_Manager_Home refers to the installation root directory for Installation Manager

    (Default path :C:\Program Files (x86)\IBM\Installation Manager\eclipse)

    double-click IBMIM.

  • Unix

    Open a command window, and change to the Installation_Manager_Home/eclipse directory

    where Installation_Manager_Home refers to the installation root directory for Installation Manager

    (Default path :/opt/IBM/InstallationManager/eclipse)

    and run ./IBMIM.

Select Rollback

On the Installation Manager home page, click Roll Back.
The Installation Manager > Roll Back Packages panel opens.

Select the SKLM software package group

  • Select the base offering,SKLM software package group(IBM Security Key Lifecycle Manager v2.5)

  • click Next.

Provide credentials for WAS User ID

In the Roll back Packages Websphere Administrator window

Enter Username and Password for Application Server Administrator

Click on Next button

Click on Roll Back button

Click on Roll Back button


In the Roll Back Packages > Summary panel,
review the software packages that you want to roll back, and click Roll Back.

Steps for uninstalling a fix pack for IBM Security Key Lifecycle Manager version 2.5.0 on Windows and Unix platforms in silent mode

Instruction

Steps

Installation Manager utility to encrypt the passwords for users as required

Open a command window, and change to the Installation_Manager_Home/eclipse/tools directory,
where Installation_Manager_Home refers to the installation root directory for Installation Manager

  • Windows

  • Run the following command to generate an encrypted password:
    imcl.exe encryptString password_to_encrypt

  • Unix

  • Run the following command to generate an encrypted password:
    ./imcl encryptString password_to_encrypt

Make a backup of response file

For example: SKLM_Silent_Rollback_<platform>_Resp_original.xml

Edit the response file

  • Windows

  • Edit the silent response file "SKLM_Silent_Rollback__<platform>_Resp.xml"

    1. Edit WASAdmin username and password(Password need to be encrypted)
      (Sample:
      <data key='user.WAS_ADMIN_ID,com.ibm.sklm.win32>value='wasadmin'/>
      <data key='user.WAS_ADMIN_PASSWORD,com.ibm.sklm.win32>value='zN39fpCc9SqIryGJM7+02A=='/>)

  • Unix

  • Edit the silent response file "SKLM_Silent_Update_Linux_Resp.xml"

    1. Edit WASAdmin username and password(Password need to be encrypted)
      (Sample for Linux:
      <data key='user.WAS_ADMIN_ID,com.ibm.sklm.Linux>value='wasadmin'/>
      <data key='user.WAS_ADMIN_PASSWORD,com.ibm.sklm.Linux>value='zN39fpCc9SqIryGJM7+02A=='/>)

Uninstall the fix pack

  • Windows

    1. Open a command window, and change to the Installation_Manager_Home/eclipse/tools directory,
      where Installation_Manager_Home refers to the installation root directory for Installation Manager

    2. Run the following command for your platform to silently install SKLM Fix Pack 1
      imcl.exe -input <Response_File>

      Sample:
      C:\Program Files (x86)\IBM\Installation Manager\eclipse\tools\imcl.exe -input <Response_File>

      where:
      -? Returns this command usage
      Response_File should be the complete path to SKLM_Silent_Rollback_Win32_Resp.xml

  • Unix

    1. Open a command window, and change to the Installation_Manager_Home/eclipse/tools directory,
      where Installation_Manager_Home refers to the installation root directory for Installation Manager

    2. Run the following command for your platform to silently install SKLM Fix Pack 1
      ./imcl -input <Response_File>

      Sample:
      /opt/IBM/InstallationManager/eclipse/tools/imcl -input <Response_File>

      where:
      -? Returns this command usage
      Response_File should be the complete path to SKLM_Silent_Rollback<platform>_Resp.xml

Check logs for fix pack installation success
Logs are located at <Installation_Manager_Home>/logs/native

View the log file output produced for fix pack installation success


List of Fixes and Features

New Features Provided by Version 2.5.0.1

Added KMIP 1.2 Support

Added support for JSON and XML encodings


APAR fixes included in Fix Pack 1

APAR No.

Sev.

Abstract

IV55432

3

ON AIX PLATFORM RESTORE OPERATION FAILS DUE TO FILE PERMISSION ISSUE

IV55437

3

CERTIFICATE ASSOCIATED WITH JAG DEVICE CANNOT BE REMOVED

IV55446

3

ADDING A DEVICEGROUP FROM REST FOR DEVICEFAMILY GPFS FAILS

IV55447

3

WHEN WE LIST DEVICEGROUPS FROM REST/CLI IT DOES NOT LIST GPFS

IV55460

3

USING REST WHEN WE LIST DEVICEGROUPS FOR ANY TYPE IT DOES NOT LIST 2000 RECORDS

IV55472

3

REST SERVICE ATTRIBUTE NAME "ADDNEWCERTSTOPENDING" IS INCORRECTLY DISPLAYED AS "DEVICE.ADDNEWCERTSTOPENDING"

IV53802

3

THE SKLM V2.5 "SILENT INSTALL" METHOD REQUIRES ENCRYPTED PASSWORDS IN THE SKLM_RESPONSE FILE.

IV54751

1

SKLMADMIN GUI LOGIN GETS WHITE SCREEN USING IE9

IV54976

1

SECURITYKEYLIFECYCLEMANAGER_WAS.INIT FILE CONTAINS PASSWORD FOR WAS ADMIN'S USERID IN CLEAR TEXT ON LINUX SYSTEM

IV53766

2

INSTALL OF 2.5 FAILS WITH ERROR COMPLAINING ABOUT NOT ENOUGH SPACE IN FILE SYSTEM EVEN AFTER PREREQ CHECKING PASSED

IV54303

2

THE 2.5 DOCUMENTATION INCORRECTLY REFERENCES THE REPLICATION PROPERTIES FILE AS REPLICATIONSKLMGRCONFIG.PROPERTIES

IV55418

2

ECDSA ALGORITHM SHOULD NOT BE ALLOWED FOR 3592 OR DS8000 DEVICE GROUPS FROM REST INTERFACE


Copyright and trademark information

http://www.ibm.com/legal/copytrade.shtml

Notices

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Microsoft, Windows, and Windows Server are trademarks of Microsoft Corporation in the United States, other countries, or both.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

Other company, product, or service names may be trademarks or service marks of others.

THIRD-PARTY LICENSE TERMS AND CONDITIONS, NOTICES AND INFORMATION

The license agreement for this product refers you to this file for details concerning terms and conditions applicable to third party software code included in this product, and for certain notices and other information IBM must provide to you under its license to certain software code. The relevant terms and conditions, notices and other information are provided or referenced below. Please note that any non-English version of the licenses below is unofficial and is provided to you for your convenience only. The English version of the licenses below, provided as part of the English version of this file, is the official version.

Notwithstanding the terms and conditions of any other agreement you may have with IBM or any of its related or affiliated entities (collectively "IBM"), the third party software code identified below are "Excluded Components" and are subject to the following terms and conditions:

Document change history

Change Date

Reason

Modified by

11/02/14

Create initial draft for 2.5.0-ISS-SKLM-FP0001

PSR

17/02/14

Upadted with review comment

PSR



End of Document