python-ldap-dev — discussion among developers

Re: delete_s() result

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

Michael Engelhart wrote:
>> Thanks to the early design decision of David you don't have to do 
>> error handling by checking result codes. If an error occurs during 
>> deletion of an entry an exception of class ldap.LDAPError or a derived 
>> error class is raised.
> 
> maybe that little tidbit should be in the documentation somewhere? 

http://python-ldap.sourceforge.net/doc/python-ldap/node9.html

Ciao, Michael.

Re: delete_s() result

[Michael E. <men...@ka...>]

Very cool.  That's the way it should be!

maybe that little tidbit should be in the documentation somewhere?=20
although now it's archived in the mailing list... :-)

Mike
On Tuesday, October 29, 2002, at 12:07  PM, Michael Str=F6der wrote:

>
> Thanks to the early design decision of David you don't have to do=20
> error handling by checking result codes. If an error occurs during=20
> deletion of an entry an exception of class ldap.LDAPError or a derived=20=

> error class is raised.
>
> You can safely ignore results of add_s(), bind_s(), delete_s(),=20
> modify_s(), modrdn_s(), rename_s() and unbind_s().
>
> Ciao, Michael.

Re: delete_s() result

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

Michael Engelhart wrote:
> The result of the operation is succesful either way in 
> that it deletes the dn passed to it which is really all I care about 
> anyway.  I'll  just ignore results from delete.

Thanks to the early design decision of David you don't have to do error 
handling by checking result codes. If an error occurs during deletion of an 
entry an exception of class ldap.LDAPError or a derived error class is raised.

You can safely ignore results of add_s(), bind_s(), delete_s(), modify_s(), 
modrdn_s(), rename_s() and unbind_s().

Ciao, Michael.

Re: delete_s() result

[Michael E. <men...@ka...>]

Great - thanks.   The result of the operation is succesful either way=20
in that it deletes the dn passed to it which is really all I care about=20=

anyway.  I'll  just ignore results from delete.

Mike
On Tuesday, October 29, 2002, at 10:28  AM, Michael Str=F6der wrote:

> Michael Engelhart wrote:
> > Does a succesful ldap.delete_s() call return an empty list?
>
> Hmm, according to the ancient __doc__ string it should return None.
>
> But maybe this changed because of the new implementation of delete_s()=20=

> in the Python wrapper class ldap.ldapobject.SimpleLDAPObject.
>
> Best bet is to ignore the result of delete_s(). It won't contain any=20=

> useful information. In opposite delete() returns the msgid as usual=20
> for async methods.
>
> Ciao, Michael.
>

Re: delete_s() result

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

Michael Engelhart wrote:
 > Does a succesful ldap.delete_s() call return an empty list?

Hmm, according to the ancient __doc__ string it should return None.

But maybe this changed because of the new implementation of delete_s() in 
the Python wrapper class ldap.ldapobject.SimpleLDAPObject.

Best bet is to ignore the result of delete_s(). It won't contain any useful 
information. In opposite delete() returns the msgid as usual for async methods.

Ciao, Michael.

delete_s() result

[Michael E. <men...@ka...>]

Hi all -
Does a succesful ldap.delete_s() call return an empty list?

It seems to be the case but the documentation doesn't specify what the 
return value should be.

On a related note, if this is the correct return value from that call, 
then searching, modifying and deleting all work properly on a Mac OS X 
build of python-ldap even though there is an error message at the end 
of the setup.py build script.

Cheers
Mike

Re: compile python-ldap on macosx

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

you did not quite understand. i am talking about the fact that the 
standard slapd.conf points to a database file that does not exist by 
default. (-> /var/db/openldap/network.nidb or somesuch thing).

jens


On Sunday, Oct 27, 2002, at 12:29 US/Eastern, Michael Engelhart wrote:

>> clean or not, it does not work out of the box ;)
> Huh?? We're talking about Mac OS X desktop here right?   Why does 
> having to adjust a configuration file before you run slapd considered 
> not working out of the box?  How would you have them pre-configure 
> it???  It's not any different than having to configure an email client 
> to read email from your POP account.  In my mind I would say that it 
> totally works out of the box.  All I had to do was add the following 
> to /etc/openldap/slapd.conf (making changes to work within your needs 
> ---  I also commented out the netinfo stuff because I'm not using 
> NetInfo)
>
> database ldbm
> suffix "o=mydomain.com"
> rootdn "cn=Directory Manager,o= mydomain.com"
> rootpw somepw
> directory /var/db/openldap/openldap-data/
> cachesize       1000000
> dbcachesize     10000000
> index uid,cn,sn,givenName pres,eq,sub
> sizelimit       5000
>
> -- I wouldn't expect Apple to guess for me what I wanted here :-)
>
> Then you can either set LDAP to run at startup (which has been 
> discussed here) or type /usr/libexec/slapd and you're up and running.  
>   You of course need to add the entries (either with the command line 
> ldapadd or via some GUI admin tool) you want to search on to it to 
> make it do what you want but I assume that's true of any LDAP server.
> BTW, the database you're talking about not existing with the default 
> slapd.conf is because you probably  don't have anything in your 
> netinfo setup.   Try launching slapd and then going into Netinfo and 
> adding users and see if it gets created.
>
>
> Mike
>
>
> On Sunday, October 27, 2002, at 10:39  AM, Jens Vagelpohl wrote:
>
>> clean or not, it does not work out of the box ;)  the slapd.conf 
>> points to a database that does not exist, at least on my own system. 
>> i assume you have to make some explicit gesture to build that 
>> database file.
>>
>> even if this database existed and some unsuspecting person started 
>> using it i wonder what kind of security hole you open by not 
>> explicitly disabling the serving of netinfo data...
>>
>> on my own system i have now switched to using the built-in OpenLDAP 
>> by adjusting the slapd.conf (and commenting out the pieces pertaining 
>> to the netinfo bridge) and use it without problems through 
>> python-ldap compiled against my self-built python 2.1.3.
>>
>> jens
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: ApacheCon, November 18-21 in
> Las Vegas (supported by COMDEX), the only Apache event to be
> fully supported by the ASF. http://www.apachecon.com
> _______________________________________________
> Python-LDAP-dev mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev

Re: compile python-ldap on macosx

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

The python bit is out of the openldap-netinfo bridge's hand :) As for 
there not being a database, that is true. There are steps required to 
enabling that, and users are expected to use the Directory Services 
Admin app in the Application->Utilities folder to manage it. The 
settings as provided are a template that point to an as-yet-to-be-made 
backend link. Remember, security first. Second, by default, users are 
told to limit the LDAP exposure to explicit hosts (using the firewall 
components) -- one annoying trait is that by default the LDAP-enabled 
Netinfo is exposed without SSL-enabled connections. Again, its off by 
default and is generally managed through the GUI tools.

If people want to use the LDAP server is the "normal" way, modifying 
slapd.conf to use different backends is simple. "we" fought hard to 
make sure various schemas were supported out of the box.

On Sunday, October 27, 2002, at 07:39 AM, Jens Vagelpohl wrote:

> clean or not, it does not work out of the box ;)  the slapd.conf 
> points to a database that does not exist, at least on my own system. i 
> assume you have to make some explicit gesture to build that database 
> file.
>
> even if this database existed and some unsuspecting person started 
> using it i wonder what kind of security hole you open by not 
> explicitly disabling the serving of netinfo data...
>
> on my own system i have now switched to using the built-in OpenLDAP by 
> adjusting the slapd.conf (and commenting out the pieces pertaining to 
> the netinfo bridge) and use it without problems through python-ldap 
> compiled against my self-built python 2.1.3.
>
> jens
>
> On Saturday, Oct 26, 2002, at 14:20 US/Eastern, Joe Little wrote:
>
>>
>> its an openldap to Netinfo bridge, done by Luke Howard (padl.com). In 
>> other words.. its as clean as you can get. Its compliant and works 
>> fine. I'm already using it as such in one case. Anybody can modify 
>> the schema to be what not and it won't break anything, since by 
>> default the system uses Netinfo and not LDAP and some steps are 
>> required to activate the LDAP bridge.
>>
>> Software update won't modify the slapd.conf to my knowledge. That is 
>> generated one time with a mkslapdconf command from the netinfo 
>> sources (during activation). Its similar to what a .deb or .rpm would 
>> do with the default slapd.conf -- not change it unless its not there.
>>
>> On Saturday, October 26, 2002, at 07:48 AM, Jens Vagelpohl wrote:
>>
>>> looking at the configuration files under /etc/openldap i suppose 
>>> this "built-in" ldap server is designed to serve NetInfo data 
>>> through LDAP. not sure what that is supposed to be good for on a 
>>> normal OS X > install.
>>>
>>> i'd be weary to try and use that server to serve out other stuff as 
>>> well. i'm not sure Software Update would recognize changes and not 
>>> just replace the files the next time there is an updated ldap >>> bundle.
>>>
>>> jens
>>>
>>>
>>> On Saturday, Oct 26, 2002, at 03:22 US/Eastern, Michael Engelhart 
>>> wrote:
>>>
>>>> Hello Juergen,
>>>>
>>>> I just recently installed python-ldap on a stock Mac OS 10.2 
>>>> powerbook using the stock python 2.2 distribution that is >>>> installed.
>>>>
>>>> first  - in setup.py do change the first 2 lines to:
>>>>
>>>> library_dirs = /usr/lib
>>>> include_dirs = /usr/include
>>>>
>>>> I believe you'll get that same gcc error message but after you run 
>>>> python setup.py build, do a:
>>>> sudo python setup.py install
>>>>
>>>> and it should install the libraries fine.
>>>>
>>>> I am new  to OpenLDAP so I'm having lots of trouble modifying 
>>>> entries and will be posting here soon but want to make sure my 
>>>> OpenLDAP configuration is setup correctly before I do that.
>>>>
>>>> BTW, for those who were asking, OpenLDAP v 2.1.0 is what is 
>>>> installed by default on Mac OS X v 10.2   There may have been some 
>>>> minor changes in the latest System update but it's at least 2.1.x
>>>>
>>>> Cheers
>>>> Mike
>>>> On Friday, October 25, 2002, at 07:38  AM, J. Scholtes wrote:
>>>>
>>>>> Hi.
>>>>> I'm new to the list. In the list-archive I didn't find much about 
>>>>> macosx, so here is my post.
>>>>>
>>>>> I'm trying to set up ZOPE with the LDAPuserFolder on a 
>>>>> macosx-system and therefor I need python-ldap. But I#m not able to 
>>>>> compile it on MacOsX 10.2
>>>>> Is anyone on the List who did it successfull ?
>>>>>
>>>>> thanks
>>>>> Juergen Scholtes
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> -------------------------------------------------------
>>>>> This sf.net email is sponsored by: Influence the future of 
>>>>> Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) 
>>>>> program now. 
>>>>> http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en
>>>>> _______________________________________________
>>>>> Python-LDAP-dev mailing list
>>>>> Pyt...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
>>>>>
>>>>
>>>>
>>>>
>>>> -------------------------------------------------------
>>>> This SF.net email is sponsored by: ApacheCon, November 18-21 in
>>>> Las Vegas (supported by COMDEX), the only Apache event to be
>>>> fully supported by the ASF. http://www.apachecon.com
>>>> _______________________________________________
>>>> Python-LDAP-dev mailing list
>>>> Pyt...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
>>>
>>>
>>>
>>> -------------------------------------------------------
>>> This SF.net email is sponsored by: ApacheCon, November 18-21 in
>>> Las Vegas (supported by COMDEX), the only Apache event to be
>>> fully supported by the ASF. http://www.apachecon.com
>>> _______________________________________________
>>> Python-LDAP-dev mailing list
>>> Pyt...@li...
>>> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
>>
>>
>>
>> -------------------------------------------------------
>> This SF.net email is sponsored by: ApacheCon, November 18-21 in
>> Las Vegas (supported by COMDEX), the only Apache event to be
>> fully supported by the ASF. http://www.apachecon.com
>> _______________________________________________
>> Python-LDAP-dev mailing list
>> Pyt...@li...
>> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: ApacheCon, November 18-21 in
> Las Vegas (supported by COMDEX), the only Apache event to be
> fully supported by the ASF. http://www.apachecon.com
> _______________________________________________
> Python-LDAP-dev mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev

