IBM Support

IBM Guardium Key Lifecycle Manager Version 5.1.0 - Fix Pack 2 README

Fix Readme


Abstract

Readme file for IBM Guardium Key Lifecycle Manager(GKLM) for distributed and containerized platforms, Version 5.1.0 Fix Pack 2 (5.1.0.2) including installation instructions, prerequisites and corequisites, and a list of fixes.

Content

 
Features and fixes
 
 
Internal fixes
 

This release includes the fixes for the following issues.

  • Guardium Key Lifecycle Manager deployment on OCP with 2 or more replica is not working.
  • HSM test connection is failing when FIPS is enabled.
  • Extended 3592 endpoints wrapping keys are behaving abnormally.
 
Security fixes
 

This release includes following security fixes:

CVE-2026-5450, CVE-2026-31790, CVE-2026-42198, CVE-2026-34477, CVE-2026-34478, CVE-2025-13151, CVE-2024-34459, CVE-2026-42198, CVE-2026-34479, CVE-2026-34480, CVE-2026-34477

 

For more information, see Known issues in IBM Guardium Key Lifecycle Manager, Version 5.1.0 .

 

APAR fixes included in Version 5.1.0.2.

APAR No.

Sev.

Abstract

DT467878

3

Openjceplus provider getting removed from java.security after fixpack.

DT469638

3

Unable to delete trusted certificate if UKO is selected.

 

APAR fixes included in Version 5.1.0.1.

APAR No.

Sev.

Abstract

DT461082

3

Replication is failing in FIPS enabled GKLM server.

DT461371

3

Master key refresh does not work in GKLM 5.1 when Entrust HSM is configured and master key is on HSM.
 
 
Upgraded middleware
 
  • IBM Semeru Runtime Certified Edition 21.0.11.0
  • WebSphere Application Server Liberty 26.0.0.6
 
Download instructions
 
  1. Go to IBM Fix Central home page: http://www.ibm.com/support/fixcentral/
  2. In the Product selector field, type IBM Security Key Lifecycle Manager, and select the product name when it appears.
  3. From the Installed Version list, select IBM Guardium Key Lifecycle Manager 5.1.0.0 version.
  4. From the Platform list, select the appropriate platform, and click Continue.
  5. On the Identify Fixes page, ensure that the Browse for Fixes is selected, and click Continue.
  6. On the Select Fixes page, select fix pack 5.1.0-ISS-GKLM-FP0002, and click Continue.
    You might be prompted to Sign In.  If you do not have an ID, click the Register now link and follow the registration steps.
  7. On the Download options page, select a download method (default is Download using Download Director).
  8. Select the associated files and README for fix pack: 5.1.0-ISS-GKLM-FP0002 and click Download now.

Back to top

 
 

Fix pack files checksum

Fix pack files checksum for IBM Guardium Key Lifecycle Manager traditional
 

Product/Component name

Platform

File name

Command

Checksum

IBM Guardium Key Lifecycle Manager 5.1.0.2AIX5.1.0-ISS-GKLM-FP0002-AIX.tar.gz

md5sum FileName.tar.gz

 

For example (UNIX/Linux): md5sum 5.1.0-ISS-GKLM-FP0002-AIX.tar.gz

Sample output
0f09b63ecfa13c51da83e23bfbb9e989 5.1.0-ISS-GKLM-FP0002-AIX.tar.gz

0f09b63ecfa13c51da83e23bfbb9e989

 

IBM Guardium Key Lifecycle Manager 5.1.0.2Linux5.1.0-ISS-GKLM-FP0002-Linux.tar.gze3aadc8ab46ec6c6671b0427fef5c4bb
IBM Guardium Key Lifecycle Manager 5.1.0.2zLinux (IBM Z)5.1.0-ISS-GKLM-FP0002-zLinux.tar.gzffadcaf2a268822e587efb407ef7f7e4
IBM Guardium Key Lifecycle Manager 5.1.0.2Linux PPC5.1.0-ISS-GKLM-FP0002-LinuxPPC.tar.gza942b9ba787fa274a5e894d67a332684
IBM Guardium Key Lifecycle Manager 5.1.0.2Windows5.1.0-ISS-GKLM-FP0002-Windows.zip

