SASL response is not a SASL BindRequest

[Jens Vagelpohl]

i think the last time i checked CommuniGate did not have a complete 
LDAP server implementation. this might have changed, but when we tried 
to use the communigate LDAP server internally for LDAP purposes we 
quickly came against limitations and decided to use OpenLDAP instead.

jens


On Sunday, Mar 23, 2003, at 08:50 US/Eastern, Michael Ströder 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, 
> 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 
> SASL bind? Can you please check the rootDSE for attributes 
> supportedSASLMechanisms.
>
> >     login_dn = 'uid=zen,cn=commongroundpublishing.com,o=Common 
> Ground'
> >     password = 'secret'
> >
> >     l = ldap.open('localhost')
> >     auth = ldap.sasl.digest_md5(login_dn,password)
>
> Note that a SASL user name is normally something like uid at realm.
>
> Ciao, Michael.
>