=?ISO-8859-1?Q?Re:=20R=E9p.=20:=20Re:=20NDS=20library=20linking?=

[Olivier D. <OD...@is...>]

Tim,

Thank you for your explanation. I'm not sure it is a NDS/LDAP problem.

Here is a python script using python-ldap. When a DN is provided to =
simple_bind_s(), the script is frozen. When the same DN is provided to a C =
Novell LDAP library program using simple_bind_s() (bind.c sample), it =
works. An other LDAP tool, LDAP browser/editor (in java - http://www.iit.ed=
u/~gawojar/ldap/download.html), works fine with NDS, using the same DN. =
For testing, I use the Novell NDS/LDAP Services Access Test Site (http://ww=
w.nldap.com/NLDAP/).

---------------------

import ldap
l =3D ldap.open( 'www.nldap.com', 389 )

#this line is frozen
l.simple_bind_s( 'cn=3Dadmin,ou=3DCRD,ou=3Duser,o=3DNOVELL', 'xxxxxx' )

l.unbind()

---------------------

Notes :
- the real password is not provided in this sample
- open(), anonymous simple_bind_s( '', '' ), and unbind() are working
- search is working (with anonymous bind) :
obj =3D l.search_s( 'ou=3DCRD,ou=3Duser,o=3DNOVELL', ldap.SCOPE_ONELEVEL, =
"(objectclass=3D*)" )
print obj

>>> Timothy Wilson <wi...@vi...> 05/09/01 19:13:27 >>>
On Wed, 5 Sep 2001, Olivier Dewit wrote:

> When binding to NDS with simple_bind_s() function, it works fine with a =
C program calling the Novell LDAP library, but it doesn't work with a =
python script using python-LDAP : the program is frozen.

Can you post a code snippet?

I'm not a NetWare admin, but from what I understand there's an NDS -> LDAP
translation tool that you may have to tweak so that the fields in NDS get
mapped correctly to LDAP. I haven't had to mess with it yet, but maybe in
your case NDS isn't translating to LDAP in the way your program expects.

-Tim

--
Tim Wilson      |   Visit Sibley online:   | Check out:
Henry Sibley HS |  http://www.isd197.org   | http://www.zope.com=20
W. St. Paul, MN |                          | http://slashdot.org=20
wi...@vi... |  <dtml-var pithy_quote>  | http://linux.com=20