NetIQ eDirectory 9.2 Service Pack 9 Release Notes

January 2024

NetIQ eDirectory 9.2 SP9 resolves several previous issues. 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 our products meet all your needs. You can post feedback in the eDirectory Community Support Forums, our community Web site that also includes product notifications, blog, and product user groups.

For a full list of all issues resolved in NetIQ eDirectory 9.x, including all patches and service packs, refer to KM000010604.

For more information about this release and for the latest release notes, see the Documentation Web site. To download this product, see the Product Upgrade Web site.

1.0 What’s New?

eDirectory 9.2 SP9 provides the following enhancements and fixes in this release:

1.1 Operating System Support

In addition to the platforms supported in previous releases of eDirectory, this release adds support for the following operating system:

  • Red Hat Enterprise Linux (RHEL) 8.8, 8.9, 9.2, and 9.3

  • SUSE Linux Enterprise Server (SLES) 15 SP5

  • Red Hat Universal Base Image 9.3 (for containers)

1.2 Fixed Issues

eDirectory 9.2 SP9 includes the following software fixes that resolve several previous issues:

cn=monitor Not Showing Checkpoint Runtime in 927

Fix: cn=monitor search does not display the checkpoint's runtime. Valid start time is displayed while performing a cn=monitor search.(Defect: 639100)

Running tsands Backup From OES is fixed

Fix: The tsands closes all the open connections without causing any connection leak. (Defect: 377287)

Configuring Product SAS is Improved

Fix: Creating a new tree needs /etc/hosts to have IP address which is successfully handled in container. (Defect: 587047)

Login to Port 8030 From edirutil Works as Expected

Fix: eDirectory schema has been enhanced so that login to port 8030 from edirutil works with the OES and java.(Defect: 633006)

Customer Correlation ID Corrected

Fix: The driver assigns a unique correlation ID during the start-work-flow action. (Defect: 742001)

NICI with NDSD Works as Expected

Fix: eDirectory code is improved to manage NICI context and locks to prevent crashes in function. (Defect: 579215)

LDAP Query to Find Records with an Integer 64 Attribute Provides Required Results

Fix: The Integer64 type numbers in the FLAIM database have been fixed. The FLAIM database now reconstructs numbers from big-endian format for each query. (Defect:648072)

2.0 System Requirements

For information about prerequisites, hardware requirements, and supported operating systems, see the NetIQ eDirectory Installation Guide.

3.0 Installing or Upgrading

To upgrade to eDirectory 9.2 SP9, you need to be on eDirectory 8.8.8.x or 9.x. For more information on upgrading eDirectory, see the NetIQ eDirectory Installation Guide.

NOTE:You must upgrade your Identity Manager before using this version of eDirectory. For more information on the version compatibility see, Identity Manager Component Versions table in the System Requirements for Identity Manager 4.8x.

4.0 Known Issues

NetIQ Corporation 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 Warning Message 'No Version Information Available (Required by ndstrace)' in NDS Utilities

Issue: The ncurses library in the RHEL operating system does not provide version information.

Workaround: There is no workaround at this time. However, there is no functionality loss.

5.0 Additional Documentation

5.1 Identity Console

For more information on Identity Console, see Identity Console documentation page.

5.2 Novell International Cryptographic Infrastructure (NICI)

The NICI Administration Guide is included in the eDirectory documentation page.

5.3 eDirectory Issues on Open Enterprise Server

For more information on eDirectory issues on Open Enterprise Server (OES), see OES Readme.