5.4. Known Issues

Important

Note that this document only contains release notes for features which are not available in the base Red Hat Enterprise Linux 7.3 release. Many of the new features and bug fixes in Red Hat Directory Server are in the 389-ds-base package, and those are documented in Red Hat Enterprise Linux 7.3 Release Notes.
The following are some of the most important known issues in Directory Server 10.1. If applicable, supported workarounds are also described.

The Directory Server Console is not able to connect to all instances in multi-homed environments

The Directory Server Console is only able to connect to the first instance, if all of the following conditions are met:
  • Multiple Directory Server instances are installed on one host.
  • Each instance is bound to a different local network interface.
  • All instances use the same port number, such as 389.
To work around the problem, run the Directory Server instances on different ports.
For further details, see the corresponding section in the Red Hat Directory Server 10 Installation Guide.

Directory Server Console logins fail using the uid value

The Directory Server Console enables users to log in using the full distinguished name (DN) or the value of the uid attribute of an account. When using the uid value to log in, the Directory Server Console performs an anonymous bind to locate the entry matching the value. As a consequence, if anonymous binds are disabled, the Directory Server Console is unable to locate the entry, and logging in using the uid value fails. To work around this problem, enter the full DN in the user name field and as a result, logins work like expected.

Stopping and starting a remote Admin Server fails when SELinux is enabled

Due to a limitation of systemd, Admin Express and the Directory Server Console fails to start or stop the Admin Server on remote hosts running SELinux in enforcing mode. To work around the problem, start and stop the Admin Server on the host that is running the service.