OpenText™ Identity Manager CE 24.4 (v4.10) Release Notes
OpenText Identity Manager 24.4 (v4.10) includes new features and enhancements, improves usability, and resolves several previous issues. The updates in this release are cumulative. They include software fixes and enhancements in the current version, as well as all previously released fixes from the service packs, patches, and hotfixes. Many of these improvements were made in direct response to suggestions from our customers. We thank you for your time and valuable input. We hope you continue to help us ensure that our products meet all your needs. You can post feedback in the Identity Manager Community Forums on OpenText Forums, our online community that also includes product information, blogs, and links to helpful resources.
For information about what’s new in previous releases, see the “Previous Releases” section on the OpenText Identity Manager documentation website.
For more information about this release and the latest release notes, see the Documentation page.
To download this product, see the Software License and Download portal.
8.0 Known Issues
OpenText strives to ensure our products provide quality solutions for your enterprise software needs. The following issues are currently being researched. If you need further assistance with any issue, please contact Technical Support.
For the list of known issues in Designer, see the OpenText™ Identity Manager CE 24.4 (v4.10) Designer Release Notes.
-
Failed to load class “org.slf4j.impl.StaticLoggerBinder” Error
-
Authentication Reports Not Generated on Sentinel After Upgrade
-
An Error Reported in the OpenText eDirectory Log File After Upgrade
-
The DirXML Command-Line Utility Displays an Error After Upgrade
-
The dirxml_remote and RLConsole Properties Display the Outdated Product Version
-
Organization Chart Buttons for a Level 2 or Higher Relationship Hierarchy Is Missing
-
Remote Loader Reports Invalid Driver Object Password After Upgrade
-
Observing Error: StatusLogger Reconfiguration Failed in Catalina Log File
8.1 Issue with the Ellucian Banner Driver After Upgrade
Issue: The Integration Module for Banner by Ellucian fails due to incompatibility with Jetty libraries shipped with OpenText Identity Manager 24.4 (v4.10).
Workaround: If you have installed the driver, we recommend to use with Remote Loader 4.9.
8.2 Failed to load class “org.slf4j.impl.StaticLoggerBinder” Error
Issue: During the configuration of Identity Applications, the Linux installation program generates a new master key. However, you may encounter the error “SLF4J: Failed to load class 'org.slf4j.impl.StaticLoggerBinder’” during this process or while updating the master key. [Issue: OCTCR56A701128]
Workaround: The error does not affect any functionality. You can ignore it.
8.3 Set SSO Credential Action Displays an Error
Issue: After upgrading to version 24.4 (v4.10), the do-set-sso-credential action in the Credential Provisioning policy displays an error. This issue occurs specifically when credential provisioning is implemented with SecureLogin. [Issue: OCTCR56A675056]
Workaround: Perform the following steps to resolve this issue:
-
Log in to the Identity Manager Engine server.
-
Download and extract Java SSO SDK zip from the following location: https://www.netiq.com/documentation/securelogin-88/references/Java%20SSO%20SDK-8.8.0-0.zip.
-
Rename the JAR files as follows:
-
Change jssoapi-prov-8.8.0-0-SNAPSHOT.jar to jsso-prov.jar
-
Change jssoapi-cmd-8.8.0-0-20191207.071450-46.jar to jsso-cmd.jar
-
-
Navigate to /opt/novell/eDirectory/lib/dirxml/classes and replace jsso-prov.jar with the JAR file you renamed in Step 3. Also, add jsso-cmd.jar to the same directory.
-
Restart the server.
8.4 Appender Error is Seen in Catalina Logs for WFCEF
Issue: While upgrading Identity Application to 4.10, you might see similar appender error in the catalina logs.
com.netiq.logging.log4j2.Log4jLogger.addAppender Error adding Appender WFCEF to Logger com.microfocus
com.netiq.logging.log4j2.Log4jLogger.addAppender Error adding Appender WFCEF to Logger com.sssw
com.netiq.logging.log4j2.Log4jLogger.addAppender Error adding Appender WFCEF to Logger com.novell
com.netiq.logging.log4j2.Log4jLogger.addAppender Error adding Appender WFCEF to Logger workflow.log
com.netiq.logging.log4j2.Log4jLogger.addAppender Error adding Appender WFCEF to Logger com.netiq
This happens when you configure auditing prior to upgrading the Identity Applications.
[OCTCR56A679501]
Workaround:
-
Navigate to the following directories:---
-
Linux: /opt/netiq/idm/apps/tomcat/conf
-
Windows: C:\NetIQ\IDM\apps\tomcat\conf
Comment the following entries from the ism-configuration.properties file:
workflow.logging.wfs.definition.workflow.log = {\"name\":\"workflow.log\",\"level\":\"INFO\",\"additivity\":true,\"appenderRefs\":[\"WFCEF\"]}
workflow.logging.wfs.definition.com.novell = {\"name\":\"com.novell\",\"level\":\"INFO\",\"additivity\":true,\"appenderRefs\":[\"WFCEF\"]}
workflow.logging.wfs.definition.com.netiq = {\"name\":\"com.netiq\",\"level\":\"INFO\",\"additivity\":true,\"appenderRefs\":[\"WFCEF\"]}
workflow.logging.wfs.definition.com.sssw = {\"name\":\"com.sssw\",\"level\":\"INFO\",\"additivity\":true,\"appenderRefs\":[\"WFCEF\"]}
workflow.logging.wfs.definition.com.microfocus = {\"name\":\"com.microfocus\",\"level\":\"INFO\",\"additivity\":true,\"appenderRefs\":[\"WFCEF\"]}
-
-
Restart Tomcat services.
8.5 Authentication Reports Not Generated on Sentinel After Upgrade
Issue: Following the upgrade of OpenText Identity Manager to version 24.4 (v4.10), the Authentication by User and Authentication by server reports are not generated on Sentinel. This issue is observed on SUSE Linux Enterprise Server 15 SP5.
[OCTCR56A655281]
Workaround: Delete the existing data synchronization policy in Identity Manager Data Collection Service (idmdcs) and Sentinel Log Management for IGA, then create a new one. For more information about how to create a data synchronization policy, see Administrator Guide to Identity Reporting.
8.6 An Error Reported in the OpenText eDirectory Log File After Upgrade
Issue: After upgrading OpenText Identity Manager from version 4.9 to 24.4 (v4.10), users may encounter the following error in the ndsd.log file:
Loader Failed:for lib/opt/novell/eDirectory/lib64/nds-modules/libdxevent.so.3.so,error lib/opt/novell/eDirectory/lib64/nds-modules/libdxevent.so.3.so: cannot open shared object file: No such file or directory,errno 2
This issue is observed in the All-in-One server setup for OpenText Identity Manager on Linux. [OCTCR56A639009]
Workaround: The error does not affect any functionality. You can ignore it.
8.7 An Error During Non-root Installation of Engine
Issue: When installing the OpenText Identity Manager engine, non-root users may encounter the following error in the idminstall.log file:
novell-edirectory-xdaslog-9.3.0.0000-1error: lsetfilecon: (/opt/novell, system_u:object_r:usr_t:s0) Operation not permittederror: Plugin selinux: hook fsm_file_prepare failed########################################error: unpacking of archive failed on file /opt/novell: cpio: (error 0x2)error: novell-edirectory-xdaslog-9.3.0.0000-169.x86_64: install failed
This occurs when unpacking the novell-edirectory-xdaslog-<version> RPM at /opt/novell location fails because a non-root user does not have the required access to this directory.[OCTCR56A647216]
Workaround: The error does not affect any functionality. You can ignore it.
8.8 An Error Reported in the PostgreSQL Startup Log
Issue: When configuring Identity Applications and Identity Reporting components on PostgreSQL database, users may encounter the following errors in the startup logs:
[OCTCR56A662182]
Workaround: The error does not affect any functionality. You can ignore it.
8.9 An Error Reported in the Upgrade Log File
Issue: After upgrading OpenText Identity Manager to 24.4 (v4.10), users may encounter the following SSPR-related errors in the idmupgrade.log file:
ERROR password.pwm.util.cli.MainClass - 5083 ERROR_ENVIRONMENT_ERROR (unable to establish operating environment: file for option 'outputFile' at '/opt/netiq/idm/apps/sspr/sspr_data/SSPRConfiguration.xml' already exists)
[OCTCR56A662286]
Workaround: These error does not affect any SSPR functionality. You can ignore it.
8.10 An Error Reported in the Catalina Log File
Issue: After installing or upgrading to OpenText Identity Manager 24.4 (v4.10), users may encounter an error when starting Tomcat. The error is reported in the catalina.out log file.
[RPT-CORE] Error validating report configuration schema.com.netiq.persist.PersistenceException: java.lang.RuntimeException: Cannot use default schema name idm_rpt_cfg on Microsoft SQL Server because the login schema of the current user (dbo) is different and MSSQL does not support setting the default schema per session.
This issue occurs when the Identity Manager engine and Identity Reporting are configured in a distributed server setup on the MS SQL 2019 database. [OCTCR56A667011]
Workaround: The error does not affect any functionality. You can ignore it.
8.11 The DirXML Command-Line Utility Displays an Error After Upgrade
Issue: After upgrading OpenText Identity Manager to version 24.4 (v4.10), users may encounter the following LDAP error when launching the DirXML command-line utility:
Connection lost waiting for results from 10.71.142.57:636 (91) Connect Error javax.net.ssl.SSLException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-emp
This issue occurs when OpenText Identity Manager is configured to operate in the FIPS-enabled mode. [Issue: OCTCR56A669101]
Workaround: The error does not affect any functionality. You can ignore it.
8.12 An Error While Upgrading SSPR with Identity Applications
Issue: If Identity Applications and Self-Service Password Reset (SSPR) are on the same server, users may encounter an IO operation error during the upgrade of the SSPR service. This error can occur while upgrading from version 4.8.x to 24.4 (v4.10) on Linux. [OCTCR56A670098]
Workaround: The error does not affect any functionality. You can ignore it.
8.13 Invalid Keystore Format: An Error During Upgrade
Issue: While upgrading OpenText Identity Manager in the FIPS-enabled mode, users may encounter the following error while importing the reCAPTCHA public key certificate into the keystore:
keytool error: java.io.IOException: Invalid keystore format
[Issue: OCTCR56A671139]
Workaround: Import the public key certificate from the cacerts file into the idm.bcfks keystore by using the following command:
keytool -importkeystore -srckeystore /opt/netiq/common/jre/lib/security/cacerts -srcstorepass changeit -srcstoretype BCFKS -destkeystore /opt/netiq/idm/apps/tomcat/conf/idm.bcfks -deststorepass novell -deststoretype BCFKS -providerclass org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider -providerpath $CLASSPATH --noprompt
8.14 An Error Displayed During Identity Manager Engine Upgrade
Issue: While upgrading OpenText Identity Manager Engine in FIPS-enabled mode, users might encounter the following exception on Linux and Windows:
LDAPException: Error configuring LDAP SSL/TLS. (82) Local Errorjava.security.KeyStoreException: BCFKS not found
[Issue: OCTCR56A670109]
Workaround: The error does not affect any functionality. You can ignore it.
8.15 The Windows Installer Displays an Error
Issue: After installing OpenText Identity Manager 24.4 (v4.10) components, the following error is displayed on starting Tomcat: SEVERE [main] org.apache.catalina.util.LifecycleBase.handleSubClassException Failed to start component [Connector["ajp-nio-<IP_address>-8010"]]
This issue occurs during a fresh installation and after upgrading to OpenText Identity Manager 24.4 (v4.10). [Issue: OCTCR56A607041]
Workaround: It does not cause any functionality loss. However, if you want to resolve the issue, delete the following line in the server.xml file:
<Connector port="8010" protocol="AJP/1.3" redirectPort="8543"/>
The server.xml file is available in C:\NetIQ\idm\apps\tomcat\conf
8.16 The dirxml_remote and RLConsole Properties Display the Outdated Product Version
Issue: When you install or upgrade Remote Loader through the Identity_Manager_4.10.0_RL_Windows.iso or Identity_Manager_4.10.0_RL_Linux.iso, you might notice that the does not change in the window. It still shows . The same issue is seen in properties. [Issue: OCTCR56A608072]
Workaround: It does not impact the Remote Loader functionality. You can check the in the same window to confirm whether Remote Loader is installed successfully.
8.17 OpenText Identity Manager Does Not Reflect Changes Made to the Use SMTP TLS Option in OpenText Identity Console
Issue: While setting up an email server in OpenText Identity Console, if you enable or disable the notSMTPUseTLS attribute for the default notification template in the Tree View, the same value might not be available on the Email Based Approval page in OpenText Identity Manager. However, the selection is saved, and the email server is updated based on your preference.
This discrepancy happens because the notfSMTPUseTLS LDAP attribute is updated differently in Identity Applications and OpenText Identity Console. When you make the change in OpenText Identity Console, the attribute is updated directly. However, changing the value in of OpenText Identity Manager’s Email Based Approval page, it updates the com.netiq.rbpm.smtp.tls property in the ism-configuration.properties file. But, the value you select in OpenText Identity Console is still applied, even if it does not appear on the Email Based Approval page in OpenText Identity Manager. [Issue: OCTCR56A585739]
Workaround: To ensure consistent behavior, you can modify the value in the option on Identity Manager’s Email Based Approval page based on the value you select in Identity Console.
8.18 Organization Chart Buttons for a Level 2 or Higher Relationship Hierarchy Is Missing
Issue: For a level 2 or higher relationship, the organization chart does not show the options to choose a relationship for viewing, navigate to the next level in the relationship hierarchy, send emails, and view more information about that entity. This issue is seen when the hierarchical depth in the is set to a level 2 (or higher). [Issue: OCTCR56A585426]
Workaround: To view the organization chart buttons for the level 2 (or higher) relationship, search for the level 2 user/entity in the organization chart.
8.19 Remote Loader Reports Invalid Driver Object Password After Upgrade
Issue: After upgrading Remote Loader to version 24.4 (v4.10) on Windows, it is unable to connect to the Active Directory driver using the basic authentication password. [Issue: OCTCR56A584022]
Workaround: After upgrading Identity Manager to 24.4 (v4.10), perform the following steps:
-
Stop the Remote Loader instance on the Remote Loader server.
-
Reset the driver object password and the Remote Loader password.
-
Start the Remote Loader instance for the Active Directory driver.
8.20 Observing Error: StatusLogger Reconfiguration Failed in Catalina Log File
Issue: After installing OpenText Identity Manager 24.4 (v4.10) on Windows, you might encounter the following error in catalina.out logs:
ERROR StatusLogger Reconfiguration failed: No configuration found for '<xxxxxxxx>' at 'null' in 'null'
[Issue: OCTCR56A584800]
Workaround: The error does not affect any functionality. You can ignore it.
8.21 Form Builder Issues
You might encounter the following issues while working with JSON forms in Form Builder:
Field Validation Messages Lack Clarity
Issue: Form field validation messages notify users when they enter an invalid or unacceptable value into a field. These messages typically consist of a key-value pair, with the value intended for user display. However, in this release, the form fields display keys rather than the corresponding values. For example, entering an invalid email address presents invalid_email instead of Email must be a valid email.
[Issue: OCTCR56A598009]
Workaround: To add the messages in English:
-
Launch Form Builder.
-
Click the
icon. -
Click to expand.
-
Add a trailing comma and the key-value pairs for the messages to the last line.
For example,
{ "Submit": "", "error": "Please fix the following errors before submitting.", "invalid_date": "{{field}} is not a valid date.", "invalid_email": "{{field}} must be a valid email.", "invalid_regex": "{{field}} does not match the pattern {{regex}}.", "mask": "{{field}} does not match the mask.", "max": "{{field}} cannot be greater than {{max}}.", "maxLength": "{{field}} must be shorter than {{length}} characters.", "min": "{{field}} cannot be less than {{min}}.", "minLength": "{{field}} must be longer than {{length}} characters.", "next": "Next", "pattern": "{{field}} does not match the pattern {{pattern}}", "previous": "Previous", "required": "{{field}} is required" } -
Click .
Form Builder Hangs While Scrolling
Issue: The form builder occasionally freezes while scrolling through the JSON forms in and views. This issue is observed in two scenarios:
-
While working with a JSON form that contains many functions and methods.
-
When your screen resolution differs from the system-recommended value.
[Issue: OCTCR56A602415]
Workaround: There is no workaround is available. You can relaunch Form Builder.
The Button Component Does Not Work
Issue: After upgrading to Designer 4.9, the Button component in JSON forms does not work for approve and request actions. [Issue: OCTCR56A604329]
Workaround: Perform the following steps:
-
Go to the Button component’s tab.
-
Copy the logic specified in the or fields.
-
Change the to custom.
-
Specify the logic copied from Step 2.
-
Click .
Tree Component Issues
You might encounter the following issues with the Tree component in Form Builder:
-
The fields display a nonarray validation error in the form . This error occurs when the Tree component is set to display a default value. You cannot submit the form until you resolve the validation error. [Issue: OCTCR56A585664]
To resolve the error, change the default value with ID of that field in the view.
-
The expand functionality of a Tree component does not work as expected. The form does not allow you to expand or select a sub-container.
-
When you select a container or sub-container, the field displays the dn value instead of name.
The following is a sample data from the Tree component:
{ "dn": "unique id", "name": "container data", "data": "any meta-data attached with the container", "subContainers": [ { "dn": "id1", "name": "container data1", "icon": "glyphicon glyphicon-cloud" }, { "dn": "id2", "name": "container data2", "data": "any meta-data attached with the container", "subContainers": [ { "dn": "id3", "name": "container data3", "icon": "glyphicon glyphicon-cloud" } ] } ] }When you select the option in the , the field displays the unique id instead of the container data. [Issue: OCTCR56A603396]