NetIQ Identity Manager 24.2.3 (v4.9.0.0300) includes security updates for third-party components supported by Identity Manager. This document provides instructions 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.
This release includes the following updates:
Security updates for the following third-party components:
|
Component |
Supported version |
|---|---|
|
Tomcat |
9.0.120 |
|
ActiveMQ |
5.19.9 |
|
PostgreSQL |
16-14 |
|
Log4j |
2.25.4 |
|
Java Runtime Environment (JRE) |
11.90.19 |
|
NGINX |
1.30.4-0 |
Includes software fixes from version 24.2.1 (v4.9.0.0100) and 24.2.2 (v4.9.0.0200). For more information, see Resolved issues in previous versions.
Version 24.2.2 (v4.9.0.0200) 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. |
Version 4.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. |
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
NetIQ Identity Manager 24.2.3 (v4.9.0.0300) supports upgrades from versions 24.2.2 (v4.9.0.0200), 4.9.0.0100 and 4.9. Before starting the upgrade, review the release notes for your installed version.
IMPORTANT:Version 24.2.3 (v4.9.0.0300) is cumulative and includes all software fixes from patch 1 and patch 2.
Version 24.2.3 (v4.9.2.0.0300) includes an updated, certified Java Runtime Environment (JRE) required for Identity Manager components. Updating the JRE ensures compatibility with the latest fixes, security updates, and platform enhancements.
IMPORTANT:
Ensure no applications are actively using Java during the update.
It is recommended to perform this update before updating other Identity Manager components.
After updating the JRE, ensure that any services using Java (such as Identity Manager engine, Identity Applications, and others) are restarted so they use the updated runtime environment.
Download and extract Identity_Manager_4.9.0_P3.zip.
If you are updating the JRE on a 32-bit system, then:
Back up all the files from /opt/netiq/common/i586/jre/.
Go to <extracted location>/common/JRE/Linux/ and update the JRE package.
rpm -Uvh netiq-jrex-11.90.19-1.i586.rpm
Go to /opt/netiq/common/i586/jre/conf/security and open the java.security file.
Locate the jdk.tls.disabledAlgorithms property and remove TLS_RSA_* from the list of disabled algorithms.
Save the file.
If you are updating the JRE on a 64-bit system, then:
Back up all the files from /opt/netiq/common/jre/.
Go to <extracted location>/common/JRE/Linux/ and update the JRE package.
rpm -Uvh netiq-jrex-11.90.19-1.x86_64.rpm
Go to /opt/netiq/common/jre/conf/security and open the java.security file.
Locate the jdk.tls.disabledAlgorithms property and remove TLS_RSA_* from the list of disabled algorithms.
Save the file.
(Optional) To verify that the installed JRE version is 11.90.19, run:
/opt/netiq/common/jre/bin/java -version
Download and extract Identity_Manager_4.9.0_P3.zip.
Open a command prompt with administrative privileges.
If you are updating the JRE on a 32-bit system, then:
Back up all the files from C:\NetIQ\Common\JRE32.
Go to <extracted location>\common\JRE\Windows\32bit and update the JRE package.
.\NetIQ-JRE32.exe -i PRODUCT_NAME=IDM PRODUCT_VERSION=4.9.0.0300 STAND_ALONE_UPGRADE=false VERSION_XML=version_x86.xml
NOTE:
Set STAND_ALONE_UPGRADE=false if Identity Manager components on the machine have not been upgraded to the latest version.
Set STAND_ALONE_UPGRADE=true if Identity Manager components on the machine are already upgraded to the latest version.
Go to <JAVA_HOME>\conf\security\java.security and open the java.security file.
Locate the jdk.tls.disabledAlgorithms property and remove TLS_RSA_* from the list of disabled algorithms.
Save the file.
If you are updating the JRE on a 64-bit system, then:
Back up all the files from C:\NetIQ\Common\JRE.
Go to <extracted location>\common\JRE\Windows\64bit and update the JRE package.
.\NetIQ-JRE.exe -i PRODUCT_NAME=IDM PRODUCT_VERSION=4.9.0.0300 STAND_ALONE_UPGRADE=false VERSION_XML=version.xml
NOTE:
Set STAND_ALONE_UPGRADE=false if the Identity Manager components on the machine have not been upgraded to the latest version.
Set STAND_ALONE_UPGRADE=true if the Identity Manager components on the machine are already upgraded to the latest version.
Go to <JAVA_HOME>\conf\security\java.security and open the java.security file.
Locate the jdk.tls.disabledAlgorithms property and remove TLS_RSA_* from the list of disabled algorithms.
Save the file.
(Optional) to verify that the installed JRE version is 11.90.19, run:
java -version
Follow the instructions to update the Identity Manager engine to version 4.9.2.0300 on your Linux or Windows system. The update procedure includes backing up existing engine libraries, installing or replacing the updated engine components, updating the User Application Driver, and then restarting the Identity Vault.
Sign in to the Identity Manager engine server.
Go to /opt/novell/eDirectory/lib/dirxml/classes and back up the following files:
log4j-api-*.jar
log4j-core-*.jar
activemq-all-*.jar
dirxml_misc.jar
dirxml.jar
Stop the Identity Vault.
ndsmanage stopall
Download and extract Identity_Manager_4.9.0_P3.zip.
If you are applying this patch as the root user, then:
Go to <extracted location>/engine/Linux and run the following command:
rpm -Uvh novell-DXMLbasenoarch-4.9.0-0300.x86_64.rpm
Proceed to Step 7.
If you are applying this patch as the non-root user, then:
Set the root directory path for the Identity Vault.
export ROOTDIR='<root directory path>'
For example,
export ROOTDIR='/home/idvault'
Update the RPM using the following command:
rpm --dbpath $ROOTDIR/rpm -Uvh --relocate=/usr=$ROOTDIR/opt/novell/eDirectory --relocate=/etc=$ROOTDIR/etc --relocate=/opt/novell/eDirectory=$ROOTDIR/opt/novell/eDirectory --relocate=/opt/novell/dirxml=$ROOTDIR/opt/novell/dirxml --relocate=/var=$ROOTDIR/var --badreloc --nodeps --replacefiles /<path to the new rpm>
For example,
rpm --dbpath /home/idvault/rpm -Uvh --relocate=/usr=/home/idvault/opt/novell/eDirectory --relocate=/etc=/home/idvault/etc --relocate=/opt/novell/eDirectory=/home/idvault/opt/novell/eDirectory --relocate=/opt/novell/dirxml=/home/idvault/opt/novell/dirxml --relocate=/var=/home/idvault/var --badreloc --nodeps --replacefiles /Linux/novell-DXMLbasenoarch-4.9.0.0300.x86_64.rpm
Update the User Application Driver. For more information, see Updating Identity Manager drivers.
Start the Identity Vault.
ndsmanage startall
Sign in to the Identity Manager engine server.
Stop the Identity Vault instance from the Windows Services console.
Go to <Identity Manager installed location>\IDM\NDS\lib and back up the following files:
log4j-api-*.jar
log4j-core-*.jar
activemq-all-*.jar
dirxml_misc.jar
dirxml_misc.jar
Download and extract Identity_Manager_4.9.0_P3.zip.
Replace dirxml_misc.jar and dirxml.jar in <Identity Manager installed location>\IDM\NDS\lib with the versions from <extracted location>\engine\Windows\.
Replace activemq-all-*.jar in <Identity Manager installed location>\IDM\NDS\lib with activemq-all-5.19.9.jar from <extracted location>\common\activemq\.
Update the User Application Driver. For more information, see Updating Identity Manager drivers.
Start the Identity Vault instance from the Windows Services console.
Follow the instructions to update the Remote Loader on your Linux or Windows system. The update procedure includes stopping all Remote Loader instances, associated drivers, and the Remote Loader Console, backing up existing library files, installing or replacing the updated components, and then restarting the Remote Loader instances.
Before updating the Remote Loader, ensure that the following components are stopped:
Remote Loader instances
All driver instances running with the Remote Loader
Remote Loader Console
Go to /opt/novell/eDirectory/lib/dirxml/classes and back up the following files:
dirxml_misc.jar
dirxml.jar
log4j-api-*.jar
log4j-core-*.jar
activemq-all-*.jar
Download and extract Identity_Manager_4.9.0_P3.zip.
Go to <extracted location>/engine/Linux and run the following command:
rpm -Uvh novell-DXMLbasenoarch-4.9.0.0300.x86_64.rpm
Update the User Application Driver. For more information, see Updating Identity Manager drivers.
Start the Remote Loader instances.
Go to C:\NetIQ\IDM\RemoteLoader\64bit\lib and back up the following files:
dirxml_misc.jar
dirxml.jar
log4j-api-*.jar
log4j-core-*.jar
Logging-*.jar
LogCache-*.jar
activemq-all-*.jar
Download and extract Identity_Manager_4.9.0_P3.zip.
Replace the existing files in C:\NetIQ\IDM\RemoteLoader\64bit\lib with the following versions from <extracted location>\engine\Windows\.
Logging-2.3.0.0300.jar
LogCache-2.3.0.0300.jar
dirxml_misc.jar
dirxml.jar
Replace activemq-all-*.jar in <Identity Manager installed location>\IDM\NDS\lib with the activemq-all-5.19.9.jar from <extracted location>\common\activemq\.
Update the User Application Driver. For more information, see Updating Identity Manager drivers.
Start the Remote Loader instances.
Go to C:\NetIQ\IDM\RemoteLoader\32bit\lib and back up the following files:
log4j-api-*.jar
log4j-core-*.jar
Logging-*.jar
LogCache-*.jar
Download and extract Identity_Manager_4.9.0_P3.zip.
Replace the existing files in C:\NetIQ\IDM\RemoteLoader\32bit\lib with the following versions from <extracted location>\common\log4j\windows\:
Logging-2.3.0.0300.jar
LogCache-2.3.0.0300.jar
Update the User Application Driver. For more information, see Updating Identity Manager drivers.
Start the Remote Loader instances.
Go to C:\NetIQ\IDM\RemoteLoader\.Net\lib and back up the following files:
log4j-api-*.jar
log4j-core-*.jar
Logging-*.jar
LogCache-*.jar
Download and extract Identity_Manager_4.9.0_P3.zip.
Replace the existing files in C:\NetIQ\IDM\RemoteLoader\.Net\lib with the following versions from <extracted location>\common\log4j\windows\:
Logging-2.3.0.0300.jar
LogCache-2.3.0.0300.jar
Update the User Application Driver. For more information, see Updating Identity Manager drivers.
Start the .NET Remote Loader instance.
Follow the instructions to update the User Application Driver on your Linux or Windows system. The update procedure includes stopping the required services, backing up existing driver libraries, installing or replacing the updated driver files, and then restarting the services.
Stop the User Application Driver.
Sign in to the Identity Vault server as the root user and stop the Identity Vault.
ndsmanage stopall
Go to /opt/novell/eDirectory/lib/dirxml/classes and back up the following files:
srvprvUAD-*.jar
ComposerDriverShim.jar
wssdk-*.jar
Download and extract Identity_Manager_4.9.0_P3.zip.
Go to <extracted location>/Driver/Linux and install the new RPM.
rpm -Uvh netiq-DXMLuad-4.9.0.0300.noarch.rpm
Start the Identity Vault.
ndsmanage startall
Start the User Application Driver.
Stop the User Application Driver and the eDirectory service.
Go to C:\NetIQ\idm\nds\lib and back up the following files:
srvprvUAD-*.jar
ComposerDriverShim.jar
wssdk-*.jar
Download and extract Identity_Manager_4.9.0_P3.zip.
Replace srvprvUAD-*.jar, ComposerDriverShim.jar, and wssdk-*.jar in C:\NetIQ\idm\nds\lib with the following versions from <extracted location>/Driver/Windows:
srvprvUAD-4.9.0.0300.jar
ComposerDriverShim.jar
wssdk-4.9.0.0000.jar
Replace log4j-api-*.jar and log4j-core-*.jar in C:\NetIQ\IDM\NDS\lib with the following versions from <extracted_location>\common\log4j\windows\:
log4j-api-2.25.4.jar
log4j-core-2.25.4.jar
Start the eDirectory service and the User Application Driver.
Follow the instructions to update ActiveMQ to version 5.19.9 on your Linux or Windows system. The procedure includes stopping the ActiveMQ service, backing up the existing configuration, installing the updated package, restoring any custom configuration changes, and restarting the service.
Stop ActiveMQ.
cd /opt/netiq/idm/activemq/bin
export PATH=/opt/netiq/common/jre/bin/:$PATH
./activemq stop
To take a backup of the conf directory located at /opt/netiq/idm/activemq/conf:
Create a new backup directory.
mkdir /root/backup
Copy the files to the backup location.
cp -rvf /opt/netiq/idm/activemq/conf/ /root/backup/
Download and extract Identity_Manager_4.9.0_P3.zip.
Go to <extracted_location>/common/activemq/Linux and install the RPM package.
rpm -Uvh netiq-activemq-5.19.9-1.noarch.rpm
NOTE:You may observe multiple warning messages during the ActiveMQ RPM installation (for example, remove failed: No such file or directory). You can safely ignore these warnings, as they do not impact the functionality or the upgrade process.
Restore your customizations from the backed-up conf directory.
Start ActiveMQ.
cd /opt/netiq/idm/activemq/bin
export PATH=/opt/netiq/common/jre/bin/:$PATH
./activemq start
Open a command prompt with administrative privileges.
Go to <activemq_home>\bin (for example, C:\NetIQ\common\activemq\bin) and run:
.\activemq stop
If Tomcat is integrated into your environment, then stop Tomcat before proceeding with library updates.
Back up the conf folder located at <activemq_home>\conf (for example, C:\NetIQ\common\activemq\conf).
Download and extract Identity_Manager_4.9.0_P3.zip.
Go to <extracted_location>\common\activemq\Windows and run the command:
.\NetIQ-ACTIVEMQ.exe -i PRODUCT_NAME=IDM PRODUCT_VERSION=4.9.0.0300 STAND_ALONE_UPGRADE=false VERSION_XML=version.xml
NOTE:
Set STAND_ALONE_UPGRADE=false if the Identity Manager components on the machine have not been upgraded to the latest version.
Set STAND_ALONE_UPGRADE=true if the Identity Manager components on the machine are already upgraded to the latest version.
Restore customizations from the backed-up conf directory.
Go to <activemq_home>\bin (for example, C:\NetIQ\common\activemq\bin) and run:
.\activemq start
Follow the instructions to update the Fanout Agent on your Linux or Windows system. The update procedure includes backing up the existing configuration and library files, installing or replacing the updated components, updating the logging configuration, and then restarting the Fanout Agent and driver instances.
NOTE:Ensure that the driver instance and the Fanout Agent instance are stopped before updating the Fanout Agent.
Backup the config directory located at <FOA_HOME>/config/.
Download and extract Identity_Manager_4.9.0_P3.zip.
Go to <extracted location>/foa/Linux and run the following commands to update the RPMs:
rpm -Uvh novell-DXMLfanoutagent-1.3.0-0300.noarch.rpm
rpm -Uvh novell-jlogger-2.3.0-0300.noarch.rpm
Go to <FOA_HOME>/config/ and open the fanoutlog.properties file.
Replace the contents of the file with the following configuration:
appender.stdout.layout.pattern=%5p [%t] (%F\:%L) - %m%n appender.stdout.layout.type=PatternLayout appender.stdout.name=stdout appender.stdout.type=Console appender.syslog_local1.facility=LOCAL1 appender.syslog_local1.filter.threshold.level=info appender.syslog_local1.filter.threshold.onMatch=ACCEPT appender.syslog_local1.filter.threshold.onMismatch=DENY appender.syslog_local1.filter.threshold.type=ThresholdFilter appender.syslog_local1.host=localhost appender.syslog_local1.layout.pattern=%p %t %c - %m%n appender.syslog_local1.layout.type=PatternLayout appender.syslog_local1.name=syslog_local1 appender.syslog_local1.port=514 appender.syslog_local1.protocol=UDP appender.syslog_local1.type=Syslog name=FanoutAgentLogConfig rootLogger.appenderRef.stdout.ref=stdout rootLogger.appenderRef.syslog_local1.ref=syslog_local1 rootLogger.appenderRefs=stdout,syslog_local1 rootLogger.level=info status=warn
Start the Fanout Agent instance and the driver instance.
Back up the config folder located at <FOA_HOME>\config.
Go to C:\NetIQ\IDM\FanoutAgent\lib and back up the following files:
log4j-api-*.jar
log4j-core-*.jar
Logging-*.jar
LogCache-*.jar
activemq-all-*.jar
Download and extract Identity_Manager_4.9.0_P3.0.zip.
Replace the existing files in C:\NetIQ\IDM\FanoutAgent\lib with the following versions from <extracted location>\common\log4j\Windows\:
log4j-api-*.jar
log4j-core-*.jar
Logging-2.3.0.0300.jar
LogCache-2.3.0.0300.jar
Replace the activemq-all-*.jar in C:\NetIQ\IDM\FanoutAgent\lib with activemq-all-5.19.9.jar from <extracted location>\common\activemq\.
Go to <FOA_HOME>\config and open the fanoutlog.properties file.
Replace the contents of the file with the following configuration:
appender.stdout.layout.pattern=%5p [%t] (%F\:%L) - %m%n appender.stdout.layout.type=PatternLayout appender.stdout.name=stdout appender.stdout.type=Console appender.syslog_local1.facility=LOCAL1 appender.syslog_local1.filter.threshold.level=info appender.syslog_local1.filter.threshold.onMatch=ACCEPT appender.syslog_local1.filter.threshold.onMismatch=DENY appender.syslog_local1.filter.threshold.type=ThresholdFilter appender.syslog_local1.host=localhost appender.syslog_local1.layout.pattern=%p %t %c - %m%n appender.syslog_local1.layout.type=PatternLayout appender.syslog_local1.name=syslog_local1 appender.syslog_local1.port=514 appender.syslog_local1.protocol=UDP appender.syslog_local1.type=Syslog name=FanoutAgentLogConfig rootLogger.appenderRef.stdout.ref=stdout rootLogger.appenderRef.syslog_local1.ref=syslog_local1 rootLogger.appenderRefs=stdout,syslog_local1 rootLogger.level=info status=warn
Start the Fanout Agent instance and the driver instance.
NOTE:This procedure applies only when you are using the PostgreSQL database included with the Identity Manager installer.
Follow the instructions to update PostgreSQL to version 16.14 on your Linux or Windows system. The update procedure includes replacing the existing PostgreSQL upgrade components with the updated package, running the PostgreSQL upgrade procedure, and verifying the database configuration after the upgrade is complete.
Stop the Tomcat service running Identity Applications and Identity Reporting.
Download Identity_Manager_4.9.0_Linux.iso from the Software Download and License portal and extract the file to a local directory.
Make a copy of the extracted files to a location with write access.
For example,
mkdir -p /home/49
cp -r <mount-location>/* /home/49/
Delete the older PostgreSQL package.
rm -f /home/49/common/packages/postgres/netiq-postgresql-<version>.noarch.rpm
Delete the PostgreSQL upgrade script.
rm -f /home/49/common/scripts/pg-upgrade.sh
Download Identity_Manager_4.9.0_P3.zip from the Software Download and License portal and extract the file to a local directory.
Copy netiq-postgresql-16.14-0.noarch.rpm from the extracted directory to /home/49/common/packages/postgres.
cp <extracted_directory>/common/postgres/Linux/netiq-postgresql-16.14-0.noarch.rpm /home/49/common/packages/postgres
For example, cp Identity_Manager_4.9.0_P3/common/postgres/Linux/netiq-postgresql-16.14-0.noarch.rpm /home/49/common/packages/postgres
Copy ./pg-upgrade.sh from the extracted directory to /home/49/common/scripts.
cp <extracted_directory>/common/postgres/Linux/pg-upgrade.sh /home/49/common/scripts
Go to /home/49/common/scripts and run:
./pg-upgrade.sh
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.
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.
To update PostgreSQL, follow the procedure described in Upgrading the PostgreSQL database.
In step 4, do not run the TomcatPostgreSQL.exe file included in Identity_Manager_4.9.0_Windows.iso. Instead, run the following executable from the extracted Identity_Manager_4.9.0_P3 package, and then continue with the remaining steps in the procedure:
Identity_Manager_4.9.0_P3/common/postgres/Windows/TomcatPostgreSQL.exe
Follow the instructions to update Tomcat to version 9.0.120 on your Linux or Windows system. The update procedure includes backing up the existing Tomcat configuration and custom files, installing the updated Tomcat components, restoring required customizations, updating dependent libraries, and restarting the Tomcat service.
Sign in to the server where Tomcat is installed.
Stop the Tomcat service.
systemctl stop netiq-tomcat.service
Copy the contents of /opt/netiq/idm/apps/tomcat/conf/ to a secure backup location (for example, /home/backup/tomcat_conf/).
Back up the setenv.sh file located in /opt/netiq/idm/apps/tomcat/bin.
Download Identity_Manager_4.9.0_P3.zip from the Software Download and License portal and extract the file to a local directory.
Go to <extracted location>/common/Tomcat/Linux and run the following commands:
rpm -Uvh netiq-tomcatconfig-4.9.0.0300-2.noarch.rpm
rpm -Uvh netiq-idmtomcat-9.0.120-1.noarch.rpm
NOTE:You may observe multiple warning messages during the Tomcat config RPM installation (for example, remove failed: No such file or directory). You can safely ignore these warnings, as they do not impact the functionality or the upgrade process.
Go 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.120.0
Go to /opt/netiq/idm/apps/tomcat/temp and /opt/netiq/idm/apps/tomcat/temp/work/Catalina and delete all files and directories.
Start the Tomcat service.
systemctl start netiq-tomcat.service
Sign in as an administrator on the computer where you want to update Tomcat.
In Windows services, stop the IDM Apps Tomcat Service running on your server.
Back up all the files in tomcat folder to tomcat_old. This includes the setenv.bat file. Also, ensure that the planned installation path does not include any tomcat directory.
From the directory containing the installation files [for example, <extracted folder path>\common\postgres\Windows], run TomcatPostgreSQL.exe.
Review the introductory information, then click Next.
Accept the License Agreement, then click Next.
When prompted to choose the components to install [Tomcat, PostgreSQL, or both], select Tomcat only.
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: If you do not use TLS/SSL protocols, specify the port to which the application server redirects requests that require SSL transport. The default value is 8443.
Tomcat ajp port: 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.
NOTE:During the upgrade, an Overwrite Existing File dialog might appear indicating that a file (for example, uninstaller.jar) already exists in the target location. When prompted, select Yes to All to overwrite the existing files and continue the upgrade without interruption.
Copy setenv.bat from tomcat_old folder to the new Tomcat installation. For example, C:\NetIQ\IDM\apps\tomcat\bin.
Update the following parameter in setenv.bat:
-Dinternal.osp.container.plugin.server-version=9.0.120.0
Copy the cache folder from the Tomcat backup directory to the new Tomcat installation. For example, C:\NetIQ\IDM\apps\tomcat.
Replace all files and folders under conf with those from the Tomcat backup directory, except for the catalina.policy file.
Copy the JAR files from the backup lib folder to the new Tomcat lib folder, but do not overwrite any existing JARs.
Copy the logs folder from the Tomcat backup directory to the new Tomcat installation, excluding the catalina.out file.
Copy all WAR files from the webapps folder of the Tomcat backup to the webapps folder of the new Tomcat installation.
Go to <extracted location>\common\activemq and copy activemq-all-5.19.9.jar to C:\NetIQ\IDM\apps\tomcat\lib folder.
Go to <extracted location>\common\postgres and copy postgresql-42.7.9.jar to C:\NetIQ\IDM\apps\tomcat\lib folder.
Go to <extracted location>\common\log4j\windows\ and copy log4j-api-2.25.4.jar and log4j-core-2.25.4.jar to C:\NetIQ\IDM\apps\tomcat\lib folder.
Delete all the files and folders from the <Identity Applications Tomcat installed location>\temp and <Identity Applications Tomcat installed location>\work\Catalina folders.
In Windows services, start the IDM Apps Tomcat Service on Identity Applications server.
Follow the instructions to update Identity Applications to version 24.2.3 (v4.9.0.0300) on your Linux or Windows operating system. The update procedure includes backing up the existing application WAR files, deploying the updated application packages, and then restarting the Tomcat service.
Sign in to the Identity Applications server.
Stop the Tomcat service.
systemctl stop netiq-tomcat.service
Go to /opt/netiq/idm/apps/tomcat/webapps and back up the following files to a local directory:
IDMProv.war
idmdash.war
workflow.war
idmappsdoc.war
Delete the following files and directories from the /opt/netiq/idm/apps/tomcat/webapps directory:
IDMProv.war
IDMProv
idmdash.war
idmdash
workflow.war
workflow
idmappsdoc.war
idmasppsdoc
Download Identity_Manager_4.9.0_P3.zip from the Software License and Download portal and extract the file to a local directory.
Go to <extracted location>/apps/Linux and run the following commands:
rpm -Uvh netiq-userapp-4.9.0.0300-0.noarch.rpm
rpm -Uvh netiq-workflow-1.8.0.0300-1.noarch.rpm
Go to /opt/netiq/idm/apps/tomcat/webapps/ and restore the required permissions and ownership.
chmod +x idmdash.war IDMProv.war workflow.war idmappsdoc.war
chown novlua:novlua idmdash.war IDMProv.war workflow.war idmappsdoc.war
Go to /opt/netiq/idm/apps/tomcat/temp and /opt/netiq/idm/apps/tomcat/temp/work/Catalina and delete all files and directories.
Start the Tomcat service.
systemctl start netiq-tomcat.service
Sign in to the Identity Applications server.
In Windows services, stop the IDM Apps Tomcat Service running on Identity Applications server.
Go to <Identity Applications Tomcat installed location>\webapps\ and back up the following files:
idmappsdoc.war
IDMProv.war
idmdash.war
workflow.war
Delete the following files and folders from <Identity Applications Tomcat installed location>\webapps\:
idmappsdoc.war
idmappsdoc
IDMProv.war
IDMProv
idmdash
idmdash.war
workflow
workflow.war
Download the Identity_Manager_APPS_4.9.0_P3.zip from the Software Download and License portal and extract the file to a local folder.
Copy the idmappsdoc.war, IDMProv.war, idmdash.war and workflow.war files from <extracted location>\Windows to <Identity Applications Tomcat installed location>\webapps\ folder.
Go to <Identity Applications Tomcat installed location>\temp and <Identity Applications Tomcat installed location>\work\Catalina folders and delete all files and folders.
In Windows services, start the IDM Apps Tomcat Service on the Identity Applications server.
Follow the instructions to update NGINX on your Linux or Windows system. The update procedure includes backing up the existing NGINX configuration, installing the updated NGINX package, restoring customized settings, and then restarting the associated services.
Stop the NGINX service.
systemctl stop netiq-nginx.service
Go to /opt/netiq/common/nginx and back up the NGINX configuration file (nginx.conf).
Download Identity_Manager_4.9.0_P3.zip from the Software License and Download portal and extract the file to a local directory.
Go to <extracted location>/common/nginx/Linux and run the command:
rpm -Uvh netiq-nginx-1.30.4-0.x86_64.rpm
Restore the backed-up nginx.conf at /opt/netiq/common/nginx.
Locate all instances of the ssl directives in the file and comment them out:
# ssl on;
Save the file.
Start the NGINX service.
systemctl start netiq-nginx.service
In Windows services console, stop the NetIQ IGA Form Renderer Service and NetIQ Nginx Service running on Identity Applications server.
Back up the NGINX configuration file (nginx.conf) located at C:\NetIQ\Common\Nginx\conf.
Download the Identity_Manager_APPS_4.9.0_P3.zip from the Software Download and License portal and extract the file to a local folder.
Go to <extracted location>\common\nginx\Windows and run the command:
.\NetIQ-NGINX.exe -i PRODUCT_NAME=IDM PRODUCT_VERSION=4.9.0.0300 STAND_ALONE_UPGRADE=false VERSION_XML=version.xml
NOTE:
Set STAND_ALONE_UPGRADE=false if the Identity Manager components on the machine have not been upgraded to the latest version.
Set STAND_ALONE_UPGRADE=true if the Identity Manager components on the machine are already upgraded to the latest version.
Go to C:\NetIQ\Common\Nginx\conf and replace the existing nginx.conf file with the backup file created in Step 2.
Locate and comment out the ssl directives.
# ssl on;
Save the file.
In Windows services console, start the NetIQ IGA Form Renderer Service and NetIQ Nginx Service on Identity Applications server.
Follow the instructions to update Identity Reporting on your Linux or Windows system. The update procedure includes backing up and replacing the existing Identity Reporting application files, clearing the Tomcat cache, and then restarting the Tomcat service.
Stop the Tomcat service.
systemctl stop netiq-tomcat.service
Go to /opt/netiq/idm/apps/tomcat/webapps and back up the idmdcs.war and IDMDCS-CORE.war files to a local directory.
Delete the following files and directories from /opt/netiq/idm/apps/tomcat/webapps:
idmdcs.war
idmdcs
IDMDCS-CORE.war
IDMDCS-CORE
Download Identity_Manager_4.9.0_P3.zip from the Software Download and License portal and extract the file to a local directory.
Go to <extracted location>/reporting/Linux and run:
rpm -Uvh netiq-IDMDCS-7.2.0-0300.noarch.rpm
Go to /opt/netiq/idm/apps/tomcat/webapps/ and restore the required permissions and ownership.
chmod +x idmdcs.war IDMDCS-CORE.war
chown novlua:novlua idmdcs.war IDMDCS-CORE.war
Go to /opt/netiq/idm/apps/tomcat/temp and /opt/netiq/idm/apps/tomcat/work/Catalina directories and delete all files and directories.
Go to /opt/netiq/idm/apps/tomcat/conf/ and update the ism-configuration.properties file by setting the following property:
com.netiq.rpt.download.server.url=https://nu.novell.com/designer/rpt720-Patch3/
Save the file.
NOTE:When upgrading Identity Manager from 24.2.3 (v4.9.0.0300) to a later version, ensure that the com.netiq.rpt.download.server.url property points to the report repository corresponding to the supported Identity Reporting version.
Start the Tomcat service.
systemctl start netiq-tomcat.service
In Windows services, stop the IDM Apps Tomcat Service running on Identity Applications server.
Go to C:\NetIQ\idm\apps\tomcat\webapps and back up idmdcs.war and IDMDCS-CORE.war to a local folder.
Delete the following files and folders from C:\NetIQ\idm\apps\tomcat\webapps:
idmdcs.war
idmdcs
IDMDCS-CORE.war
IDMDCS-CORE
Go to <extracted location>\reporting\Windows and copy idmdcs.war and IDMDCS-CORE.war files to C:\NetIQ\idm\apps\tomcat\webapps.
Go to C:\NetIQ\idm\apps\tomcat\temp and C:\NetIQ\idm\apps\tomcat\work\Catalina\ and delete all files and folders.
Go to C:\NetIQ\IDM\apps\tomcat\conf\ and update the ism-configuration.properties file by setting the following property:
com.netiq.rpt.download.server.url=https://nu.novell.com/designer/rpt720-Patch3/
Save the file.
NOTE:When upgrading Identity Manager from 24.2.3 (v4.9.0.0300) to a later version, ensure that the com.netiq.rpt.download.server.url property points to the report repository corresponding to the supported Identity Reporting version.
In Windows services, start the IDM Apps Tomcat Service on Identity Applications server.
This section describes how to update Identity Manager containers. The procedure applies to both single-server and distributed deployments.
Update the containers in the following sequence:
Identity Manager engine
Remote Loader
Fanout Agent
One SSO Provider (OSP) container
PostgreSQL
Identity Applications
Form Renderer
ActiveMQ
Identity Reporting
To update the Identity Manager engine container:
Stop the existing Docker container.
docker stop <container_id>
Remove the Docker container.
docker rm <container_id>
Delete the Identity Manager engine Docker image.
docker rmi <image_id>
Create a credentials.properties file in the shared /data directory with the following content:
ID_VAULT_ADMIN_LDAP="<ID_VAULT_ADMIN_LDAP>" ID_VAULT_PASSWORD="<ID_VAULT_PASSWORD>"
Where, the value for ID_VAULT_ADMIN_LDAP must be specified in comma-separated DN format.
For example,
ID_VAULT_ADMIN_LDAP="cn=admin,ou=sa,o=system" ID_VAULT_PASSWORD="novell"
Go to the directory where Identity_Manager_4.9.0_P3_Containers.tar.gz is extracted.
Go to docker-images and run the following command to load the image:
docker load --input IDM_4903_identityengine.tar.gz
To update the container, run the following command based on your deployment type:
If you are deploying the Identity Manager engine on a distributed server using the overlay network:
docker run --restart unless-stopped -d --ip=192.168.0.12 --network=idmoverlaynetwork --hostname=identityengine.example.com --name=engine-container -v /etc/hosts:/etc/hosts -v /data:/config -p 8028:8028 -p 524:524 -p 389:389 -p 8030:8030 -p 636:636 -e SILENT_INSTALL_FILE=/config/credentials.properties --stop-timeout 100 identityengine:idm-4.9.0.0300-20
If you are deploying the Identity Manager engine on a distributed server using the host network, or on a single server:
docker run --restart unless-stopped -d --network=host --name=engine-container -v /data:/config -e SILENT_INSTALL_FILE=/config/credentials.properties --stop-timeout 100 identityengine:idm-4.9.0.0300-20
Check the log files to verify that the container has been deployed successfully.
docker logs -f engine-container
To sign in to the container, run:
docker exec -it <container> <command>
For example, docker exec -it engine-container bash
NOTE:To run the Identity Vault utilities such as ndstrace or ndsrepair, sign in to the container as a non-root user called as nds. These utilities cannot be run if you are signed in as a root user. To sign in as nds user to the container, run docker exec -it engine-container su nds.
To update the Remote Loader container:
Stop the existing Docker container.
docker stop <container_id>
Remove the Docker container.
docker rm <container_id>
Delete the Remote Loader Docker image.
docker rmi <image_id>
Go to the directory where Identity_Manager_4.9.0_P3_Containers.tar.gz is extracted.
Go to docker-images and run the following command to load the image:
docker load --input IDM_4903_remoteloader.tar.gz
To update the container, run the following command based on your deployment type:
If you are deploying Remote Loader on a single server using the overlay network:
docker run --restart unless-stopped -d --network=host --name=rl-container -v /data:/config --stop-timeout 100 remoteloader:idm-4.9.0.0300-20
If you are deploying Remote Loader on a distributed server using the overlay network:
docker run --restart unless-stopped -d --ip=192.168.0.2 --network=idmoverlaynetwork --hostname=remoteloader.example.com -p 8090:8090 --name=rl-container -v /etc/hosts:/etc/hosts -v /data:/config --stop-timeout 100 remoteloader:idm-4.9.0.0300-20
The driver files can be found at the /opt/novell/eDirectory/lib/dirxml/classes/ directory of the container.
Check the log files to verify that the container has been deployed successfully.
docker logs -f rl-container
To sign in to the container, run:
docker exec -it <container> <command>
For example, docker exec -it rl-container bash
Configure Remote Loader. For more information, see Configuring the Remote Loader and Drivers in the NetIQ Identity Manager Driver Administration Guide.
Ensure that the configuration files are available in the shared volume.
To update the Fanout Agent container:
Stop the existing Docker container.
docker stop <container_id>
Remove the Docker container.
docker rm <container_id>
Delete the Fanout Agent Docker image.
docker rmi <image_id>
Go to the directory where Identity_Manager_4.9.0_P3_Containers.tar.gz is extracted.
Go to docker-images and run the following command to load the image:
docker load --input IDM_4903_fanoutagent.tar.gz
To update the container, run the following command based on your deployment type:
If you are deploying Fanout Agent on a single server using the overlay network:
docker run --restart unless-stopped -d --network=host --name=foa-container -v /data:/config --stop-timeout 100 fanoutagent:idm-4.9.0.0300-20
If you are deploying Fanout Agent on a distributed server using the overlay network:
docker run --restart unless-stopped -d --ip=192.168.0.3 --network=idmoverlaynetwork --hostname=fanoutagent.example.com --name=foa-container -v /etc/hosts:/etc/hosts -v /data:/config --stop-timeout 100 fanoutagent:idm-4.9.0.0300-20
Open the fanoutlog.properties file and replace the contents of the file with the following configuration:
appender.stdout.layout.pattern=%5p [%t] (%F\:%L) - %m%n appender.stdout.layout.type=PatternLayout appender.stdout.name=stdout appender.stdout.type=Console appender.syslog_local1.facility=LOCAL1 appender.syslog_local1.filter.threshold.level=info appender.syslog_local1.filter.threshold.onMatch=ACCEPT appender.syslog_local1.filter.threshold.onMismatch=DENY appender.syslog_local1.filter.threshold.type=ThresholdFilter appender.syslog_local1.host=localhost appender.syslog_local1.layout.pattern=%p %t %c - %m%n appender.syslog_local1.layout.type=PatternLayout appender.syslog_local1.name=syslog_local1 appender.syslog_local1.port=514 appender.syslog_local1.protocol=UDP appender.syslog_local1.type=Syslog name=FanoutAgentLogConfig rootLogger.appenderRef.stdout.ref=stdout rootLogger.appenderRef.syslog_local1.ref=syslog_local1 rootLogger.appenderRefs=stdout,syslog_local1 rootLogger.level=info status=warn
Check the log files to verify that the container has been deployed successfully.
docker logs -f foa-container
To sign in to the container, run:
docker exec -it <container> <command>
For example, docker exec -it foa-container bash
Configure the Fanout Agent. For more information, see Configuring the Fanout Agent in the JDBC Fanout driver implementation guide.
Restart the Docker container.
docker restart <container_id>
To update the One SSO Provider (OSP) container:
Stop the existing Docker container.
docker stop <container_id>
Remove the Docker container.
docker rm <container_id>
Delete the OSP Docker image.
docker rmi <image_id>
Go to the directory where Identity_Manager_4.9.0_P3_Containers.tar.gz is extracted.
Go to docker-images and run the following command to load the image:
docker load --input IDM_4903_osp.tar.gz
To update the container, run the following command based on your deployment type:
If you are deploying OSP on a single server using the overlay 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:idm-4.9.0.0300-20
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.0300-20
Update the following parameter in the setenv.sh file:
-Dinternal.osp.container.plugin.server-version=9.0.120.0
Check the log files to verify that the container has been deployed successfully.
docker logs -f osp-container
To update the PostgreSQL container:
On the Docker host, navigate to any location. For example, cd /tmp.
Back up the existing PostgreSQL container data.
docker exec postgresql-container pg_dumpall -U postgres > /tmp/dump.sql
Stop the existing Docker container.
docker stop <container_id>
Remove the Docker container.
docker rm <container_id>
Back up the pg_hba.conf file and delete the existing PostgreSQL data directory.
rm -rf /data/postgres
Delete the PostgreSQL Docker image.
docker rmi <image_id>
Create a sub-directory under the shared /data directory. For example, postgres.
mkdir postgres
Go to the directory where Identity_Manager_4.9.0_P3_Containers.tar.gz is extracted.
Go to docker-images and run the following command to load the image:
docker load --input IDM_4903_postgres.tar.gz
To update the container, run the following command based on your deployment type:
If you are deploying PostgreSQL on a single server using the overlay network:
docker run --restart unless-stopped -d --network=host --name=postgresql-container -e POSTGRES_PASSWORD=<password> -v /data/postgres:/var/lib/postgresql/data --stop-timeout 100 postgres:16.14
For example, docker run --restart unless-stopped -d --network=host --name=postgresql-container -e POSTGRES_PASSWORD=novell -v /data/postgres:/var/lib/postgresql/data --stop-timeout 100 postgres:16.14
If you are deploying PostgreSQL on a distributed server using the overlay network:
docker run --restart unless-stopped -d --ip=192.168.0.6 --network=idmoverlaynetwork --hostname=postgresql.example.com --name=postgresql-container -p 5432:5432 -e POSTGRES_PASSWORD=<password> -v /data/postgres:/var/lib/postgresql/data -v /etc/hosts:/etc/hosts -v /data:/config --stop-timeout 100 postgres:16.14
For example, docker run --restart unless-stopped -d --ip=192.168.0.6 --network=idmoverlaynetwork --hostname=postgresql.example.com --name=postgresql-container -p 5432:5432 -e POSTGRES_PASSWORD=novell -v /data/postgres:/var/lib/postgresql/data -v /etc/hosts:/etc/hosts -v /data:/config --stop-timeout 100 postgres:16.14
Copy the data file you backed up on the Docker host (in step 2) to the new PostgreSQL data directory.
cp /tmp/dump.sql /data/postgres
To sign in to the container, run:
docker exec -it <container> <command>
For example, docker exec -it postgresql-container bash
Go to /var/lib/postgresql/data/ and restore the data backed up in step 2 to the new PostgreSQL container.
psql -U postgres < dump.sql
Run the exit command to exit the container.
Go to postgres directory by running: cd /data/postgres/.
Replace the existing pg_hba.conf file with the backup created in step 5.
Restart the PostgreSQL container.
docker restart postgresql-container
To update the Identity Applications container:
Stop the existing Docker container.
docker stop <container_id>
Remove the Docker container.
docker rm <container_id>
Delete the Identity Applications Docker image.
docker rmi <image_id>
Go to the directory where Identity_Manager_4.9.0_P3_Containers.tar.gz is extracted.
Go to docker-images and run the following command to load the image:
docker load --input IDM_4903_identityapplication.tar.gz
To update the container, run the appropriate command based on your deployment type:
If you are deploying Identity Applications on a single server using the overlay network:
docker run --restart unless-stopped -d --network=host --name=idapps-container -v /data:/config -e MASTER_KEYSTORE_PWD=<keystore-pwd> --stop-timeout 100 identityapplication:idm-4.9.0.0300-20
If you are deploying Identity Applications on a distributed server using the overlay network:
docker run --restart unless-stopped -d --ip=192.168.0.7 --network=idmoverlaynetwork --hostname=identityapps.example.com -p 18543:18543 --name=idapps-container -v /etc/hosts:/etc/hosts -v /data:/config -e MASTER_KEYSTORE_PWD=<keystore-pwd> --stop-timeout 100 identityapplication:idm-4.9.0.0300-20
Update the following parameter in the setenv.sh file:
-Dinternal.osp.container.plugin.server-version=9.0.120.0
Check the log files to verify that the container has been deployed successfully.
docker logs -f idapps-container
To update the Form Renderer container:
Stop the existing Docker container.
docker stop <container_id>
Remove the Docker container.
docker rm <container_id>
Delete the Form Renderer Docker image.
docker rmi <image_id>
Go to the directory where Identity_Manager_4.9.0_P3_Containers.tar.gz is extracted.
Go to docker-images and run the following command to load the image:
docker load --input IDM_4903_formrenderer.tar.gz
To update the container, run the following command based on your deployment type:
If you are deploying Form Renderer on a single server using the overlay network:
docker run --restart unless-stopped -d --network=host --name=fr-container -v /data:/config --stop-timeout 100 formrenderer:idm-4.9.0.0300-20
If you are deploying Form Renderer on a distributed server using the overlay network:
docker run --restart unless-stopped -d --ip=192.168.0.8 --network=idmoverlaynetwork --hostname=formrenderer.example.com -p 8600:8600 --name=fr-container -v /data:/config --stop-timeout 100 formrenderer:idm-4.9.0.0300-20
Check the log files to verify that the container has been deployed successfully.
docker logs -f fr-container
To sign in to the container, run:
docker exec -it <container> <command>
For example, docker exec -it fr-container bash
To update the ActiveMQ container:
Stop the existing Docker container.
docker stop <container_id>
Remove the Docker container.
docker rm <container_id>
Delete the ActiveMQ Docker image.
docker rmi <image_id>
Go to the directory where Identity_Manager_4.9.0_P3_Containers.tar.gz is extracted.
Go to docker-images and run the following command to load the image:
docker load --input IDM_4903_activemq.tar.gz
To update the container, run the following command based on your deployment type:
If you are deploying ActiveMQ on a single server using the overlay network:
docker run --restart unless-stopped -d --network=host --name=amq-container -v /data:/config --stop-timeout 100 activemq:idm-4.9.0.0300-20
If you are deploying ActiveMQ on a distributed server using the overlay network:
docker run --restart unless-stopped -d --ip=192.168.0.9 --network=idmoverlaynetwork --hostname=activemq.example.com -p 61616:61616 --name=amq-container -v /data:/config --stop-timeout 100 activemq:idm-4.9.0.0300-20
Check the log files to verify that the container has been deployed successfully.
docker logs -f amq-container
To sign in to the container, run:
docker exec -it <container> <command>
For example, docker exec -it amq-container bash
To update Identity Reporting container:
Stop the existing Docker container.
docker stop <container_id>
Remove the Docker container.
docker rm <container_id>
Delete the Identity Reporting Docker image.
docker rmi <image_id>
Go to the directory where Identity_Manager_4.9.0_P3_Containers.tar.gz is extracted.
Go to docker-images and run the following command to load the image:
docker load --input IDM_4903_identityreporting.tar.gz
To update the container, run the following command based on your deployment type:
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.0300-20
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.0300-20
Update the following parameter in the setenv.sh file:
-Dinternal.osp.container.plugin.server-version=9.0.120.0
Check the log files to verify that the container has been deployed successfully.
docker logs -f rpt-container
Update the ism-configuration.properties file by setting the following property:
com.netiq.rpt.download.server.url=https://nu.novell.com/designer/rpt720-Patch3
Save the file.
NOTE:When upgrading Identity Manager from 24.2.3 (v4.9.0.0300) to a later version, ensure that the com.netiq.rpt.download.server.url property points to the report repository corresponding to the supported Identity Reporting version.
Restart the Docker container.
docker restart <container_id>
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 theNetIQ Identity Manager 4.9 Release Notes. If you need further assistance with any issue, please contact, contact Technical Support.
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:
Product documentation, Knowledge Base articles, and videos: https://www.microfocus.com/support-and-services/
The Micro Focus Community pages: https://www.microfocus.com/communities/
Copyright 2009 - 2026 Open Text.
The only warranties for products and services of Open Text and its affiliates and licensors (“Open Text”) are as may be set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Open Text shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice.