[Samba] LdapSearch returns a user first instead of the domain base

[Olivier BILHAUT]

Hi Rowland, 

Thanks for your opinion about this. 

Since the dev works
for one of the world biggest company of the sector, he will never change
it's client behavior for us. 

He will not admit that he's dev isn't
very "resilient" and "compatible". 

That's unfortunate for us and I
will continue to defend good devs against tourists. 

Thanks for good
work and support. 

Cheers, 

Olivier B. 

Le 2021-09-28 18:21, Rowland
Penny via samba a écrit :

> On Tue, 2021-09-28 at 17:43 +0200, Olivier
BILHAUT wrote:
>> I Rowland,
>> Thanks for quick reply.
>> 
>> An
exemple of ldapsearch could be :
>> ldapsearch -h PDC.domain.local -x -W
-D "administrator at FHM.LOCAL" -b
>> "DC=FHM,DC=local"
>> 
>> Returns with
Samba :
>> 
>> # extended LDIF
>> #
>> # LDAPv3
>> # base
<DC=FHM,DC=local> with scope subtree
>> # filter: (objectclass=*)
>> #
requesting: ALL
>> #
>> 
>> # Firstname LASTNAME, ou1, Users,
domain.local
>> dn: CN=Firstname
LASTNAME,OU=ou1,OU=Users,DC=domain,DC=local
>> objectClass: top
>>
objectClass: person
>> objectClass: organizationalPerson
>> objectClass:
user
>> CN: Firstname LASTNAME
>> [...]
>> 
>> And returns on Microsoft
AD :
>> # extended LDIF
>> #
>> # LDAPv3
>> # base <DC=FHM,DC=local>
with scope subtree
>> # filter: (objectclass=*)
>> # requesting: ALL
>>
#
>> dn: DC=domain,DC=local
>> objectClass: top
>> objectClass:
domain
>> objectClass: domainDNS
>> instanceType: 5
>> whenCreated:
20120613130158.0
>> [...]
>> 
>> Our dev relies on the first element
returned to grab the domain.
>> Our version is Samba 4.14.3.
>>
Thanks,
>> Olivier B
>> 
> 
> I see what you mean, I didn't know that
windows responded in that way,
> there must be something on the windows
end to 'sort' the results before
> printing them, code that Samba does
not have.
> 
> As this is Unix, there are numerous other ways of
obtaining the
> 'domain' name (by which, I think you mean the netbios
domain name, aka
> 'workgroup').
> 
> Rowland