diff options
| author | Stefan Metzmacher <metze@samba.org> | 2019-10-22 12:12:32 +0200 |
|---|---|---|
| committer | Andrew Bartlett <abartlet@samba.org> | 2019-10-24 09:46:28 +0000 |
| commit | 6d43d82b49c8cd47da2f1489fe8b52d5a873a19c (patch) | |
| tree | 17b08f868593f26aac9ae544efffadd9fc82e9c7 /selftest | |
| parent | 9471508391fd3bcf199b1e94f8d9ee2b956e8f8e (diff) | |
| download | samba-6d43d82b49c8cd47da2f1489fe8b52d5a873a19c.tar.gz | |
s4:tests/dirsync: add tests for dirsync with extended_dn
This demonstrates a problems that the extended_dn returned
by the dirsync module always uses the SDDL format for GUID/SID
components.
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
Signed-off-by: Stefan Metzmacher <metze@samba.org>
Reviewed-by: Andrew Bartlett <abartlet@samba.org>
Diffstat (limited to 'selftest')
| -rw-r--r-- | selftest/knownfail.d/dirsync_extended_dn | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/selftest/knownfail.d/dirsync_extended_dn b/selftest/knownfail.d/dirsync_extended_dn new file mode 100644 index 00000000000..0ef6ea56391 --- /dev/null +++ b/selftest/knownfail.d/dirsync_extended_dn @@ -0,0 +1 @@ +^samba4.ldap.dirsync.python.*.__main__.ExtendedDirsyncTests.test_dirsync_extended_dn |