NetIQ Identity Manager 24.2.2 (v4.9.0.0200) Release Notes

December 2025

NetIQ Identity Manager 24.2.2 (v4.9.0.0200) resolves some of the previous issues. This document outlines the steps for installing this patch.

For the list of software fixes and enhancements in the previous release, see NetIQ Identity Manager 4.9 Release Notes.

For more information about this release and for the latest release notes, see the Identity Manager Documentation page. To download this product, see the Software Licenses and Downloads portal.

1.0 What’s New?

2.0 Resolved Issues in 24.2.2 (v4.9.0.0200)

This release provides the following software fixes:

Global ID

Description

OCTCR56A731321

 The Other option does not appear under Access > Permissions for a user or group when the Provisioning Manager permission is assigned to that user or group.

OCTCR56A732178

Escalation of approval workflows fails when the Approver Type is set to Normal.

3.0 Resolved Issues in Previous Version

 Version 24.2.1 (v4.9.0.0100) provides the following software fixes:

Global ID

Description

OCTCR56A585354 and OCTCR56A584062

In Dashboard’s Access > Request > Manage Featured Items, users are unable to sort request permissions within a category in the preferred order.

OCTCR56A656069

A DAL query with the DN parameter containing a $ symbol causes an NDS error: illegal ds name (-610).

OCTCR56A677165

The IDMProv component of Identity Manager does not log events in Sentinel. The Sentinel server log shows the following error message: A connection from machine <Identity Applications Server IP> was lost with the Syslog Event Source Server.

OCTCR56A687087

After upgrading to version 4.9, workflow request initiated using the REST API (/IDMProv/rest/access/requests/permissions/item) fails with the following error message: ERROR com.novell.soa.af.rest.controller.WfRestController - [WORKFLOW] Workflow request has failed.com.novell.soa.af.WorkException: Workflow request has failed.

4.0 System Requirements

To apply this patch, you must at least have the following minimum versions:

  • eDirectory 9.2.9

  • Identity Console 1.8

  • Identity Manager 4.9

5.0 Updating to This Patch

IMPORTANT:

  • The updates in patch 2 are cumulative. They include software fixes for the Identity Applications in the current version, as well as all previously released fixes from patch 1.

  • If you are upgrading from patch 1, your PostgreSQL is already up to date with the packaged RPM.

Before starting the upgrade, review the release notes for your current version.

Depending on your operating system or deployment platform, follow the instructions below to upgrade Identity Manager to 4.9.0.0200 version:

5.1 Updating This Patch on Linux

  1. Stop the Tomcat service by executing the following command:

    systemctl stop netiq-tomcat.service

  2. Navigate to the /opt/netiq/idm/apps/tomcat/webapps directory and take a back up of the following files in a local directory:

    • idmappsdoc.war

    • idmdash.war

    • IDMProv.war

    • workflow.war

  3. Delete the following directories from the /opt/netiq/idm/apps/tomcat/webapps directory:

    • idmappsdoc

    • idmdash

    • IDMProv

    • workflow

  4. Download the Identity_Manager_APPS_4.9.0_P2.zip from the Software Download and License portal and extract the file to a local directory.

  5. Navigate to the <extracted location>/Linux directory.

  6. Run the following commands:

    rpm -Uvh netiq-userapp-4.9.0.0200-0.noarch.rpm
    rpm -Uvh netiq-workflow-1.8.0.0200-1.noarch.rpm

  7. If you install the rpm as root, navigate to the /opt/netiq/idm/apps/tomcat/webapps/ directory and run the following commands to add execute permission and user rights for the replaced files:

    • chmod +x idmappsdoc.war idmdash.war IDMProv.war workflow.war
    • chown novlua:novlua idmappsdoc.war idmdash.war IDMProv.war workflow.war

  8. Delete all the files and directories from the /opt/netiq/idm/apps/tomcat/temp and /opt/netiq/idm/apps/tomcat/work/Catalina directories.

  9. Run the following command to start the Tomcat service:

    systemctl start netiq-tomcat.service

