For what's it worth, this was pulled into it's own bug report because the current implementation leaks information when using LDAP credentials to do anything. For example, if a user does something that requires a connection to LDAP, but the connection credentials are wrong, then the end user will see that information.
For what's it worth, this was pulled into it's own bug report because the current implementation leaks information when using LDAP credentials to do anything. For example, if a user does something that requires a connection to LDAP, but the connection credentials are wrong, then the end user will see that information.