You can subscribe to this list here.
2000 |
Jan
|
Feb
(34) |
Mar
(9) |
Apr
|
May
(2) |
Jun
(14) |
Jul
(67) |
Aug
(34) |
Sep
(5) |
Oct
(20) |
Nov
(22) |
Dec
(31) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(15) |
Feb
(16) |
Mar
(20) |
Apr
(13) |
May
(72) |
Jun
(42) |
Jul
(41) |
Aug
(11) |
Sep
(19) |
Oct
(67) |
Nov
(59) |
Dec
(57) |
2002 |
Jan
(74) |
Feb
(69) |
Mar
(34) |
Apr
(55) |
May
(47) |
Jun
(74) |
Jul
(116) |
Aug
(68) |
Sep
(25) |
Oct
(42) |
Nov
(28) |
Dec
(52) |
2003 |
Jan
(19) |
Feb
(18) |
Mar
(35) |
Apr
(49) |
May
(73) |
Jun
(39) |
Jul
(26) |
Aug
(59) |
Sep
(33) |
Oct
(56) |
Nov
(69) |
Dec
(137) |
2004 |
Jan
(276) |
Feb
(15) |
Mar
(18) |
Apr
(27) |
May
(25) |
Jun
(7) |
Jul
(13) |
Aug
(2) |
Sep
(2) |
Oct
(10) |
Nov
(27) |
Dec
(28) |
2005 |
Jan
(22) |
Feb
(25) |
Mar
(41) |
Apr
(17) |
May
(36) |
Jun
(13) |
Jul
(22) |
Aug
(12) |
Sep
(23) |
Oct
(6) |
Nov
(4) |
Dec
|
2006 |
Jan
(11) |
Feb
(3) |
Mar
(5) |
Apr
(22) |
May
(1) |
Jun
(10) |
Jul
(19) |
Aug
(7) |
Sep
(25) |
Oct
(23) |
Nov
(5) |
Dec
(27) |
2007 |
Jan
(25) |
Feb
(17) |
Mar
(44) |
Apr
(8) |
May
(33) |
Jun
(31) |
Jul
(42) |
Aug
(16) |
Sep
(12) |
Oct
(16) |
Nov
(23) |
Dec
(73) |
2008 |
Jan
(26) |
Feb
(6) |
Mar
(46) |
Apr
(17) |
May
(1) |
Jun
(44) |
Jul
(9) |
Aug
(34) |
Sep
(20) |
Oct
(2) |
Nov
(4) |
Dec
(16) |
2009 |
Jan
(14) |
Feb
(3) |
Mar
(45) |
Apr
(52) |
May
(34) |
Jun
(32) |
Jul
(24) |
Aug
(52) |
Sep
(22) |
Oct
(23) |
Nov
(19) |
Dec
(10) |
2010 |
Jan
(10) |
Feb
(13) |
Mar
(22) |
Apr
(9) |
May
(1) |
Jun
(1) |
Jul
(8) |
Aug
(9) |
Sep
(10) |
Oct
(1) |
Nov
(2) |
Dec
(3) |
2011 |
Jan
|
Feb
(18) |
Mar
(39) |
Apr
(5) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Ludovico M. <lu...@as...> - 2003-03-23 19:14:21
|
As suggested by Michael Ströder, I am expanding a bit on my RFE for adding ldap_count_entries support. I am working for a large Italian bank (don't look at my email, I'm posting from my personal address from home), and we have all our organizational units (a few thousands) and employees (around 60k) on a few OpenLDAP servers. We have the need to extract data from OpenLDAP and manipulate it to create sets of xml files representing a hierarchical view of our organization. We are currently doing this with a set of C programs developed in house, but due to the number of rules we have to apply and the rate at which they change I'm trying to switch the processing from C to Python (the fact that I love Python and the other people working on this project do not is important too, I'm trying to convince them to learn it =)). I'm stuck at trying to generate employee count for each ou, and here's where I got to asking to add support for ldap_count_entries. Retrieving employees for every ou takes too long, I only need a count. Our current C programs use ldap_count_entries. My current options are staying with C, or using PHP which imho is a very poor choice compared to Python. Unfortunately I don't know C/C++ enough to help, and as I said the other developers don't consider Python a choice and won't help (yes, I tried asking.....). Thanks for any help Ludovico Magnocavallo |
From: Jens V. <je...@zo...> - 2003-03-23 17:37:21
|
i think the last time i checked CommuniGate did not have a complete=20 LDAP server implementation. this might have changed, but when we tried=20= to use the communigate LDAP server internally for LDAP purposes we=20 quickly came against limitations and decided to use OpenLDAP instead. jens On Sunday, Mar 23, 2003, at 08:50 US/Eastern, Michael Str=F6der wrote: > Stuart Bishop wrote: > > > > I'm getting stuck with SASL authentication - I believe my code is > > correct so > > I'd like to get an opinion on if the bug lies with my code,=20 > python-ldap > > pre6 > > or CommuniGate Pro (the LDAP server). I can bind using = bind_simple_s. > > Are you sure that CommuniGate Pro is an LDAPv3 server and supports=20 > SASL bind? Can you please check the rootDSE for attributes=20 > supportedSASLMechanisms. > > > login_dn =3D 'uid=3Dzen,cn=3Dcommongroundpublishing.com,o=3DCommon= =20 > Ground' > > password =3D 'secret' > > > > l =3D ldap.open('localhost') > > auth =3D ldap.sasl.digest_md5(login_dn,password) > > Note that a SASL user name is normally something like uid@realm. > > Ciao, Michael. > |
From: <mi...@st...> - 2003-03-23 13:50:20
|
Stuart Bishop wrote: > > I'm getting stuck with SASL authentication - I believe my code is > correct so > I'd like to get an opinion on if the bug lies with my code, python-ldap > pre6 > or CommuniGate Pro (the LDAP server). I can bind using bind_simple_s. Are you sure that CommuniGate Pro is an LDAPv3 server and supports SASL bind? Can you please check the rootDSE for attributes supportedSASLMechanisms. > login_dn = 'uid=zen,cn=commongroundpublishing.com,o=Common Ground' > password = 'secret' > > l = ldap.open('localhost') > auth = ldap.sasl.digest_md5(login_dn,password) Note that a SASL user name is normally something like uid@realm. Ciao, Michael. |
From: Stuart B. <stu...@co...> - 2003-03-23 10:44:46
|
Hi. I'm getting stuck with SASL authentication - I believe my code is correct so I'd like to get an opinion on if the bug lies with my code, python-ldap pre6 or CommuniGate Pro (the LDAP server). I can bind using bind_simple_s. My code: import ldap import ldap.sasl login_dn = 'uid=zen,cn=commongroundpublishing.com,o=Common Ground' password = 'secret' l = ldap.open('localhost') auth = ldap.sasl.digest_md5(login_dn,password) l.sasl_bind_s('',auth) l.unbind() The result: SASL/DIGEST-MD5 authentication started Traceback (most recent call last): File "t.py", line 9, in ? l.sasl_bind_s('',auth) File "/usr/local/lib/python2.1/site-packages/ldap/ldapobject.py", line 162, in sasl_bind_s return self._ldap_call(self._l.sasl_bind_s,who,auth) File "/usr/local/lib/python2.1/site-packages/ldap/ldapobject.py", line 94, in _ldap_call result = apply(func,args,kwargs) ldap.LOCAL_ERROR: {'desc': 'Local error', 'info': ''} Server log: 20:55:14.83 5 LDAP connection request from [127.0.0.1], socket=27 20:55:14.83 4 LDAP-00540([127.0.0.1]) got connection on [127.0.0.1], port 389 20:55:14.83 5 LDAP-00540([127.0.0.1]) input request(27): 02 01 01 60 16 02 01 03 04 03 7A 65 6E A3 0C 04 0A 44 49 47 45 53 54 2D 4D 44 35 20:55:14.83 5 LDAP-00540([127.0.0.1]) out: 30 5D 02 01 01 61 58 0A 01 0E 04 00 04 00 04 4F 6E 6F 6E 63 65 3D 22 35 34 30 61 31 30 34 38 34 31 33 33 31 34 61 63 6F 6D 6D 6F 6E 67 72 6F 75 6E 64 70 75 20:55:14.83 5 LDAP-00540([127.0.0.1]) input request(5): 02 01 02 42 00 20:55:14.83 1 LDAP-00540([127.0.0.1]) SASL response is not a SASL BindRequest 20:55:14.83 1 LDAP-00540([127.0.0.1]) BIND failed: SASL protocol has been interrupted 20:55:14.83 5 LDAP-00540([127.0.0.1]) out: 30 2E 02 01 01 61 29 0A 01 31 04 00 04 22 53 41 53 4C 20 70 72 6F 74 6F 63 6F 6C 20 68 61 73 20 62 65 65 6E 20 69 6E 74 65 72 72 75 70 74 65 64 20:55:14.83 3 LDAP-00540([127.0.0.1]) read failed. Error Code=connection closed by peer 20:55:14.83 4 LDAP-00540([127.0.0.1]) closing connection 20:55:14.83 4 LDAP-00540([127.0.0.1]) releasing stream -- Stuart Bishop <stu...@co...> |
From: <mi...@st...> - 2003-03-22 13:38:37
|
Jerry, good catches. Your fixes are committed into CVS. Thanks for taking the time to report the bugs. And glad to see that someone is using ldap.schema... I couldn't get hold of a sub schema sub entry with nameForms, matchingRuleUse and so on. Therefore I'd appreciate to receive test data as LDIF. Ideally if you know a public LDAP server with those attributes set please let me know. Ciao, Michael. Jerry Lee wrote: > > I've been using your schema code and I came across the following in > models.py > > line 337: > > schema_attribute = 'matchingRuleUses' > > should read > > schema_attribute = 'matchingRuleUse' > > and > > line 352: > > assert type(self.obsolete)==type(0) and (type(self.obsolete)==0 or > type(self.obsolete)==1) > > should read > > assert type(self.obsolete)==type(0) and (self.obsolete==0 or > self.obsolete==1) > > > I'm not too sure on the second one - I don't really understand it. > However I was getting errors before the change and so I just copied the > line from the _set_attrs section of MatchinRule and I don't get errors > anymore. > > Thanks for your efforts! > > Jerry. |
From: Jens V. <je...@zo...> - 2003-03-19 04:59:06
|
you need to install the python-ldap package. this is clearly mentioned=20= in the documentation. http://python-ldap.sourceforge.net jens On Tuesday, Mar 18, 2003, at 23:24 US/Eastern, Paul Naveen Raj Jeyaraj=20= wrote: > Hi,=A0 > =A0 > I=A0=A0want to use LDAP user folder in my zope(2.5.1) installation. I = have=20 > dowloaded the same and put that in the zope's products folder, but I=20= > am not seeing it in the types' drop down when I access zope's=20 > management interface. It is said in the installation document that=20 > ldapmodule.so is required to use LDAP user folder, but I dont find=20 > any. Where can I get the same and where should I put that in order to=20= > get it working? Please help. Its a very urgent requirement. Thank > = you.=A0 > =A0 > Regards,=A0 > =A0Paul. |
From: <mi...@st...> - 2003-03-12 22:00:39
|
Christian Nygaard wrote: > > Hi how do I add account posixAccount info with the add_s operation? Just like any other entry (see Demo/simple.py) and the right data for posixAccount. Ciao, Michael. |
From: <mi...@st...> - 2003-03-12 13:14:39
|
Paul Robinson wrote: > > I'm looking for information with regard to the license under which the > Python ldap module can be used and distributed in a commercial > environment. In all the downloads I can find and through all the web > pages available on SourceForge there is no explicit licensing info. > > I only have the "License: Public Domain" statement from the project > homepage on sourceforge to go on. Is there any more info I could feed to > a hungry lawyer? ;-) I try to give an answer. We had this discussion on the python-ldap-dev mailing list (see list archive). While it seemed that there was general consensus that we might prefer the unprecise term "Python Style License" there was no real action taken. Mainly the intention behind saying "Python Style License" is that you can do everything with python-ldap what you're allowed to do with e.g. Python 2.2.x. Not sure if that satisfies your lawyer though. Ciao, Michael. |
From: Christian N. <chr...@ma...> - 2003-03-10 12:41:21
|
Hi how do I add account posixAccount info with the add_s operation? //Christian |
From: Rakesh N. <rn...@ze...> - 2003-03-10 07:18:25
|
hi, i think u need to build python-ldap2.0.0pre6 , perfectly, other wise definitly this problem will persisit. rakesh. www.zeomega.com Venkateswara Rayapaneni wrote: >Hi >I am on Solaris9, Sunone Directory server 5.1sp2. >I have zope2.6.1 and python2.2.2. When I try to build >python-ldap2.0.0pre6 I have all kinds of problems. >Does it work on the above config ? The first error for >me is: >Traceback (most recent call last): > File "setup.cfg", line 2, in ? > [_ldap] >NameError: name '_ldap' is not defined > >Any help is appreciated >thanks >rv > >__________________________________________________ >Do you Yahoo!? >Yahoo! Tax Center - forms, calculators, tips, more >http://taxes.yahoo.com/ > > >------------------------------------------------------- >This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger >for complex code. Debugging C/C++ programs can leave you feeling lost and >disoriented. TotalView can help you find your way. Available on major UNIX >and Linux platforms. Try it free. www.etnus.com >_______________________________________________ >Python-LDAP-dev mailing list >Pyt...@li... >https://lists.sourceforge.net/lists/listinfo/python-ldap-dev > > |
From: <mi...@st...> - 2003-03-09 15:22:37
|
Venkateswara Rayapaneni wrote: > I am on Solaris9, Sunone Directory server 5.1sp2. > I have zope2.6.1 and python2.2.2. As Joe already pointed out you need the OpenLDAP client libs. > The first error for > me is: > Traceback (most recent call last): > File "setup.cfg", line 2, in ? > [_ldap] > NameError: name '_ldap' is not defined To me it seems you invoked setup.cfg instead setup.py. setup.cfg is the config file for the build/installation script setup.py. After installing OpenLDAP libs and tweaking setup.cfg use $ python setup.py build ^^^ Ciao, Michael. |
From: Joe L. <jl...@op...> - 2003-03-09 06:39:48
|
The directory server itself doesn't matter, but Python LDAP requires OpenLDAP libraries to build against, and is not presently designed to built against the Solaris 9 provided versions of those libraries. You'll need to build OpenLDAP, use those libraries, and make sure the LD_LIBRARY_PATH points to said libraries when using python-ldap to make it work. On Saturday, March 8, 2003, at 10:07 PM, Venkateswara Rayapaneni wrote: > Hi > I am on Solaris9, Sunone Directory server 5.1sp2. > I have zope2.6.1 and python2.2.2. When I try to build > python-ldap2.0.0pre6 I have all kinds of problems. > Does it work on the above config ? The first error for > me is: > Traceback (most recent call last): > File "setup.cfg", line 2, in ? > [_ldap] > NameError: name '_ldap' is not defined > > Any help is appreciated > thanks > rv > > __________________________________________________ > Do you Yahoo!? > Yahoo! Tax Center - forms, calculators, tips, more > http://taxes.yahoo.com/ > > > ------------------------------------------------------- > This SF.net email is sponsored by: Etnus, makers of TotalView, The > debugger > for complex code. Debugging C/C++ programs can leave you feeling lost > and > disoriented. TotalView can help you find your way. Available on major > UNIX > and Linux platforms. Try it free. www.etnus.com > _______________________________________________ > Python-LDAP-dev mailing list > Pyt...@li... > https://lists.sourceforge.net/lists/listinfo/python-ldap-dev |
From: Venkateswara R. <ray...@ya...> - 2003-03-09 06:07:13
|
Hi I am on Solaris9, Sunone Directory server 5.1sp2. I have zope2.6.1 and python2.2.2. When I try to build python-ldap2.0.0pre6 I have all kinds of problems. Does it work on the above config ? The first error for me is: Traceback (most recent call last): File "setup.cfg", line 2, in ? [_ldap] NameError: name '_ldap' is not defined Any help is appreciated thanks rv __________________________________________________ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/ |
From: Jerry L. <te...@ho...> - 2003-03-04 20:16:29
|
Hi Michael, >From: Michael Ströder <mi...@st...> >To: Jerry Lee <te...@ho...> >CC: pyt...@li... >Subject: Re: Blocking bind.... >Date: Tue, 04 Mar 2003 19:30:08 +0100 > >Jerry Lee wrote: >>Michael Ströder wrote: >>>Jerry Lee wrote: >>>> >>>>I recently posted to the list about a problem I am having with bind >>>>blocking for a long time before it times out if the server isn't there. >>> >>>You can elaborate on "the server isn't there"? >> >>The machine doesn't exist - an ip address that I can't ping. > >I think it depends whether and which ICMP response your LDAP client >receives in this case. > >>How do I set the TIMEOUT values with set_option. >>Could you give me an example of how to set OPT_TIMEOUT and >>OPT_NETWORK_TIMEOUT to 10 secs?? > > >>> l.set_option(ldap.OPT_TIMELIMIT,60.0) > >>> l.get_option(ldap.OPT_TIMELIMIT) >60 > No joy. The option got set OK but it still doesn't timeout after the TIMELIMIT I specify. >>Is the synchronous/asynchronous nature of the call controlled in the >>python-ldap module or is it a function of the OpenLDAP libs?? > >It's controlled in the OpenLDAP libs. Updating OpenLDAP could be a good >idea. > >My attempt to implement a result() method which controls the timeout was a >CPU hog. > >Ciao, Michael. I'm going to update my OpenLDAP later this week. I'll keep you posted on the results. Thanks for all your help, Jerry. _________________________________________________________________ Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=features/junkmail |
From: <mi...@st...> - 2003-03-04 18:30:31
|
Jerry Lee wrote: > Michael Str=F6der wrote: >> Jerry Lee wrote: >>> >>> I recently posted to the list about a problem I am having with bind=20 >>> blocking for a long time before it times out if the server isn't ther= e. >> >> You can elaborate on "the server isn't there"? >=20 > The machine doesn't exist - an ip address that I can't ping. I think it depends whether and which ICMP response your LDAP client recei= ves=20 in this case. > How do I set the TIMEOUT values with set_option. > Could you give me an example of how to set OPT_TIMEOUT and=20 > OPT_NETWORK_TIMEOUT to 10 secs?? >>> l.set_option(ldap.OPT_TIMELIMIT,60.0) >>> l.get_option(ldap.OPT_TIMELIMIT) 60 > Is the synchronous/asynchronous nature of the call controlled in the=20 > python-ldap module or is it a function of the OpenLDAP libs?? It's controlled in the OpenLDAP libs. Updating OpenLDAP could be a good i= dea. My attempt to implement a result() method which controls the timeout was = a=20 CPU hog. Ciao, Michael. |
From: Jerry L. <te...@ho...> - 2003-03-04 18:09:43
|
Hi Michael, Thanks for the response. >From: Michael Ströder <mi...@st...> >To: Jerry Lee <te...@ho...> >CC: pyt...@li... >Subject: Re: Blocking bind.... >Date: Tue, 04 Mar 2003 17:31:23 +0100 > >Jerry Lee wrote: >> >>I recently posted to the list about a problem I am having with bind >>blocking for a long time before it times out if the server isn't there. > >You can elaborate on "the server isn't there"? > The machine doesn't exist - an ip address that I can't ping. I'm writing a QT-based LDAP browser and I want to make it user friendly. Give the user an option of cancelling a request if they typed the wrong IP address (for example) > >>Mario Cicognini (thx Mario!!) was kind enough to suggest the following: >> >> l = ldap.open(LDAPServer) >> id = l.simple_bind(LDAPbindUsername, LDAPbindPassword) >> status,res = l.result(id, 1, 60) >> if status != 'RES_BIND': >> return -1 >> >>which I tried with no success. > >First note that the connection timeout part is done within OpenLDAP libs. >It might be worth testing with newer OpenLDAP lib version 2.1.x. There's >nothing more you can do at Python level. > How do I set the TIMEOUT values with set_option. Could you give me an example of how to set OPT_TIMEOUT and OPT_NETWORK_TIMEOUT to 10 secs?? I had thought from reading the python-ldap docs that simple_bind was an asynchronous operation - that control would be returned to my program immediately after issuing the request. However, on my machine, it blocks - and then times out after around 90secs. Kind of annoying. Is the synchronous/asynchronous nature of the call controlled in the python-ldap module or is it a function of the OpenLDAP libs?? >>My app blocks at the >>id = l.simple_bind(LDAPbindUsername, LDAPbindPassword) >>line and doesn't return until around 90secs later. > >Note that opening the connection is deferred until attempting first the >LDAP operation. The ldap_initialize() function of OpenLDAP libs just >returns a LDAP connection struct without actually connecting to the server. >I guess your simple bind is the first LDAP operation. > >Ciao, Michael. Yes, this seems to be OK. I get program control back immediately after the ldap_open (ldap_initialie worked the same way). Thanks for the response and many thanks for the work you've done on python-ldap. You've helped make developing the app a much simpler task and even kind of fun!! Yours, Jerry. _________________________________________________________________ Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=features/junkmail |
From: <mi...@st...> - 2003-03-04 16:31:42
|
Jerry Lee wrote: > > I recently posted to the list about a problem I am having with bind > blocking for a long time before it times out if the server isn't there. You can elaborate on "the server isn't there"? > Mario Cicognini (thx Mario!!) was kind enough to suggest the following: > > l = ldap.open(LDAPServer) > id = l.simple_bind(LDAPbindUsername, LDAPbindPassword) > status,res = l.result(id, 1, 60) > if status != 'RES_BIND': > return -1 > > which I tried with no success. First note that the connection timeout part is done within OpenLDAP libs. It might be worth testing with newer OpenLDAP lib version 2.1.x. There's nothing more you can do at Python level. > My app blocks at the > id = l.simple_bind(LDAPbindUsername, LDAPbindPassword) > line and doesn't return until around 90secs later. Note that opening the connection is deferred until attempting first the LDAP operation. The ldap_initialize() function of OpenLDAP libs just returns a LDAP connection struct without actually connecting to the server. I guess your simple bind is the first LDAP operation. Ciao, Michael. |
From: Jerry L. <te...@ho...> - 2003-03-03 22:53:38
|
Hello again, I recently posted to the list about a problem I am having with bind blocking for a long time before it times out if the server isn't there. Mario Cicognini (thx Mario!!) was kind enough to suggest the following: l = ldap.open(LDAPServer) id = l.simple_bind(LDAPbindUsername, LDAPbindPassword) status,res = l.result(id, 1, 60) if status != 'RES_BIND': return -1 which I tried with no success. My app blocks at the id = l.simple_bind(LDAPbindUsername, LDAPbindPassword) line and doesn't return until around 90secs later. I have to kill it otherwise. Is my supposedly async bind a sync bind?? (I tried bind_s with exactly the same results) If so, how can I change the timeout so it doesn't wait 90secs? Where is the async bind hiding or does it exist?? Am I missing something?? I'm running Linux Mandrake 9.0, openldap 2.0.25 and lib2-devel (Mandrake separate the libs from the openldap server and clients). I downloaded python-ldap 2.0.0pre06 and compiled it and things work OK - except for this ;-) Thanks, Jerry. _________________________________________________________________ Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail |
From: Mauro C. <mci...@si...> - 2003-02-28 12:35:44
|
Jerry Lee wrote: > Hello, > > I'm adapting a QT LDAP browser using PyQT and Python-LDAP that will be > freely available when it's useful - still a ways to got yet ;-) > > I have a question about bind. > If I try to bind to a machine that isn't there, the app hangs for > about 90 secs. > > It seems to be stuck at ldap.simple_bind. > > Is there a way to make it timeout after a certain amount of time? > > I've looked at set_option(OPT_NETWORK_TIMEOUT) and OPT_TIMEOUT but > (assuming that bind actually looks at them) I can't figure out how to > put meaningful values in there. Every time I > set_option(OPT_NETWORK_TIMEOUT,5.0) > meaning a timeout of 5 seconds and then check the value with > get_option it reads > 1.36904e+08 !!!! Have you tried using an explicit timeout argument? I usually call ldap.simple_bind this way: l = ldap.open(LDAPServer) id = l.simple_bind(LDAPbindUsername, LDAPbindPassword) status,res = l.result(id, 1, 60) if status != 'RES_BIND': return -1 The third argument to ldap.result is indeed the timeout. It usually appears to work :-) Mauro Cicognini |
From: Jerry L. <te...@ho...> - 2003-02-28 01:32:35
|
Hello, I'm adapting a QT LDAP browser using PyQT and Python-LDAP that will be freely available when it's useful - still a ways to got yet ;-) I have a question about bind. If I try to bind to a machine that isn't there, the app hangs for about 90 secs. It seems to be stuck at ldap.simple_bind. Is there a way to make it timeout after a certain amount of time? I've looked at set_option(OPT_NETWORK_TIMEOUT) and OPT_TIMEOUT but (assuming that bind actually looks at them) I can't figure out how to put meaningful values in there. Every time I set_option(OPT_NETWORK_TIMEOUT,5.0) meaning a timeout of 5 seconds and then check the value with get_option it reads 1.36904e+08 !!!! Help would be much appreciated. Thx, Jerry. _________________________________________________________________ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail |
From: Jens V. <je...@zo...> - 2003-02-18 18:12:15
|
what you are saying does not make any sense to me. if you instantiate a LDAPUserFolder then it will be used for=20 authentication purposes in that place of your directory structure and=20 "downward". this is not the right mailing list to discuss zope issues. this mailing=20= list is for the python-ldap module only. jens On Tuesday, Feb 18, 2003, at 04:26 US/Eastern, Rakesh Naidu wrote: > hello jens, > i was able to import the ldap client(LDAPUserFolder) in to zope=20 > managament > iinterface...and now i have set the server name etc to the proper=20 > values.... > now, the user that owns zope needs to be authernticated with ldap to=20= > the > required directory....how to bind the user to the particular=20 > directory...so > that authentication happens from zope, using the client=20 > ldapuserfolder..... > > please let me know if you need any more details in specific.... > > regards, > rakesh.... > > > ----- Original Message ----- > From: "Jens Vagelpohl" <je...@zo...> > To: "python-ldap" <pyt...@li...> > Sent: Tuesday, December 17, 2002 6:59 PM > Subject: Re: error installing ldapmodule1.8 > > > well thank you michael ;) > > > On Tuesday, Dec 17, 2002, at 06:22 US/Eastern, Michael Str=F6der = wrote: > >> Rakesh Naidu wrote: >>> michael...can u throw some light on this error..... >>> 2002-12-17T10:50:45 ERROR(200) Zope Could not import >>> Products.LDAPUserFolder >>> Traceback (innermost last): >>> [..] >>> ImportError: No module named ldap >> >> This was recently discussed here. I've attached a posting by Jens >> before he has to repeat it. >> >> Furthermore you can search the mailing list archive for 'Zope'. >> >> Ciao, Michael >> >> -------- Original Message -------- >> Subject: Re: Problems importing ldap in Zope >> Date: Fri, 29 Nov 2002 20:12:57 -0500 >> From: Jens Vagelpohl <je...@zo...> >> To: Jorge Loureiro Dias <lou...@dt...> >> CC: pyt...@li... >> >> this problem has nothing to do with zope. the ldap module zope is >> trying to import is messed up. the one zope is trying to import is=20 >> most >> likely not the same one that gets imported if you run python itself >> from the command line. >> >> you need to locate the exact python binary zope uses and rebuild the >> python-ldap module with that binary. >> >> jens >> >> >> >> ------------------------------------------------------- >> This sf.net email is sponsored by: >> With Great Power, Comes Great Responsibility Learn to use your power >> at OSDN's High Performance Computing Channel >> http://hpc.devchannel.org/ >> _______________________________________________ >> Python-LDAP-dev mailing list >> Pyt...@li... >> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev > > > > ------------------------------------------------------- > This sf.net email is sponsored by: > With Great Power, Comes Great Responsibility > Learn to use your power at OSDN's High Performance Computing Channel > http://hpc.devchannel.org/ > _______________________________________________ > Python-LDAP-dev mailing list > Pyt...@li... > https://lists.sourceforge.net/lists/listinfo/python-ldap-dev > > |
From: Rakesh N. <rn...@ze...> - 2003-02-18 09:21:09
|
hello jens, i was able to import the ldap client(LDAPUserFolder) in to zope managament iinterface...and now i have set the server name etc to the proper values.... now, the user that owns zope needs to be authernticated with ldap to the required directory....how to bind the user to the particular directory...so that authentication happens from zope, using the client ldapuserfolder..... please let me know if you need any more details in specific.... regards, rakesh.... ----- Original Message ----- From: "Jens Vagelpohl" <je...@zo...> To: "python-ldap" <pyt...@li...> Sent: Tuesday, December 17, 2002 6:59 PM Subject: Re: error installing ldapmodule1.8 well thank you michael ;) On Tuesday, Dec 17, 2002, at 06:22 US/Eastern, Michael Ströder wrote: > Rakesh Naidu wrote: >> michael...can u throw some light on this error..... >> 2002-12-17T10:50:45 ERROR(200) Zope Could not import >> Products.LDAPUserFolder >> Traceback (innermost last): >> [..] >> ImportError: No module named ldap > > This was recently discussed here. I've attached a posting by Jens > before he has to repeat it. > > Furthermore you can search the mailing list archive for 'Zope'. > > Ciao, Michael > > -------- Original Message -------- > Subject: Re: Problems importing ldap in Zope > Date: Fri, 29 Nov 2002 20:12:57 -0500 > From: Jens Vagelpohl <je...@zo...> > To: Jorge Loureiro Dias <lou...@dt...> > CC: pyt...@li... > > this problem has nothing to do with zope. the ldap module zope is > trying to import is messed up. the one zope is trying to import is most > likely not the same one that gets imported if you run python itself > from the command line. > > you need to locate the exact python binary zope uses and rebuild the > python-ldap module with that binary. > > jens > > > > ------------------------------------------------------- > This sf.net email is sponsored by: > With Great Power, Comes Great Responsibility Learn to use your power > at OSDN's High Performance Computing Channel > http://hpc.devchannel.org/ > _______________________________________________ > Python-LDAP-dev mailing list > Pyt...@li... > https://lists.sourceforge.net/lists/listinfo/python-ldap-dev ------------------------------------------------------- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ _______________________________________________ Python-LDAP-dev mailing list Pyt...@li... https://lists.sourceforge.net/lists/listinfo/python-ldap-dev |
From: <mi...@st...> - 2003-02-17 19:35:07
|
Allan Streib wrote: > > AttributeError: ReconnectLDAPObject has no attribute '_store_last_bind' Thanks for catching this. > I have found that the following change seems to result in the correct > functionality. Your patch is in CVS now (together with support for ReconnectLDAPObject.search_ext_s()). Ciao, Michael. |
From: <mi...@st...> - 2003-02-11 23:06:00
|
Allan Streib wrote: > Trying to build -pre06, with the following in setup.cfg: > > libs = ldap_r lber sasl ssl crypto > [..] > ImportError: /usr/kerberos/lib/libk5crypto.so.3: shared object not open > [..] > I saw this previously and thought it might be that I was using > openldap-2.0.23, contrary to advice in the README file. So I built 2.0.27 > and used those libraries to build python-ldap-2.0.0-pre06 > > Looking at ldd output for _ldap.so, it seems to be finding > everything: Try to play with LD_LIBRARY_PATH or add /usr/kerberos/lib to /etc/ld.so.conf. > If I specify ldap instead of ldap_r in my setup.cfg libs, I do not get > this error on import ldap. I'm not even sure if libldap_r of OpenLDAP 2.0.x works well with your Kerberos setup. Is it Heimdal? I would consider libldap_r of OpenLDAP 2.1.x to be more mature. But not sure if that solves *your* problem. Ciao, Michael < |
From: Allan S. <as...@in...> - 2003-02-11 18:53:20
|
In python-ldap-2.0.0pre06, attempting to use sasl_bind_s in the a ReconnectLDAPObject, I received the following error: AttributeError: ReconnectLDAPObject has no attribute '_store_last_bind' I have found that the following change seems to result in the correct functionality. There may be a more elegant solution.... --- ldapobject.py.orig Tue Feb 11 13:34:46 2003 +++ ldapobject.py Tue Feb 11 11:25:38 2003 @@ -672,7 +672,10 @@ def _apply_last_bind(self): if self._last_bind!=None: func,args,kwargs = self._last_bind - apply(func,args,kwargs) + if kwargs: + apply(func,args,kwargs) + else: + apply(func,args) def _restore_options(self): """Restore all recorded options""" @@ -741,7 +744,7 @@ """ sasl_bind_s(who, auth) -> None """ - self._store_last_bind(self.sasl_bind_s,who,auth) + self._last_bind = (self.sasl_bind_s,(who,auth),{}) return self._ldap_call(self._l.sasl_bind_s,who,auth) def add_s(self,*args,**kwargs): |