Chapter 4. Red Hat Directory Server 12.4

Learn about important updates and new features, known issues, and bug fixes implemented in Directory Server 12.4.

4.1. Important updates and new features in the 389-ds-base package

Important updates in Red Hat Directory Server 12.4 that are included in the 389-ds-base package are documented in Red Hat Enterprise Linux 9.4 Release Notes:

4.2. Bug fixes

Learn about bugs fixed in Red Hat Directory Server 12.4 that have a significant impact on users.

Directory Server now flushes the entry cache less frequently

Previously, Directory Server flushed its entry cache even when it was not necessary. As a result, in certain situations, Directory Server was unresponsive and had bad performance. With this update, Directory Server flushes the entry cache only when it is necessary.

(BZ#2234613)

The web console no longer changes attribute names to lowercase characters when attributeTypes are added

Previously, when you added an attribute to an object class by using the web console, the uppercase characters in the attribute name were changed to lowercase characters. With this update, the attribute name case is no longer changed.

(BZ#2236181)

Directory Server 12.4 bug fixes that are included in the 389-ds-base package are documented in Red Hat Enterprise Linux 9.4 Release Notes:

4.3. Known issues

Learn about known problems and, if applicable, workarounds in Directory Server 12.4.

Directory Server web console does not automatically update settings that are changed outside the web console

Because of the design of the Directory Server module in the Red Hat Enterprise Linux 8 web console, the web console does not automatically display the latest settings if you change the configuration outside of the console window. For example, if you change the configuration using the command line while the web console is open, the new settings are not automatically updated in the web console. This applies also if you change the configuration by using the web console on a different computer.

To work around the problem, manually refresh the web console in the browser if the configuration was changed outside the console window.

(BZ#1654281) (BZ#1751047)

Directory Server can import LDIF files only from /var/lib/dirsrv/slapd-instance_name/ldif/

Since RHEL 8.3, Red Hat Directory Server (RHDS) uses its own private directories, and the PrivateTmp systemd directive is enabled by default for the LDAP services. As a result, RHDS can only import LDIF files from the /var/lib/dirsrv/slapd-instance_name/ldif/ directory. If the LDIF file is stored in a different directory, such as /var/tmp, /tmp, or /root, the import fails with an error similar to the following: 

Could not open LDIF file "/tmp/example.ldif", errno 2 (No such file or directory)

To work around this problem, complete the following steps:

  1. Move the LDIF file to the /var/lib/dirsrv/slapd-instance_name/ldif/ directory: 

    # mv /tmp/example.ldif /var/lib/dirsrv/slapd-instance_name__/ldif/

  2. Set permissions that allow the dirsrv user to read the file: 

    # chown dirsrv /var/lib/dirsrv/slapd-instance_name/ldif/example.ldif

  3. Restore the SELinux context: 

    # restorecon -Rv /var/lib/dirsrv/slapd-instance_name/ldif/

For more information, see the solution article LDAP Service cannot access files under the host’s /tmp and /var/tmp directories.

(BZ#2075525)

Known issues in the 389-ds-base package

Red Hat Directory Server 12.4 known issues that affect 389-ds-base package are documented in Red Hat Enterprise Linux 9.4 Release Notes: