NetIQ Identity Manager 4.9 Patch 1 Release Notes

March 2025

NetIQ Identity Manager 4.9 Patch 1 (4.9.0.0100) resolves some of the previous issues. This document outlines how you can apply 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?

This release includes PostgreSQL 14.16 binaries to address known vulnerabilities. It also contains software fixes for previous issues. For more information, see Resolved Issues.

2.0 Resolved Issues

This release 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.

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

4.0 Updating Identity Applications to This Patch

You must be on Identity Manager 4.9 at a minimum to apply this patch.

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

4.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_P1.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.0100-0.noarch.rpm
    rpm -Uvh netiq-workflow-1.8.0.0100-1.noarch.rpm

  7. (Conditional) 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

4.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 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_P1.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.

4.3 Updating Identity Applications Containers

This section provides information on updating the Identity Applications container. These steps can be used to update both single and distributed servers.

  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_P1_Containers.tar.gz file.

  5. Navigate to the docker-images directory.

  6. Run the following command to load the image:

    docker load --input IDM_4901_identityapplication.tar.gz

  7. (Conditional) 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.0100-55

  8. (Conditional) 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.0100-55

5.0 Updating PostgreSQL to this Patch

Applies only when you are using PostgreSQL database.

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.

5.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/4900100
cp -r <mount-location>/* /home/4900100/

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

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

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

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

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

  6. Navigate to the /home/4900100/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

5.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_P1/Windows/TomcatPostgreSQL.exe.

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

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

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