python-ldap-dev — discussion among developers

Re: Referral support (was: port of Net::LDAP::Entry)

[Robert S. <ml-...@ep...>]

On Fri, 26 Jul 2002 10:43:28 +0000 (UTC),
 Michael Ströder <mi...@st...> wrote:
>> We have a "wrapper" search function that will deal with this.
> 
> This might be a nice inspiration for python-ldap.

Good, I haven't tested it very well, but it seems to work.

Here it is:

    import ldap, ldapurl

    def ldapsearch(self,
                   server,
                   base,
                   scope = ldap.SCOPE_SUBTREE,
                   filter,
                   attrs = None,
                   attrsonly = 0,
                   binddn = None,
                   bindpw = None,
                   debug = None):
        if debug:
            print "%s [%s]: %s; %s" % (server, base, filter, attrs)
	l = ldap.open(server)
	l.set_option(ldap.OPT_PROTOCOL_VERSION, ldap.VERSION3)
        l.set_option(ldap.OPT_REFERRALS, 0)
        l.simple_bind_s(binddn, bindpw)
        hash = {}
        if self.debug:
            print " searching in %s for %s" % ( base, filter )
        try:
            for entry, values in l.search_s(base, scope, filter, attrs, attrsonly):
                if entry:
                    hash[entry] = values
                    if debug:
                        print "  found %s" % entry
                else:
                    for value in values:
                        if debug:
                            print " got reference to %s" % value
                        url = ldapurl.LDAPUrl(value)
                        hash.update(ldapsearch(server=url.hostport, base=url.dn, scope=scope, filter=filter, attrs=attrs, attrsonly=attrsonly, binddn=binddn, bindpw=bindpw, debug=debug))
        except ldap.REFERRAL, er:
            if er.has_key('info'):
                url = ldapurl.LDAPUrl(er['info'])
                hash.update(ldapsearch(server=url.hostport, base=url.dn, scope=scope, filter=filter, attrs=attrs, attrsonly=attrsonly, binddn=binddn, bindpw=bindpw, debug=debug))
        l.unbind()
        return hash

It fills a hash indexed by the dn with the value of the dn.

Currently it needs the same binddn on every server accessed. But you can
easily integrate a method that returns a new binddn and bindpw depending
on the server and/or the search base.

Greetings
-- 
Robert Sander
Manager
Information Systems        www.epigenomics.com        Kastanienallee 24
+493024345330                                              10435 Berlin

Re: ldap.schema: str2objectclass() fails

[David L. <dav...@it...>]

On Sun, 28 Jul 2002, Jacek Konieczny typed thusly:

> On Sat, Jul 27, 2002 at 10:38:35PM +0200, Michael Str=F6der wrote:
> It seems ldap_str2objectclass() fails, but no proper python-way error
> hadnling is done. The fix should be easy (just replace
> /* XXX Do error handling... */ with exception object initialization).
> Unfortunately I am not able to do it now (lack of time) :-(

is ret important?
is a subclassed error the right thing to do?

Index: schema.c
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
RCS file: /cvsroot/python-ldap/python-ldap/Modules/schema.c,v
retrieving revision 1.2
diff -u -r1.2 schema.c
--- schema.c=094 May 2002 18:14:48 -0000=091.2
+++ schema.c=0928 Jul 2002 11:39:00 -0000
@@ -8,6 +8,8 @@
 #include "schema.h"
 #include "ldap_schema.h"

+static PyObject *SchemaError;
+
 /*
    This utility function takes a null delimited C array of (null
    delimited) C strings, creates its python equivalent and returns a
@@ -91,8 +93,7 @@
 =09return NULL;
   o =3D ldap_str2objectclass( oc_string, &ret, &errp, flag);
   if (ret) {
-    printf("Error: %d: %s", ret, errp);
-    /* XXX Do error handling... */
+    PyErr_SetString(SchemaError, errp);
     return NULL;
   }

@@ -139,8 +140,7 @@
     return NULL;
   a =3D ldap_str2attributetype( at_string, &ret, &errp, flag);
   if (ret) {
-    printf("Error: %d: %s", ret, errp);
-    /* XXX Do error handling... */
+    PyErr_SetString(SchemaError, errp);
     return NULL;
   }

@@ -208,8 +208,7 @@
     return NULL;
   s =3D ldap_str2syntax(syn_string, &ret, &errp, flag);
   if (ret) {
-    printf("Error: %d: %s", ret, errp);
-    /* XXX Do error handling... */
+    PyErr_SetString(SchemaError, errp);
     return NULL;
   }
   py_ret =3D PyList_New(4);
@@ -243,8 +242,7 @@
     return NULL;
   m =3D ldap_str2matchingrule(mr_string, &ret, &errp, flag);
   if (ret) {
-    printf("Error: %d: %s", ret, errp);
-    /* XXX Do error handling... */
+    PyErr_SetString(SchemaError, errp);
     return NULL;
   }
   py_ret =3D PyList_New(6);
@@ -285,5 +283,8 @@

 void
 LDAPinit_schema( PyObject* d ) {
+    SchemaError =3D PyErr_NewException("ldap.SchemaError",
+=09LDAPexception_class, NULL);
+    PyDict_SetItemString(d, "SchemaError", SchemaError);
     LDAPadd_methods( d, methods );
 }
--=20
David Leonard                           Dav...@it...
Dept of Inf. Tech. and Elec. Engg   _   Ph:+61 404 844 850
The University of Queensland       |+|  http://www.itee.uq.edu.au/~leonard/
QLD 4072  AUSTRALIA               ~` '~ B73CD65FBEF4C089B79A8EBADF1A932F13E=
A0FC8

Re: ldap.schema: str2objectclass() fails

[Jacek K. <ja...@bn...>]

On Sat, Jul 27, 2002 at 10:38:35PM +0200, Michael Str=F6der wrote:
> Well, I'd like to see some better error reporting with the help of=20
> exceptions. Anyway, there is a debug output text "Error: 6: .."=20
> produced. Don't know whether by the OpenLDAP libs or some code in=20
> Modules/schema.c.
Here is a fragment of Modules/schema.c:

  o =3D ldap_str2objectclass( oc_string, &ret, &errp, flag);
  if (ret) {
    printf("Error: %d: %s", ret, errp);
    /* XXX Do error handling... */
    return NULL;
  }

It seems ldap_str2objectclass() fails, but no proper python-way error
hadnling is done. The fix should be easy (just replace=20
/* XXX Do error handling... */ with exception object initialization).
Unfortunately I am not able to do it now (lack of time) :-(

Greets,
        Jacek

Re: Changes to setup.py and setup.cfg

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

Jens Vagelpohl wrote:
> a simplistic test connecting to and getting search results from a server 
> works for me on mac OS X version 10.1.5, compiled against OpenLDAP 2.1.3 
> libs.
> 
> i noticed that setup.cfg now has 2 uncommented "libs" lines, the 
> "simple" one and the "full featured" one. since the full feature line is 
> after the simple one it will get executed in this case.

Thanks for reporting that. I've corrected that to one line for the 
sparse build.

Ciao, Michael.

Re: Changes to setup.py and setup.cfg

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

a simplistic test connecting to and getting search results from a server=20=

works for me on mac OS X version 10.1.5, compiled against OpenLDAP 2.1.3=20=

libs.

i noticed that setup.cfg now has 2 uncommented "libs" lines, the =
"simple"=20
one and the "full featured" one. since the full feature line is after =
the=20
simple one it will get executed in this case.

jens



On Saturday, July 27, 2002, at 09:25 , Michael Str=F6der wrote:

> HI!
>
> I've checked in some changes to setup.py and setup.cfg hopefully=20
> simplyfing this.
>
> 1. Renamed DEFINE name HAVE_LDAP_START_TLS_S to HAVE_TLS.
>
> 2. HAVE_TLS is set by looking at line libs in setup.cfg. If it =
contains=20
> ssl *and* crypto HAVE_TLS is set. Otherwise support for StartTLS =
extended=20
> operation and LDAP over SSL is turned off.
>
> 3. I dropped support for line class in section [_ldap] of setup.cfg =
since=20
> we won't have support for other LDAP C SDKs.
>
> Please test if these changes have any bad implications on various =
build=20
> platforms.
>
> Ciao, Michael.

ldap.schema: str2objectclass() fails

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

HI!

ldap.schema.str2objectclass() fails when parsing the following 
string (from Netscape DS 4.16SP1 sub schema sub entry):

"( 2.5.6.1 NAME 'alias' DESC 'Standard ObjectClass' SUP 'top' MUST 
( objectclass $ aliasedObjectName )  MAY ( aci ) )"

This schema string does not look unusual to me but...

 >>> ldap.schema.str2objectclass("( 2.5.6.1 NAME 'alias' DESC 
'Standard ObjectClass' SUP 'top' MUST ( objectclass $ 
aliasedObjectName )  MAY ( aci ) )")
Error: 6:  MUST ( objectclass $ aliasedObjectName )  MAY ( aci ) 
)Traceback (most recent call last):
   File "<stdin>", line 1, in ?
   File "/usr/lib/python2.2/site-packages/ldap/schema.py", line 
43, in str2objectclass
     return 
ldap.functions._ldap_function_call(_ldap.str2objectclass,schema_element_str)
   File "/usr/lib/python2.2/site-packages/ldap/__init__.py", line 
56, in _ldap_function_call
     result = apply(func,args,kwargs)
SystemError: NULL result without error in PyObject_Call
 >>>

Well, I'd like to see some better error reporting with the help of 
exceptions. Anyway, there is a debug output text "Error: 6: .." 
produced. Don't know whether by the OpenLDAP libs or some code in 
Modules/schema.c.

Hans, before I ask on the OpenLDAP list what this error means can 
you please review your code and test with the string above? Make 
sure to bring your CVS working tree in sync!

Ciao, Michael.

Changes to setup.py and setup.cfg

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

HI!

I've checked in some changes to setup.py and setup.cfg hopefully 
simplyfing this.

1. Renamed DEFINE name HAVE_LDAP_START_TLS_S to HAVE_TLS.

2. HAVE_TLS is set by looking at line libs in setup.cfg. If it 
contains ssl *and* crypto HAVE_TLS is set. Otherwise support for 
StartTLS extended operation and LDAP over SSL is turned off.

3. I dropped support for line class in section [_ldap] of 
setup.cfg since we won't have support for other LDAP C SDKs.

Please test if these changes have any bad implications on various 
build platforms.

Ciao, Michael.

Re: ZLDAPAdapter problems

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

Jacob Behm wrote:
> I don't know that I'm using any OpenLDAP.  Would that be my problem?
> This Zope is running on a win32 machine.  The python LDAP module is
> v1.10a3.

Then your Win32 python-ldap binaries are using the old Umich LDAP 
libraries which can only do LDAPv2. This is probably the reason 
for your problems with MS AD.

Also note that python-ldap 1.10a3 is pretty outdated and only 
supports LDAPv2.

Ciao, Michael.

Re: ZLDAPAdapter problems

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

i think another problem is active directory itself.

i have a few python-based software pieces that work with LDAP and i =
always=20
explicitly tell people there is no guarantee it will work with the=20
"wannabe LDAP server" M$ calls "active directory". in the best M$=20
tradition it follows its very own standards, not anyone else's. trying =
to=20
code around all those nonstandard behaviors is a *pain*.

jens


On Friday, July 26, 2002, at 04:16 , Jacob Behm wrote:

> I don't know that I'm using any OpenLDAP.  Would that be my problem?
> This Zope is running on a win32 machine.  The python LDAP module is
> v1.10a3.
>
>
>> -----Original Message-----
>> From: Michael Str=F6der [mailto:mi...@st...]
>> Sent: Friday, July 26, 2002 2:12 PM
>> To: Jacob Behm
>> Cc: pyt...@li...
>> Subject: Re: ZLDAPAdapter problems
>>
>> Jacob Behm wrote:
>>>
>>> Error Type: DECODING_ERROR
>>> Error Value: {'desc': 'Decoding error'}"
>>
>> Which version of OpenLDAP? Which version of python-ldap?
>>
>> Ciao, Michael.
>

RE: ZLDAPAdapter problems

[Jacob B. <po...@bi...>]

I don't know that I'm using any OpenLDAP.  Would that be my problem?
This Zope is running on a win32 machine.  The python LDAP module is
v1.10a3.


> -----Original Message-----
> From: Michael Str=F6der [mailto:mi...@st...]
> Sent: Friday, July 26, 2002 2:12 PM
> To: Jacob Behm
> Cc: pyt...@li...
> Subject: Re: ZLDAPAdapter problems
>=20
> Jacob Behm wrote:
> >
> > Error Type: DECODING_ERROR
> > Error Value: {'desc': 'Decoding error'}"
>=20
> Which version of OpenLDAP? Which version of python-ldap?
>=20
> Ciao, Michael.

Re: ZLDAPAdapter problems

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

ZLDAPAdapter is a really old zope product. i don't think it is being 
actively maintained. the correct people to talk to are the maintainers of 
that particular product.

jens


On Friday, July 26, 2002, at 02:58 , Jacob Behm wrote:

> Hi,
>
> I'm new to this group so if I'm out line with any of my questions please
> let me know.
>
> I'm building an intra/extranet in Zope and as my company already has all
> the groups and users defined in a MS Active Directory system, I'm trying
> to link Zope to our AD server using LDAP.  I've installed the LDAP
> module for python and the ZLDAPAdapter for Zope seems to be working.
> But when I try to use it I get the following Zope error:
>
> "Zope has encountered an error while publishing this resource.
>
> Error Type: DECODING_ERROR
> Error Value: {'desc': 'Decoding error'}"
>
> I understand that this means that python couldn't interpret the response
> it got from my AD server.  Is there a way for me to see the response?
>
> Has anyone tried this before?  I could use a little guidance.
>
> Thanks,
>
> Jacob Behm

Re: ZLDAPAdapter problems

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

Jacob Behm wrote:
> 
> Error Type: DECODING_ERROR
> Error Value: {'desc': 'Decoding error'}"

Which version of OpenLDAP? Which version of python-ldap?

Ciao, Michael.

ZLDAPAdapter problems

[Jacob B. <po...@bi...>]

Hi,

I'm new to this group so if I'm out line with any of my questions please
let me know.

I'm building an intra/extranet in Zope and as my company already has all
the groups and users defined in a MS Active Directory system, I'm trying
to link Zope to our AD server using LDAP.  I've installed the LDAP
module for python and the ZLDAPAdapter for Zope seems to be working.
But when I try to use it I get the following Zope error:

"Zope has encountered an error while publishing this resource.

Error Type: DECODING_ERROR
Error Value: {'desc': 'Decoding error'}"

I understand that this means that python couldn't interpret the response
it got from my AD server.  Is there a way for me to see the response?  

Has anyone tried this before?  I could use a little guidance.

Thanks,

Jacob Behm

Re: python-ldap-2.0.0pre05 and zope

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

Joe Little wrote:
> OpenLDAP depends on the cyrus-sasl package.. Though you can install 
> OpenLDAP without it,

Yes, ./configure --without-cyrus-sasl is the solution if one does 
not need SASL support.

> the python-ldap API links to that package as well 
> via OpenLDAP libs.

Only if line "libs" in setup.cfg contains "sasl" which is not the 
way it is shipped in the download distribution.

There are other dependencies like StartTLS support which needs 
OpenLDAP libs built with OpenSSL (--with-tls). One can switch that 
off by editing the DEFINEs in setup.py.

Ciao, Michael.

Re: python-ldap-2.0.0pre05 and zope

[Joe L. <jl...@op...>]

I can only guess that it cannot find the cyrus-sasl libs. Check the 
library path.

On Friday, July 26, 2002, at 11:45 AM, <mba...@me...> wrote:

> Hi,
>
> Even when I configure openldap-2.0.25 with cyrus-sasl, I get the same
> errors when I run the 'make' command.
>
> --Madhavi
> <mbagepll.vcf>

Re: python-ldap-2.0.0pre05 and zope

[<mba...@me...>]

Hi,

Even when I configure openldap-2.0.25 with cyrus-sasl, I get the same 
errors when I run the 'make' command.

--Madhavi

Re: python-ldap-2.0.0pre05 and zope

[Joe L. <jl...@op...>]

OpenLDAP depends on the cyrus-sasl package.. Though you can install 
OpenLDAP without it, the python-ldap API links to that package as well 
via OpenLDAP libs.

On Friday, July 26, 2002, at 11:25 AM, <mba...@me...> wrote:

> To compile openldap-2.0.25, I followed the INSTALL manual.
> I did the following:
>
> 1)  ./configure --disable-slapd --disable-slurpd --with-
> python=/opt/local/web/zope/bin/python
>
> 2) make depend
>
> 3) make
> when run the make command, I get the following errors.
>
> ld: fatal: library -lsasl: not found
> ld: fatal: File processing errors. No output written
> to .libs/libldap.so.2.0.16
> *** Error code 1
> make: Fatal error: Command failed for target `libldap.la'
> Current working directory /opt/local/web/ldap/openldap-
> 2.0.25/libraries/libldap
> *** Error code 1
> make: Fatal error: Command failed for target `all-common'
> Current working directory /opt/local/web/ldap/openldap-2.0.25/libraries
> *** Error code 1
> make: Fatal error: Command failed for target `all-common'
>
> I checked the /opt/local/web/ldap/openldap-2.0.25/libraries/
> for 'libldap.la' file and there was not one. Instead it has a libldap
> folder. I checked to see if the file exists there, but could not find
> one.
>
> Am i missing something here?
>
> --Madhavi
>
> <mbagepll.vcf>