certutil -hashfile FileName.zip md5

 

For example (Windows): certutil -hashfile 5.1.0-ISS-GKLM-FP0002-Windows.zip md5

Sample output
MD5 hash of file 5.1.0-ISS-GKLM-FP0002-Windows.zip: cb0036ec4c115aeb845b023d38845828
CertUtil: -hashfile command completed successfully.

cb0036ec4c115aeb845b023d38845828


 

Fix pack files checksum for IBM Guardium Key Lifecycle Manager container
 

Product/Component name

Platform

File name

Command

Checksum

IBM Guardium Key Lifecycle Manager 5.1.0.2Linux PPCgklm5102-ppc64le.tar

md5sum FileName.tar.gz

 

For example (UNIX/Linux): md5sum gklm5102-ppc64le.tar

Sample output
8aaccacb2110a8f02c305c7e2118534c gklm5102-ppc64le.tar

8aaccacb2110a8f02c305c7e2118534c
IBM Guardium Key Lifecycle Manager 5.1.0.2zLinux (IBM Z)gklm5102-s390x.tar7fdef9e999870da5f1b61f21113d2d6c
IBM Guardium Key Lifecycle Manager 5.1.0.2x86_64gklm5102-x86_64.tar088de807df4b44eb7d0f442d3ae69f88
 
 
 

Back to top

 
Known limitations and issues
 

Known limitations

  • Rollback of installed fix pack is not supported.
  • Key management operations over IPP will not work with FIPS on. To use key management over IPP with GKLM, FIPS has to be turned off. This limitations impacts following endpoints(device-groups) LTO, 3592, and DS8000. Support for FIPS 140-3 continues to be available for LTO and DS8000 when key management operations are performed using KMIP protocol.
  • Symmetric key export will not work with FIPS on. To export symmetric key on GKLM, FIPS has to be turned off.

Known issues

    1. (Applicable for Ubuntu) Db2 crashes on ubuntu when fp is applied.

      Workaround:
      • Manually start db2 for FP installation.

    2. (Applicable for Linux) Non root fixpack upgrade in GUI mode on Linux prompts for non root user password multiple time (5-6 times).

      Workaround:
      1. Enter password when prompted to reload respective services.

    3. (Applicable for Ubuntu) The installation of GKLM might fail with a invalid Db2 password error in both GUI and silent fix pack installation modes.

      Workaround:
      1. Log in as the root user and open a terminal window.

      2. Run the following command:

        ln -s {db2_inst_home}/gklm51properties/ $HOME/gklm51properties
        For example,
        ln -s /home/klmdb51/gklm51properties/ /root/gklm51properties


     

Back to top

 
 
Installation instructions
 
Prerequisites
 