5.2 Updating This Patch on Windows

  1. From the Windows services, stop the IDM Apps Tomcat Service running on your Identity Applications server.

  2. Take a back up of the following files from the <Identity Applications Tomcat installed location>\webapps\ folder.

    • idmappsdoc.war

    • IDMProv.war

    • idmdash.war

    • workflow.war

  3. Delete the following folders from the <Identity Applications Tomcat installed location>\webapps\ folder:

    • idmappsdoc

    • IDMProv

    • idmdash

    • workflow

  4. Download the Identity_Manager_APPS_4.9.0_P2.zip from the Software Download and License portal and extract the file to a local folder.

  5. Navigate to the <extracted location>\Windows and copy the idmappsdoc.war, IDMProv.war, idmdash.war and workflow.war files to the <Identity Applications Tomcat installed location>\webapps\ folder.

  6. Delete all the files and folders from the <Identity Applications Tomcat installed location>\temp and <Identity Applications Tomcat installed location>\work\Catalina folders.

  7. From the Windows services, start the IDM Apps Tomcat Service on your Identity Applications server.

5.3 Updating Identity Manager Containers

This section provides information about updating the Identity Manager containers. These steps can be used to update both single and distributed servers.

Updating the OSP Container

  1. Stop the existing Docker container by using the docker stop command. For example,

    docker stop <container_id>

  2. Remove the Docker container by using the docker rm command. For example,

    docker rm <container_id>

  3. Delete the OSP Docker image by using the docker rmi command. For example,

    docker rmi <image_id>

  4. Navigate to the location where you have extracted the Identity_Manager_4.9.0_P2_Containers.tar.gz file.

  5. Navigate to the docker-images directory.

  6. Run the following command to load the image:

    docker load --input IDM_4902_osp.tar.gz

  7. Update the container using the following command:

    • If you are deploying OSP on a distributed server using the overlay network:

      docker run --restart unless-stopped -d --ip=192.168.0.5 --network=idmoverlaynetwork --hostname=osp.example.com -p 8543:8543 --name=osp-container -v /etc/hosts:/etc/hosts -v /data:/config -e MASTER_KEYSTORE_PWD=<keystore-pwd> --stop-timeout 100 osp:idm-4.9.0.0200-9

    • If you are deploying OSP on a single server using the host network:

      docker run --restart unless-stopped -d --network=host --name=osp-container -v /data:/config -e MASTER_KEYSTORE_PWD=<keystore-pwd> --stop-timeout 100 osp:4.9.0.0200-9

  8. Update the following parameter in the setenv.sh file:

    -Dinternal.osp.container.plugin.server-version=9.0.111.0

  9. Restart the Docker container using the following command:

    docker restart <container_id>

Updating Identity Applications Containers

  1. Stop the existing docker container by using the docker stop command.

    For example, docker stop <container_id>

  2. Remove the docker container by using the docker rm command.

    For example, docker rm <container_id>

  3. Delete the Identity Applications docker image by using the docker rmi command.

    For example, docker rmi <image_id>

  4. Navigate to the location where you have extracted the Identity_Manager_4.9.0_P2_Containers.tar.gz file.

  5. Navigate to the docker-images directory.

  6. Run the following command to load the image:

    docker load --input IDM_4902_identityapplication.tar.gz

  7. To update the Identity Applications container on distributed servers, use the following command:

    docker run -d --ip=192.168.0.7 --network=idmoverlaynetwork --hostname=identityapps.example.com -p 18543:18543 --name=idappscontainer -v /etc/hosts:/etc/hosts -v /data:/config --stop-timeout 100 identityapplication:idm-4.9.0.0200-9

  8. To update the Identity Applications container on single server, use the following command:

    docker run -d --network=host --name=idapps-container -v /data:/config --stoptimeout 100 identityapplication:idm-4.9.0.0200-9

  9. Update the following parameter in the setenv.sh file:

    -Dinternal.osp.container.plugin.server-version=9.0.111.0

  10. Restart the Docker container using the following command:

    docker restart <container_id>