Re: compile python-ldap on macosx

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

Michael Engelhart wrote:
>> clean or not, it does not work out of the box ;)
> 
> Huh?? We're talking about Mac OS X desktop here right?   Why does having 
> to adjust a configuration file before you run slapd considered not 
> working out of the box?  How would you have them pre-configure it???  
> It's not any different than having to configure an email client to read 
> email from your POP account.  In my mind I would say that it totally 
> works out of the box.  All I had to do was add the following to 
> /etc/openldap/slapd.conf (making changes to work within your needs ---  
> I also commented out the netinfo stuff because I'm not using NetInfo)

As I understand it this thread is shifting off-topic at this point. Please 
let's stick to discussing python-ldap build problems on Max OS X here. And 
please take discussion about Open Directory installation/configuration to 
another more appropriate forum.

Thanks.

Ciao, Michael.

Re: compile python-ldap on macosx

[Michael E. <men...@ka...>]

I've been using python-ldap  scenario below for a few weeks now:
>
> - against built-in OpenLDAP and the built-in python 2.2: fails with 
> the error message that started this whole thread. the _ldap.so shared 
> module is not created because linking fails.

Even though it fails with an error the library is already built by that 
point so if you do a python setup.py install, it installs python ldap 
libraries which do work (at least partially - see below).  I've only 
tested connecting to a server and doing searches which all work fine 
and provide correct results.

BUT, when I try to do a delete or modify, I get an error message that 
says:
{'info': 'modifications require authentication', 'desc': 'Operations 
error'}

I'm connected (at least it seems like I am) with the rootdn and rootpw 
that I have configured in slapd.conf.
 From my understanding binding with that user/password should allow me 
to modify any entry in the database.
On the other hand maybe this is happening because the python-ldap 
library isn't built correctly.  I'm very new to LDAP in general so I 
can't tell.  maybe someone else on this list can help decipher that 
error response?   BTW, is there any way to determine how an ldap object 
is actually bound to the server (e.g., getBoundUserName type of method?)

The code I"m using to do this is based on my own simple LDAPWrapper 
class which is this:

import ldap

class LDAPWrapper:

	def __init__(self, user="", password=""):
		self.server = ldap.open("127.0.0.1")
		self.server.simple_bind(user, password)
		
	def search(self, base, filter, scope=ldap.SCOPE_SUBTREE, 
retrieveAttributes=None, limit=10):
		try:
			ldap_result_id = self.server.search(base, scope, filter, 
retrieveAttributes)	
			result_set = []
			for i in range(limit):
				result_type, result_data = self.server.result(ldap_result_id, 0)
				if (result_data == []):
					return result_set
				else:
					if result_type == ldap.RES_SEARCH_ENTRY:
						result_set.append(result_data)
			return result_set
		except ldap.SIZELIMIT_EXCEEDED, e:
			print e
		
	def delete(self, dn):
		try:
			result_type, result_data = self.server.delete_s(dn)
			if (result_type == 'RES_DELETE'):
				return 1 # true
			else:	
				return 0 # false
		except Exception, e:
			print e
			print "An error occurred during LDAPSearch.delete()"
			return None
			
	def close(self):
		self.server.unbind()
		

Any help would be appreciated and I will gladly test builds of 
python-ldap  on my OS X box since I need this to work for development 
purposes.

Cheers
Mike
On Sunday, October 27, 2002, at 10:34  AM, Jens Vagelpohl wrote:

> as far as compiling python-ldap goes, here is the outcome of a couple 
> experiments i did yesterday. all were done with the current CVS HEAD:
>
> - against self-compiled OpenLDAP 2.1.4 and self-compiled python 2.1.3: 
> no problem.
>
> - against built-in OpenLDAP and self-compiled python 2.1.3: no 
> problem. i specified "/usr/lib" as library_dirs and "/usr/include" as 
> include_dirs. libs was "ldap_r lber ssl crypto" (sasl did not compile 
> - could not find sasl.h, even though OS X has the library itself).
>
> - against built-in OpenLDAP and the built-in python 2.2: fails with 
> the error message that started this whole thread. the _ldap.so shared 
> module is not created because linking fails.
>
> it seems that the culprit might be the built-in python2.2. the python 
> build flags, i assume, govern the build flags used when compiling 
> these extension modules.
>
> jens

Re: compile python-ldap on macosx

[Michael E. <men...@ka...>]

> clean or not, it does not work out of the box ;)
Huh?? We're talking about Mac OS X desktop here right?   Why does 
having to adjust a configuration file before you run slapd considered 
not working out of the box?  How would you have them pre-configure 
it???  It's not any different than having to configure an email client 
to read email from your POP account.  In my mind I would say that it 
totally works out of the box.  All I had to do was add the following to 
/etc/openldap/slapd.conf (making changes to work within your needs ---  
I also commented out the netinfo stuff because I'm not using NetInfo)

database ldbm
suffix "o=mydomain.com"
rootdn "cn=Directory Manager,o= mydomain.com"
rootpw somepw
directory /var/db/openldap/openldap-data/
cachesize       1000000
dbcachesize     10000000
index uid,cn,sn,givenName pres,eq,sub
sizelimit       5000

-- I wouldn't expect Apple to guess for me what I wanted here :-)

Then you can either set LDAP to run at startup (which has been 
discussed here) or type /usr/libexec/slapd and you're up and running.   
  You of course need to add the entries (either with the command line 
ldapadd or via some GUI admin tool) you want to search on to it to make 
it do what you want but I assume that's true of any LDAP server.
BTW, the database you're talking about not existing with the default 
slapd.conf is because you probably  don't have anything in your netinfo 
setup.   Try launching slapd and then going into Netinfo and adding 
users and see if it gets created.


Mike


On Sunday, October 27, 2002, at 10:39  AM, Jens Vagelpohl wrote:

> clean or not, it does not work out of the box ;)  the slapd.conf 
> points to a database that does not exist, at least on my own system. i 
> assume you have to make some explicit gesture to build that database 
> file.
>
> even if this database existed and some unsuspecting person started 
> using it i wonder what kind of security hole you open by not 
> explicitly disabling the serving of netinfo data...
>
> on my own system i have now switched to using the built-in OpenLDAP by 
> adjusting the slapd.conf (and commenting out the pieces pertaining to 
> the netinfo bridge) and use it without problems through python-ldap 
> compiled against my self-built python 2.1.3.
>
> jens

Re: compile python-ldap on macosx

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

clean or not, it does not work out of the box ;)  the slapd.conf points 
to a database that does not exist, at least on my own system. i assume 
you have to make some explicit gesture to build that database file.

even if this database existed and some unsuspecting person started 
using it i wonder what kind of security hole you open by not explicitly 
disabling the serving of netinfo data...

on my own system i have now switched to using the built-in OpenLDAP by 
adjusting the slapd.conf (and commenting out the pieces pertaining to 
the netinfo bridge) and use it without problems through python-ldap 
compiled against my self-built python 2.1.3.

jens

On Saturday, Oct 26, 2002, at 14:20 US/Eastern, Joe Little wrote:

>
> its an openldap to Netinfo bridge, done by Luke Howard (padl.com). In 
> other words.. its as clean as you can get. Its compliant and works 
> fine. I'm already using it as such in one case. Anybody can modify the 
> schema to be what not and it won't break anything, since by default 
> the system uses Netinfo and not LDAP and some steps are required to 
> activate the LDAP bridge.
>
> Software update won't modify the slapd.conf to my knowledge. That is 
> generated one time with a mkslapdconf command from the netinfo sources 
> (during activation). Its similar to what a .deb or .rpm would do with 
> the default slapd.conf -- not change it unless its not there.
>
> On Saturday, October 26, 2002, at 07:48 AM, Jens Vagelpohl wrote:
>
>> looking at the configuration files under /etc/openldap i suppose this 
>> "built-in" ldap server is designed to serve NetInfo data through 
>> LDAP. not sure what that is supposed to be good for on a normal OS X 
>> > install.
>>
>> i'd be weary to try and use that server to serve out other stuff as 
>> well. i'm not sure Software Update would recognize changes and not 
>> just replace the files the next time there is an updated ldap bundle.
>>
>> jens
>>
>>
>> On Saturday, Oct 26, 2002, at 03:22 US/Eastern, Michael Engelhart 
>> wrote:
>>
>>> Hello Juergen,
>>>
>>> I just recently installed python-ldap on a stock Mac OS 10.2 
>>> powerbook using the stock python 2.2 distribution that is installed.
>>>
>>> first  - in setup.py do change the first 2 lines to:
>>>
>>> library_dirs = /usr/lib
>>> include_dirs = /usr/include
>>>
>>> I believe you'll get that same gcc error message but after you run 
>>> python setup.py build, do a:
>>> sudo python setup.py install
>>>
>>> and it should install the libraries fine.
>>>
>>> I am new  to OpenLDAP so I'm having lots of trouble modifying 
>>> entries and will be posting here soon but want to make sure my 
>>> OpenLDAP configuration is setup correctly before I do that.
>>>
>>> BTW, for those who were asking, OpenLDAP v 2.1.0 is what is 
>>> installed by default on Mac OS X v 10.2   There may have been some 
>>> minor changes in the latest System update but it's at least 2.1.x
>>>
>>> Cheers
>>> Mike
>>> On Friday, October 25, 2002, at 07:38  AM, J. Scholtes wrote:
>>>
>>>> Hi.
>>>> I'm new to the list. In the list-archive I didn't find much about 
>>>> macosx, so here is my post.
>>>>
>>>> I'm trying to set up ZOPE with the LDAPuserFolder on a 
>>>> macosx-system and therefor I need python-ldap. But I#m not able to 
>>>> compile it on MacOsX 10.2
>>>> Is anyone on the List who did it successfull ?
>>>>
>>>> thanks
>>>> Juergen Scholtes
>>>>
>>>>
>>>>
>>>>
>>>> -------------------------------------------------------
>>>> This sf.net email is sponsored by: Influence the future of Java(TM) 
>>>> technology. Join the Java Community Process(SM) (JCP(SM)) program 
>>>> now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en
>>>> _______________________________________________
>>>> Python-LDAP-dev mailing list
>>>> Pyt...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
>>>>
>>>
>>>
>>>
>>> -------------------------------------------------------
>>> This SF.net email is sponsored by: ApacheCon, November 18-21 in
>>> Las Vegas (supported by COMDEX), the only Apache event to be
>>> fully supported by the ASF. http://www.apachecon.com
>>> _______________________________________________
>>> Python-LDAP-dev mailing list
>>> Pyt...@li...
>>> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
>>
>>
>>
>> -------------------------------------------------------
>> This SF.net email is sponsored by: ApacheCon, November 18-21 in
>> Las Vegas (supported by COMDEX), the only Apache event to be
>> fully supported by the ASF. http://www.apachecon.com
>> _______________________________________________
>> Python-LDAP-dev mailing list
>> Pyt...@li...
>> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: ApacheCon, November 18-21 in
> Las Vegas (supported by COMDEX), the only Apache event to be
> fully supported by the ASF. http://www.apachecon.com
> _______________________________________________
> Python-LDAP-dev mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev

Re: compile python-ldap on macosx

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

as far as compiling python-ldap goes, here is the outcome of a couple=20
experiments i did yesterday. all were done with the current CVS HEAD:

- against self-compiled OpenLDAP 2.1.4 and self-compiled python 2.1.3:=20=

no problem.

- against built-in OpenLDAP and self-compiled python 2.1.3: no problem.=20=

i specified "/usr/lib" as library_dirs and "/usr/include" as=20
include_dirs. libs was "ldap_r lber ssl crypto" (sasl did not compile -=20=

could not find sasl.h, even though OS X has the library itself).

- against built-in OpenLDAP and the built-in python 2.2: fails with the=20=

error message that started this whole thread. the _ldap.so shared=20
module is not created because linking fails.

it seems that the culprit might be the built-in python2.2. the python=20
build flags, i assume, govern the build flags used when compiling these=20=

extension modules.

jens


On Sunday, Oct 27, 2002, at 08:12 US/Eastern, Michael Str=F6der wrote:

> Michael Engelhart wrote:
>> On Sunday, October 27, 2002, at 07:32  AM, Michael Str=F6der wrote:
>>> Sourceforge recently added Mac OS X to their compile farm:
>>> http://sourceforge.net/forum/forum.php?forum_id=3D113664
>>> Anyone interested in using that for testing python-ldap? We maybe=20
>>> could request the OpenDirectory standard package to be added to the=20=

>>> compile farm system.
> >
> > OpenLDAP is part of the default OS X install.  I guess the =
developers
> > would need access to the slapd.conf file to set the direcotry =
manager
> > name/password.
>
> Maybe my comment was misleading. I was only thinking about using Mac=20=

> OS X's LDAP client libs to compile binaries of python-ldap for Mac OS=20=

> X.
>
> Ciao, Michael.
>

Re: compile python-ldap on macosx

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

Michael Engelhart wrote:
> On Sunday, October 27, 2002, at 07:32  AM, Michael Str=F6der wrote:
>=20
>> Sourceforge recently added Mac OS X to their compile farm:
>> http://sourceforge.net/forum/forum.php?forum_id=3D113664
>> Anyone interested in using that for testing python-ldap? We maybe=20
>> could request the OpenDirectory standard package to be added to the=20
>> compile farm system.
 >
 > OpenLDAP is part of the default OS X install.  I guess the developers
 > would need access to the slapd.conf file to set the direcotry manager
 > name/password.

Maybe my comment was misleading. I was only thinking about using Mac OS X=
's=20
LDAP client libs to compile binaries of python-ldap for Mac OS X.

Ciao, Michael.

Re: compile python-ldap on macosx

[Michael E. <men...@ka...>]

OpenLDAP is part of the default OS X install.  I guess the developers=20
would need access to the slapd.conf file to set the direcotry manager=20
name/password.

Mike
On Sunday, October 27, 2002, at 07:32  AM, Michael Str=F6der wrote:

> HI!
>
> Sourceforge recently added Mac OS X to their compile farm:
>
> http://sourceforge.net/forum/forum.php?forum_id=3D113664
>
> Anyone interested in using that for testing python-ldap? We maybe=20
> could request the OpenDirectory standard package to be added to the=20
> compile farm system.
>
> Ciao, Michael

Re: compile python-ldap on macosx

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

HI!

Sourceforge recently added Mac OS X to their compile farm:

http://sourceforge.net/forum/forum.php?forum_id=113664

