Getting "failed to decode LDAP controls" messages while using bind-dyndb-ldap

Issue

When using the LDAP driver for BIND ( bind-dyndb-ldap ) with RHDS, it might fail with the following error messages:

In the RHDS access log:

# grep "failed to decode LDAP controls"  /var/log/dirsrv/slapd-<INSTANCE_NAME>/access | tail -3
[10/Jul/2018:15:41:24.905941241 +0200] conn=11 op=1 SRCH base="(null)" scope=2 filter="(|(objectClass=idnsConfigObject))", failed to decode LDAP controls
[10/Jul/2018:15:42:24.908102959 +0200] conn=12 op=1 SRCH base="(null)" scope=2 filter="(|(objectClass=idnsConfigObject))", failed to decode LDAP controls
[10/Jul/2018:15:43:24.910949632 +0200] conn=13 op=1 SRCH base="(null)" scope=2 filter="(|(objectClass=idnsConfigObject))", failed to decode LDAP controls
#

In the /var/log/messages file:

Jul 10 15:41:24 <HOST> named[17159]: LDAP error: Critical extension is unavailable: unable to start SyncRepl session: is RFC 4533 supported by LDAP server?
Jul 10 15:41:24 <HOST> named[17159]: LDAP configuration synchronization failed: socket is not connected
Jul 10 15:41:24 <HOST> named[17159]: ldap_syncrepl will reconnect in 60 seconds
Jul 10 15:42:24 <HOST> named[17159]: successfully reconnected to LDAP server
Jul 10 15:42:24 <HOST> named[17159]: LDAP error: Critical extension is unavailable: unable to start SyncRepl session: is RFC 4533 supported by LDAP server?
Jul 10 15:42:24 <HOST> named[17159]: LDAP configuration synchronization failed: socket is not connected
Jul 10 15:42:24 <HOST> named[17159]: ldap_syncrepl will reconnect in 60 seconds