OpenText™ Identity Manager CE 24.4 (v4.10) Designer Release Notes

January 2025

OpenText™ Identity Manager CE 24.4 (v4.10) Designer includes new features, 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 Micro Focus 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 Identity Manager Documentation Website.

For more information about this release and for the latest release notes, see the OpenText Identity Manager Documentation Website.

To download this product, see the Software License and Download portal.

1.0 What’s New?

This release includes the following enhancements:

1.1 Supported Operating System

This release adds support for Red Hat Enterprise Linux (RHEL) 9.4.

1.2 Latest Driver Packages Available

This release includes the latest driver packages. You can upgrade any package installed in your OpenText Identity Manager environment if a newer version of the package is available. This release also includes the SAP HANA driver package.

1.3 Support for TLSv1.3

This release adds support for TLSv1.3. When you install Designer, communication will occur using TLSv1.3, while support for TLSv1.2 will still be available.

NOTE:You must install the following OpenText Identity Manager components for TLSv1.3 communication:

  • OpenText™ Identity Manager 24.4 (v4.10) Designer

  • OpenText™ eDirectory 24.4 (v9.3)

  • Identity Manager Engine 4.10

2.0 System Requirements

For information about hardware requirements and supported operating systems, see the System Requirements for OpenText™ Identity Manager CE 24.4 (v4.10) document.

3.0 Installing Designer 24.4 (v4.10)

IMPORTANT:You must install Designer 24.4 (v4.10) with OpenText Identity Manager 24.4 (v4.10). Previous Designer versions are not compatible. However, Designer 24.4 (v4.10) can be used with Identity Manager 4.8.x and 4.9.

After you purchase OpenText Identity Manager 24.4 (v4.10), log in to the Software License and Download portal and follow the link to download the software. The following files are available for download:

File Name

Description

Identity_Manager_4.10.0_Designer_Linux.tar.gz

Contains Designer for Linux

Identity_Manager_4.10.0_Designer_Windows.zip

Contains Designer for Windows

Identity_Manager_4.10.0_Designer_MacOSX.dmg

Contains Designer for Mac

The OpenText Identity Manager components must be installed in a specific order. Review the installation prerequisites and considerations before installing Designer.

This release does not support:

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

4.1 The Designer Splash Screen Is Inverted

Issue: When you launch Designer on a Mac running on macOS Sonoma, you might notice an inverted splash screen. (Issue: OCTCR56A585814)

Workaround: This issue is only observed on macOS Sonoma and does not affect the functionality of Designer. Therefore, you can safely ignore it.

4.2 Provisioning Request Definition’s Compare Does Not Show Form Dependencies for a New JSON Form

Issue: When Provisioning Request Definition (PRD) is associated with a new JSON form, the Compare feature does not display form dependencies. This happens when Compare > Reconcile operation is used for deploying the PRD, changes in the form fields does not get deployed.

Workaround: Use the Deploy feature to see the form dependencies and to deploy the changes made in the form.

4.3 PRD Does Not Get Updated When the Select Form Field Is Changed from Single to Multiple Value

Issue: In Form Builder, if you modify an attribute of a field, the change is not reflected in the PRD. For example, if you change the Select field from a single value to a multiple value, the PRD in the text editor shows target-type="single-value":

<data-item
                data-type="string" name="select2"
                target="flowdata.Start/selectfieldrequest/select2"
                target-type="single-value"/>

Workaround: Update the target-type to multi-value-list in the PRD by performing the following steps:

  1. Go to the PRD view and click the activity associated with the form. This updates the target-type="multi-value-list" for the Select field.

  2. Save and deploy the PRD.

4.4 Encountering an Issue When Using the token-map Verb in a Designer Project

Issue: When a token-map verb is used in a project that contains the src attribute, the project does not work as expected when you try to edit the mapping from Designer. This issue is observed because the src attribute is no longer supported.

Workaround: To work around this issue, perform the following steps:

  1. Log in to Designer.

  2. Navigate to the policy containing the token-map verb.

  3. Navigate to the XML Source tab.

  4. Modify all the occurrences of the src attribute to source manually.

  5. Save the policy.

  6. Deploy the changes.

4.5 Policy Validation in Designer Results in Multiple Errors

Issue: When you validate a policy in Designer, the project checker displays incorrect errors. Errors such as A '(' character or an element type is required in the declaration of element type if-dest-attr and error against valid policies from REST, SAP, AD and other drivers are reported. (Issue: OCTCR56A580475)

Workaround: Manually modify if-dest-attr and if-src-attr attributes in dirxmlscript4.8.3.dtd document available at the DTD location. For example: C:\NetIQ\IDM\apps\Designer\plugins\com.novell.idm.policybuilder_4.0.0.202102182056\DTD\dirxmlscript4.8.3.dtd

In the dirxmlscript4.8.3.dtd document search and replace below attribute rules:

  • <!ELEMENT if-dest-attr (((arg-dn | arg-association),( value? | component* ))? | (#PCDATA | component)*)> to <!ELEMENT if-dest-attr (#PCDATA | component | arg-dn | arg-association | value)*>

  • <!ELEMENT if-src-attr (((arg-dn | arg-association),( value? | component* ))? | (#PCDATA | component)*)> to <!ELEMENT if-src-attr (#PCDATA | component | arg-dn | arg-association | value)*>

4.6 Field Validation Messages Do Not Convey the Message Clearly

For more information about this Form Builder issue, see Field Validation Messages Lack Clarity.

4.7 Tree Component Issues

For issues related to the Tree component, see Tree Component Issues.

4.8 Live Server Update Retrieves Incorrect Version of OpenText Identity Manager

Issue: The live update icon on the server properties page display the OpenText Identity Manager version incorrectly. When importing a project from Identity Manager 4.9 to Designer 4.10, it shows the version as 4.10 instead of 4.9. (Issue: OCTCR56A686063)

It does not cause any functionality loss.

5.0 Contacting OpenText

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

Additional technical information or advice is available from several sources: