python-ldap-dev — discussion among developers

Re: Multiple Email Values

[Chris D. <pa...@ft...>]

On Wed, Dec 30, 2009 at 02:41:03PM +0100, Christoph Holtermann wrote:
> Hello all !
> 
> I have a basic question about data representation in LDAP.
> I know just this list, maybe you can point me to the right one.
> I use LDAP for storing my contacts. I keep thinking about the
> simple case of people having multiple email. One case
> would be to have an attribute "mail" another one "mozillaSecond
> Email". On the other hand I know that it
> is possible to store multiple values in the corresponding LDAP-
> attribute. but i wonder how it could be possible to also store
> an additional information about these email. For example
> Hans Wurst has
> a@b.c "work",
> b@b.c "outdated since 2000"...
> I guess that this is not possible or needs complex modifications.
> Does anybody know something helpful about this ?

You probably want a general LDAP or openldap mailing list for this but...
I'm not subscribed to one either :-).

First take a peek at this from the openldap-software list

http://www.openldap.org/lists/openldap-software/200203/msg00646.html

If you're caring from an MTA perspective...
Postfix's LDAP maps suggest a 'maildrop' attribute for calculating actual
delivery.

And now a suggestion so you can spend an afternoon seeing what it
breaks...
Well, atleast in my LDAP schemas the mail attribute has syntax
1.3.6.1.4.1.1466.115.121.1.15

And looking at 6.10 of RFC2252
http://tools.ietf.org/html/rfc2252

You can put any unicode string there you want to such
as 
Christoph Holtermann Obsolete  <c.h...@fo...r>


-- 
Chris Dukes
"In cynicism she's about 35" -- Terry Pratchett's "Hog Father"

Re: Multiple Email Values

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

Christoph Holtermann wrote:
> I have a basic question about data representation in LDAP.
> I know just this list, maybe you can point me to the right one.

For general LDAP questions you might find ld...@um... more helpful since
there are more people lurking there.

> I use LDAP for storing my contacts. I keep thinking about the
> simple case of people having multiple email.

Unfortunately this case is not simple.

> One case
> would be to have an attribute "mail" another one "mozillaSecond
> Email". On the other hand I know that it
> is possible to store multiple values in the corresponding LDAP-
> attribute. but i wonder how it could be possible to also store
> an additional information about these email. For example
> Hans Wurst has
> a@b.c "work",
> b@b.c "outdated since 2000"...
> I guess that this is not possible or needs complex modifications.
> Does anybody know something helpful about this ?

The big question is what your LDAP-enabled MUAs or other LDAP clients expect
in the attribute 'mail' or how you can configure the clients used to handle
other attributes etc. E.g. I don't any MUA which handles multiple attribute
values in 'mail' in a smart way. Simply the first value is taken.

I guess at the end you'll find yourself to add separate entries for all e-mail
adresses and office locations.

Ciao, Michael.

Multiple Email Values

[Christoph H. <c.h...@gm...>]

Hello all !

I have a basic question about data representation in LDAP.
I know just this list, maybe you can point me to the right one.
I use LDAP for storing my contacts. I keep thinking about the
simple case of people having multiple email. One case
would be to have an attribute "mail" another one "mozillaSecond
Email". On the other hand I know that it
is possible to store multiple values in the corresponding LDAP-
attribute. but i wonder how it could be possible to also store
an additional information about these email. For example
Hans Wurst has
a@b.c "work",
b@b.c "outdated since 2000"...
I guess that this is not possible or needs complex modifications.
Does anybody know something helpful about this ?

regards,

C.Holtermann

Re: python-ldap syncrepl consumer

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

Mikkel Kruse Johnsen wrote:
> Sean did you ever get your python-ldap consumer to work ?

I'd also like to know this. But I suspect it's currently not possible due to
http://sourceforge.net/tracker/?func=detail&aid=2829057&group_id=2072&atid=352072

> I was searching the net for a way to update other systems, when my LDAP
> changed. I found your attempt to make a python consumer. Do you have any
> code, other than want i can find in the maillinglist ?

In a customer project we've implemented a short-time polling system querying
OpenLDAP's accesslog database which also leads to quick updates on the target.

Ciao, Michael.

Re: Patch for broken slapd.py

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

Christian Oudard wrote:
> 2009/12/17 Michael Ströder <mi...@st...>:
>> In this case I'm not familiar with slapd.py which was written by David and
>> after glancing over it I strongly dislike some of the assumptions made
>> therein. So I'm not going to touch that now because of lack of time.
>
> I'm in the process of adapting slapd.py to be a general purpose mock
> ldap test server for running unit tests against. I would be interested
> in contributing improvements to it that keep it compatible with the
> test suite of python-ldap.
> Specifically, what sort of assumptions are you trying to get rid of?

Some short comments:

1. It should also work on Windows which is not possible with the currently
implemented filename handling.

2. Probably a template for slapd.conf should be used which can be more easily
adapted to various OpenLDAP releases, especially no references to specific
schema files etc.