Re: python-ldap-2.0.0pre05 and zope

[<mba...@me...>]

To compile openldap-2.0.25, I followed the INSTALL manual.
I did the following:

1)  ./configure --disable-slapd --disable-slurpd --with-
python=/opt/local/web/zope/bin/python

2) make depend

3) make
when run the make command, I get the following errors. 

ld: fatal: library -lsasl: not found
ld: fatal: File processing errors. No output written 
to .libs/libldap.so.2.0.16
*** Error code 1
make: Fatal error: Command failed for target `libldap.la'
Current working directory /opt/local/web/ldap/openldap-
2.0.25/libraries/libldap
*** Error code 1
make: Fatal error: Command failed for target `all-common'
Current working directory /opt/local/web/ldap/openldap-2.0.25/libraries
*** Error code 1
make: Fatal error: Command failed for target `all-common'

I checked the /opt/local/web/ldap/openldap-2.0.25/libraries/ 
for 'libldap.la' file and there was not one. Instead it has a libldap 
folder. I checked to see if the file exists there, but could not find 
one. 

Am i missing something here?

--Madhavi

Re: python-ldap-2.0.0pre05 and zope

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

mba...@me... wrote:
> 
> I am trying to install python-ldap module for zope 2.5.1 on solaris 8. 
> I am using netscape LDAP C library (there was no problem compiling it). 

Note that since LDAP C libs are diverging solely building against 
OpenLDAP 2.x libs is supported.

> ImportError: ld.so.1: /opt/local/web/zope/jed/bin/python: fatal: 
> libgcc_s.so.1: open failed: No such file or directory

No clue...

> And then, i invoked the zope python interpreter and tried to import 
> _ldap module. The error it throws is -
> 
>>>>import _ldap
>>>
> Traceback (most recent call last):
>   File "<stdin>", line 1, in ?
> ImportError: ld.so.1: /opt/local/web/zope/jed/bin/python: fatal: 
> relocation error: file /opt/local/web/zope/jed/lib/python2.1/site-
> packages/_ldap.so: symbol ldap_start_tls_s: referenced symbol not found

Although Netscape libs are not supported you could try to comment 
the line with HAVE_LDAP_START_TLS_S in setup.py. But don't waste 
too much time with it. I removed some code for old Netscape 3 API.
=> grab OpenLDAP 2.0.25 and compile the libs.

Ciao, Michael.

Re: python-ldap-2.0.0pre05 and zope

[Mauro C. <mci...@si...>]

mba...@me... wrote:

>I am trying to install python-ldap module for zope 2.5.1 on solaris 8. 
>I am using netscape LDAP C library ...
>
Unfortunately the current version of Python-ldap uses only the OpenLDAP 
2.x libraries.
There's no more support for Netscape libs since the 1.x branch was 
abandoned.

Mauro

python-ldap-2.0.0pre05 and zope

[<mba...@me...>]

Hi all,

I am trying to install python-ldap module for zope 2.5.1 on solaris 8. 
I am using netscape LDAP C library (there was no problem compiling it). 
I built and installed python-ldap and there were no errors. But, when i 
try to start zope, I get the following error-

------
2002-07-26T14:22:40 ERROR(200) Zope Could not import 
Products.LDAPUserFolder
Traceback (innermost last):
  File /opt/local/web/zope/jed/lib/python/OFS/Application.py, line 531, 
in import_product
  
File /opt/local/web/zope/jed/lib/python/Products/LDAPUserFolder/__init__
.py, line 13, in ?
  
File /opt/local/web/zope/jed/lib/python/Products/LDAPUserFolder/LDAPUser
Folder.py, line 11, in ?
  
File /opt/local/web/zope/jed/lib/python/Products/LDAPUserFolder/LDAPUser
.py, line 20, in ?
    (Object: aq_inner)
  
File /opt/local/web/zope/jed/lib/python/Products/LDAPUserFolder/utils.py
, line 32, in ?
  File /opt/local/web/zope/jed/lib/python2.1/site-
packages/ldap/__init__.py, line 11, in ?
ImportError: ld.so.1: /opt/local/web/zope/jed/bin/python: fatal: 
libgcc_s.so.1: open failed: No such file or directory


And then, i invoked the zope python interpreter and tried to import 
_ldap module. The error it throws is -

>>> import _ldap
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
ImportError: ld.so.1: /opt/local/web/zope/jed/bin/python: fatal: 
relocation error: file /opt/local/web/zope/jed/lib/python2.1/site-
packages/_ldap.so: symbol ldap_start_tls_s: referenced symbol not found
>>> 

Can anyone help me in this matter?

--Madhavi

Re: Referral support (was: port of Net::LDAP::Entry)

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

Robert Sander wrote:
> 
>>Note that there are many issues to deal with either in your 
>>concept or your application when extensively using referrals.
> 
> We have a "wrapper" search function that will deal with this.

This might be a nice inspiration for python-ldap.

Ciao, Michael.

Re: Referral support (was: port of Net::LDAP::Entry)

[Robert S. <gur...@ep...>]

On Thu, Jul 25, 2002 at 11:21:17PM +0200, Michael Ströder wrote:
> I forgot something: If the search root is itself matched by a 
> referral a ldap.REFERRAL exception is raised.

I already got that exception.

> Note that there are many issues to deal with either in your 
> concept or your application when extensively using referrals.

We have a "wrapper" search function that will deal with this.

Greetings
-- 
Robert Sander
Manager
Information Systems        www.epigenomics.com        Kastanienallee 24
+493024345330                                              10435 Berlin

setting/getting ldap.OPT_TIMEOUT and ldap.OPT_NETWORK_TIMEOUT

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

HI!

Hmm, I tried to implement setting/getting options LDAP_OPT_TIMEOUT 
and LDAP_OPT_NETWORK_TIMEOUT in Moduls/options.c.

But it does not seem to work. No wonder because C makes my eyes 
hurt! Can somebody please dig into options.c and review the 
nonsense I added? ;-)

Ciao, Michael.

Referral support (was: port of Net::LDAP::Entry)

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

Robert Sander wrote:
> We have a directory service set up with OpenLDAP extensively using
> referrals. It seems that python-ldap currently is not able to handle
> these. Is this correct?

There is support for it. But it's a rather complex topic. Your 
mileage may vary.

Before I write a pile of postings about it I'd like to know what 
your understanding of handling referrals is.

Ciao, Michael.