Anyone interested in using that for testing python-ldap? We maybe could 
request the OpenDirectory standard package to be added to the compile farm 
system.

Ciao, Michael

Re: compile python-ldap on macosx

[kapil t. <kv...@wm...>]

for those interested i found this presentation os osx and directory services

http://conferences.oreillynet.com/cs/macosx2002/view/e_sess/3298

cheers from a recently converted linux user,

-k

Re: compile python-ldap on macosx

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

its an openldap to Netinfo bridge, done by Luke Howard (padl.com). In 
other words.. its as clean as you can get. Its compliant and works 
fine. I'm already using it as such in one case. Anybody can modify the 
schema to be what not and it won't break anything, since by default the 
system uses Netinfo and not LDAP and some steps are required to 
activate the LDAP bridge.

Software update won't modify the slapd.conf to my knowledge. That is 
generated one time with a mkslapdconf command from the netinfo sources 
(during activation). Its similar to what a .deb or .rpm would do with 
the default slapd.conf -- not change it unless its not there.

On Saturday, October 26, 2002, at 07:48 AM, Jens Vagelpohl wrote:

> looking at the configuration files under /etc/openldap i suppose this 
> "built-in" ldap server is designed to serve NetInfo data through LDAP. 
> not sure what that is supposed to be good for on a normal OS X > install.
>
> i'd be weary to try and use that server to serve out other stuff as 
> well. i'm not sure Software Update would recognize changes and not 
> just replace the files the next time there is an updated ldap bundle.
>
> jens
>
>
> On Saturday, Oct 26, 2002, at 03:22 US/Eastern, Michael Engelhart 
> wrote:
>
>> Hello Juergen,
>>
>> I just recently installed python-ldap on a stock Mac OS 10.2 
>> powerbook using the stock python 2.2 distribution that is installed.
>>
>> first  - in setup.py do change the first 2 lines to:
>>
>> library_dirs = /usr/lib
>> include_dirs = /usr/include
>>
>> I believe you'll get that same gcc error message but after you run 
>> python setup.py build, do a:
>> sudo python setup.py install
>>
>> and it should install the libraries fine.
>>
>> I am new  to OpenLDAP so I'm having lots of trouble modifying entries 
>> and will be posting here soon but want to make sure my OpenLDAP 
>> configuration is setup correctly before I do that.
>>
>> BTW, for those who were asking, OpenLDAP v 2.1.0 is what is installed 
>> by default on Mac OS X v 10.2   There may have been some minor 
>> changes in the latest System update but it's at least 2.1.x
>>
>> Cheers
>> Mike
>> On Friday, October 25, 2002, at 07:38  AM, J. Scholtes wrote:
>>
>>> Hi.
>>> I'm new to the list. In the list-archive I didn't find much about 
>>> macosx, so here is my post.
>>>
>>> I'm trying to set up ZOPE with the LDAPuserFolder on a macosx-system 
>>> and therefor I need python-ldap. But I#m not able to compile it on 
>>> MacOsX 10.2
>>> Is anyone on the List who did it successfull ?
>>>
>>> thanks
>>> Juergen Scholtes
>>>
>>>
>>>
>>>
>>> -------------------------------------------------------
>>> This sf.net email is sponsored by: Influence the future of Java(TM) 
>>> technology. Join the Java Community Process(SM) (JCP(SM)) program 
>>> now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en
>>> _______________________________________________
>>> Python-LDAP-dev mailing list
>>> Pyt...@li...
>>> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
>>>
>>
>>
>>
>> -------------------------------------------------------
>> This SF.net email is sponsored by: ApacheCon, November 18-21 in
>> Las Vegas (supported by COMDEX), the only Apache event to be
>> fully supported by the ASF. http://www.apachecon.com
>> _______________________________________________
>> Python-LDAP-dev mailing list
>> Pyt...@li...
>> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: ApacheCon, November 18-21 in
> Las Vegas (supported by COMDEX), the only Apache event to be
> fully supported by the ASF. http://www.apachecon.com
> _______________________________________________
> Python-LDAP-dev mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev

Re: compile python-ldap on macosx

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

i personally had no idea that ldap comes standard. so i poked around 
and sure enough if you go to /etc/hostconfig and add a line that says...

LDAPSERVER=-YES-

then the built-in server starts up on system start. i then went in and 
changed /System/Library/StartupItems/LDAP/LDAP to point to my 
self-compiled slapd instead. works wonderfully.

i probably should make use of the built-in one instead. i just have to 
change the configuration and *hope* that it can deal with my already 
existing database files and my schemata...  but at any rate, at least 
for folks who just want to use python-ldap as a client without running 
a LDAP server the mere existence of the libraries and header files will 
simplify building the module a lot.

jens


On Saturday, Oct 26, 2002, at 12:12 US/Eastern, Michael Engelhart wrote:

> Well NetInfo is one of "many" things OpenLDAP can serve up.   I doubt 
> that Software Update would change the slapd.conf file since it 
> basically just points to the apple.schema file.   I'm guessing it is 
> safe and to be sure I just keep a copy of the configuration file.   
> BUt that's just me.
>
>
> On Saturday, October 26, 2002, at 10:48  AM, Jens Vagelpohl wrote:
>
>> looking at the configuration files under /etc/openldap i suppose this 
>> "built-in" ldap server is designed to serve NetInfo data through 
>> LDAP. not sure what that is supposed to be good for on a normal OS X 
>> > install.
>>
>> i'd be weary to try and use that server to serve out other stuff as 
>> well. i'm not sure Software Update would recognize changes and not 
>> just replace the files the next time there is an updated ldap bundle.
>>
>> jens
>