3. Data should be kept locally in a sub-directory like with OpenLDAP's test
suite. No need for /var/blurb.

4. The assumption about slapd executable being in something like /usr/sbin/ is
wrong. Rather the full path to slapd and slaptest should be specified.

Ciao, Michael.

Re: Patch for broken slapd.py

[Christian O. <chr...@gm...>]

I'm in the process of adapting slapd.py to be a general purpose mock
ldap test server for running unit tests against. I would be interested
in contributing improvements to it that keep it compatible with the
test suite of python-ldap.

Specifically, what sort of assumptions are you trying to get rid of?

2009/12/17 Michael Ströder <mi...@st...>:
> Christian Oudard wrote:
>> On my system, slapd.py fails because of a missing /var/tmp/python-ldap-test .
>>
>> Not sure what your patch submission procedure is, but here's a patch
>> to fix that:
>
> Hmm, normally I review patches and commit them. So you did the right thing
> posting it here.
>
> In this case I'm not familiar with slapd.py which was written by David and
> after glancing over it I strongly dislike some of the assumptions made
> therein. So I'm not going to touch that now because of lack of time.
>
> Ciao, Michael.
>
>

Re: Patch for broken slapd.py

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

Christian Oudard wrote:
> On my system, slapd.py fails because of a missing /var/tmp/python-ldap-test .
> 
> Not sure what your patch submission procedure is, but here's a patch
> to fix that:

Hmm, normally I review patches and commit them. So you did the right thing
posting it here.

In this case I'm not familiar with slapd.py which was written by David and
after glancing over it I strongly dislike some of the assumptions made
therein. So I'm not going to touch that now because of lack of time.

Ciao, Michael.

Patch for broken slapd.py

[Christian O. <chr...@gm...>]

On my system, slapd.py fails because of a missing /var/tmp/python-ldap-test .

Not sure what your patch submission procedure is, but here's a patch
to fix that:
==================================


diff --git a/pstat/dynamic_ldap/slapd.py b/pstat/dynamic_ldap/slapd.py
index 735b58e..2cd3e25 100644
--- a/pstat/dynamic_ldap/slapd.py
+++ b/pstat/dynamic_ldap/slapd.py
@@ -13,12 +13,25 @@ def quote(s):
     '''Quotes the '"' and '\' characters in a string and surrounds
with "..."'''
     return '"' + s.replace('\\','\\\\').replace('"','\\"') + '"'

-def mkdirs(path):
-    """Creates the directory path unless it already exists"""
-    if not os.access(os.path.join(path, os.path.curdir), os.F_OK):
-        _log.debug("creating temp directory %s", path)
-        os.mkdir(path)
-    return path
+def mkdir(newdir):
+    #http://code.activestate.com/recipes/82465/
+    """works the way a good mkdir should :)
+        - already exists, silently complete
+        - regular file in the way, raise an exception
+        - parent directory(ies) does not exist, make them as well
+    """
+    if os.path.isdir(newdir):
+        pass
+    elif os.path.isfile(newdir):
+        raise OSError("a file with the same name as the desired " \
+                      "dir, '%s', already exists." % newdir)
+    else:
+        head, tail = os.path.split(newdir)
+        if head and not os.path.isdir(head):
+            mkdir(head)
+        if tail:
+            os.mkdir(newdir)
+    return newdir

 def delete_directory_content(path):
     for dirpath,dirnames,filenames in os.walk(path, topdown=False):
@@ -138,7 +151,8 @@ class Slapd:
         cfg.append("allow bind_v2")

         # Database
-        ldif_dir = mkdirs(os.path.join(self.get_tmpdir(), "ldif-data"))
+        ldif_dir = os.path.join(self.get_tmpdir(), "ldif-data")
+        mkdir(ldif_dir)
         delete_directory_content(ldif_dir) # clear it out
         cfg.append("database ldif")
         cfg.append("directory " + quote(ldif_dir))
@@ -150,7 +164,7 @@ class Slapd:
     def _write_config(self):
         """Writes the slapd.conf file out, and returns the path to it."""
         path = os.path.join(self._tmpdir, "slapd.conf")
-        ldif_dir = mkdirs(self._tmpdir)
+        mkdir(self._tmpdir)
         if os.access(path, os.F_OK):
             self._log.debug("deleting existing %s", path)
             os.remove(path)

python-ldap syncrepl consumer

[Mikkel K. J. <mi...@li...>]

Hi All and Sean Burford

Sean did you ever get your python-ldap consumer to work ?

I was searching the net for a way to update other systems, when my LDAP
changed. I found your attempt to make a python consumer. Do you have any
code, other than want i can find in the maillinglist ?

Thoughts for usability is:

    GConf LDAP proxy/backend
    Kerberos password updater
    OpenAFS user administration 

Med Venlig Hilsen / Kind Regards




Mikkel Kruse
Johnsen
Adm.Dir.

Linet
Ørholmgade 6 st tv
Copenhagen N 2200
Denmark

