python-ldap-dev — discussion among developers

Re: ldap.schema: str2objectclass() fails

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

Hans Aschauer wrote:
> On Dienstag, 30. Juli 2002 22:20, Michael Str=F6der wrote:
>=20
>>Michael Str=F6der wrote:
>>
>>>Frankly I'd prefer to check the numerical error code in
>>>ldap.schema.str2objectclass() and the other wrapper functions and
>>>raise Python-declared exceptions instead of create the exception
>>>instances in Modules/schema.c.
>>
>>How about this approach assuming _ldap.str2objectclass() only
>>returns a error code as integer in case of an error?
>=20
>=20
> [...]
>=20
> This a really easy approach to the problem. Should I commit that patch?=


Yes!

Ciao, Michael.

Re: ldap.schema: str2objectclass() fails

[Hans A. <Han...@Ph...>]

On Dienstag, 30. Juli 2002 22:20, Michael Ströder wrote:
> Michael Ströder wrote:
> > Frankly I'd prefer to check the numerical error code in
> > ldap.schema.str2objectclass() and the other wrapper functions and
> > raise Python-declared exceptions instead of create the exception
> > instances in Modules/schema.c.
>
> How about this approach assuming _ldap.str2objectclass() only
> returns a error code as integer in case of an error?

[...]

This a really easy approach to the problem. Should I commit that patch?

Hans

-- 
Han...@Ph...

Re: ldap.schema: str2objectclass() fails

[Hans A. <Han...@Ph...>]

On Mittwoch, 31. Juli 2002 00:37, Michael Ströder wrote:


> It should be accepted with schema_allow=31.
>
> See discussion for issue filed in OpenLDAP's ITS:
>
>    http://www.OpenLDAP.org/its/index.cgi?findid=1996
>
> Please cross-check that the client library ALLOW flags are
> "properly enabled".

I did some printf - debugging, and I think it is a real openldap bug:

>>> ldap.schema.str2objectclass(b,31)
Error: 5: ( nsHost-oid NAME 'nsHost' DESC 'iPlanet defined objectclass' 
SUP top STRUCTURAL MUST cn MAY ( serverHostName $ description $ l $ 
nsHostLocation $ nsHardwarePlatform $ nsOsVersion ) X-ORIGIN 'iPlanet' 
). flag = 31
   ^^^^^^^^^

The "flag = 31" is printf'ed by the C wrapper code, using the same 
variable that is passed to the openldap - function.


This is a small C test code in order to exclude errors from the python 
side (maybe you could post it to the ITS):

----------------------------------------------------------------------
#include "ldap_schema.h"

char *oclass = "( nsHost-oid NAME 'nsHost' DESC 'iPlanet defined 
objectclass' SUP top STRUCTURAL MUST cn MAY ( serverHostName $ 
description $ l $ nsHostLocation $ nsHardwarePlatform $ nsOsVersion ) 
X-ORIGIN 'iPlanet' )";

const char *errp;
int ret = 0;

int main(){
  ldap_str2objectclass(oclass, &ret, &errp, LDAP_SCHEMA_ALLOW_ALL);
  if (ret)
    printf ("Error: %d: %s\n", ret, errp);
}
----------------------------------------------------------------------
compile it with 'gcc schema_test.c -lldap -o schema_test' and have fun 
;-)

Hans

-- 
Han...@Ph...

Re: ldap.schema: str2objectclass() fails

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

Hans Aschauer wrote:
> On Dienstag, 30. Juli 2002 11:42, Michael Str=F6der wrote:
>=20
> The problem is that they do not provide OID's where there must be OID's=
:

It should be accepted with schema_allow=3D31.

See discussion for issue filed in OpenLDAP's ITS:

   http://www.OpenLDAP.org/its/index.cgi?findid=3D1996

Please cross-check that the client library ALLOW flags are=20
"properly enabled".

Ciao, Michael.

Re: ldap.schema: str2objectclass() fails

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

