Chapter 11. Red Hat Directory Server 12.1
Learn about new system requirements, highlighted updates and new features, known issues, and deprecated functionality implemented in Directory Server 12.1.
11.1. Highlighted updates and new features Copy linkLink copied to clipboard!
This section documents new features and important updates in Directory Server 12.1.
Directory Server 12.1 rebased to upstream version 2.1.3
Directory Server 12.1 is based on upstream version 2.1.3 which provides a number of bug fixes and enhancements over the previous version. For a complete list of notable changes, read the upstream release notes before updating:
The LDAP browser is now fully supported
With this enhancement, you can manage LDAP entries from the LDAP Browser tab in the web console. For example, you can:
- Browse the directory using Tree or Table view.
- Manage entries, such as users, groups, roles, organizational units (OUs), and custom entries.
- Manage Access Control Instructions (ACIs).
- Manage classes of service definition (CoS).
- Search for entries.
Highlighted updates and new features in the 389-ds-base package
Features in Red Hat Directory Server, that are included in the 389-ds-base package, are documented in the Red Hat Enterprise Linux 9.1 Release Notes:
-
Directory Server now supports recursive delete operations when using
ldapdelete - You can now set basic replication options during the Directory Server installation
- Directory Server now supports canceling the Auto Membership plug-in task
- Directory Server now supports instance creation by a non-root user
- Replication changelog trimming is now enabled by default in Directory Server
11.2. Known issues Copy linkLink copied to clipboard!
This section documents known problems and, if applicable, workarounds in Directory Server 12.1.
Directory Server can import LDIF files only from /var/lib/dirsrv/slapd-instance_name/ldif/
The dsconf backend import command requires that you specify the path to the LDIF file you want to import. However, due to file system and SELinux permissions, as well as other operating system restrictions, Directory Server 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, 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:
Move the file to the /var/lib/dirsrv/slapd-instance_name/ldif/ directory:
# mv /tmp/example.ldif /var/lib/dirsrv/slapd-instance_name/ldif/Set permissions that allow the
dirsrvuser to read the file:# chown dirsrv /var/lib/dirsrv/slapd-instance_name/ldif/example.ldifRestore the SELinux context:
# restorecon -Rv /var/lib/dirsrv/slapd-instance_name/ldif/
(BZ#2081352)
Directory Server replication fails after changing password of the replication manager account
After a password change, Directory Server does not properly update the password cache for the replication agreement. As a consequence, when you change the password for the replication manager account, the replication breaks. To work around this problem, restart the Directory Server instance. As a result, the cache is rebuilt at start-up, and the replication connection binds with the new password instead of the old one.
(BZ#1956987)
Known issues in the 389-ds-base package
Known issues in Red Hat Directory Server, that are included in the 389-ds-base package, are documented in the Red Hat Enterprise Linux 9.1 Release Notes:
Deprecated functionality in the 389-ds-base package
Red Hat Directory Server deprecated functionality that has been removed from the 389-ds-base package is documented in the Red Hat Enterprise Linux 9.1 Release Notes: