s4:dirsync: fix interaction of dirsync and extended_dn controls
authorStefan Metzmacher <metze@samba.org>
Fri, 4 Oct 2019 12:57:40 +0000 (14:57 +0200)
committerKarolin Seeger <kseeger@samba.org>
Tue, 5 Nov 2019 10:07:28 +0000 (10:07 +0000)
commit7e0d00eaa69e9a2aefacd5baabb2b5279a84e2d5
treeb5a642371f6f8bb7d658dd250e2ca96a1e67a9e1
parent328f89cb9b86cc4312c23c043674c9f91f972c60
s4:dirsync: fix interaction of dirsync and extended_dn controls

Azure AD connect reports discovery errors:
  reference-value-not-ldap-conformant
for attributes member and manager.
The key is that it sends the LDAP_SERVER_EXTENDED_DN_OID without
an ExtendedDNRequestValue blob, which means the flag value should
be treated as 0 and the HEX string format should be used.

BUG: https://bugzilla.samba.org/show_bug.cgi?id=14153
RN: Prevent azure ad connect from reporting discovery errors:
reference-value-not-ldap-conformant

Signed-off-by: Stefan Metzmacher <metze@samba.org>
Reviewed-by: Andrew Bartlett <abartlet@samba.org>
Autobuild-User(master): Andrew Bartlett <abartlet@samba.org>
Autobuild-Date(master): Thu Oct 24 11:06:58 UTC 2019 on sn-devel-184

(cherry picked from commit d0f566c4ad32d69a1cf896e2dde56fc2489bb7fc)
selftest/knownfail.d/dirsync_extended_dn [deleted file]
source4/dsdb/samdb/ldb_modules/dirsync.c