How do I check what patches are installed for ForgeRock products?

Last updated Jan 11, 2023

The purpose of this article is to provide details for checking what patches are installed for AM, DS, IDM and IG.

2 readers recommend this article

Overview

This article provides details for checking what patches are installed by product:

AM
Agents
DS
IDM
IG

You can also use the patchinfo utility in AM and IG as detailed in How do I use the patchinfo utility to check what patches are installed for AM or IG (All versions)?

Checking for patches in AM

Providing you have unzipped your patches directly in the openam directory as recommended, you can check what patches are installed as follows:

$ cd /path/to/tomcat/webapps/am/WEB-INF $ ls README.* README.1.12345 README.201901

Where each README represents a set of installed patches. READMEs are named to indicate either the ticket number where the patch was given (README.1.12345) or the security advisory ID (README.201901).

Embedded DS

You can check what patches are installed using the status -V command as follows:

$ cd /path/to/am/opends/bin $ ./status -V ForgeRock Directory Services 7.1.1+OPENDJ-1234,OPENDJ-5678 Build 20210729151600

Any installed patches will be listed after the product name and version as an issue tracker ID (JIRA).

Checking for patches in Agents

You can check the debug log to see what patch version you have installed, for example:

####################################################### # OpenAM Web Agent # # Version: 5.8.0 # # Revision: 98f3362 # # Container: Apache Server 2.4.x 64bit # # Build date: eb 22 2021 10:16:22. # ######################################################

For Web Agents, you can also check the version using the agentadmin --v command as follows:

$ ./agentadmin --v OpenAM Web Agent for Apache Server 2.4.x 64bit Version: 5.8.0 Revision: 98f3362 Build machine: Build date: Feb 22 2021 10:16:22

Checking for patches in DS

You can check what patches are installed using the status -V command as follows:

$ cd /path/to/ds/bin $ ./status -V ForgeRock Directory Services 7.1.1+OPENDJ-1234,OPENDJ-5678 Build 20210729151600

Any installed patches will be listed after the product name and version as an issue tracker ID (JIRA).

Checking for patches in IDM

You can check what patches are installed using the PS command when running IDM interactively, for example:

ps START LEVEL 12 ID State Level Name [ 0] [Active ] [ 0] System Bundle (6.0.3) [ 1] [Active ] [ 1] OpenIDM System Bundle (7.0.1) [ 2] [Active ] [ 2] Apache Felix Log Service (1.2.2) [ 3] [Resolved ] [ 3] OpenIDM fragment for jetty security (7.0.1) ... [ 8] [Active ] [ 4] OpenIDM Repository Bundle - JDBC (7.0.1-OPENIDM-1234-5678) ...

Any installed patches will be listed after a product bundle as an issue tracker ID (JIRA). Patches only apply to a bundle (not the whole product), so you will need to check all bundles for patches, focusing on any that start OpenIDM, ForgeRock or OpenICF. You can search for version-JIRA_prefix and version.JIRA_prefix to easily find the patched bundles, for example:

(7.0.1-OPENIDM (7.0.1-OPENICF (7.0.1-CREST

Checking the End user UI Version (IDM 6.5 and later)

Note

The End user UI version that's included with IDM 6.5 and later is independent of the IDM version. Please ensure to include the End user UI version details when raising a ticket with Support. You can find the complete list of End user UI versions and associated IDM releases in Where can I find source code for IDM? (Using the End user UI source code).

When raising a support ticket, you should include the End user UI version details included in the following file:

$ /path/to/idm/ui/enduser/COMMITHASH

This is the version of the End user UI you are currently using.

Checking for patches in IG

Providing you have unzipped your patches directly in the top-level IG WAR directory as recommended, you can check what patches are installed as follows:

$ cd /path/to/jetty/webapps/root/WEB-INF $ ls README.* README.1.12345 README.201606

Where each README represents a set of installed patches. READMEs are named to indicate either the ticket number where the patch was given (README.1.12345) or the security advisory ID (README.201606).

Related Training

N/A

Related Issue Tracker IDs

N/A