f work in Net::LDAP::LDIF to make it correct.
Any objections ?
Further ideas, ... welcome.
CU
Peter
P.S: I have implemented a few more controls and will upload
them to SVN by the end of the week.
$entry->update($ldap);
where $entry is a Net::LDAP::Entry object and $ldap is a
Net::LDAP object.
I want to extend this method so that you can pass it a
Net::LDAP::LDIF object:
$entry->update($ldif);
CU
Peter
arbage in, garbage out).
Time to get the next version of perl-ldap released ;-)
Peter
sting RFC is the one about LDIF: RFC 2849
What you call binary is just some form of input/output encoding to
let the server know unambigously whether a leading space belongs to
the attribute or whether it is part of the LDIF file syntax.
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
sole authoritative source.
> When modifying these attributes, separate "delete" and "add" LDIF
> changes are generated, instead of a single "replace" change.
I have not been able to find the new versions.
Neither in the freshly cut release 0.29 nor in the CVS on perl-ldap.sf.net.
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
by the problem.
Even if I login annoymously and check out a copy from the CVS tree
I only get an outdated version compared to the 0.29 release
(LDAP.pm pretends the version is "0.28_01" ;-(
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
ry server?
>Does it need a login or can be bind anynomously?
This depends on the server.
Usually write operations to a need need authentication.
> 3. Is there a sample script to do the import? All i
> can see right now
>is to read the ldif file entry by entry and do
> $ld
his as anonymous)
> *Is there any function to get return code to control the status.*
Try
$mesg = $ldap->bind(DN, password => PW);
if ($mesg->code() != LDAP_SUCCESS)
{
do_what_you_need_to_do_an_a_failed_bind();
}
It's documented in the man page.
Peter
--
Peter
;-)
But then we have the same problem: How can I enter a character
of a character set different from my default input character set ?
The mapping from UTF-16 to UTF-8 is a 1:1 mapping and no character set
conversion (both are data representations of Unicode)
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
here $mysub is a reference to a subroutine like
$mysub = &testerror() { print "some message"; . }
Nothing happens probably due to syntax but why?
regards and thanks
Peter Sørensen/University of Southern Denmark/email: [EMAIL PROTECTED]
se cases in
general just to stay in 8bit instead of doing it correct with UTF-8.
But wait: AFAIK Net::LDAP is subclassable. You do not need to change Net::LDAP
but can make your private sublass that does it with conversion if you want
it.
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
APIs specifically designed to do transcoding).
Thank you very much, Kurt.
I absolutely concur.
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
to a 5.8.x machine to test it).
On the perl-ldap side I remember some discussions on the ML that
there were some issues with "character semantics".
I don't know If they are still there ?
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
attribute's value, an additional option [e.g. chars => 1]
can tell get_value() to use character semantics instead of the default byte
semantics. This allows the user to get Perl strings from attributes he knows
to be encoded in UTF8.
e.g.
# get givenName as a string in character semantics
or some reason the perl.exe processes
> aren't exiting.
>
> Any suggestions on how to address the problem? And/or is there some way of
> limiting the resources used by perl-ldap to sidetrack the memory issue?
Have you tried perl-ldap 0.29 ?
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
references, why don't you simply use the
values itself:
# get value from entry (set it to empty string if it is not in the entry)
$homedir = $entry->get_value('homedirectory') || '';
print $homedir."\n";
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
eans nor am I at all familiar
> with the Net::LDAP code so I think I've hit a stand-still. Has anybody else
> experienced this (I did try a couple searches and came up empty). Or better
> yet, does anybody know how to fix it :).
It would help people willing to help you if they knew
* the
Hi Everyone,
I've been thinking about this for a little while now, but haven't hit on a
suitable solution.
The DSA I'm querying allows an approximate search, which uses a synonym
lookup. So as an example, if I search for Jim, Jim can also be known as
James, Jamie, Jimmy.
Now the results from th
* Peter Lavender ([EMAIL PROTECTED]) wrote:
Not great replying to yourself, but just for the archive:
> I've been thinking about this for a little while now, but haven't hit on a
> suitable solution.
>
> The DSA I'm querying allows an approximate search, which uses
cking:
$ldaps = new Net::LDAPS('myserver.example.com') or die "$@";
It won't make it work but it will give hints about the error.
Calling the constructor with a debug argument might give even more clues.
(see the Net::LDAP man mage for more information)
If you
;, but not much detail into why.
Are you on Windows ?
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
gt;bind("CN=$name",$LDAPSearchBase,password=>$password);
return "Can't bind:".$result->error if $result->code;
bind() always returns a message object.
See man Net::LDAP for details
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
binary syntax (e.g.
name) LDAP expects data to be UTF8 encoded.
Your example is not UTF8 encoded but simple ISO8859-1.
(the UTF8 encoding of "Félix" would look like "Félix")
For en-/decoding between 8bit character set and the unicode encodeing UTF8
there are various modules on CPAN.
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
in my bind call?
> I'm sure that my DN and password are correct as the command line search
> tool can authenticate with them.
A snippet of your code might help to diagnose the problem.
With only the information given above only guesses are possible.
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
of the network.
netfilter filters network packets while perl-ldap allows to write LDAP clients
(which eventually cross the network).
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
ve
> Directory group with attribute "member", I get 'undef' from get_value().
> Does anyone know what the value count limit is, and is there a way to
> extend it?
>
> my (@member) = $entry->get_value("member");
It might be pure coincidence but AD
e warn function and i get:
>
> '81' at ./nis2ldap line 150.
>
> However my script works if I do
>
> my $ldap = Net::LDAP->new($ldaphost,version => 2)
>
> but fails if we use the default version => 3.
Does the server you connect to support LDAPv3 ?
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
erl-ldap, IO::Socket::INET, Perl, ...)
Can you reach your LDAP server using another program (maybe even another Perl
script) ?
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
I do and
I am looking forward to seeing them in the CVS and/or
the next release of perl-ldap.
Yours
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
# patch to fix indenting / extend documentation
# created by Peter Marschall <[EMAIL PROTECTED]>
--- lib/Net/LDAP/LDIF.pod
+++ lib/Net/LDAP/LDI
Hi Chris,
On Sunday 18 January 2004 20:59, Chris Ridd wrote:
> On 18/1/04 6:31 pm, Peter Marschall <[EMAIL PROTECTED]> wrote:
> > * perl-ldap-0.31supportedFeatures.patch
> > - add the attribute supportedFeatures to the default list of
> > attributes for the roo
think an
> error's safer.)
> Good catch, thanks for the bug report.
The patch attached should fix the problem.
It sets the error string and returns undef on undefined filters.
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
# patch to check that filter is defined in Net::LDAP::Filter
remnant from pre LDIF v1 versions of
Net::LDAP::LDIF, but to me it seems strange to simply slurp away those lines
from each entry without telling the user that this may possibly be an error.
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
# patch to allow comments separated by blank lines i
Hi Chris,
I know re-posts are bad, but since I did not see any reaction to the attached
post I'll do nonetheless (maybe it got lost due to MyDoom)
May I ask you please to check the attached patch and maybe include it into the
perl-ldap CVS.
Thanks in advance
Peter
-- Forw
p 0.29
> IO-Socket-SSL-0.95
>
> Also i tried some thing like Timeout=> '540' didn't work
I doubt that it is the cause of your problem, but ...
The timeout option in Net::LDAP->new() is in lower case
e.g. timeout => 540
Have you tried perl-ldap 0.31 ?
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
think of it.
Peter
-- Forwarded Message --
Subject: Net::LDAP::LDIF patches
Date: Sunday 01 February 2004 14:40
From: Peter Marschall <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Hi Graham, hi Chris, hi list,
plaiying a bit with Net::LDAP::LDIF I found that Net::LDAP::LDI
Hi Chris,
I appreciate your support a lot.
Thank you very much
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
h() call there might
be other problems.
The first cause can be only cured by the server administrator.
The memory issue can be solved by either putting in more RAM into your client
or you may use callbacks for the search. See the callback parameter to the
Net::LDAP->search() method and the CA
Hi Grahan, Chris and list,
attached is a patch that fixes a type in my recent (well, no soo recent ;-)
additions to Net:LDAP::Util.pm
The patch applies cleanly to the trunk.
CU
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
# correct argument pattern
--- lib/Net/LDAP/Util.pm 2004-03-07 17
the recommendation about URL types to
support in RFC2849
I'd appreciate if this patch could make it into the standard perl- ldap
distribution.
What about an April Fool's Day relase of perl-ldap to make the recent
additions and changes official ?
Thanks in advance
Peter
--
Peter Marschall
patch against the SVN trunk of perl-ldap that implements this
feature.
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
doing wrong ?
have you tried to copy/rename the file an open it in an image viewer ?
Maybe the magic file (the one that defines the file derermination criteria for
file) is not good enough to detect this special case,
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
other words: regardless of platform, use binmode() on binary data,
like for example images.
I have added the binmode() call to the examples in the perl-ldap SVN.
Yours
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
'bindip'
> or similar argument in the documentation.
Quite simple. Do
$ldap = Net::LDAP->new('IP.AD.DR.ESS', ...);
where IP.AD.DR.ESS is the IP address you want to connect to.
If this IP address has a specific DNS entry you can use that as well.
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
Oops,
it fell off the list ;-)
Anyway. it seems to be halfway correct at most,
now that I have read Graham's answer.
Peter
On Monday 05 April 2004 19:05, Peter Marschall wrote:
> Hi,
>
> On Monday 05 April 2004 18:05, Safford, Brian wrote:
> > I obviously didn't
configration file on the client side that determines the relation
between the user's authorisation and the attributes the user is allowed to
change.
Of course you may also create special LDAP attributes/entries for that
purpose.
Peter
> Also, my LDAP server is authenticating against SASL/Kerb
Hi,
On Tuesday 06 April 2004 17:01, [EMAIL PROTECTED] wrote:
> In a message dated: Tue, 06 Apr 2004 16:06:14 +0200
> Peter Marschall said:
> >Better use a configration file on the client side that determines the
> > relation between the user's authorisation and the
x27;);
@cn = &$decodeUTF8(@cn) if ($decodeUTF8);
This works fine in Perl 5.6.x as well as in Perl 5.8.x
I do not know if the modules are available in/for ActivePerl (you may need a C
compiler to compile them)
Another alternative that only works in Perl 5.8 or higher is the Encoding.pm
module. IIRC there is also a Encoding::Compat.pm that makes the funkctions of
Encoding.pm available for Perl 5.6.1+
Hope it helps
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
s
documented ?
With this version parse() should return undef on errors as it is stated in the
pod file.
@Chris, Graham,
if you do not object I'l commit his change after Claude's tests.
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
# Copyright (c) 1998-2004 Graham Barr <
Hi,
On Friday 23 April 2004 09:28, Claude wrote:
> >>>>> "Peter" == Peter Marschall <[EMAIL PROTECTED]> writes:
> $ ./test0.pl
> Never printed at ./test0.pl line 9.
> Can't call method "error" without a package or object re
Hi Chris, hi Graham,
On Thursday 22 April 2004 21:01, Chris Ridd wrote:
> On 22/4/04 4:34 pm, Peter Marschall <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > On Tuesday 20 April 2004 11:39, Claude wrote:
> >> I tried this code which, IMO, confirms that "parse
from the server
e.g.qop=auth
So Paul's fixes match the RFCs.
(If I understand the RFCs and the code correctly he is even right in saying
that the client sending qop values auth-int and auth-conf is not supported in
the code)
I have converted his fixes into unified diff format and added a
SASL::Perl::DIGEST_MD5.pm.
Unfortunately I have not had the time to test this patch yet, but if I
interpreted the RFC correctly it should work ;-)
Yours
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
# allow option authzid in Digest MD5 SASL mech
--- lib/Authen/SASL/Perl/DIGEST_MD5.pm
+++ lib/Authen
recting my patch until now.
But now it is not necessary any more since you already did it.
(and you did it in less code than I would have needed ;-)
Thanks
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
around you may change the name of your objectclass so that it is
different from all the variable names you pass to Net::LDAP::Schema->may()
But the correct solution is to change
if ( UNIVERSAL::isa( $oc[0], "Net::LDAP::Entry" ) ) {
my $entry = $oc[0];
@oc = $entry->get_v
ntax
that makes it impossible for them to distinguish a correct certificate from a
bunch of bytes.
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
get the changetype into any object written to the file.
My intention is to provide an alternative to
the ::LDIF->write() method by extending the
::Entry->update() method, which in my intension shall
create LDIF entries with changetype regardless of the
value of the changes option in the ::LDIF object.
Peter
>
> Seems reasonable to me.
I have commited the patch to SVN head ...
>
> Note to all future patch submitters, a doc patch with any API change
> would be quite appropriate
...along with a small documentation update.
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
d be nice, and the one above might be necessary.
What do you think ?
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
ne can wait until after the release.
>
> I still do not understand what it is you are trying todo with this
> second one, so I would like to see some sample code before it is
> applied.
>
> To me it does not make any sense to update an ldif object, there is
> nothing to update
Hi,
On Thursday 10 June 2004 20:26, Graham Barr wrote:
> > Shall I give it a try ?
>
> Sure, I don't have time right now, thats why I put it in the mail :-)
Done.
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
someone enlighten me?
Although the information you gave is very scarce I beleive you did not get an
error but references I.e. the server directs you to othr servers that can
answer your questions. MS should really have documented that behaviour.
Try to ask an GC as they are much less prone to r
re
dynamically filled from the users of the Authen::SASL object.
When used with Net::LDAP SERVICE is set to "ldap" and HOST is the name
of the host Net::LDAP->new() connects to.
See the MS docuemtnation what kind of digest-uri MS ADS 2003 GCs support.
Google found MS KB article 298718 (just a hint ;-)
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
te in one modify operation (look for changes in the
Net::LDAP man page)
* You may try to use the set_password extended operation
(IMHO this is not yet part of 0.25 so you may need to upgrade)
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
Makefile.PL
instead of the well known
perl Makefile.PL
Hope it helps
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
Hi Graham, hi list,
the attached patch adds documetnation to the SASL machanisms in
Authen::SASL.
It may not be perfect as I am no naticve english speaker but better than
nothing.
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
--- Authen-SASL/lib/Authen/SASL/Perl/ANONYMOUS.pm
+++ Authen
Hi Everyone,
Sorry to be a pain, but does anyone know where a searchable archive of
the list is? I've searched google, and it didn't give me any hints, I
even went to the perl-ldap homepage.. but nothing.
I seem to recall that someone posted something about a threaded
perl-ldap script they wrot
the method
to do it.
Is it possible to do what I am asking?
More to the point, should I be doing what I'm asking?
How is it done?
Thanks in advance
Peter
err=13 nentries=0
> text=confidentiality required
Since root_dse is little more than a search with scope base on the DIT's root
it all depends on your server's configuration whether root_dse() fails or not.
I'd suggest to allow access to the DIT's root to anybody since th
Thanks for all the feedback. I went ahead an wrote a simple recursive
desent for my containers. I made the assumption that they were all
organizationalUnits.
But what if the OU is not the only way you have structured your DIT?
By changing the filter to objectClass=* it will remove your curren
;surname");
> $entry = $ldap->search(base => "$opt{b}",
> scope => "$opt{s}",
> filter => "$search",
> attrs => @attr);
Try
attrs => [EMA
value conforming to the
attribute's syntax (resp. an existing value when deleting) , an existing $dn,
your LDAP server was up and you were bound with a DN that was allowed to
perform this operation.
Unfortunately you did not send these parameters in your mail, which makes
answering the question a bit of guesswork.
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
Hi,
thanks for the bug report.
I've committed the fix to the SVN repository
Peter
On Saturday 21 August 2004 15:01, Rolandas Naujikas wrote:
> I'm using FreeBSD 4.9 and latest p5-perl-ldap module version (0.32.02)
> from ports. My script doesn't start because of compila
er.
I have added a line to Search.pod in SVN head that makes this a bit clearer.
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
t the credentials your
script is running under from the session / OS.
perl-ldap does not provide such a feature.
Alternatively the script can ask the caller for its DN and password to bind
with (either by commandline arguments or interactively).
Hope this helps
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
applications in that case.
(It is hard to search for somebody called "Müller" in a web-based directory
application if you do not have the "ü" (= ü in HTML) on your keyboard or
not even in your client's character set ;-)
CU
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
Hi Chris,
On Tuesday 23 November 2004 09:10, Chris Ridd wrote:
> On 21/11/04 6:02 pm, Peter Marschall <[EMAIL PROTECTED]> wrote:
> > Do we need an option that changes the behaviour to the one the RFC
> > suggests ? (maybe alloptions => 0 i.e. defined but false ;-)))
no leading or trailing spaces or tabs
- try to replace the braces by spaces (ehm, not the opening one ;-)))
Hope it helps
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
tras/lib/perl5/site_perl/5.8.0/Net/LDAP.pm
> line 296, line 225.
I think you are right.
If Net::LDAP.pm does not import the constant,
Net::LDAP::Bind.pm cannot hope to get it imported from Net::LDAP.pm
I applied a fix to SVN
Thanks
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
Hi,
On Monday 24 January 2005 03:30, Graham Barr wrote:
> On Sat, January 22, 2005 9:33 am, Peter Marschall said:
> > I think you are right.
> > If Net::LDAP.pm does not import the constant,
> > Net::LDAP::Bind.pm cannot hope to get it imported from Net::LDAP.pm
>
>
Hi,
On Monday 24 January 2005 13:03, Matt Stevenson wrote:
> OK i've done some more testing and it seems to error
> if Net::LDAP is installed as a user module. It seems
> fine if installed into core perl. Did you have it
> installed as a user module Peter?
What do you mean
"-" SEP
Re-reading the RFC I think your analysis is correct.
I committed a patch to the perl-ldap SVN repository that appends
the dash to each modify operation when the 'version' option of the
Net::LDAP::LDIF object is set.
Please test.
> Although the question remains how well supported this syntax is by the
> various directory products out there.
I tested the one I had access to: OpenLDAP supports it.
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
sample,dc=local
...
# EOF
--- cut ---
Any objections ?
(I'd like to start coding on Monday)
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
e: what will be updated on the directory server?
> There is no DN specified? It looks like "nirwana code".
You are right, the example should be improved.
>
> How can $entry be directly bound to a user object like
> $dn = "CN=x99,OU=Test,OU=OrgUsers,OU=DepartementX,D
t do other people on the list think about it ?
Is it a bug in Net::LDAP::LDIF ?
Is the bug in Net::LDAP::Entry for not properly checking its input ?
Or is it even a bug in Unicode::String [incomplete implementation of
substr()] ?
CU
PEter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
Dear Mir biggin,
you sent your mai lto a public mailing list but adressed it only to
Graham Barr.
So I received your mail in error and hereby I inform you about your
error.
Yours
Peter Marschall
PS: AFAIK Graham does not respond to mails about perl ldap-sent to
his private mail address
to write a script that walks through
all entries, fetches the telephonenumber (or any other attibute with leading
or trailing spaces), check if the attributee has leading or trailing spaces
and if it does, delete those spcaes and write back the attribute to the
entry.
Might not seem very elegant, but does the trick.
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
applies to the DN.
For other attributes the check is not necessary since they can
either be written verbatim to the LDIF or get encoded using
MIME::Base64 before they are written.
I'll change the documentation in CVS to make it more clear.
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
Hi again,
On Tuesday 05 April 2005 16:13, Peter Marschall wrote:
> > I think that either the encode flag needs to be renamed encodedn
> > (none|base64|canonical) and the encode flag redirected to apply to
> > attribute values, but that would break a lot of existing code.
characters from being written
to the file.
Can you find a minimal test case so that we can find out where exactly the
problem is ?
CU
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
Hi Graham
On Wednesday 06 April 2005 02:55, Graham Barr wrote:
> On Apr 5, 2005, at 11:18 AM, Peter Marschall wrote:
> > Just for reference: it's in SVN since August 2004 ;-)
> >
> > Since there were some posts about documentation on the ML recently
> > maybe Gr
Hi,
On Wednesday 06 April 2005 07:58, Erik Ableson wrote:
> Le 5 avr. 2005, à 21:59, Peter Marschall a écrit :
> > It is not said that Net::LDAP::LDIF is the part with the problems.
> > It might as well be MIIS.
>
> That's entirely possible. although the odd behaviour
the ProxyAuth control.
Called with the parameters for the old version of the draft the new code
produces data that is identical to that of the old version.
Hoping for perl-ldap 0.33
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
Hi David,
On Wednesday 13 April 2005 20:49, Faltermier, David (HP Directory) wrote:
> Hi Peter,
>
> Thanks for patching Net::LDAP::Control::ProxyAuth.pm. It was on my list
> of things to do, but... .
>
> TEST RESULTS
>
> I applied and tested your patch aga
is: " . $mesg->error);
> return(0);
> } else {
> logmsg("$name: bind was successful");
> logmsg("$name: performing search");
> }
This is O.K.
> Is the second part just overly redundant?
No, the first part was ;-)
Hope it helps
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
("$password") )
> }
> );
>
> }
I may be mistaken, but I think Encode is only available with Perl 5.8.
In addition to that I think that your function only works with passwords in
the Latin1 (aka ISO-8859-1) character set.
The solution in the FAQ works for earlier
lity.
The ability to search for objects is part of the features thet an LDAP server
provides.
> Basically my aim is to search a huge ldif dump when possible,
> rather than hit the directory everytime.
Why ?
That's what LDAP srvers are for.
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
mber 2 and the subject DN (in the X.509 notation)
/C=US/O=Example\5C,Ltd./CN=John Doe/[EMAIL PROTECTED]
Trying to do things like that on LDIF files is quite hard IMHO (and one of the
major steps towards an LDAP server in Perl ;-)
Have fun
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
the installation which chokes on the
line
include_deps('Test::More');
in Makefile.PL (added after 2.08).
M::I 0.34 does the same, while the current
M::I 0.36 seems to work.
CU
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
an
packages for myself.
Now i can bug the Debian maintainer of these packages to update
the official packages as well so that they might get into Debian Sarge ;-)
CU
PEter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
ind() method to check if the password is
correct.
Net::LDAP::FAQ should give hints.
Hope it helps
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
1 - 100 of 330 matches
Mail list logo
