s3: Fix EnumDomainAliases when no aliases are in LDAP
commit1fc9f1489507058ae351ba68d7963db0dd0e6cd3
authorVolker Lendecke <vl@samba.org>
Thu, 10 Jun 2010 13:40:14 +0000 (10 15:40 +0200)
committerKarolin Seeger <kseeger@samba.org>
Thu, 13 Jan 2011 16:58:49 +0000 (13 17:58 +0100)
tree83dd72fc73e2ac96b405a2313add86f2579305cc
parent3633fad4422a1e9f5852bd552a2fb62a444fbd21
s3: Fix EnumDomainAliases when no aliases are in LDAP

We used to return NT_STATUS_ACCESS_DENIED, now we just return 0 entries, just
like W2k8 does.

usrmgr.exe was pretty unhappy with the NT_STATUS_ACCESS_DENIED
(cherry picked from commit f66cc827096c53d4d16b8c850c83a3b5664e9725)

Fix bug #7262 (Unable to maintain users' groups via UsrMgr).
(cherry picked from commit 1439a1d7ff406dd5dce885100349751151c14bf6)
(cherry picked from commit bd6a48e687636d5d9489129faff00e45d50d0d31)
source3/passdb/pdb_ldap.c