Re: compile python-ldap on macosx

[Michael E. <men...@ka...>]

Well NetInfo is one of "many" things OpenLDAP can serve up.   I doubt 
that Software Update would change the slapd.conf file since it 
basically just points to the apple.schema file.   I'm guessing it is 
safe and to be sure I just keep a copy of the configuration file.   BUt 
that's just me.


On Saturday, October 26, 2002, at 10:48  AM, Jens Vagelpohl wrote:

> looking at the configuration files under /etc/openldap i suppose this 
> "built-in" ldap server is designed to serve NetInfo data through LDAP. 
> not sure what that is supposed to be good for on a normal OS X > install.
>
> i'd be weary to try and use that server to serve out other stuff as 
> well. i'm not sure Software Update would recognize changes and not 
> just replace the files the next time there is an updated ldap bundle.
>
> jens

Re: compile python-ldap on macosx

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

looking at the configuration files under /etc/openldap i suppose this 
"built-in" ldap server is designed to serve NetInfo data through LDAP. 
not sure what that is supposed to be good for on a normal OS X install.

i'd be weary to try and use that server to serve out other stuff as 
well. i'm not sure Software Update would recognize changes and not just 
replace the files the next time there is an updated ldap bundle.

jens


On Saturday, Oct 26, 2002, at 03:22 US/Eastern, Michael Engelhart wrote:

> Hello Juergen,
>
> I just recently installed python-ldap on a stock Mac OS 10.2 powerbook 
> using the stock python 2.2 distribution that is installed.
>
> first  - in setup.py do change the first 2 lines to:
>
> library_dirs = /usr/lib
> include_dirs = /usr/include
>
> I believe you'll get that same gcc error message but after you run 
> python setup.py build, do a:
> sudo python setup.py install
>
> and it should install the libraries fine.
>
> I am new  to OpenLDAP so I'm having lots of trouble modifying entries 
> and will be posting here soon but want to make sure my OpenLDAP 
> configuration is setup correctly before I do that.
>
> BTW, for those who were asking, OpenLDAP v 2.1.0 is what is installed 
> by default on Mac OS X v 10.2   There may have been some minor changes 
> in the latest System update but it's at least 2.1.x
>
> Cheers
> Mike
> On Friday, October 25, 2002, at 07:38  AM, J. Scholtes wrote:
>
>> Hi.
>> I'm new to the list. In the list-archive I didn't find much about 
>> macosx, so here is my post.
>>
>> I'm trying to set up ZOPE with the LDAPuserFolder on a macosx-system 
>> and therefor I need python-ldap. But I#m not able to compile it on 
>> MacOsX 10.2
>> Is anyone on the List who did it successfull ?
>>
>> thanks
>> Juergen Scholtes
>>
>>
>>
>>
>> -------------------------------------------------------
>> This sf.net email is sponsored by: Influence the future of Java(TM) 
>> technology. Join the Java Community Process(SM) (JCP(SM)) program 
>> now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en
>> _______________________________________________
>> Python-LDAP-dev mailing list
>> Pyt...@li...
>> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
>>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: ApacheCon, November 18-21 in
> Las Vegas (supported by COMDEX), the only Apache event to be
> fully supported by the ASF. http://www.apachecon.com
> _______________________________________________
> Python-LDAP-dev mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev

Re: compile python-ldap on macosx

[Michael E. <men...@ka...>]

Hello Juergen,

I just recently installed python-ldap on a stock Mac OS 10.2 powerbook 
using the stock python 2.2 distribution that is installed.

first  - in setup.py do change the first 2 lines to:

library_dirs = /usr/lib
include_dirs = /usr/include

I believe you'll get that same gcc error message but after you run 
python setup.py build, do a:
sudo python setup.py install

and it should install the libraries fine.

I am new  to OpenLDAP so I'm having lots of trouble modifying entries 
and will be posting here soon but want to make sure my OpenLDAP 
configuration is setup correctly before I do that.

BTW, for those who were asking, OpenLDAP v 2.1.0 is what is installed 
by default on Mac OS X v 10.2   There may have been some minor changes 
in the latest System update but it's at least 2.1.x

Cheers
Mike
On Friday, October 25, 2002, at 07:38  AM, J. Scholtes wrote:

> Hi.
> I'm new to the list. In the list-archive I didn't find much about 
> macosx, so here is my post.
>
> I'm trying to set up ZOPE with the LDAPuserFolder on a macosx-system 
> and therefor I need python-ldap. But I#m not able to compile it on 
> MacOsX 10.2
> Is anyone on the List who did it successfull ?
>
> thanks
> Juergen Scholtes
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: Influence the future of Java(TM) 
> technology. Join the Java Community Process(SM) (JCP(SM)) program now. 
> http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en
> _______________________________________________
> Python-LDAP-dev mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
>

Re: compile python-ldap on macosx

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

My understanding is that they include the OpenLDAP server 2.1.x on=20
their server product. That being said I assume the client side build=20
and libraries is based on the same version.

Let me take a stab at it..

Ok. the framework lists it as an OpenLDAP 2.0.21 based library.=20
However, the LDAP binary is built with liblber and libldap version 2.1.x