Work:    +45
21287793
Mobile: +45
21287793
Email:
mi...@li...
IM:
mi...@li...
(MSN)
 Professional
Profile
Healthcare 


Network
Consultant 

Using the test ldap server for unittests

[Christian O. <chr...@gm...>]

I tried to run the runtests.sh script in the Tests/ directory, but it
didn't work, saying that the test ldap server wasn't running. I tried
installing slapd, but it still didn't work even when slapd was
running. What do I need to have installed or running to use these
unittests?

Also, I would like to set up a test ldap server for my own unittests
in another project, can anyone point me in the right direction for
this?

Decoding binary packets

[Attila N. <br...@fs...>]

Hello,

I would like to decode LDAP packets (queries and responses), captured 
with BPF. Is there any easy way with py-ldap to do this?

I've seen the LDAPmessage_to_python function, but it's not exported to 
python. Is that what I'm looking for?

Thanks,

Re: Compile error on RHEL 5.3 (x86_64), python-ldap-2.3.10

[Zhang H. <zhb...@gm...>]

On Nov 13, 2009, at 4:47 PM, Michael Ströder wrote:
> 
> Sorry, please try again from HEAD. I fixed also another typo.

It (HEAD) works now. :)

-- 
Best Regards.

Zhang Huangbin

- Open Source Mail Server Solution for Red Hat(R) Enterprise Linux,
  CentOS, Debian, Ubuntu: http://www.iredmail.org/

Re: Compile error on RHEL 5.3 (x86_64), python-ldap-2.3.10

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

Zhang Huangbin wrote:
> On Nov 5, 2009, at 1:14 AM, Michael Ströder wrote:
> 
>> This is because of older OpenLDAP libs. Try the patch below. It's also in HEAD
>> now.
> 
> I tested patch moment ago, failed to build, same as in HEAD (checked out moment ago):

Sorry, please try again from HEAD. I fixed also another typo.

Ciao, Michael.

Re: Compile error on RHEL 5.3 (x86_64), python-ldap-2.3.10

[Zhang H. <zhb...@gm...>]

On Nov 5, 2009, at 1:14 AM, Michael Ströder wrote:

> This is because of older OpenLDAP libs. Try the patch below. It's also in HEAD
> now.

I'm so sorry that i forgot this thread :(

I tested patch moment ago, failed to build, same as in HEAD (checked out moment ago):