Michael Str=F6der wrote:
> Frankly I'd prefer to check the numerical error code in=20
> ldap.schema.str2objectclass() and the other wrapper functions and raise=
=20
> Python-declared exceptions instead of create the exception instances in=
=20
> Modules/schema.c.

How about this approach assuming _ldap.str2objectclass() only=20
returns a error code as integer in case of an error?

------------------------- snip -------------------------
class SchemaError(Exception): pass

class SCHERR_OUTOFMEM(SchemaError): pass

class SCHERR_UNEXPTOKEN(SchemaError): pass

class SCHERR_NOLEFTPAREN(SchemaError): pass

class SCHERR_NORIGHTPAREN(SchemaError): pass

class SCHERR_NODIGIT(SchemaError): pass

class SCHERR_BADNAME(SchemaError): pass

class SCHERR_BADDESC(SchemaError): pass

class SCHERR_BADSUP(SchemaError): pass

class SCHERR_DUPOPT(SchemaError): pass

class SCHERR_EMPTY(SchemaError): pass

ERRCODE2SCHERR =3D {
    1:SCHERR_OUTOFMEM
    2:SCHERR_UNEXPTOKEN
    3:SCHERR_NOLEFTPAREN
    4:SCHERR_NORIGHTPAREN
    5:SCHERR_NODIGIT
    6:SCHERR_BADNAME
    7:SCHERR_BADDESC
    8:SCHERR_BADSUP
    9:SCHERR_DUPOPT
   10:SCHERR_EMPTY
}

# Wrapper functions to serialize calls into OpenLDAP libs with
# a module-wide thread lock
def str2objectclass(schema_element_str,schema_allow=3D0):
     r =3D ldap.functions._ldap_function_call(
       _ldap.str2objectclass,schema_element_str,schema_allow
     )
     if type(res)=3D=3Dtype(0):
       raise ERRCODE2SCHERR.get(r,SchemaError)(
         r,schema_element_str
       )
     else:
       assert type(res)=3D=3Dtype(())
       return r
------------------------- snip -------------------------

Ciao, Michael.

Re: ldap.schema: str2objectclass() fails

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

David Leonard wrote:
 > is ret important?

Yes, I think so.

 > is a subclassed error the right thing to do?

Frankly I'd prefer to check the numerical error code in 
ldap.schema.str2objectclass() and the other wrapper functions and 
raise Python-declared exceptions instead of create the exception 
instances in Modules/schema.c.

This is much easier to maintain (at least for me) and the schema 
exception class can be sub-classed etc.

Ciao, Michael.

Re: python-ldap-2.0.0pre05 and openldap-2.1.3

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

yes, i had built and installed openldap correctly. Anyway, I had to 
copy the files to the library_dir directory. Now, I have python-ldap 
working. Thank you for your help.

--Madhavi

Re: ldap.schema: str2objectclass() fails

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

Hans Aschauer wrote:
> On Dienstag, 30. Juli 2002 11:42, Michael Str=F6der wrote:
>=20
>>You can check yourself by invoking recently checked in
>>Demo/schema.py:
>>
>>$ python Demo/schema.py ldap://memberdir.netscape.com/
>=20
> The problem is that they do not provide OID's where there must be OID's=
:
 > objectClasses: ( inetsubscriber-oid

Yes, that's what i suspected too. But I thought one of

#define LDAP_SCHEMA_ALLOW_DESCR		0x04
/* Allow descr instead of OID   */

#define LDAP_SCHEMA_ALLOW_DESCR_PREFIX	0x08
/* Allow descr as OID prefix  */

#define LDAP_SCHEMA_ALLOW_OID_MACRO	0x10
/* Allow OID macros in slapd */

would do the trick.

> There's not much that we=20
> can do in this case (except for writing our own parser,

Jacek already has a pure-Python parser in his curses-based LDAP=20
client...

> or filing a=20
> "bug" report, and hoping the best...)

I suspect that Kurt will not accept that but I will try to file an=20
issue report anyway.

> Of course, if we already had better error handling, we could also use=20
> some heuristics after an exception is caught ;-)

No.

Ciao, Michael.

