[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: ldapsearch vs AD output

To: Cherubini Enrico <bestkevin@gmail.com>
Subject: Re: ldapsearch vs AD output
From: Michael Ströder <michael@stroeder.com>
Date: Sat, 24 Oct 2009 01:45:46 +0200
Cc: openldap-technical@openldap.org
In-reply-to: <32222ace0910231149m2ea491dax24a809d501c38319@mail.gmail.com>
References: <32222ace0910231149m2ea491dax24a809d501c38319@mail.gmail.com>
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.23) Gecko/20090823 SeaMonkey/1.1.18

Cherubini Enrico wrote:
> Good day,
> hope to be not OT. I have to get members of a group in AD, so here is
> what I do and what I get:
> 
> ldapsearch -x -D "pippo@dominio.com <mailto:pippo@dominio.com>" -w
> pippopw "cn=groupname"
> 
> member:: W049X1MgVmlhPPAaXTDoCxPVT1fQSBNYW51dGOOOemlvbmUgZSBHZXN0aW9uZSBQYX=
> Rya
>  W1vbmlvLERDPXByb3ZpbmNpYSxEQz12cixEQz1pdA=3D=3D
> member: CN=_SubGroup2,OU=_SubGroupArea,DC=dominio,DC=com
> 
> If I do a search whith phpldapadmin I get both name (_SubGroup1 and
> _SubGroup2), so I guess the problem is how ldapsearch handles the output
> from AD server or in config file, but can't find a solution.

Note that with LDIF :: indicates that the value is base64-encoded in the LDIF
representation (not the value received) because LDIF is meant to be
ASCII-clean. See RFC 2849 on how to interpret LDIF correctly.

Ciao, Michael.

References:
- ldapsearch vs AD output
  - From: Cherubini Enrico <bestkevin@gmail.com>

Prev by Date: Re: Using Arbitrary X509 certificates for LDAPS authentication
Next by Date: Re: Using Arbitrary X509 certificates for LDAPS authentication
Index(es):
- Chronological
- Thread