----
# python setup.py clean
extra_compile_args: 
extra_objects: 
include_dirs: /usr/local/openldap-2.3/include /usr/include/sasl
library_dirs: /usr/local/openldap-2.3/lib
libs: ldap_r lber sasl2 ssl crypto
running clean
[root@r6 python-ldap]# python setup.py install
extra_compile_args: 
extra_objects: 
include_dirs: /usr/local/openldap-2.3/include /usr/include/sasl
library_dirs: /usr/local/openldap-2.3/lib
libs: ldap_r lber sasl2 ssl crypto
running install
running bdist_egg
running egg_info
creating Lib/python_ldap.egg-info
writing requirements to Lib/python_ldap.egg-info/requires.txt
writing Lib/python_ldap.egg-info/PKG-INFO
writing top-level names to Lib/python_ldap.egg-info/top_level.txt
writing dependency_links to Lib/python_ldap.egg-info/dependency_links.txt
writing manifest file 'Lib/python_ldap.egg-info/SOURCES.txt'
file Lib/ldap.py (for module ldap) not found
file Lib/ldap/schema.py (for module ldap.schema) not found
reading manifest template 'MANIFEST.in'
warning: no files found matching 'Makefile'
warning: no files found matching 'Modules/LICENSE'
writing manifest file 'Lib/python_ldap.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-x86_64/egg
running install_lib
running build_py
file Lib/ldap.py (for module ldap) not found
file Lib/ldap/schema.py (for module ldap.schema) not found
creating build
creating build/lib.linux-x86_64-2.4
copying Lib/ldapurl.py -> build/lib.linux-x86_64-2.4
copying Lib/ldif.py -> build/lib.linux-x86_64-2.4
copying Lib/dsml.py -> build/lib.linux-x86_64-2.4
creating build/lib.linux-x86_64-2.4/ldap
copying Lib/ldap/__init__.py -> build/lib.linux-x86_64-2.4/ldap
copying Lib/ldap/async.py -> build/lib.linux-x86_64-2.4/ldap
copying Lib/ldap/controls.py -> build/lib.linux-x86_64-2.4/ldap
copying Lib/ldap/cidict.py -> build/lib.linux-x86_64-2.4/ldap
copying Lib/ldap/dn.py -> build/lib.linux-x86_64-2.4/ldap
copying Lib/ldap/filter.py -> build/lib.linux-x86_64-2.4/ldap
copying Lib/ldap/functions.py -> build/lib.linux-x86_64-2.4/ldap
copying Lib/ldap/ldapobject.py -> build/lib.linux-x86_64-2.4/ldap
copying Lib/ldap/modlist.py -> build/lib.linux-x86_64-2.4/ldap
copying Lib/ldap/resiter.py -> build/lib.linux-x86_64-2.4/ldap
copying Lib/ldap/sasl.py -> build/lib.linux-x86_64-2.4/ldap
creating build/lib.linux-x86_64-2.4/ldap/schema
copying Lib/ldap/schema/__init__.py -> build/lib.linux-x86_64-2.4/ldap/schema
copying Lib/ldap/schema/models.py -> build/lib.linux-x86_64-2.4/ldap/schema
copying Lib/ldap/schema/subentry.py -> build/lib.linux-x86_64-2.4/ldap/schema
copying Lib/ldap/schema/tokenizer.py -> build/lib.linux-x86_64-2.4/ldap/schema
file Lib/ldap.py (for module ldap) not found
file Lib/ldap/schema.py (for module ldap.schema) not found
running build_ext
building '_ldap' extension
creating build/temp.linux-x86_64-2.4
creating build/temp.linux-x86_64-2.4/Modules
gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fPIC -DHAVE_LIBLDAP_R -DHAVE_SASL -DHAVE_TLS -DLDAPMODULE_VERSION=2.3.10 -IModules -I/usr/local/openldap-2.3/include -I/usr/include/sasl -I/usr/include/python2.4 -c Modules/LDAPObject.c -o build/temp.linux-x86_64-2.4/Modules/LDAPObject.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fPIC -DHAVE_LIBLDAP_R -DHAVE_SASL -DHAVE_TLS -DLDAPMODULE_VERSION=2.3.10 -IModules -I/usr/local/openldap-2.3/include -I/usr/include/sasl -I/usr/include/python2.4 -c Modules/ldapcontrol.c -o build/temp.linux-x86_64-2.4/Modules/ldapcontrol.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fPIC -DHAVE_LIBLDAP_R -DHAVE_SASL -DHAVE_TLS -DLDAPMODULE_VERSION=2.3.10 -IModules -I/usr/local/openldap-2.3/include -I/usr/include/sasl -I/usr/include/python2.4 -c Modules/common.c -o build/temp.linux-x86_64-2.4/Modules/common.o
gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fPIC -DHAVE_LIBLDAP_R -DHAVE_SASL -DHAVE_TLS -DLDAPMODULE_VERSION=2.3.10 -IModules -I/usr/local/openldap-2.3/include -I/usr/include/sasl -I/usr/include/python2.4 -c Modules/constants.c -o build/temp.linux-x86_64-2.4/Modules/constants.o
Modules/constants.c: In function ‘LDAPinit_constants’:
Modules/constants.c:186: error: ‘LDAP_OPT_X_TLS_NEWCTX’ undeclared (first use in this function)
Modules/constants.c:186: error: (Each undeclared identifier is reported only once
Modules/constants.c:186: error: for each function it appears in.)
error: command 'gcc' failed with exit status 1
----

-- 
Best Regards.

Zhang Huangbin

- Open Source Mail Server Solution for Red Hat(R) Enterprise Linux,
  CentOS, Debian, Ubuntu: http://www.iredmail.org/

Re: Compile error on RHEL 5.3 (x86_64), python-ldap-2.3.10

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

Rob Orsini wrote:
> Hi, I'm also having trouble getting 2.3.10 to compile on RHEL 5. I tried
> applying the patches supplied in this thread (I just joined this email
> list, btw):
> 
> In file included from Modules/LDAPObject.c:4:
> Modules/common.h:10:20: error: Python.h: No such file or directory

Please make sure you have all the necessary headers available on your system
for building Python extension modules and all the libs needed by python-ldap.
I don't know the package names on RHEL though.

Ciao, Michael.

Re: Best way to add an implementation specific schema model?

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

Chris Dukes wrote:
> I have to work with IBM Directory Server on a regular basis, and that
> includes some nasty schema analysis for moving some history local schema
> modifications to new versions of the product.
> I was able to use ldap.schema to simplify most of the nastiness.
> 
> However, IBM extends the schema with the additional attribute
> IBMAttributetypes, which describes chracteristics of how attributes will
> be stored in the backend.
> 
> IBM was polite enough to document the grammar for this new attribute and
> I'll be attempting to create an IBMAttributetype class to hold these.

I vaguely remember coming across these proprietary IBM schema attributes. I
wonder why they did not add their specific things to normal
AttributeTypeDescription like other directory vendors did. Oh, well...

Could you please refer to docs of the grammar?

> Now, should I just add the new class to ldap.schema.models and submit a
> patch once done?  Or should a long term approach of being able to
> indicate the addition of server specific extensions be contemplated?

I already thought about this when looking at vendor-specific extensions for
AttributeTypeDescription for Novell eDirectory and OpenLDAP.

Here are some remarks:

1. ldap.schema is somewhat experimental although quite robust in recent
deployments. The API is still undocumented mainly because I would be willing
to change it if someone comes up with good ideas how to improve it.

2. Lib/ldap/schema/models.py is very closely modeled after RFC 4512. If the
IBM grammar loosely follows what's in that RFC 4512 you have a good chance to
derive from these classes and extend them by setting class attribute
token_defaults according to what's needed.

3. There's ldap.schema.subentry.SCHEMA_CLASS_MAPPING which maps subschema
subentry attribute types to Python schema classes in ldap.schema.models. So
you have to somewhat register the IBM-specific attributes there.

Curious to hear about how to proceed with that.

Ciao, Michael.

RE: Compile error on RHEL 5.3 (x86_64), python-ldap-2.3.10

[Rob O. <rob...@gm...>]

Hi, I'm also having trouble getting 2.3.10 to compile on RHEL 5. I tried
applying the patches supplied in this thread (I just joined this email list,
btw):


http://sourceforge.net/mailarchive/forum.php?thread_name=4AF1B687.9040501%40stroeder.com&forum_name=python-ldap-dev

but that didn't work.

I noticed that some work related to this has been going on in the trunk:


http://python-ldap.cvs.sourceforge.net/viewvc/python-ldap/python-ldap/CHANGES?revision=1.217&view=markup

I downloaded that version and tried to build it. It failed, with:

$ python ./setup.py build
extra_compile_args:
extra_objects:
include_dirs: /usr/local/openldap-2.3/include /usr/include/sasl
library_dirs: /usr/local/openldap-2.3/lib
libs: ldap_r lber sasl2 ssl crypto
running build
running build_py
file Lib/ldap.py (for module ldap) not found
file Lib/ldap/schema.py (for module ldap.schema) not found
file Lib/ldap.py (for module ldap) not found
file Lib/ldap/schema.py (for module ldap.schema) not found
running egg_info
writing requirements to Lib/python_ldap.egg-info/requires.txt
writing Lib/python_ldap.egg-info/PKG-INFO
writing top-level names to Lib/python_ldap.egg-info/top_level.txt
writing dependency_links to Lib/python_ldap.egg-info/dependency_links.txt
file Lib/ldap.py (for module ldap) not found
file Lib/ldap/schema.py (for module ldap.schema) not found
reading manifest template 'MANIFEST.in'
warning: no files found matching 'Makefile'
warning: no files found matching 'Modules/LICENSE'
writing manifest file 'Lib/python_ldap.egg-info/SOURCES.txt'
running build_ext
building '_ldap' extension
gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -Wall
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
--param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fPIC
-DHAVE_LIBLDAP_R -DHAVE_SASL -DHAVE_TLS -DLDAPMODULE_VERSION=2.3.10
-IModules -I/usr/local/openldap-2.3/include -I/usr/include/sasl
-I/usr/include/python2.4 -c Modules/LDAPObject.c -o
build/temp.linux-x86_64-2.4/Modules/LDAPObject.o
In file included from Modules/LDAPObject.c:4:
Modules/common.h:10:20: error: Python.h: No such file or directory
In file included from Modules/LDAPObject.c:4:
Modules/common.h:35: error: expected ‘)’ before ‘*’ token
Modules/LDAPObject.c:5:24: error: patchlevel.h: No such file or directory
In file included from Modules/LDAPObject.c:9:
Modules/errors.h:11: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’
before ‘*’ token
Modules/errors.h:12: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’
before ‘*’ token
Modules/errors.h:13: error: expected ‘)’ before ‘*’ token
Modules/errors.h:14: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’
before ‘*’ token
In file included from Modules/LDAPObject.c:10:
Modules/constants.h:8: error: expected ‘)’ before ‘*’ token
Modules/constants.h:9: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘*’ token
In file included from Modules/LDAPObject.c:11:
Modules/LDAPObject.h:16: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘*’ token
Modules/LDAPObject.h:22: error: expected specifier-qualifier-list before
‘PyObject_HEAD’
Modules/LDAPObject.h:28: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘LDAP_Type’
In file included from Modules/LDAPObject.c:12:
Modules/ldapcontrol.h:10: error: expected ‘)’ before ‘*’ token
Modules/ldapcontrol.h:12: error: expected ‘)’ before ‘*’ token
Modules/ldapcontrol.h:13: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘*’ token
In file included from Modules/LDAPObject.c:13:
Modules/message.h:11: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘*’ token
In file included from Modules/LDAPObject.c:14:
Modules/berval.h:10: error: expected ‘)’ before ‘*’ token
Modules/berval.h:11: error: expected ‘)’ before ‘*’ token
Modules/berval.h:13: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’
before ‘*’ token
In file included from Modules/LDAPObject.c:15:
Modules/options.h:5: error: expected declaration specifiers or ‘...’ before
‘PyObject’
Modules/options.h:6: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’
before ‘*’ token
Modules/LDAPObject.c: In function ‘newLDAPObject’:
Modules/LDAPObject.c:28: warning: implicit declaration of function
‘PyObject_NEW’
Modules/LDAPObject.c:28: error: expected expression before ‘LDAPObject’
Modules/LDAPObject.c:28: warning: cast to pointer from integer of different
size
Modules/LDAPObject.c:31: error: ‘LDAPObject’ has no member named ‘ldap’
Modules/LDAPObject.c:32: error: ‘LDAPObject’ has no member named ‘_save’
Modules/LDAPObject.c:33: error: ‘LDAPObject’ has no member named ‘valid’
Modules/LDAPObject.c: In function ‘dealloc’:
Modules/LDAPObject.c:42: error: ‘LDAPObject’ has no member named ‘ldap’
Modules/LDAPObject.c:43: error: ‘LDAPObject’ has no member named ‘valid’
Modules/LDAPObject.c:44: error: ‘LDAPObject’ has no member named ‘_save’
Modules/LDAPObject.c:44: warning: implicit declaration of function
‘Py_FatalError’
Modules/LDAPObject.c:44: error: ‘LDAPObject’ has no member named ‘_save’
Modules/LDAPObject.c:44: warning: implicit declaration of function
‘PyEval_SaveThread’
Modules/LDAPObject.c:45: error: ‘LDAPObject’ has no member named ‘ldap’
Modules/LDAPObject.c:46: error: ‘_threadstate’ undeclared (first use in this
function)
Modules/LDAPObject.c:46: error: (Each undeclared identifier is reported only
once
Modules/LDAPObject.c:46: error: for each function it appears in.)
Modules/LDAPObject.c:46: error: expected ‘;’ before ‘_save’
Modules/LDAPObject.c:46: error: ‘LDAPObject’ has no member named ‘_save’
Modules/LDAPObject.c:46: warning: implicit declaration of function
‘PyEval_RestoreThread’
Modules/LDAPObject.c:46: error: ‘_save’ undeclared (first use in this
function)
Modules/LDAPObject.c:47: error: ‘LDAPObject’ has no member named ‘valid’
Modules/LDAPObject.c:49: error: ‘LDAPObject’ has no member named ‘ldap’
Modules/LDAPObject.c:51: warning: implicit declaration of function
‘PyObject_DEL’
Modules/LDAPObject.c: In function ‘not_valid’:
Modules/LDAPObject.c:65: error: ‘LDAPObject’ has no member named ‘valid’
Modules/LDAPObject.c:68: warning: implicit declaration of function
‘PyErr_SetString’
Modules/LDAPObject.c:68: error: ‘LDAPexception_class’ undeclared (first use
in this function)
Modules/LDAPObject.c: In function ‘LDAPMod_DEL’:
Modules/LDAPObject.c:81: warning: implicit declaration of function
‘PyMem_DEL’
Modules/LDAPObject.c: At top level:
Modules/LDAPObject.c:104: error: expected ‘)’ before ‘*’ token
Modules/LDAPObject.c:207: error: expected ‘)’ before ‘*’ token
Modules/LDAPObject.c:259: error: expected ‘)’ before ‘*’ token
Modules/LDAPObject.c:327: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘*’ token
Modules/LDAPObject.c:367: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘*’ token
Modules/LDAPObject.c:407: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘*’ token
Modules/LDAPObject.c:453: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘*’ token
Modules/LDAPObject.c:554: error: expected declaration specifiers or ‘...’
before ‘PyObject’
Modules/LDAPObject.c: In function ‘interaction’:
Modules/LDAPObject.c:557: error: ‘PyObject’ undeclared (first use in this
function)
Modules/LDAPObject.c:557: error: ‘result’ undeclared (first use in this
function)
Modules/LDAPObject.c:559: warning: implicit declaration of function
‘PyObject_CallMethod’
Modules/LDAPObject.c:559: error: ‘SASLObject’ undeclared (first use in this
function)
Modules/LDAPObject.c:570: warning: implicit declaration of function
‘PyString_AsString’
Modules/LDAPObject.c:570: warning: assignment makes pointer from integer
without a cast
Modules/LDAPObject.c:586: warning: implicit declaration of function
‘Py_DECREF’
Modules/LDAPObject.c: In function ‘py_ldap_sasl_interaction’:
Modules/LDAPObject.c:608: error: ‘PyObject’ undeclared (first use in this
function)
Modules/LDAPObject.c:608: error: ‘SASLObject’ undeclared (first use in this
function)
Modules/LDAPObject.c:608: error: expected expression before ‘)’ token
Modules/LDAPObject.c:612: error: too many arguments to function
‘interaction’
Modules/LDAPObject.c: At top level:
Modules/LDAPObject.c:619: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘*’ token
Modules/LDAPObject.c:697: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘*’ token
Modules/LDAPObject.c:739: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘*’ token
Modules/LDAPObject.c:784: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘*’ token
Modules/LDAPObject.c:825: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘*’ token
Modules/LDAPObject.c:873: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘*’ token
Modules/LDAPObject.c:917: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘*’ token
Modules/LDAPObject.c:1015: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘*’ token
Modules/LDAPObject.c:1082: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘*’ token
Modules/LDAPObject.c:1126: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘*’ token
Modules/LDAPObject.c:1148: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘*’ token
Modules/LDAPObject.c:1165: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘*’ token
Modules/LDAPObject.c:1178: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘*’ token
Modules/LDAPObject.c:1235: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘methods’
Modules/LDAPObject.c:1264: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘*’ token
Modules/LDAPObject.c:1273: error: expected declaration specifiers or ‘...’
before ‘PyObject’
Modules/LDAPObject.c: In function ‘setattr’:
Modules/LDAPObject.c:1275: error: ‘PyExc_AttributeError’ undeclared (first
use in this function)
Modules/LDAPObject.c: At top level:
Modules/LDAPObject.c:1281: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘LDAP_Type’
error: command 'gcc' failed with exit status 1


