Re: SASL response is not a SASL BindRequest

[Jens V. <je...@zo...>]

i think the last time i checked CommuniGate did not have a complete=20
LDAP server implementation. this might have changed, but when we tried=20=

to use the communigate LDAP server internally for LDAP purposes we=20
quickly came against limitations and decided to use OpenLDAP instead.

jens


On Sunday, Mar 23, 2003, at 08:50 US/Eastern, Michael Str=F6der wrote:

> Stuart Bishop wrote:
> >
> > I'm getting stuck with SASL authentication - I believe my code is
> > correct so
> > I'd like to get an opinion on if the bug lies with my code,=20
> python-ldap
> > pre6
> > or CommuniGate Pro (the LDAP server). I can bind using =
bind_simple_s.
>
> Are you sure that CommuniGate Pro is an LDAPv3 server and supports=20
> SASL bind? Can you please check the rootDSE for attributes=20
> supportedSASLMechanisms.
>
> >     login_dn =3D 'uid=3Dzen,cn=3Dcommongroundpublishing.com,o=3DCommon=
=20
> Ground'
> >     password =3D 'secret'
> >
> >     l =3D ldap.open('localhost')
> >     auth =3D ldap.sasl.digest_md5(login_dn,password)
>
> Note that a SASL user name is normally something like uid@realm.
>
> Ciao, Michael.
>