x27;t know how to handle the Sync Info Message which is an LDAP
Intermediate Response Message (see 2.5 in RFC). perl-ldap doesn't
seems to support intermediate responses in response to LDAP::Search.
What is the way to correct this ?
thanks
Mathieu Parent
diff -urN --exclude=blib --exclude=debian
On Tue, Jun 17, 2008 at 5:16 PM, Graham Barr <[EMAIL PROTECTED]> wrote:
> On Jun 14, 2008, at 2:01 PM, Mathieu PARENT wrote:
>>
>> Hi,
>>
>> I have implemented LDAP Content Synchronization Operation (rfc4533) in
>> perl-ldap (See the attached patch). Thi
).
Waiting for feedback before (I hope) inclusion.
Regards
Mathieu Parent
---
MANIFEST |5 +
lib/Net/LDAP/ASN.pm | 52 +++-
lib/Net/LDAP/Constant.pm | 46 ++-
lib/Net/LDAP/Control.pm | 15 ++-
lib/Net/LDAP
Regards
Mathieu Parent
On Wed, Jul 16, 2008 at 8:02 PM, Mathieu PARENT <[EMAIL PROTECTED]> wrote:
> Hi,
>
> This patch implements Intermediate Message and RFC 4533.
>
> Notes:
> - The only intrusive change is in lib/Net/LDAP/Search.pm
> - Net::LDAP::Intermediate::SyncInf
Subject: [PATCH] IntermediateMessage and LDAP Content synchronisation fixes:
- Fix ASN parsing of syncRequestValue, syncDoneValue and syncInfoValue
(attributes with default value are threated as optional values)
- Renamed syncInfoValue ASN name to match RFC
- Fixed parsing of SyncDone and Syn
Subject: [PATCH] LDAP Content synchronisation fixes
- Fixed parsing of SyncState: avoid emptying the value
- Fill in default values in Intermediate::SyncInfo
---
lib/Net/LDAP/Control/SyncState.pm | 10 +-
lib/Net/LDAP/Intermediate/SyncInfo.pm | 21 +
2 files
e packages for the next release [3]
(and slurpd from OpenLDAP 2.3 is not in this release).
Can perl-ldap 0.39 be released soon, to be included in Suse 11.1 and
permit kolab to work again?
Thanks
Mathieu Parent
[1]: http://kolab.org/
[2]: https://www.intevation.de/roundup/kolab/issue1755
Hi,
2008/10/16 Graham Barr <[EMAIL PROTECTED]>:
> On Oct 15, 2008, at 4:38 PM, Mathieu Parent wrote:
>>
>> (snip)
>>
>> Can perl-ldap 0.39 be released soon, to be included in Suse 11.1 and
>> permit kolab to work again?
>
> I can make one this wee
Thanks to Richard Boss for spotting this.
---
lib/Net/LDAP/Control/SyncRequest.pm |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/lib/Net/LDAP/Control/SyncRequest.pm
b/lib/Net/LDAP/Control/SyncRequest.pm
index 95cd716..d905d7b 100644
--- a/lib/Net/LDAP/Control/SyncReques
Part of RFC 4533.
---
lib/Net/LDAP/Constant.pm |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/lib/Net/LDAP/Constant.pm b/lib/Net/LDAP/Constant.pm
index a9bebe9..7098d8c 100644
--- a/lib/Net/LDAP/Constant.pm
+++ b/lib/Net/LDAP/Constant.pm
@@ -437,6 +437,10 @@ A loop has
cases. For a working example (refreshOnly) see "sub searchCallback()"
in module Kolab::LDAP::Backend::syncrepl in Kolab ([kolab-syncrepl]).
Also you can encounter some problems with rereshAndPersist mode.
I will propose a patch to update the doc.
Mathieu Parent
[kolab-syncrepl]:
http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/perl-kolab/lib/Kolab/LDAP/Backend/syncrepl.pm?rev=1.6&content-type=text/vnd.viewcvs-markup
---
lib/Net/LDAP/Control/SyncDone.pm | 31 +--
lib/Net/LDAP/Control/SyncState.pm | 31 +--
lib/Net/LDAP/Intermediate/SyncInfo.pm | 31 +--
3 files changed, 3 insertions(+), 90 deletions(-)
diff --gi
, even when changing entries in the LDAP.
Any idea?
As my explanation is probably insufficient, see the code below, the
attached output and http://www.ietf.org/rfc/rfc4533.txt
Mathieu Parent
=== CODE ===
#!/usr/bin/perl
#BEGIN {
#push @INC, './perl-ldap/lib';
#}
use Data::Dumpe
hi Graham,
Thanks for your fast reply.
On Thu, Dec 3, 2009 at 9:22 PM, Graham Barr wrote:
> On Dec 3, 2009, at 1:55 PM, Mathieu Parent wrote:
>> Hello,
>>
>> (OK, this is my code, so this is probably my fault, but it appears to
>> be above my knowledge.)
slave is notified.
NB: the user is added using a web interface hosted on the master. This
stream is not captured.
Mathieu Parent
capture.pcap
Description: application/cap
Hello,
On Thu, Dec 3, 2009 at 10:40 PM, Mathieu Parent wrote:
> A little more info.
>
> The attached capture reproduce the following scenario:
> 192.168.0.132 is the Net::LDAP test machine
> 192.168.0.15 is the master
> 192.168.0.16 is the slave
>
> at 0 the slave sla
I'm going to be crazy..
Now this works. I have not changed anything!
In the meantime, I have added support for LDAP intermediate response
in Wireshark.
Mathieu Parent
On Wed, Dec 9, 2009 at 6:15 PM, Mathieu Parent wrote:
> Hello,
>
> On Thu, Dec 3, 2009 at 10:40 PM, Mathieu
?
Does removing line 61 of Net/LDAP/Intermediate/SyncInfo.pm
($self->{asn}{cookie};) suppress the second warning?
Mathieu Parent
On Wed, Sep 8, 2010 at 12:54 PM, Dieter Kluenter wrote:
> Mathieu Parent writes:
>
>> On Mon, Sep 6, 2010 at 10:48 PM, Dieter Kluenter wrote:
>>> Hi,
>>> after updating Authen::SASL to version 2.15 and Net::LDAP to version
>>> 0.4001, running http:
19 matches
Mail list logo