I would love to help test this. Please let me know what I can send you to be
most useful.

Also, thanks for all your work on this.

Rob

Best way to add an implementation specific schema model?

[Chris D. <pak...@gm...>]

I have to work with IBM Directory Server on a regular basis, and that
includes some nasty schema analysis for moving some history local schema
modifications to new versions of the product.
I was able to use ldap.schema to simplify most of the nastiness.

However, IBM extends the schema with the additional attribute
IBMAttributetypes, which describes chracteristics of how attributes will be
stored in the backend.

IBM was polite enough to document the grammar for this new attribute and
I'll be attempting to create an IBMAttributetype class to hold these.

Now, should I just add the new class to ldap.schema.models and submit a
patch once done?  Or should a long term approach of being able to indicate
the addition of server specific extensions be contemplated?

Thanks,
Chris Dukes

Re: How to modify several dn in one time

[Marcus <ma...@py...>]

Hi,

Anyone knows of any python based LDAP servers? The main objective is to 
have on that run on Windows. The OpenLdap i have
tested is pretty unstable in Windows, crashes every 4-5 days.  The 
Apache DS in java works better but would prefer if there is a python 
version.
Or anyone have ldaptor working as a basic LDAP, i just need to provide 
simple lookups , don't even need full compliance of authentication etc.

Marc.


Zhang Huangbin wrote:
> On Nov 5, 2009, at 1:15 AM, Michael Ströder wrote:
>
>   
>> Zhang Huangbin wrote:
>>     
>>> it seems .modify() or .modify_s() can only modify one dn in one time.
>>> How can i modify several dn in one time?
>>>       
>> You can't. These methods strictly follow the LDAP functional model  
>> (see RFC
>> 4511, section 4.6. Modify Operation).
>>     
>
> Got it. Thanks Chris & Chaos & Michael. :)
>
>   

Re: How to modify several dn in one time

[Zhang H. <zhb...@gm...>]

On Nov 5, 2009, at 1:15 AM, Michael Ströder wrote:

> Zhang Huangbin wrote:
>> it seems .modify() or .modify_s() can only modify one dn in one time.
>> How can i modify several dn in one time?
>
> You can't. These methods strictly follow the LDAP functional model  
> (see RFC
> 4511, section 4.6. Modify Operation).

Got it. Thanks Chris & Chaos & Michael. :)

-- 
Best Regards.

Zhang Huangbin

- Open Source Mail Server Solution for Red Hat(R) Enterprise Linux,
   CentOS, Debian, Ubuntu: http://www.iredmail.org/

Contributing Mac OS X packages to PyPI

[Ben G. <bgo...@tc...>]

I have built universal binary packages for Python-LDAP 2.3.10 on both  
Mac OS X 10.5 (Python 2.5) and 10.6 (Python 2.6). Is it possible to  
add these to the PyPI page, to go along with the Windows installers?  
They can be very useful for users that don't have Xcode / gcc installed.


Cheers,
-- 
Ben

Re: connection pooling

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

Anil wrote:
> I am looking to do connection pooling and am thinking of doing something 
> like http://www.sqlalchemy.org/docs/05/reference/sqlalchemy/pooling.html
> 
> Can you guys give some advice and/or better yet, has someone already 
> done this?

I don't know any connection pooling for python-ldap's LDAPObject instances. It
would be certainly nice to have one. I'd recommend to make it look like
ReconnectLDAPObject instances.

Ciao, Michael.

Re: How to modify several dn in one time

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

Zhang Huangbin wrote:
> it seems .modify() or .modify_s() can only modify one dn in one time.  
> How can i modify several dn in one time?

You can't. These methods strictly follow the LDAP functional model (see RFC
4511, section 4.6. Modify Operation).

> Such as ldapadd command:
> 
> # ldapadd -x -D 'cn=Manager,dc=xxx,dc=xxx' -wpasswd -f new.ldif
> 
> Content of new.ldif:
> 
> dn: cn=vmail,dc=xxx,dc=xxx
> changetype: modify
> add: cn
> cn: newCN
> cn: newCN2
> --
> dn: cn=user01,dc=xxx,dc=xxx
> changetype: modify
> cn: newCN
> cn: newCN2