Let's look at the /usr/lib directory for the libraries themselves.=20
Strings results in the same 2.1.x (no indication of the specific=20
version. MacOSX uses .dylib extensions without major/minor numbers)

Pulling python-ldap from CVS and building it...

I get the same error with the "python setup.py build" approach, but it=20=

appears to correctly generate the files. I get further errors when=20
simply using "make" -- a lot about the inability to generate i386=20
libraries. However, it completes and a subsequent make shows that=20
everything is up to date and nothing is left to build. Thus, the nature=20=

of the beast is that the included setup.cfg doesn't know that MacOSX=20
can build for multiple architectures and its platform (python setup.py=20=

--platform) is "UNKNOWN". Is this normally the case for packages using=20=

setup.py/distutils?

I hope this helps out the discussion a bit.

On Friday, October 25, 2002, at 12:04 PM, Michael Str=F6der wrote:

> Joe Little wrote:
>> Though you may build from source, it is probably wiser for=20
>> distribution to depend on the now included LDAP release with Darwin=20=

>> and MacOSX Jaguar (which ties into OpenDirectory).
>
> Is it possible to build python-ldap against this LDAP release? Any=20
> information about whether that's OpenLDAP 2 or not?
>
> I have to admit that I do not have any clue about the buzz-word=20
> 'OpenDirectory' and all the Mac OSX stuff.
>
> Ciao, Michael.
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: Influence the future of Java(TM)=20
> technology. Join the Java Community Process(SM) (JCP(SM)) program now.=20=

> http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en
> _______________________________________________
> Python-LDAP-dev mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev

Re: compile python-ldap on macosx

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

Joe Little wrote:
> Though you may build from source, it is probably wiser 
> for distribution to depend on the now included LDAP release with Darwin 
> and MacOSX Jaguar (which ties into OpenDirectory).

Is it possible to build python-ldap against this LDAP release? Any 
information about whether that's OpenLDAP 2 or not?

I have to admit that I do not have any clue about the buzz-word 
'OpenDirectory' and all the Mac OSX stuff.

Ciao, Michael.

Re: compile python-ldap on macosx

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

MacOSX has two supported architectures, as does Darwin. Apple only 
sells one and mothballed the other architecture. With Darwin, you still 
have both. When compiling, you are build Mach-O binaries that can be 
"FAT" -- both intel and ppc. Many defaults for Darwin build for both 
architectures. Though you may build from source, it is probably wiser 
for distribution to depend on the now included LDAP release with Darwin 
and MacOSX Jaguar (which ties into OpenDirectory). It will lower the 
entropy of support and likely not cause the "which libldap library am I 
linking to today" problems :)

On Friday, October 25, 2002, at 08:58 AM, Jens Vagelpohl wrote:

> well, something about your setup is strange. just to compare, here is 
> the output from my own machine::
>
> **************************
> gcc -flat_namespace -bundle -undefined suppress 
> build/temp.darwin-6.1-Power Macintosh-2.1/LDAPObject.o 
> build/temp.darwin-6.1-Power Macintosh-2.1/common.o 
> build/temp.darwin-6.1-Power Macintosh-2.1/constants.o 
> build/temp.darwin-6.1-Power Macintosh-2.1/errors.o 
> build/temp.darwin-6.1-Power Macintosh-2.1/functions.o 
> build/temp.darwin-6.1-Power Macintosh-2.1/schema.o 
> build/temp.darwin-6.1-Power Macintosh-2.1/ldapmodule.o 
> build/temp.darwin-6.1-Power Macintosh-2.1/linkedlist.o 
> build/temp.darwin-6.1-Power Macintosh-2.1/message.o 
> build/temp.darwin-6.1-Power Macintosh-2.1/version.o 
> build/temp.darwin-6.1-Power Macintosh-2.1/options.o -L/usr/local/lib 
> -R/usr/local/lib -lldap_r -llber -lssl -lcrypto -o 
> build/lib.darwin-6.1-Power Macintosh-2.1/_ldap.so
> gcc: unrecognized option `-R/usr/local/lib'
> [dhcp192:local/src/python-ldap-HEAD] jens%
> ***************************
>
> as you can see, no "arch" arguments whatsoever. by the way, my python 
> is "hand-made" as well. it's a self-compiled python 2.1.3.
>
> i don't know much about compilers, but it seems strange that there are 
> more than a single arch argument, anyway. or is it possible to build 
> for two completely disparate architectures in one compile run? sounds 
> unlikely to me.
>
> jens
>
> On Friday, Oct 25, 2002, at 09:00 US/Eastern, J. Scholtes wrote:
>
>>
>> Am Freitag, 25.10.02, um 14:39 Uhr (Europe/Budapest) schrieb Jens 
>> Vagelpohl:
>>
>>> now that i am looking at it, why does it say something about 
>>> building for the i386 architecture in the build output? something 
>>> about your build is horribly wrong.
>>>
>>> jens
>>>
>>>
>>> On Friday, Oct 25, 2002, at 08:21 US/Eastern, J. Scholtes wrote:
>>>> gcc -arch i386 -arch ppc -bundle -flat_namespace -undefined 
>>>> suppress build/temp.darwin-6.1-Power Macintosh-2.2/
>>
>> mmh.
>> but the second switch (-arch ppc) is correct
>>
>> Juergen
>>
>>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: Influence the future of Java(TM) 
> technology. Join the Java Community Process(SM) (JCP(SM)) program now. 
> http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en
> _______________________________________________
> Python-LDAP-dev mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev