python-ldap-dev

Re: SASL response is not a SASL BindRequest

[<mi...@st...>]

Stuart Bishop wrote:
> 
> Traceback (most recent call last):
>   File "tldap.py", line 54, in ?
>     l.sasl_bind_s(login_dn,auth)
>   File  "/usr/local/stow/python-2.3/lib/python2.3/site-packages/ldap/ 
> ldapobject.py", line 162, in sasl_bind_s
>     return self._ldap_call(self._l.sasl_bind_s,who,auth)
>   File  "/usr/local/stow/python-2.3/lib/python2.3/site-packages/ldap/ 
> ldapobject.py", line 94, in _ldap_call
>     result = apply(func,args,kwargs)
> ldap.LOCAL_ERROR: {'desc': 'Local error'}

I think I found the error. Do you have by any chance (like me) a library mix 
of Cyrus-SASL 1.x and 2.x on your system?

This issue can be solved by editing setup.cfg and using setup.py checked in 
recently. I've tested it against the test server you mentioned in a personal 
e-mail.

Please bring your CVS working tree in sync and test!

Ciao, Michael.

Re: SASL response is not a SASL BindRequest

[Stuart B. <stu...@co...>]

Finally got a chance to get back onto this... sorry if anyone was=20
waiting.

On Saturday, April 12, 2003, at 02:44  AM, Michael Str=F6der wrote:

> I think I found the error. Do you have by any chance (like me) a=20
> library mix of Cyrus-SASL 1.x and 2.x on your system?

I might have on one of the original test machines (old laptop since=20
upgraded).
Current test box is OSX 10.2.5 with:
		cyrus-sasl-2.1.12 (installed via fink package manager)
		openldap 2.1.16 (installed via fink package manager)

Out of the OSX box I'm getting:

Traceback (most recent call last):
   File "t.py", line 10, in ?
     l.sasl_bind_s("", auth)
   File "/sw/lib/python2.3/site-packages/ldap/ldapobject.py", line 157,=20=

in sasl_bind_s
     return self._ldap_call(self._l.sasl_bind_s,who,auth)
   File "/sw/lib/python2.3/site-packages/ldap/ldapobject.py", line 87,=20=

in _ldap_call
     result =3D apply(func,args,kwargs)
ldap.AUTH_UNKNOWN: {'info': 'SASL(-4): no mechanism available: No=20
worthy mechs found', 'desc': 'Unknown authentication method'}

I've also got a Redhat 7.2 box I can test from, but the RPM installed
OpenLDAP is coredumping when I attempt to SASL auth against the ldap
server, so I don't think python-ldap has much chance :-)

Test script is just Demo/sasl_bind.py with a tweaked LDAP URL and=20
password.

--=20
Stuart Bishop <ze...@sh...>
http://shangri-la.dropbear.id.au/

Re: SASL response is not a SASL BindRequest

[<mi...@st...>]

Stuart Bishop wrote:
> Out of the OSX box I'm getting:
 > [..]
> ldap.AUTH_UNKNOWN: {'info': 'SASL(-4): no mechanism available: No worthy 
> mechs found', 'desc': 'Unknown authentication method'}

A wild guess: The SASL plugin libs on this box are not found...

> I've also got a Redhat 7.2 box I can test from, but the RPM installed
> OpenLDAP is coredumping when I attempt to SASL auth against the ldap
> server,

This sounds like a library mix. You have to build python-ldap with exactly 
the libs the OpenLDAP client libs were built with. Check with ldd _ldap 
which shared libs are dynamically linked.

See output of ldd _ldap on my box.

$ ldd /usr/lib/python2.2/site-packages/_ldap.so
         libldap_r.so.2 => 
/usr/local/openldap-REL_ENG_2_1/lib/libldap_r.so.2 (0x40010000)
         liblber.so.2 => /usr/local/openldap-REL_ENG_2_1/lib/liblber.so.2 
(0x40052000)
         libsasl2.so.2 => /usr/local/cyrus-sasl/lib/libsasl2.so.2 (0x40060000)
         libssl.so.0.9.6 => /usr/lib/libssl.so.0.9.6 (0x40084000)
         libcrypto.so.0.9.6 => /usr/lib/libcrypto.so.0.9.6 (0x400b5000)
         libc.so.6 => /lib/libc.so.6 (0x4018b000)
         libresolv.so.2 => /lib/libresolv.so.2 (0x402a9000)
         libdl.so.2 => /lib/libdl.so.2 (0x402bb000)
         /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)

> so I don't think python-ldap has much chance :-)

Well, it works with *your* server from my box.

Ciao, Michael.

Re: SASL response is not a SASL BindRequest

[Stuart B. <stu...@co...>]

On Friday, April 18, 2003, at 02:34  AM, Michael Str=F6der wrote:

> Stuart Bishop wrote:
>> Out of the OSX box I'm getting:
> > [..]
>> ldap.AUTH_UNKNOWN: {'info': 'SASL(-4): no mechanism available: No=20
>> worthy mechs found', 'desc': 'Unknown authentication method'}
>
> A wild guess: The SASL plugin libs on this box are not found...

Yup. Turns out that runtime libraries support via distutils is
broken in Python 2.2 under OS X. Python 2.3a2 is working fine,
and I've got a bug report open to fix the distutils problem in
any future 2.2.x release.

Looking good. Thanks for your help on this Michael :-)

--=20
Stuart Bishop <ze...@sh...>
http://shangri-la.dropbear.id.au/