Applicable to all operating systems and platforms
 
  • Ensure that IBM Guardium Key Lifecycle Manager, Version 5.1.0 GA (5.1.0), 5.1.0 IF(01), or 5.1.0 FP1 (5.1.0.1) is already installed.
  • Ensure that IBM Guardium Key Lifecycle Manager is not in use (that is, storage devices should not communicate with GKLM).
  • Back up the IBM Guardium Key Lifecycle Manager server. For instructions, see Configuring backup and restore.
  • Ensure that /tmp directory does not contain klmPrev.properties. If it is present, rename or remove this file before you start applying the fix pack. Also, ensure that the /tmp directory has all the permissions and does not have noexec set.
  • Ensure that umask is set to 0022.
  • Back up the WebSphere Liberty files.
    1. Open a command line.
    2. Stop WebSphere Liberty. 

      • Windows 

        WAS_HOME\bin\stopServer.bat

      • Linux 

        WAS_HOME/bin/stopServer.sh
    3. Make a temporary directory. 

      • Windows 

        mkdir WAS_BACKUP_DIRECTORY
        For example,
        mkdir C:\wasbackup

      • Linux 

        mkdir WAS_BACKUP_DIRECTORY
        For example, 
        mkdir /tmp/wasbackup
    4. Change directory to the temporary directory. 

      • Windows 

        cd C:\wasbackup

      • Linux 

        cd /tmp/wasbackup
    5. Copy or archive the files from the directory where WebSphere Liberty is installed. 

      • Windows 

        xcopy /y /e /d WAS_HOME C:\wasbackup

      • Linux 

        tar -cvf wasbackup.tar WAS_HOME/*
    6. Start WebSphere Liberty. 

      • Windows 

        WAS_HOME\bin\startServer.bat

      • Linux 

        WAS_HOME/bin/startServer.sh
 
Applicable to Linux/Ubuntu/AIX
 

  • On Ubuntu, run the following command as root user: 

    ln -s DB_INSTANCE_HOME/gklm51properties/ $HOME/gklm51properties

    Where, DB_INSTANCE_HOME is the directory that contains the Db2 database instance for IBM Guardium Key Lifecycle Manager.

    For example,
    ln -s /home/klmdb51/gklm51properties/ $HOME/gklm51properties

  • On Linux for System z server, ensure that gtk 2 libraries are installed. Also, add the following parameter in the IM_INSTALL_DIR/eclipse/IBMIM.ini file. Add the following properties just before "--launcher.appendVmargs" in IBMIM.ini file. 

    --launcher.GTK_version
2
 
 
 
Installation steps
 
Depending on your setup, see the relevant section:
 
 

Installing the fix pack on GKLM traditional

You can use one of the following modes to install a fix pack:
 
 

Graphical mode

 
Complete the following instructions:
 
  1. Download the fix pack installer files. For instructions, see Download instructions.
  2. Extract the installer files to a folder of your choice.
  3. Open a command line.
  4. Change the directory to the directory where you extracted the fix pack installer files.
  5. Run the following command to launch the Installation Manager.

    • Windows

      updateSKLM.bat IM_INSTALL_LOCATION WAS_HOME
      For example:
      updateSKLM.bat "C:\Program Files\IBM\Installation Manager" "C:\Program Files\IBM\WebSphere\Liberty"
      Note: If Installation Manager crashes, follow steps mentioned in Known limitations and issues.

    • Linux

      chmod +x ./updateSKLM.sh
./updateSKLM.sh IM_INSTALL_DIR WAS_HOME
      For example:
      ./updateSKLM.sh /opt/IBM/InstallationManager /opt/IBM/WebSphere/Liberty
  6. In the Update Packages pane, select the Update all packages (mandatory) with recommended updates and recommended fixes checkbox. Click Next.
  7. Read the license agreement carefully. If okay, accept the license agreement. Click Next.
  8. In the WebSphere Liberty configuration window, do not select the checkbox to connect to the online IBM WebSphere Liberty Repository. Click Next.
  9. Installation Manager fetches the assets and lists all the fixes and features to be installed. Click Next.
  10. In the Update Packages Configuration for IBM Guardium Key Lifecycle Manager v5.1.0.2 pane:
    • Enter Username and Password for IBM Guardium Key Lifecycle Manager Application Administrator.
    • Enter Username and Password for IBM Db2 user.
  11. Click Validate Credentials. Validation might take few minutes. Wait until the Next button is enabled. Click Next.
  12. In the Update Packages > Summary pane, 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, a message is displayed.
 

Silent mode

 
Complete the following instructions:
 
  1. Download the fix pack installer files. For instructions, see Download instructions.
  2. Go to the directory where you extracted the fix pack installation files.
  3. Open the /sklm directory, which is within the directory where the fix pack is extracted. It contains the response file (SKLM_Silent_Update_platform_Resp.xml) that we need to edit for the installation.

  4. Locate the response file and create a backup of the response file. 

    For example: SKLM_Silent_Update_platform_Resp_original.xml. 
  5. Open the response file and edit the relevant elements of the response file SKLM_Silent_Update_platform_Resp.xml.
  6. Edit the repository location to point to the current location of the installer. 

    • Windows 

      <repository location='C:\sklminstall_windowsfp\wasfp\repository.config'/>
<repository location='C:\sklminstall_windowsfp\sklmwasfp\repository.config'/>

    • Linux 

      <repository location='/sklminstall_linuxfp/wasfp/repository.config'/>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   <repository location='/sklminstall_linuxfp/sklm/repository.config'/>
  7. Edit GKLM Administrator username and password. The password must be encrypted. To encrypt the password, see Encrypting a password. 

    • Windows 

      <data key='user.SKLM_ADMIN_USER,com.ibm.gklm51.win' value='SKLMAdmin'/>
<data key='user.SKLM_ADMIN_PASSWORD,com.ibm.gklm51.win' value='9YTRJMRIydDSdfhaHPs1ag=='/>

    • Linux 

      <data key='user.SKLM_ADMIN_USER,com.ibm.gklm51.linux' value='SKLMAdmin'/>
<data key='user.SKLM_ADMIN_PASSWORD,com.ibm.gklm51.linux' value='9YTRJMRIydDSdfhaHPs1ag=='/>
  8. Edit Db2 username and password. The password must be encrypted. To encrypt the password, see Encrypting a password.
    • Windows
      <data key='user.DB_ADMIN_USER,com.ibm.gklm51.win' value='klmdb51'/>
<data key='user.DB_ADMIN_PASSWORD,com.ibm.gklm51.win' value='QTh/0AiFvrljhs9gnOYkGA=='/>

    • Linux 

      <data key='user.DB_ADMIN_USER,com.ibm.gklm51.linux' value='klmdb51'/>
<data key='user.DB_ADMIN_PASSWORD,com.ibm.gklm51.linux' value='9YTRJMRIydDSdfhaHPs1ag=='/>
  9. Open a command line, and change directory to the directory where the installer files are extracted.
  10. Run the following command:

    • Windows 

      silent_updateSKLM.bat IM_INSTALL_DIR WAS_HOME
      For example:
      silent_updateSKLM.bat "C:\Program Files\IBM\Installation Manager" "C:\Program Files\IBM\WebSphere\Liberty"

    • Linux 

      chmod +x ./silent_updateSKLM.sh
./silent_updateSKLM.sh IM_INSTALL_DIR WAS_HOME

      For example: 

      chmod +x ./silent_updateSKLM.sh
./silent_updateSKLM.sh /opt/IBM/InstallationManager /opt/IBM/WebSphere/Liberty
 
Encrypting a password
 
Generate an encrypted password. To do so, follow these steps:
  1. Open a command line.
  2. Change directory to the IM_INSTALL_DIR/eclipse/tools directory.

  3. Run the following command.

    imcl.exe encryptString password_to_encrypt

    An encrypted password is generated.

 

Installing the fix pack on a Multi-Master setup


Prerequisites  

If the original primary master server is acting as a standby master server, promote it to primary and then, install the fix pack. Otherwise, the database updates are not applied to the cluster.

To promote a master server to primary, see Promote to primary. 

To install the fix pack
  1. Stop WebSphere Liberty on all the master servers, in any sequence.
    1. Open a command line.

    2. Go to the WAS_HOME\bin directory and run the following command.

      Windows

      C:\Program Files\IBM\WebSphere\Liberty\bin

      stopServer.bat

       

      Linux

      /opt/IBM/WebSphere/Liberty/bin

      ./stopServer.sh

       

  2. Stop Agent on all the master servers, in any sequence.
    1. Open a command line.
    2. Go to the GKLM_INSTALL_HOME\agent directory.
      Windows
      C:\Program Files\IBM\GKLMV50\agent
      Linux
      /opt/IBM/GKLMV50/agent

    3. Stop the Agent.
      Windows
      stopAgent.bat WAS_HOME
      For example: 

      stopAgent.bat "C:\Program Files\IBM\WebSphere\Liberty"
       

      Linux
      ./stopAgent.sh WAS_HOME
      For example: 

      ./stopAgent.sh /opt/IBM/WebSphere/Liberty
       

  3. Apply fix pack on each master server and verify the installation.
    Complete this step in the following sequence.
    • Primary master server
    • Principal standby master server
    • Auxiliary standby master servers
  4. For steps to install the fix pack, see Installing the fix pack.
    • To verify the installation:
    • Log in to IBM Guardium Key Lifecycle Manager and check the version number.
    • Ensure that the master server is running and available for use.
 
Installing the fix pack on GKLM container
 

Depending on your platform, see the relevant section:

Installing on a Kubernetes cluster

Install IBM Guardium Key Lifecycle Manager container V5.1.0.2 (target).

In the Helm charts, ensure that you configure the same database and volume details that were referenced by the earlier container (source).

For more information, see Install on a Kubernetes cluster.

Installing on a Red Hat OpenShift Container Platform cluster

Install IBM Guardium Key Lifecycle Manager container V5.1.0.2 (target).

In the Helm charts, ensure that you configure the same database and volume details that were referenced by the earlier container (source).

For more information, see Install on a Red Hat OpenShift Container Platform cluster.

Back to top

 

Post fix-pack installation activities

 
  1. Use one of the following methods to verify the installation.
    1. Using graphical user interface:
      a. Log in to the graphical user interface.
      b. On the Welcome page header bar, click the Help (?) icon.
      c. Click About.
      The page displays the version details.

      • Using REST interface:
        Run the Version Info REST Service.  For more information, see Swagger UI.  

        For IBM Guardium Key Lifecycle Manager Traditional:
        IBM Guardium Key Lifecycle Manager version: 5.1.0.2
IBM Guardium Key Lifecycle Manager build level: 202607070425
WebSphere liberty version: 26.0.0.6
Database version: DB2/NT64 SQL120130
JAVA version: JRE 21.0.11 Eclipse OpenJ9 VM 21.0.11+10-openj9-0.59.0
Operating system version: Windows Server 2022:10.0:amd64
Agent version: 2.0
License status: Active
        For IBM Guardium Key Lifecycle Manager Container:
        IBM Guardium Key Lifecycle Manager version: 5.1.0.2
IBM Guardium Key Lifecycle Manager build level: 202607070604
WebSphere liberty version: 26.0.0.6
Database version: PostgreSQL 16.3 (Debian 16.3-1.pgdg120+1)
JAVA version: JRE 21.0.11 Eclipse OpenJ9 VM 21.0.11+10-openj9-0.59.0
Operating system version: Linux:4.18.0-553.139.1.el8_10.x86_64:amd64
Image tag: 5.1.0.2
License status: Active
  2. Remove the old certificates from Guardium Key Lifecycle Manager version 5.1.
    1. Login to Guardium Key Lifecycle Manager UI.
    2. Go to Configuration > Encryption endpoint certificates > Show preinstalled certificates.
    3. On the row of expiring certificate, click 3 dots for Options > Delete.

    4. Delete the following expired certificates.

      - ibmrootca

      - realsubcacert

  3. Back up the IBM Guardium Key Lifecycle Manager server. For more information, see Configuring backup and restore.

Back to top

 
 
Uninstalling the fix pack
 

Important: The following steps uninstall the entire product package, including IBM Guardium Key Lifecycle Manager, IBM Db2, and WebSphere Liberty, and all your data is lost. Take a backup before uninstalling.

Uninstalling IBM Guardium Key Lifecycle Manager with the fix pack by using the graphical user interface

Uninstalling IBM Guardium Key Lifecycle Manager with the fix pack silently

Back to top

 

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 might 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.

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.

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

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:

  • the Excluded Components are provided on an "AS IS" basis.
  • IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
  • IBM will not be liable to you or indemnify you for any claims related to the Excluded Components.
  • IBM will not be liable for any direct, indirect, incidental, special, exemplary, punitive or consequential damages with respect to the Excluded Components.
 
 
 

[{"Type":"MASTER","Line of Business":{"code":"LOB76","label":"Data Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSTJE47","label":"IBM Security Guardium Key Lifecycle Manager"},"ARM Category":[{"code":"a8m0z000000cvdzAAA","label":"SKLM-\u003EINSTALL-\u003EFIXPACK"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1.0"}]

Document Information

Modified date:
08 July 2026

UID

ibm17278880

Page Feedback