These will lead to sevaral add requests being sent by command-line tool
ldapadd. Same with ldapmodify reading several change records from LDIF file
and sending a modify request for each of these.

Ciao, Michael.

Re: Compile error on RHEL 5.3 (x86_64), python-ldap-2.3.10

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

Zhang Huangbin wrote:
> 
> I got below compile error on Red Hat Enterprise Linux 5.3 (x86_64)  
> with python-ldap-2.3.10, but 2.3.8 was compiled and installed success.
> What's wrong with it?
> 
> Modules/constants.c:184: error: ‘LDAP_OPT_X_TLS_NEWCTX’ undeclared  

Well, I asked for testing long *before* releasing 2.3.10...
This is because of older OpenLDAP libs. Try the patch below. It's also in HEAD
now.

Ciao, Michael.

Index: Modules/constants.c
===================================================================
RCS file: /cvsroot/python-ldap/python-ldap/Modules/constants.c,v
retrieving revision 1.43
diff -u -r1.43 constants.c
--- Modules/constants.c 23 Oct 2009 09:09:37 -0000      1.43
+++ Modules/constants.c 4 Nov 2009 15:48:04 -0000
@@ -162,7 +162,9 @@
        add_int(d,OPT_URI);
 #ifdef HAVE_TLS
        add_int(d,OPT_X_TLS);
+#ifdef LDAP_OPT_X_TLS_NEWCTX
        add_int(d,OPT_X_TLS_CTX);
+#endif
        add_int(d,OPT_X_TLS_CACERTFILE);
        add_int(d,OPT_X_TLS_CACERTDIR);
        add_int(d,OPT_X_TLS_CERTFILE);
Index: Modules/options.c
===================================================================
RCS file: /cvsroot/python-ldap/python-ldap/Modules/options.c,v
retrieving revision 1.33
diff -u -r1.33 options.c
--- Modules/options.c   23 Oct 2009 09:09:37 -0000      1.33
+++ Modules/options.c   4 Nov 2009 15:48:04 -0000
@@ -79,7 +79,9 @@
 #ifdef HAVE_TLS
     case LDAP_OPT_X_TLS:
     case LDAP_OPT_X_TLS_REQUIRE_CERT:
+#ifdef LDAP_OPT_X_TLS_NEWCTX
     case LDAP_OPT_X_TLS_NEWCTX:
+#endif
 #ifdef OPT_X_TLS_PROTOCOL_MIN
     case LDAP_OPT_X_TLS_PROTOCOL_MIN:
 #endif

Compile error on RHEL 5.3 (x86_64), python-ldap-2.3.10

[Zhang H. <zhb...@gm...>]

Hi, list.

I got below compile error on Red Hat Enterprise Linux 5.3 (x86_64)  
with python-ldap-2.3.10, but 2.3.8 was compiled and installed success.
What's wrong with it?

----
# easy_install python-ldap==2.3.10
Searching for python-ldap==2.3.10
Reading http://cheeseshop.python.org/pypi/python-ldap/
Reading http://cheeseshop.python.org/pypi/python-ldap/2.3.8
Reading http://www.python-ldap.org/
Reading http://cheeseshop.python.org/pypi/python-ldap/2.3.10
Best match: python-ldap 2.3.10
Downloading http://pypi.python.org/packages/source/p/python-ldap/python-ldap-2.3.10.tar.gz#md5=564d741a7c6d5fdcb45322fe9262d1a5
Processing python-ldap-2.3.10.tar.gz
Running python-ldap-2.3.10/setup.py -q bdist_egg --dist-dir /tmp/ 
easy_install-H9lpqP/python-ldap-2.3.10/egg-dist-tmp-qxCHzX
extra_compile_args:
extra_objects:
include_dirs: /usr/local/openldap-2.3/include /usr/include/sasl
library_dirs: /usr/local/openldap-2.3/lib
libs: ldap_r lber sasl2 ssl crypto
file Lib/ldap.py (for module ldap) not found
file Lib/ldap/schema.py (for module ldap.schema) not found
warning: no files found matching 'Makefile'
warning: no files found matching 'Modules/LICENSE'
file Lib/ldap.py (for module ldap) not found
file Lib/ldap/schema.py (for module ldap.schema) not found
file Lib/ldap.py (for module ldap) not found
file Lib/ldap/schema.py (for module ldap.schema) not found
Modules/constants.c: In function ‘LDAPinit_constants’:
Modules/constants.c:184: error: ‘LDAP_OPT_X_TLS_NEWCTX’ undeclared  
(first use in this function)
Modules/constants.c:184: error: (Each undeclared identifier is  
reported only once
Modules/constants.c:184: error: for each function it appears in.)
error: Setup script exited with error: command 'gcc' failed with exit  
status 1
----
-- 
Best Regards.

Zhang Huangbin

- Open Source Mail Server Solution for Red Hat(R) Enterprise Linux,
   CentOS, Debian, Ubuntu: http://www.iredmail.org/