Re: ldap.schema: str2objectclass() fails

[Hans A. <Han...@Ph...>]

On Dienstag, 30. Juli 2002 11:42, Michael Ströder wrote:

> Can you point me to where are the error codes described in OpenLDAP?

In ldap_schema.h:

----------------------------------------------
/* Codes for parsing errors */

#define LDAP_SCHERR_OUTOFMEM            1
#define LDAP_SCHERR_UNEXPTOKEN          2
#define LDAP_SCHERR_NOLEFTPAREN         3
#define LDAP_SCHERR_NORIGHTPAREN        4
#define LDAP_SCHERR_NODIGIT             5
#define LDAP_SCHERR_BADNAME             6
#define LDAP_SCHERR_BADDESC             7
#define LDAP_SCHERR_BADSUP              8
#define LDAP_SCHERR_DUPOPT              9
#define LDAP_SCHERR_EMPTY               10
----------------------------------------------

> You can check yourself by invoking recently checked in
> Demo/schema.py:
>
> $ python Demo/schema.py ldap://memberdir.netscape.com/

The problem is that they do not provide OID's where there must be OID's:

objectClasses: ( inetsubscriber-oid NAME 'inetSubscriber' SUP top 
AUXILIARY MAY ( inetSubscriberAccountId $ inetSubscriberChallenge $ 
inetSubscriberResponse ) X-ORIGIN 'Nortel subscriber interoperability')

In this case, the offending item is "inetsubscriber-oid", which is 
expected to be a numeric OID. In this case, the openldap schema parser 
is not liberal enough to allow such a string. There's not much that we 
can do in this case (except for writing our own parser, or filing a 
"bug" report, and hoping the best...)

Of course, if we already had better error handling, we could also use 
some heuristics after an exception is caught ;-)

Hans 

-- 
Han...@Ph...

Re: ldap.schema: str2objectclass() fails

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

Hans Aschauer wrote:
> On Montag, 29. Juli 2002 18:46, Michael Str=F6der wrote:
>=20
> I made changes to schema.c and schema.py in order to actually pass the =

> flag to the C functions:
> [...]
> Seems to work. Please test.

Thanks. It gets further but still chokes with schema of Netscape=20
DS 4.16SP1 on some object classes although called with=20
schema_allow=3D31.

Can you point me to where are the error codes described in OpenLDAP?

You can check yourself by invoking recently checked in Demo/schema.py:

$ python Demo/schema.py ldap://memberdir.netscape.com/

memberdir.netscape.com is a iPlanet-Directory/5.0 B2001.109.0903.

Feel free to use web2ldap's [ConnInfo] feature to find out more=20
about demo servers mentioned there.

It also does not work with www.nldap.com (Novell eDirectory 8.7).

$ python Demo/schema.py ldap://www.nldap.com/
*** Schema from 'cn=3Dschema'
Error: 5: ( smssmdrclass-oid NAME 'sMSSMDRClass' DESC 'Standard=20
ObjectClass' SUP resource STRUCTURAL MAY ( status $ Version $=20
sAPName $ sMSRegisteredService $ sMSProtocolAddress ) X-NDS_NAME=20
'SMS SMDR Class' X-NDS_NOT_CONTAINER '1' )Traceback (most recent=20
call last):
   File "Demo/schema.py", line 27, in ?
     schema =3D=20
ldap.schema.subSchema(subschemasubentry_entry,schema_allow=3D31)
   File "/usr/lib/python2.2/site-packages/ldap/schema.py", line=20
154, in __init__
     se =3D SCHEMA_CLASS_MAPPING[attr_type](attr_value,schema_allow)
   File "/usr/lib/python2.2/site-packages/ldap/schema.py", line=20
47, in __init__
     (
   File "/usr/lib/python2.2/site-packages/ldap/schema.py", line=20
20, in str2objectclass
     return=20
ldap.functions._ldap_function_call(_ldap.str2objectclass,schema_element_s=
tr,schema_allow)
   File "/usr/lib/python2.2/site-packages/ldap/__init__.py", line=20
56, in _ldap_function_call
     result =3D apply(func,args,kwargs)
SystemError: NULL result without error in PyObject_Call

Ciao, Michael.

Re: ldap.schema: str2objectclass() fails

[Hans A. <Han...@Ph...>]

On Montag, 29. Juli 2002 18:46, Michael Ströder wrote:

> I changed the API to pass around this flags integer. I did other
> changes.

I made changes to schema.c and schema.py in order to actually pass the 
flag to the C functions:

>>> a = "( 2.5.6.1 NAME 'alias' DESC 'Standard ObjectClass' SUP 'top' 
MUST ( objectclass $ aliasedObjectName )  MAY ( aci ) )"
>>> ldap.schema.str2objectclass(a,15)
['2.5.6.1', ['alias'], 'Standard ObjectClass', 0, ['top'], 1, 
['objectclass', 'aliasedObjectName'], ['aci'], []]
>>> ldap.schema.str2objectclass(a)
Error: 6:  MUST ( objectclass $ aliasedObjectName )  MAY ( aci ) 
)Traceback (most recent call last):
[...]

Seems to work. Please test.

Hans

-- 
Han...@Ph...

Re: python-ldap-2.0.0pre05 and openldap-2.1.3

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

mba...@me... wrote:
> yes, the shared lib liblber.so is installed in openldap-
> 2.1.3/libraries/liblber/.libs directory.

???

Are you trying to compile python-ldap with include's and libs 
directly from the OpenLDAP source tree?

Didn't you invoke
$ ./configure --prefix=/usr/local/openldap
$ make
# make install
to build *and* install OpenLDAP?

> I am not sure if the liblber.so is in the right place, as it is in a 
> hidden directory (.libs). Do I have to copy this to the 'liblber' 
> directory for the linker to see it?

Why not just try out yourself? At least you are sitting in front 
of your machine, don't you. ;-)

On Linux the liblber.so, libldap.so, etc. are in the directory 
where parameter library_dirs of setup.cfg is pointing to.

Ciao, Michael.

Re: python-ldap-2.0.0pre05 and openldap-2.1.3

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

yes, the shared lib liblber.so is installed in openldap-
2.1.3/libraries/liblber/.libs directory. And i am using gcc compiler 
and not the solaris comiler/linker.

I am not sure if the liblber.so is in the right place, as it is in a 
hidden directory (.libs). Do I have to copy this to the 'liblber' 
directory for the linker to see it?

Madhavi

Re: python-ldap-2.0.0pre05 and openldap-2.1.3

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

mba...@me... wrote:
> 
> I have got openldap installed completely. I have checked for liblber.a 
> (this time) and it was poperly installed.

And the shared lib liblber.so?

> ld: fatal: relocations remain against allocatable but non-writable 
> sections
> collect2: ld returned 1 exit status
> error: command 'gcc' failed with exit status 1

No clue about Solaris here. Are you using the Solaris compiler/linker?

Googling around I found this here:
http://gcc.gnu.org/ml/gcc-help/2000-05/msg00002.html

Hmm, but -fPIC is already used.

Ciao, Michael.

Re: python-ldap-2.0.0pre05 and openldap-2.1.3

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

Hi,

I have got openldap installed completely. I have checked for liblber.a 
(this time) and it was poperly installed. Now my problem here is - 
after changing setup.cfg (file in python-ldap-2.0.0pre05), such that 
the 'library_dir' and 'include_dir' point to the openldap 'libraries' 
directory and 'include' directoy respectively, I ran the command -
 'python setup.py build', which gave the following error-

/libraries/liblber.a(sockbuf.o)
ber_int_sb_close                    
0x5c        /opt/local/web/ldap/openldap-2.0.25/libraries/liblber.a
(sockbuf.o)
ber_pvt_sb_copy_out                 
0xe74       /opt/local/web/ldap/openldap-2.0.25/libraries/liblber.a
(sockbuf.o)
ber_pvt_sb_copy_out                 
0xf10       /opt/local/web/ldap/openldap-2.0.25/libraries/liblber.a
(sockbuf.o)
ld: fatal: relocations remain against allocatable but non-writable 
sections
collect2: ld returned 1 exit status
error: command 'gcc' failed with exit status 1