Updating the Identity Reporting Container

  1. Stop the existing Docker container by using the docker stop command. For example,

    docker stop <container_id>

  2. Remove the Docker container by using the docker rm command. For example,

    docker rm <container_id>

  3. Delete the Identity Reporting Docker image by using the docker rmi command. For example,

    docker rmi <image_id>

  4. Navigate to the location where you have extracted the Identity_Manager_4.9.0_P2_Containers.tar.gz file.

  5. Navigate to the docker-images directory.

  6. Run the following command to load the image:

    docker load --input IDM_4902_identityreporting.tar.gz

  7. Update the container using the following command:

    • If you are deploying Identity Reporting on a single server using the host network:

      docker run --restart unless-stopped -d --network=host --name=rpt-container -v /data:/config -e MASTER_KEYSTORE_PWD=<keystore-pwd> --stop-timeout 100 identityreporting:idm-4.9.0.0200-9

    • If you are deploying Identity Reporting on a distributed server using the overlay network:

      docker run --restart unless-stopped -d --ip=192.168.0.10 --network=idmoverlaynetwork --hostname=identityreporting.example.com -p 28543:28543 --name=rpt-container -v /etc/hosts:/etc/hosts -v /data:/config -e MASTER_KEYSTORE_PWD=<keystore-pwd> --stop-timeout 100 identityreporting:idm-4.9.0.0200-9

  8. Update the following parameter in the setenv.sh file:

    -Dinternal.osp.container.plugin.server-version=9.0.111.0

  9. Restart the Docker container using the following command:

    docker restart <container_id>

6.0 Updating PostgreSQL to this Patch

IMPORTANT:

  • This applies only when you are using PostgreSQL database.

  • This does not apply if you are upgrading from version 24.2.1 (v4.9.0.0100) to 24.2.2 (v4.9.0.0200). Your PostgreSQL database is already up to date with version 14.16.

Stop all services using the PostgresSQL database and follow the instructions below to update PostgreSQL to 14.16:

NOTE:The PostgreSQL binaries in this patch cannot be installed on SUSE Linux Enterprise Server 12 SP5 or earlier. It is recommended that you update to SUSE Linux Enterprise Server 15 or above before applying this patch.

6.1 Updating PostgreSQL on Linux

  1. Download the Identity_Manager_4.9_Linux.iso from the Software Download and License portal and extract the file to a local directory.

  2. Make a copy of the extracted files to a location with write access.

    For example,

    mkdir -p /home/4900200