Does any one know what this error is?

Re: ldap.schema: str2objectclass() fails

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

Michael Str=F6der wrote:
> Hans Aschauer wrote:
>=20
>> One way to solve this problem (if netscape DS always returns such=20
>> 'wrong' sub schema sub entries) would be to expose the flags argument =

>> of the C function to the python API, which allows to be more liberal=20
>> in parsing the strings.
>=20
> We definitely need this!

I changed the API to pass around this flags integer. I did other=20
changes.

Please bring your CVS working tree in sync.

Ciao, Michael.

Re: python-ldap-2.0.0pre05 and openldap-2.1.3

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

mba...@me... wrote:
> 
> I am trying to install python-ldap for solaris 8 using openldap-2.1.3. 
> The openldap configures fine without giving any errors, but gives a 
> warning which says- " Could not locate TLS/SSL package. TLS data 
> protection not supported." Do i have to have SSL package?

If you don't want to use LDAP over SSL or StartTLS extended 
operation to encrypt the LDAP data traffic you don't need to 
install OpenSSL.

> And, when I try to configure python-ldap, it throws the following 
> error -
> 
> Modules/options.c: In function `LDAP_set_option':
> Modules/options.c:79: warning: return makes integer from pointer 
> without a cast
> Modules/options.c:97: warning: return makes integer from pointer 
> without a cast

You can ignore that warning.

> ld: fatal: library -llber: not found
> ld: fatal: File processing errors. No output written to 
> build/lib.solaris-2.8-sun4u-2.1/_ldap.so
 > [..]
> I have noticed that the openldap-2.0.25 (the previous version) had 
> liblber.a in the libraries folder. Where as, in openldap-2.1.3 there is 
> no such file (liblber.a) in the libraries folder. Is this related to 
> the error?

I guess your OpenLDAP build was not complete. You should find 
liblber.a and/or liblber.so.

But this whole topic is more related to OpenLDAP itself. You might 
find the OpenLDAP Admin Guide, the FAQ-O-MATIC and mailing lists 
(archives) helpful to track those things down. Check out 
http://www.openldap.org.

Ciao, Michael.

Re: ZLDAPAdapter problems

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

Mauro Cicognini wrote:
> 
> It does work, but it takes a lot of guessing of what the search roots 
> are...

???

Attribute namingContexts in RootDSE should help. There's also an 
attribute defaultNamingContext. Access control restriction could 
be in place and off course these attributes should be queried by 
name just like with OpenLDAP 2.x.

> and after that, you may have to tweak code to interpret the 
> results correctly.

Can you elaborate on that? Tweak which code?

> Not as much as Novell Directory Service, though. ;-)

Can you elaborate on that too? As long as you don't try to handle 
Novell/NDS specific attributes it's very easy to query Novell 
eDirectory. BTW: One can have a look at ldap://www.nldap.com, 
their public demo server. You can even register to get your own 
container with write acess (http://www.nldap.com).

Ciao, Michael.

Re: ZLDAPAdapter problems

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

Jacob Behm wrote:
> 
> I'm sure someone has tried to interface with Active Directory with LDAP
> before.  Has anyone been successful?  Is it even possible?  

It should be possible. As python-ldap is concerned: I browsed an 
Active Directory server but not tested it very thoroughly.

What you get out of it also depends very much on the security 
configuration.

Ciao, Michael.

Re: ZLDAPAdapter problems

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

Jacob Behm wrote:

>>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.
>>    
>>
>
>Ah .. this is very helpful.  Does anyone know if there are updated binaries/libraries available for win32 systems?  
>  
>
Yes, there are: I have recently done a build of the newer stuff, which 
does need testing. If you're interested, I may send it to you.

It's still python-ldap2.0.0pre04 and OpenLDAP 2.0.23 (with 
cyrus-sasl-1.5.27) due to lack of time on my part to get up to the very 
latest versions.

>I'm sure someone has tried to interface with Active Directory with LDAP before.  Has anyone been successful?  Is it even possible?  
>  
>
It does work, but it takes a lot of guessing of what the search roots 
are... and after that, you may have to tweak code to interpret the 
results correctly.
Not as much as Novell Directory Service, though. ;-)

BR,
Mauro

RE: ZLDAPAdapter problems

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

> 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.

Ah .. this is very helpful.  Does anyone know if there are updated
binaries/libraries available for win32 systems?  

I'm sure someone has tried to interface with Active Directory with LDAP
before.  Has anyone been successful?  Is it even possible?  

Thanks Again,

Jacob

Re: python-ldap-2.0.0pre05 and openldap-2.1.3

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

> I am trying to install python-ldap for solaris 8 using openldap-2.1.3.
> The openldap configures fine without giving any errors, but gives a
> warning which says- " Could not locate TLS/SSL package. TLS data
> protection not supported." Do i have to have SSL package?

it's just a warning. warnings are not fatal errors. the warning tells you 
exactly what is happening: no SSL package, so you will not get ldap with 
TLS or ldap over SSL.


>
> And, when I try to configure python-ldap, it throws the following
> error -
>
> Modules/options.c: In function `LDAP_set_option':
> Modules/options.c:79: warning: return makes integer from pointer
> without a cast
> Modules/options.c:97: warning: return makes integer from pointer
> without a cast
> gcc -shared build/temp.solaris-2.8-sun4u-2.1/LDAPObject.o
> build/temp.solaris-2.8-sun4u-2.1/common.o build/temp.solaris-2.8-sun4u-
> 2.1/constants.o build/temp.solaris-2.8-sun4u-2.1/errors.o
> build/temp.solaris-2.8-sun4u-2.1/functions.o build/temp.solaris-2.8-
> sun4u-2.1/schema.o build/temp.solaris-2.8-sun4u-2.1/ldapmodule.o
> build/temp.solaris-2.8-sun4u-2.1/linkedlist.o build/temp.solaris-2.8-
> sun4u-2.1/message.o build/temp.solaris-2.8-sun4u-2.1/version.o
> build/temp.solaris-2.8-sun4u-2.1/options.o -
> L/opt/local/web/ldap/openldap-2.1.3/libraries -lldap -llber -o
> build/lib.solaris-2.8-sun4u-2.1/_ldap.so
> ld: fatal: library -llber: not found
> ld: fatal: File processing errors. No output written to
> build/lib.solaris-2.8-sun4u-2.1/_ldap.so
> collect2: ld returned 1 exit status
> error: command 'gcc' failed with exit status 1
>
> I have noticed that the openldap-2.0.25 (the previous version) had
> liblber.a in the libraries folder. Where as, in openldap-2.1.3 there is
> no such file (liblber.a) in the libraries folder. Is this related to
> the error?

obviously the error is caused by not finding liblber. liblber *is* part of 
a openldap build (at least on all the 2.1.x builds i have done on linux 
and mac os x), so either it was put in a place that the buildout does not 
know about or your openldap build went wrong.

jens

python-ldap-2.0.0pre05 and openldap-2.1.3

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

Hi all,

I am trying to install python-ldap for solaris 8 using openldap-2.1.3. 
The openldap configures fine without giving any errors, but gives a 
warning which says- " Could not locate TLS/SSL package. TLS data 
protection not supported." Do i have to have SSL package?

And, when I try to configure python-ldap, it throws the following 
error -

Modules/options.c: In function `LDAP_set_option':
Modules/options.c:79: warning: return makes integer from pointer 
without a cast
Modules/options.c:97: warning: return makes integer from pointer 
without a cast
gcc -shared build/temp.solaris-2.8-sun4u-2.1/LDAPObject.o 
build/temp.solaris-2.8-sun4u-2.1/common.o build/temp.solaris-2.8-sun4u-
2.1/constants.o build/temp.solaris-2.8-sun4u-2.1/errors.o 
build/temp.solaris-2.8-sun4u-2.1/functions.o build/temp.solaris-2.8-
sun4u-2.1/schema.o build/temp.solaris-2.8-sun4u-2.1/ldapmodule.o 
build/temp.solaris-2.8-sun4u-2.1/linkedlist.o build/temp.solaris-2.8-
sun4u-2.1/message.o build/temp.solaris-2.8-sun4u-2.1/version.o 
build/temp.solaris-2.8-sun4u-2.1/options.o -
L/opt/local/web/ldap/openldap-2.1.3/libraries -lldap -llber -o 
build/lib.solaris-2.8-sun4u-2.1/_ldap.so
ld: fatal: library -llber: not found
ld: fatal: File processing errors. No output written to 
build/lib.solaris-2.8-sun4u-2.1/_ldap.so
collect2: ld returned 1 exit status
error: command 'gcc' failed with exit status 1

I have noticed that the openldap-2.0.25 (the previous version) had 
liblber.a in the libraries folder. Where as, in openldap-2.1.3 there is 
no such file (liblber.a) in the libraries folder. Is this related to 
the error?

--Madhavi

Re: ldap.schema: str2objectclass() fails

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

Hans Aschauer wrote:
 >
> One way to solve this problem (if netscape DS always returns such 
> 'wrong' sub schema sub entries) would be to expose the flags argument 
> of the C function to the python API, which allows to be more liberal in 
> parsing the strings.

We definitely need this!

> Ok, I can try to fix things along the lines of David's patch (but 
> including the error code). It will however take me at least one week. 

Go for it.

Ciao, Michael.

Re: ldap.schema: str2objectclass() fails

[Hans A. <Han...@Ph...>]

On Samstag, 27. Juli 2002 22:38, Michael Ströder wrote:
> 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...

But it does to me. The "SUP 'top'" should be "SUP top" (as far as I 
understand RFC 2252, Chapter 4: the argument of sup is oids, which does 
not include the quotes...). Just tried it, and it worked.

One way to solve this problem (if netscape DS always returns such 
'wrong' sub schema sub entries) would be to expose the flags argument 
of the C function to the python API, which allows to be more liberal in 
parsing the strings. The flags are defined in ldap_schema.h:

#define LDAP_SCHEMA_ALLOW_NONE		0x00 /* Strict parsing               */
#define LDAP_SCHEMA_ALLOW_NO_OID	0x01 /* Allow missing oid            */
#define LDAP_SCHEMA_ALLOW_QUOTED	0x02 /* Allow bogus extra quotes     */
#define LDAP_SCHEMA_ALLOW_DESCR		0x04 /* Allow descr instead of OID   */
#define LDAP_SCHEMA_ALLOW_DESCR_PREFIX	0x08 /* Allow descr as OID prefix    
*/
#define LDAP_SCHEMA_ALLOW_OID_MACRO	0x10 /* Allow OID macros in slapd    
*/
#define LDAP_SCHEMA_ALLOW_ALL		0x1f /* Be very liberal in parsing   */

At present, the flags are set to 0x00...



[incomplete and 'bad' python error]

> 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.

Sorry that I still have not implemented correct error handling...
The return codes are (again from ldap_schema.h):

/* Codes for parsing errors */

#define LDAP_SCHERR_OUTOFMEM		1
#define LDAP_SCHERR_UNEXPTOKEN		2
#define LDAP_SCHERR_NOLEFTPAREN		3
#define LDAP_SCHERR_NORIGHTPAREN	4
#define LDAP_SCHERR_NODIGIT		5
#define LDAP_SCHERR_BADNAME		6
#define LDAP_SCHERR_BADDESC		7
#define LDAP_SCHERR_BADSUP		8
#define LDAP_SCHERR_DUPOPT		9
#define LDAP_SCHERR_EMPTY		10


> 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!

Ok, I can try to fix things along the lines of David's patch (but 
including the error code). It will however take me at least one week. 

Hans

-- 
Han...@Ph...