cp -r <mount-location>/* /home/4900200/

  3. Remove the older postgres package using the following command:

    rm /home/4900200/common/packages/postgres/netiq-postgresql-<version>.noarch.rpm

  4. Download the Identity_Manager_APPS_4.9.0_P2.zip from the Software Download and License portal and extract the file to a local directory.

  5. Replace the rpm inside /home/4900200/common/packages/postgres with Identity_Manager_4.9.0_P2/Linux/netiq-postgresql-14.16-1.noarch.rpm.

    cp Identity_Manager_4.9.0_P2/Linux/netiq-postgresql-14.16-1.noarch.rpm /home/4900200/common/packages/postgres

  6. Navigate to the /home/4900200/common/scripts directory.

  7. Run the following command:

    ./pg-upgrade.sh

  8. Specify the following details to complete the installation:

    Existing Postgres install location: Specify the location where PostgreSQL is installed. The default location is /opt/netiq/idm/postgres.

    NOTE:Ensure the user has appropriate permission to the /opt/netiq/idm/postgres directory.

    Existing Postgres Data Directory: Specify the location of the PostgreSQL data directory. The default location is /opt/netiq/idm/postgres/data.

    Existing Postgres Database Password: Specify the PostgreSQL password.

  9. Run the following command to restart PostgreSQL:

    systemctl restart netiq-postgresql.service

6.2 Updating PostgreSQL on Windows

To update PostgreSQL, follow the steps mentioned in Upgrading the PostgreSQL Database.

NOTE:In step 4 of Upgrading the PostgreSQL Database, you must run TomcatPostgreSQL.exe from the extracted directory of Identity_Manager_4.9.0_P2/Windows/TomcatPostgreSQL.exe.

6.3 Updating PostgreSQL Container

  1. Download the postgres image from the docker hub repository using the following command:

    docker pull postgres:14.16

    This step is an alternative to the docker load --input command. It is not mandatory, as you can also specify the image name directly in the docker run command. If the image is not available in your local repository, Docker will automatically attempt to fetch it from the public repository.

  2. (Conditional) To update the PostgreSQL container on distributed servers, see Updating PostgreSQL Container.

  3. (Conditional) To update the PostgreSQL container on single server, see Updating PostgreSQL Container.

7.0 Updating Tomcat to This Patch

Depending on your operating system, follow the instructions below to upgrade Tomcat to 9.0.111 version:

7.1 Updating Tomcat on Linux

  1. Log in to the server where Tomcat is installed.

  2. Stop the Tomcat service by executing the following command:

    systemctl stop netiq-tomcat.service

  3. Download the Identity_Manager_4.9.0_P2.zip file from the Software Download and License portal and extract the file to a local directory.

  4. Navigate to the <extracted location>/common/Linux directory and run the following command:

    rpm -Uvh netiq-idmtomcat-9.0.111-1.noarch.rpm

  5. Navigate to opt/netiq/idm/apps/tomcat/bin and update the following parameter in the setenv.sh file:

    -Dinternal.osp.container.plugin.server-version=9.0.111.0

  6. Delete all the files and directories from the /opt/netiq/idm/apps/tomcat/temp and /opt/netiq/idm/apps/tomcat/work/Catalina directories.

  7. Run the following command to start the Tomcat service:

    systemctl start netiq-tomcat.service

7.2 Updating Tomcat on Windows

  1. Log in as an administrator on the computer where you want to update Tomcat.

  2. From the Windows services, stop the IDM Apps Tomcat Service running on your server.

  3. Ensure that the planned installation path does not include any tomcat folder. To do this, rename the existing tomcat folder to tomcat_old.

  4. Download the Identity_Manager_4.9.0_P2.zip file from the Software Download and License portal and extract the file to a local folder.

  5. From the directory containing the installation files [for example, <extracted folder path>\common\Windows], run TomcatPostgreSQL.exe.

  6. Review the introductory information, then click Next.

  7. Accept the License Agreement, then click Next.

  8. When prompted to choose the components to install [Tomcat, PostgreSQL, or both], select Tomcat only.

  9. To complete the guided process, provide values for the following parameters:

    • Tomcat parent folder: Specifies the directory where you want to install the Tomcat files.

    • Tomcat details: Represents the ports needed for Tomcat.

      • Tomcat shutdown port: Specifies the port that you want to use for cleanly shutting down all webapps and Tomcat. The default is 8005.

      • Tomcat http port: Specifies the port that you want the Tomcat server to use for communication with client computers. The default is 8080. To use SSL, the default is 8443.

      • Tomcat redirect port: (Conditional) When you do not use TLS/SSL protocols, specifies the port to which the application server redirects requests that require SSL transport. The default value is 8443.

      • Tomcat ajp port: (Optional) Specifies the port that you want the application server to use for communication with a web connector using the AJP protocol instead of http. The default value is 8009.

        Use this parameter when you want the application server to manage the static content contained in the web application, and/or utilize the application server’s SSL processing.

  10. Copy the setenv.bat file from the Tomcat backup directory to the new Tomcat installation. For example, C:\NetIQ\IDM\apps\tomcat\bin.

  11. Update the following parameter in the setenv.sh file:

    -Dinternal.osp.container.plugin.server-version=9.0.111.0

  12. Copy the cache folder from the Tomcat backup directory to the new Tomcat installation. For example, C:\NetIQ\IDM\apps\tomcat.

  13. Replace all files and folders under the conf folder with those from the Tomcat backup directory, except for the catalina.policy file.

  14. Copy the JAR files from the backup lib folder to the new Tomcat lib folder, but do not overwrite any existing JARs

  15. Copy the logs folder from the Tomcat backup directory to the new Tomcat installation, excluding the catalina.out file.

  16. Copy all WAR files from the webapps folder of the Tomcat backup to the webapps folder of the new Tomcat installation.

  17. Delete all the files and folders from the <Identity Applications Tomcat installed location>\temp and <Identity Applications Tomcat installed location>\work\Catalina folders.

  18. From the Windows services, start the IDM Apps Tomcat Service on your Identity Applications server.

8.0 Known Issue

NetIQ strives to ensure our products provide quality solutions for your enterprise software needs. There are no new issues other than the issues mentioned in the NetIQ Identity Manager 4.9 Release Notes. If you need further assistance with any issue, please contact, contact Technical Support.

9.0 Contacting Micro Focus

For specific product issues, contact Micro Focus Support at https://www.microfocus.com/support-and-services/.

Additional technical information or advice is available from several sources: