Menu
▾
▴
perl-ldap-dev
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(200) |
Jun
(129) |
Jul
(184) |
Aug
(204) |
Sep
(106) |
Oct
(79) |
Nov
(72) |
Dec
(54) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(83) |
Feb
(123) |
Mar
(84) |
Apr
(184) |
May
(106) |
Jun
(111) |
Jul
(104) |
Aug
(91) |
Sep
(59) |
Oct
(99) |
Nov
(100) |
Dec
(37) |
| 2002 |
Jan
(148) |
Feb
(88) |
Mar
(85) |
Apr
(151) |
May
(80) |
Jun
(110) |
Jul
(85) |
Aug
(43) |
Sep
(64) |
Oct
(89) |
Nov
(59) |
Dec
(42) |
| 2003 |
Jan
(129) |
Feb
(104) |
Mar
(162) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Clif H. <cl...@di...> - 2001-04-11 13:03:54
|
> > Graham Barr <gb...@po...> wrote: > > Ah, now you are running with 5.00404, I don't have a copy of that handy. > > > > But at some point we are going to have to drop support for older versions > > of perl. > > > > Graham. > > What is the minimum version of perl that perl-ldap needs? We should test > for that in Makefile.PL. > > Cheers, > > Chris > > In my opinion the lowest version should be 5.004. All previous perl-ldap verisons installed with no problem(s) on 5.004. This is the first version that I know of that has had problems on 5.004. If we are going to set the mimimum version to 5.00503 then I think we need to let users (list) know about this well in advance of doing it. Regards, Clif Harden INTERNET: c-h...@ti... |
|
From: Chris R. <chr...@me...> - 2001-04-11 12:43:00
|
Graham Barr <gb...@po...> wrote: > Ah, now you are running with 5.00404, I don't have a copy of that handy. > > But at some point we are going to have to drop support for older versions > of perl. > > Graham. What is the minimum version of perl that perl-ldap needs? We should test for that in Makefile.PL. Cheers, Chris |
|
From: Graham B. <gb...@po...> - 2001-04-11 12:32:13
|
Ah, now you are running with 5.00404, I don't have a copy of that handy.
But at some point we are going to have to drop support for older versions
of perl.
Graham.
On Wed, Apr 11, 2001 at 07:05:25AM -0500, Clif Harden wrote:
>
> New set of errors.
>
> Here is the print out.
>
>
> /usr/local/bin/perl -I./blib/arch -I./blib/lib -I/usr/local/lib/perl5/sun4-solaris/5.00404 -I/usr/local/lib/perl5 bin/ldapsearch.PL
> >
> /home/clif/perls/perl-ldap-0.22_02 60 : make test
> PERL_DL_NONLAZY=1 /usr/local/bin/perl -I./blib/arch -I./blib/lib -I/usr/local/lib/perl5/sun4-solaris/5.00404 -I/usr/local/lib/perl5 -e 'use Test::Harness qw(&runtests $verbose); $verbose=0; runtests @ARGV;' t/*.t
> t/00ldif-entry......ok
> t/01canon_dn........Sequence (?<...) not recognized at blib/lib/Net/LDAP/Util.pm line 293.
> BEGIN failed--compilation aborted at t/01canon_dn.t line 3.
> dubious
> Test returned status 2 (wstat 512, 0x200)
> t/02filter........../^(\\.|[^\\*]*)*\*/: regexp *+ operand could be empty at blib/lib/Net/LDAP/Filter.pm line 122.
> BEGIN failed--compilation aborted at t/02filter.t line 4.
> dubious
> Test returned status 2 (wstat 512, 0x200)
> t/50populate........skipping test on this platform
> t/51search..........skipping test on this platform
> t/52modify..........skipping test on this platform
> t/53schema..........Ambiguous use of {entry} resolved to {"entry"} at blib/lib/Net/LDAP/Schema.pm line 575.
> ok
> Failed Test Status Wstat Total Fail Failed List of failed
> -------------------------------------------------------------------------------
> t/01canon_dn.t 2 512 ?? ?? % ??
> t/02filter.t 2 512 ?? ?? % ??
> Failed 2/7 test scripts, 71.43% okay. 0/14 subtests failed, 100.00% okay.
> make: *** [test_dynamic] Error 29
>
>
> Regards,
>
> Clif
>
>
>
> >
> > OK, I have fixed these error in CVS.
> >
> > If a few people could test this release on some real scripts
> > I will make a .23 release.
> >
> > Graham.
> >
> > On Tue, Apr 10, 2001 at 09:12:00PM -0500, Clif Harden wrote:
> > >
> > >
> > > Looks like we have a problem on this release when
> > > you do a make test. I get the following errors;
> > >
> > >
> > >
> > > /apps/clif/perls/perl-ldap-0.22_02 15 : make test
> > > PERL_DL_NONLAZY=1 /usr/bin/perl -Iblib/arch -Iblib/lib
> > > -I/usr/lib/perl5/5.00503/i386-linux -I/usr/lib/perl5/5.00503 -e 'use
> > > Test::Harness qw(&runtests $verbose); $verbose=0; runtests @ARGV;' t/*.t
> > > t/00ldif-entry......ok
> > > t/01canon_dn........Name "main::reforig" used only once: possible typo
> > > at t/01canon_dn.t line 86.
> > > Use of uninitialized value at blib/lib/Net/LDAP/Util.pm line 318.
> > > FAILED tests 23-28
> > > Failed 6/28 tests, 78.57% okay
> > > t/02filter..........ok
> > > t/50populate........skipping test on this platform
> > > t/51search..........skipping test on this platform
> > > t/52modify..........skipping test on this platform
> > > t/53schema..........ok
> > > Failed Test Status Wstat Total Fail Failed List of failed
> > > -------------------------------------------------------------------------------
> > > t/01canon_dn.t 28 6 21.43% 23-28
> > > 3 tests skipped.
> > > Failed 1/7 test scripts, 85.71% okay. 6/194 subtests failed, 96.91%
> > > okay.
> > > make: *** [test_dynamic] Error
> > > 29
> > >
> > >
> > > Once we fix these errors I think we should release .23.
> > >
> > > Regards,
> > >
> > > Clif Harden ch...@po...
> > >
> > >
> > >
> > >
> > > Graham Barr wrote:
> > > >
> > > > Whoops, sorry the file had the wrong permissions. It is there now
> > > >
> > > > Graham.
> > > >
> > > > On Tue, Apr 10, 2001 at 06:08:44PM +0100, Graham Barr wrote:
> > > > > I think it is about time we looked forward to a 0.23 release.
> > > > >
> > > > > I have put together a snapshot at http://monty.mutatus.co.uk/~gbarr/perl-ldap-0.22_02.tar.gz
> > > > >
> > > > > The release notes are
> > > > >
> > > > >
> > > > > perl-ldap 0.23
> > > > > ================================
> > > > >
> > > > > * Fixed bug in Net::LDAP::Filter when the filter contained an escaped *
> > > > > * Fixed SASL bind to call challenge with serverSaslCreds
> > > > > * Fixed some uninit errors in Net::LDAP::Entry
> > > > > * Various documention updates
> > > > > * Added Net::LDAP::Util::canonical_dn
> > > > > * Net::LDAP::LDIF will now call canonical_dn for any DN which
> > > > > contains non-printable characters
> > > > > * Added support for matchingruleuse, ditstructurerules, ditcontentrules
> > > > > and nameForms into Net::LDAP::Schema
> > > > > * The ->schema method in Net::LDAP has changed how it finds the
> > > > > schema to return. The new method is more correct, but there may
> > > > > be a possibility that this change has created an incompatability.
> > > > > * New control module Net::LDAP::Control::ProxyAuth from
> > > > > Olivier Dubois added
> > > > >
> > > > >
> > > > > If I have missed anything please let me know.
> > > > >
> > > > > Graham.
> > > > >
> > >
> > > --
> > >
> > >
> >
> >
>
>
>
>
|
|
From: Clif H. <cl...@di...> - 2001-04-11 12:13:04
|
Graham and company, The last set of errors that I just sent in for .23 were generated from perl version 5.004_04. Regards, Clif Harden INTERNET: c-h...@ti... |
|
From: Clif H. <cl...@di...> - 2001-04-11 12:04:15
|
New set of errors.
Here is the print out.
/usr/local/bin/perl -I./blib/arch -I./blib/lib -I/usr/local/lib/perl5/sun4-solaris/5.00404 -I/usr/local/lib/perl5 bin/ldapsearch.PL
>
/home/clif/perls/perl-ldap-0.22_02 60 : make test
PERL_DL_NONLAZY=1 /usr/local/bin/perl -I./blib/arch -I./blib/lib -I/usr/local/lib/perl5/sun4-solaris/5.00404 -I/usr/local/lib/perl5 -e 'use Test::Harness qw(&runtests $verbose); $verbose=0; runtests @ARGV;' t/*.t
t/00ldif-entry......ok
t/01canon_dn........Sequence (?<...) not recognized at blib/lib/Net/LDAP/Util.pm line 293.
BEGIN failed--compilation aborted at t/01canon_dn.t line 3.
dubious
Test returned status 2 (wstat 512, 0x200)
t/02filter........../^(\\.|[^\\*]*)*\*/: regexp *+ operand could be empty at blib/lib/Net/LDAP/Filter.pm line 122.
BEGIN failed--compilation aborted at t/02filter.t line 4.
dubious
Test returned status 2 (wstat 512, 0x200)
t/50populate........skipping test on this platform
t/51search..........skipping test on this platform
t/52modify..........skipping test on this platform
t/53schema..........Ambiguous use of {entry} resolved to {"entry"} at blib/lib/Net/LDAP/Schema.pm line 575.
ok
Failed Test Status Wstat Total Fail Failed List of failed
-------------------------------------------------------------------------------
t/01canon_dn.t 2 512 ?? ?? % ??
t/02filter.t 2 512 ?? ?? % ??
Failed 2/7 test scripts, 71.43% okay. 0/14 subtests failed, 100.00% okay.
make: *** [test_dynamic] Error 29
Regards,
Clif
>
> OK, I have fixed these error in CVS.
>
> If a few people could test this release on some real scripts
> I will make a .23 release.
>
> Graham.
>
> On Tue, Apr 10, 2001 at 09:12:00PM -0500, Clif Harden wrote:
> >
> >
> > Looks like we have a problem on this release when
> > you do a make test. I get the following errors;
> >
> >
> >
> > /apps/clif/perls/perl-ldap-0.22_02 15 : make test
> > PERL_DL_NONLAZY=1 /usr/bin/perl -Iblib/arch -Iblib/lib
> > -I/usr/lib/perl5/5.00503/i386-linux -I/usr/lib/perl5/5.00503 -e 'use
> > Test::Harness qw(&runtests $verbose); $verbose=0; runtests @ARGV;' t/*.t
> > t/00ldif-entry......ok
> > t/01canon_dn........Name "main::reforig" used only once: possible typo
> > at t/01canon_dn.t line 86.
> > Use of uninitialized value at blib/lib/Net/LDAP/Util.pm line 318.
> > FAILED tests 23-28
> > Failed 6/28 tests, 78.57% okay
> > t/02filter..........ok
> > t/50populate........skipping test on this platform
> > t/51search..........skipping test on this platform
> > t/52modify..........skipping test on this platform
> > t/53schema..........ok
> > Failed Test Status Wstat Total Fail Failed List of failed
> > -------------------------------------------------------------------------------
> > t/01canon_dn.t 28 6 21.43% 23-28
> > 3 tests skipped.
> > Failed 1/7 test scripts, 85.71% okay. 6/194 subtests failed, 96.91%
> > okay.
> > make: *** [test_dynamic] Error
> > 29
> >
> >
> > Once we fix these errors I think we should release .23.
> >
> > Regards,
> >
> > Clif Harden ch...@po...
> >
> >
> >
> >
> > Graham Barr wrote:
> > >
> > > Whoops, sorry the file had the wrong permissions. It is there now
> > >
> > > Graham.
> > >
> > > On Tue, Apr 10, 2001 at 06:08:44PM +0100, Graham Barr wrote:
> > > > I think it is about time we looked forward to a 0.23 release.
> > > >
> > > > I have put together a snapshot at http://monty.mutatus.co.uk/~gbarr/perl-ldap-0.22_02.tar.gz
> > > >
> > > > The release notes are
> > > >
> > > >
> > > > perl-ldap 0.23
> > > > ================================
> > > >
> > > > * Fixed bug in Net::LDAP::Filter when the filter contained an escaped *
> > > > * Fixed SASL bind to call challenge with serverSaslCreds
> > > > * Fixed some uninit errors in Net::LDAP::Entry
> > > > * Various documention updates
> > > > * Added Net::LDAP::Util::canonical_dn
> > > > * Net::LDAP::LDIF will now call canonical_dn for any DN which
> > > > contains non-printable characters
> > > > * Added support for matchingruleuse, ditstructurerules, ditcontentrules
> > > > and nameForms into Net::LDAP::Schema
> > > > * The ->schema method in Net::LDAP has changed how it finds the
> > > > schema to return. The new method is more correct, but there may
> > > > be a possibility that this change has created an incompatability.
> > > > * New control module Net::LDAP::Control::ProxyAuth from
> > > > Olivier Dubois added
> > > >
> > > >
> > > > If I have missed anything please let me know.
> > > >
> > > > Graham.
> > > >
> >
> > --
> >
> >
>
>
|
|
From: Chris R. <chr...@me...> - 2001-04-11 10:03:07
|
Graham Barr <gb...@po...> wrote: > Whoops, sorry the file had the wrong permissions. It is there now > > Graham. > > On Tue, Apr 10, 2001 at 06:08:44PM +0100, Graham Barr wrote: >> I think it is about time we looked forward to a 0.23 release. >> >> I have put together a snapshot at >> http://monty.mutatus.co.uk/~gbarr/perl-ldap-0.22_02.tar.gz >> >> The release notes are >> >> >> perl-ldap 0.23 >> ================================ >> >> * Fixed bug in Net::LDAP::Filter when the filter contained an escaped * >> * Fixed SASL bind to call challenge with serverSaslCreds >> * Fixed some uninit errors in Net::LDAP::Entry >> * Various documention updates >> * Added Net::LDAP::Util::canonical_dn >> * Net::LDAP::LDIF will now call canonical_dn for any DN which >> contains non-printable characters >> * Added support for matchingruleuse, ditstructurerules, ditcontentrules >> and nameForms into Net::LDAP::Schema >> * The ->schema method in Net::LDAP has changed how it finds the >> schema to return. The new method is more correct, but there may >> be a possibility that this change has created an incompatability. >> * New control module Net::LDAP::Control::ProxyAuth from >> Olivier Dubois added >> >> >> If I have missed anything please let me know. Added support for moddn in Net::LDAP::LDIF. Minor fixes to the DSML output (fixing illegal XML.) Cheers, Chris |
|
From: Graham B. <gb...@po...> - 2001-04-11 09:39:10
|
OK, I have fixed these error in CVS. If a few people could test this release on some real scripts I will make a .23 release. Graham. On Tue, Apr 10, 2001 at 09:12:00PM -0500, Clif Harden wrote: > > > Looks like we have a problem on this release when > you do a make test. I get the following errors; > > > > /apps/clif/perls/perl-ldap-0.22_02 15 : make test > PERL_DL_NONLAZY=1 /usr/bin/perl -Iblib/arch -Iblib/lib > -I/usr/lib/perl5/5.00503/i386-linux -I/usr/lib/perl5/5.00503 -e 'use > Test::Harness qw(&runtests $verbose); $verbose=0; runtests @ARGV;' t/*.t > t/00ldif-entry......ok > t/01canon_dn........Name "main::reforig" used only once: possible typo > at t/01canon_dn.t line 86. > Use of uninitialized value at blib/lib/Net/LDAP/Util.pm line 318. > FAILED tests 23-28 > Failed 6/28 tests, 78.57% okay > t/02filter..........ok > t/50populate........skipping test on this platform > t/51search..........skipping test on this platform > t/52modify..........skipping test on this platform > t/53schema..........ok > Failed Test Status Wstat Total Fail Failed List of failed > ------------------------------------------------------------------------------- > t/01canon_dn.t 28 6 21.43% 23-28 > 3 tests skipped. > Failed 1/7 test scripts, 85.71% okay. 6/194 subtests failed, 96.91% > okay. > make: *** [test_dynamic] Error > 29 > > > Once we fix these errors I think we should release .23. > > Regards, > > Clif Harden ch...@po... > > > > > Graham Barr wrote: > > > > Whoops, sorry the file had the wrong permissions. It is there now > > > > Graham. > > > > On Tue, Apr 10, 2001 at 06:08:44PM +0100, Graham Barr wrote: > > > I think it is about time we looked forward to a 0.23 release. > > > > > > I have put together a snapshot at http://monty.mutatus.co.uk/~gbarr/perl-ldap-0.22_02.tar.gz > > > > > > The release notes are > > > > > > > > > perl-ldap 0.23 > > > ================================ > > > > > > * Fixed bug in Net::LDAP::Filter when the filter contained an escaped * > > > * Fixed SASL bind to call challenge with serverSaslCreds > > > * Fixed some uninit errors in Net::LDAP::Entry > > > * Various documention updates > > > * Added Net::LDAP::Util::canonical_dn > > > * Net::LDAP::LDIF will now call canonical_dn for any DN which > > > contains non-printable characters > > > * Added support for matchingruleuse, ditstructurerules, ditcontentrules > > > and nameForms into Net::LDAP::Schema > > > * The ->schema method in Net::LDAP has changed how it finds the > > > schema to return. The new method is more correct, but there may > > > be a possibility that this change has created an incompatability. > > > * New control module Net::LDAP::Control::ProxyAuth from > > > Olivier Dubois added > > > > > > > > > If I have missed anything please let me know. > > > > > > Graham. > > > > > -- > > |
|
From: Clif H. <ch...@po...> - 2001-04-11 02:08:51
|
Looks like we have a problem on this release when
you do a make test. I get the following errors;
/apps/clif/perls/perl-ldap-0.22_02 15 : make test
PERL_DL_NONLAZY=1 /usr/bin/perl -Iblib/arch -Iblib/lib
-I/usr/lib/perl5/5.00503/i386-linux -I/usr/lib/perl5/5.00503 -e 'use
Test::Harness qw(&runtests $verbose); $verbose=0; runtests @ARGV;' t/*.t
t/00ldif-entry......ok
t/01canon_dn........Name "main::reforig" used only once: possible typo
at t/01canon_dn.t line 86.
Use of uninitialized value at blib/lib/Net/LDAP/Util.pm line 318.
FAILED tests 23-28
Failed 6/28 tests, 78.57% okay
t/02filter..........ok
t/50populate........skipping test on this platform
t/51search..........skipping test on this platform
t/52modify..........skipping test on this platform
t/53schema..........ok
Failed Test Status Wstat Total Fail Failed List of failed
-------------------------------------------------------------------------------
t/01canon_dn.t 28 6 21.43% 23-28
3 tests skipped.
Failed 1/7 test scripts, 85.71% okay. 6/194 subtests failed, 96.91%
okay.
make: *** [test_dynamic] Error
29
Once we fix these errors I think we should release .23.
Regards,
Clif Harden ch...@po...
Graham Barr wrote:
>
> Whoops, sorry the file had the wrong permissions. It is there now
>
> Graham.
>
> On Tue, Apr 10, 2001 at 06:08:44PM +0100, Graham Barr wrote:
> > I think it is about time we looked forward to a 0.23 release.
> >
> > I have put together a snapshot at http://monty.mutatus.co.uk/~gbarr/perl-ldap-0.22_02.tar.gz
> >
> > The release notes are
> >
> >
> > perl-ldap 0.23
> > ================================
> >
> > * Fixed bug in Net::LDAP::Filter when the filter contained an escaped *
> > * Fixed SASL bind to call challenge with serverSaslCreds
> > * Fixed some uninit errors in Net::LDAP::Entry
> > * Various documention updates
> > * Added Net::LDAP::Util::canonical_dn
> > * Net::LDAP::LDIF will now call canonical_dn for any DN which
> > contains non-printable characters
> > * Added support for matchingruleuse, ditstructurerules, ditcontentrules
> > and nameForms into Net::LDAP::Schema
> > * The ->schema method in Net::LDAP has changed how it finds the
> > schema to return. The new method is more correct, but there may
> > be a possibility that this change has created an incompatability.
> > * New control module Net::LDAP::Control::ProxyAuth from
> > Olivier Dubois added
> >
> >
> > If I have missed anything please let me know.
> >
> > Graham.
> >
--
|
|
From: Graham B. <gb...@po...> - 2001-04-10 20:18:06
|
Whoops, sorry the file had the wrong permissions. It is there now Graham. On Tue, Apr 10, 2001 at 06:08:44PM +0100, Graham Barr wrote: > I think it is about time we looked forward to a 0.23 release. > > I have put together a snapshot at http://monty.mutatus.co.uk/~gbarr/perl-ldap-0.22_02.tar.gz > > The release notes are > > > perl-ldap 0.23 > ================================ > > * Fixed bug in Net::LDAP::Filter when the filter contained an escaped * > * Fixed SASL bind to call challenge with serverSaslCreds > * Fixed some uninit errors in Net::LDAP::Entry > * Various documention updates > * Added Net::LDAP::Util::canonical_dn > * Net::LDAP::LDIF will now call canonical_dn for any DN which > contains non-printable characters > * Added support for matchingruleuse, ditstructurerules, ditcontentrules > and nameForms into Net::LDAP::Schema > * The ->schema method in Net::LDAP has changed how it finds the > schema to return. The new method is more correct, but there may > be a possibility that this change has created an incompatability. > * New control module Net::LDAP::Control::ProxyAuth from > Olivier Dubois added > > > If I have missed anything please let me know. > > Graham. > |
|
From: Gary F. <fl...@jm...> - 2001-04-10 17:33:11
|
I've got someone that wants to authenticate against an external LDAP server. They're running Perl 5 for Netware for CGI scripts on the Netscape web server. Anyone have any experiences with perl-ldap on this platform? thanks, -- Gary Flynn Security Engineer - Technical Services James Madison University Please R.U.N.S.A.F.E. http://www.jmu.edu/computing/info-security/engineering/runsafe.shtml |
|
From: Graham B. <gb...@po...> - 2001-04-10 17:10:00
|
I think it is about time we looked forward to a 0.23 release. I have put together a snapshot at http://monty.mutatus.co.uk/~gbarr/perl-ldap-0.22_02.tar.gz The release notes are perl-ldap 0.23 ================================ * Fixed bug in Net::LDAP::Filter when the filter contained an escaped * * Fixed SASL bind to call challenge with serverSaslCreds * Fixed some uninit errors in Net::LDAP::Entry * Various documention updates * Added Net::LDAP::Util::canonical_dn * Net::LDAP::LDIF will now call canonical_dn for any DN which contains non-printable characters * Added support for matchingruleuse, ditstructurerules, ditcontentrules and nameForms into Net::LDAP::Schema * The ->schema method in Net::LDAP has changed how it finds the schema to return. The new method is more correct, but there may be a possibility that this change has created an incompatability. * New control module Net::LDAP::Control::ProxyAuth from Olivier Dubois added If I have missed anything please let me know. Graham. |
|
From: Pooja <juh...@wo...> - 2001-04-10 14:44:59
|
I looked at the novell documentation and now the server accepts clear text passwords. The problem seems to be solved. thanks . On Tue, 10 Apr 2001 08:09:08 +0100 Chris Ridd <chr...@me...> wrote: > *This message was transferred with a trial version of > CommuniGate(tm) Pro* > Jim Harle <ha...@us...> wrote: > > Try my $mesg = $ldap->bind ($dn => $dn, password > =>$password,version => > > 3); > > > > Also, make sure you have the right password. > > > > On Mon, 9 Apr 2001, Pooja wrote: > > > >> I am new to NDS. I always get the following error > >> "LDAP_CONFIDENTIALITY_REQUIRED" when I do the bind > using dn > >> and password. > > That error *suggests* that the server is not willing to > accept simple binds > using a password sent to it in the clear, which is what > you are trying to > do. > > Instead, your server may require that you have a > 'confidential' connection, > perhaps one over SSL, eg LDAPS (supported in Net::LDAPS), > or TLS (not yet > supported by Net::LDAP.) > > Alternatively, you might be able to use SASL to negotiate > such a > connection. I'm not sure the SASL mechanisms available in > perl (read > perldoc Authen::SASL) can negotiate these, but Graham > will know for sure. > > Requiring a confidential connection would appear to be a > feature of the way > your server's been set up; perhaps you could clarify this > with the manager > of the server? > > Cheers, > > Chris |
|
From: Graham B. <gb...@po...> - 2001-04-10 08:10:17
|
On Tue, Apr 10, 2001 at 08:09:08AM +0100, Chris Ridd wrote: > Alternatively, you might be able to use SASL to negotiate such a > connection. I'm not sure the SASL mechanisms available in perl (read > perldoc Authen::SASL) can negotiate these, but Graham will know for sure. IIRC CRAM-MD5 is the only implemented method so far. But the whole Authen::SASL package needs some attention. Graham. |
|
From: Chris R. <chr...@me...> - 2001-04-10 07:09:25
|
Jim Harle <ha...@us...> wrote: > Try my $mesg = $ldap->bind ($dn => $dn, password =>$password,version => > 3); > > Also, make sure you have the right password. > > On Mon, 9 Apr 2001, Pooja wrote: > >> I am new to NDS. I always get the following error >> "LDAP_CONFIDENTIALITY_REQUIRED" when I do the bind using dn >> and password. That error *suggests* that the server is not willing to accept simple binds using a password sent to it in the clear, which is what you are trying to do. Instead, your server may require that you have a 'confidential' connection, perhaps one over SSL, eg LDAPS (supported in Net::LDAPS), or TLS (not yet supported by Net::LDAP.) Alternatively, you might be able to use SASL to negotiate such a connection. I'm not sure the SASL mechanisms available in perl (read perldoc Authen::SASL) can negotiate these, but Graham will know for sure. Requiring a confidential connection would appear to be a feature of the way your server's been set up; perhaps you could clarify this with the manager of the server? Cheers, Chris |
|
From: Jim H. <ha...@us...> - 2001-04-09 20:11:35
|
Try my $mesg = $ldap->bind ($dn => $dn, password =>$password,version => 3); Also, make sure you have the right password. On Mon, 9 Apr 2001, Pooja wrote: > I am new to NDS. I always get the following error > "LDAP_CONFIDENTIALITY_REQUIRED" when I do the bind using dn > and password. > > my $mesg = $ldap->bind (dn => $dn, password => > $password); > print " " . $mesg->code . " "; > print ldap_error_name($mesg->code) ; > > Can some one tell what am i doing wrong? > The same code works for Netscape directory server. > > thanks > > > > > > |
|
From: Pooja <juh...@wo...> - 2001-04-09 19:44:33
|
I am new to NDS. I always get the following error "LDAP_CONFIDENTIALITY_REQUIRED" when I do the bind using dn and password. my $mesg = $ldap->bind (dn => $dn, password => $password); print " " . $mesg->code . " "; print ldap_error_name($mesg->code) ; Can some one tell what am i doing wrong? The same code works for Netscape directory server. thanks |
|
From: Behruz R. <beh...@cp...> - 2001-04-09 15:55:13
|
Hi Mark, Thanks for your response, i will have a look to www.modperl.com . By the way, I found your book very interesting about different solutions to implement an LDAP directory. Thanks. Behruz. -----Original Message----- From: ma...@mj... [mailto:ma...@mj...] Sent: Sunday, April 08, 2001 9:50 AM To: Behruz Rushenas Cc: per...@li... Subject: Re: How to avoid connecting to LDAP at each Perl CGI-CALL The only way to do this is to use mod_perl instead of traditional CGI. mod_perl allows you to write to the Apache api instead of executing a seperate process. And once a mod_perl module is loaded it stays loaded. See www.modperl.com for more info. Mark On 4 Apr 01, at 8:24, Behruz Rushenas wrote: > Hi, > > I would like to know if there is way to avoid Binding to LDAP at each > time I Call a Perl CGI script? Right now, I have to bind every time I > call a script. > > I would like to keep my ldap instance created at the first begining > time and keep using it. Sorry if the question seems stupid to some of > you, but i am a novice in Perl and CGI programming. > > Thanks all of you for your help. > > Behruz. > > > > Mark Wilcox ma...@mj... Got LDAP? |
|
From: <ne...@na...> - 2001-04-09 15:41:23
|
Also make sure that reverse name resolution works. The GUI will become
often become very slow or just hang if it can resolve IP addresses into
names.
SteveN
"J Beck" <jb...@do...>@lists.sourceforge.net on 03/22/2001
09:10:58 AM
From: "J Beck" <jb...@do...>@lists.sourceforge.net on 03/22/2001
09:10 AM
Sent by: per...@li...
To: "'Lambright, Linda (N-Averstar)'" <lin...@lm...>
<per...@li...>
cc:
Subject: RE: Netscape directory server console
the rules you need are to allow tcp over 2 ports--389 & whatever your admin
port is
also ICMP packets must be allowed through.
-----Original Message-----
From: per...@li...
[mailto:per...@li...]On Behalf Of
Lambright, Linda (N-Averstar)
Sent: Wednesday, March 21, 2001 9:01 PM
To: per...@li...
Subject: Netscape directory server console
I know this isn't exactly a perl ldap question but if someone knows
the answer it would be a great deal of help
When you use the netscape console to administer the directory server
over the administration port what protocol are you using.
The reason I ask is I need to have the administration port opened in
the firewall for the correct protocol.
Thank you in advance
Linda Lambright
|
|
From: Chris R. <chr...@me...> - 2001-04-09 07:42:20
|
Robbie Allen <ra...@ci...> wrote: >> -----Original Message----- >> From: Chris Ridd [mailto:chr...@me...] >> A minor quibble: the "dn" line does not indicate an attribute called >> distinguishedName, but actually the DN of the entry being >> modified. (The DN of an entry is not held in an attribute of the > entry.) > > Actually it is in Active Directory. It is called distinguishedName. Ugh. > That's fine. What does it take to get this change incorporated into > LDIF.pm? Get one of the the maintainer's (Graham, Clif, Mark, me) attention, and if no-one objects to the change, they will integrate it. It looks a harmless enough change to integrate; I've gone ahead and done it. > Robbie Allen Thanks for the original bug-fix. Cheers, Chris |
|
From: <ma...@mj...> - 2001-04-08 19:00:07
|
The directory manager isn't even supposed to be an account in the directory. I suppose it could be in theory, but Netscape doesn't support it that way AFAIK. mark On 5 Apr 01, at 12:25, Ron Hall wrote: > > > Source of the problem has been found (I think)... > > ldif file has the following definition > > dn: cn=Directory Manager, o=McGill, c=CA > cn: Directory Manager > objectclass: top > objectclass: groupofuniquenames > uniquemember: cn=<<<<SOME STUFF>>> > > Where some stuff points to a record no longer in the > LDAP database <OH> > > This is further confounded by the aci > > aci: (target="ldap:///o=McGill, c = CA") (targetattr = "*") > (version 3.0; acl "allow all Admin group"; allow(all) > groupdn="ldap:cn=Directory Manager,o=McGill,c=CA";) > > > Which if I understand it correctly means that only people in the > admin group and do root dn things and that the admin group (as > defined by Directory Manager) needs to have a valid user in it > > Either that of make Directory Manager a simple account. > > > Am I close? > > r > > > > Mark Wilcox ma...@mj... Got LDAP? |
|
From: <ma...@mj...> - 2001-04-08 18:58:05
|
If you did, you hacked it yourself. While I have a modification that will allow this, I haven't posted it to CPAN yet (it will be at least another week before I do since I'm on the road again) It's a simple change though if you want to do it yourself. In Apache::AuthNetLDAP look for the line that says: unless($mesg->count()) replace the return ... with return DECLINED Then the PerlAuthenHandler MUST come before the AuthUserfile because AuthUserFile does not return a declined response. Mark On 6 Apr 01, at 17:43, Eamon Daly wrote: > Am I completely off my rocker or did I not once have a Location > protected so that I could auth against a htpasswd file if the LDAP > auth failed? I can't find a single trace of my old httpd.conf, but I > /swear/ I had it working at some point. Has anyone else done this? > > <Location /> > AuthName "Internal" > AuthType Basic > AuthUserFile conf/htpasswd.list > > PerlAuthenHandler Apache::AuthNetLDAP > PerlSetVar LDAPServer xxx.xxx.xxx.xxx > PerlSetVar LDAPPort 389 > PerlSetVar BaseDN "ou=xxxxx,ou=xxxxx,o=xxxxx" > PerlSetVar UIDAttr cn > > order deny,allow > deny from all > allow from 10. > allow from 127.0.0.1 > require user guest_pass > require valid-user > satisfy any > </Location> > > That results in: > > [Fri Apr 6 17:24:51 2001] [error] access to /internal/ failed for > 216.17.138.248, reason: user guest_pass: user entry not found for > filter: cn=xxxxx > > and a 401 error. Am I out of my mind? > > ______________________________ > Eamon Daly > FastWeb, Inc. > 847 568 6410 > > > > > Mark Wilcox ma...@mj... Got LDAP? |
|
From: <ma...@mj...> - 2001-04-08 16:46:55
|
The only way to do this is to use mod_perl instead of traditional CGI. mod_perl allows you to write to the Apache api instead of executing a seperate process. And once a mod_perl module is loaded it stays loaded. See www.modperl.com for more info. Mark On 4 Apr 01, at 8:24, Behruz Rushenas wrote: > Hi, > > I would like to know if there is way to avoid Binding to LDAP at each > time I Call a Perl CGI script? Right now, I have to bind every time I > call a script. > > I would like to keep my ldap instance created at the first begining > time and keep using it. Sorry if the question seems stupid to some of > you, but i am a novice in Perl and CGI programming. > > Thanks all of you for your help. > > Behruz. > > > > Mark Wilcox ma...@mj... Got LDAP? |
|
From: Dan G. L. <dan...@ta...> - 2001-04-08 10:30:33
|
On Friday 06 April 2001 09:17, you wrote:
| I'm still having trouble trying to get output from my LDAP MS Exchange
| script.
| I'm getting error 11 and error 87 when I do searches and no data.
| How do I translate the error code to a description? It might help me make
| more progress:
I had a similar problem Ian. Grahams docs explain them very well. Here is an
example of a compare.
use Net::LDAP::Util qw(ldap_error_text ldap_error_name);
use Net::LDAP::Constant qw(LDAP_COMPARE_TRUE LDAP_COMPARE_FALSE);
.
.
.
# Query the LDAP-server
$mesg = $ldap->compare(
$dn,
attr => $attr,
value => $value,
);
if ($mesg->code == LDAP_COMPARE_TRUE){
print "$thissubr: compare ok\n";
} elsif ($mesg->code == LDAP_COMPARE_FALSE) {
print "$thissubr: compare notok\n";
} else {
print "$thissubr compare error: " . ldap_error_text($mesg->code) . "\n";
}
Dan
--
Dan G. Lunde - dan...@c2...
http://home.world-online.no/~danglund/pgp/pgp...@c2...c
|
|
From: Graham B. <gb...@po...> - 2001-04-07 21:34:21
|
On Fri, Apr 06, 2001 at 04:58:10PM -0700, Robbie Allen wrote: > I'd like to use LDIF.pm for an LDIF parser I'm writing, but one of the > biggest problems I've found is that LDIF.pm silently skips LDIF lines > that are syntatically wrong. Could an option be specified to error out > on such things? This is one of those things that has been on my perpetual todo list. My thought was that _read_one should return undef on error and store the reason inside $self. read should return what it has already read and there should be an error method to access the error message. Anyone have any better ideas ? Feel like doing a patch ? Graham. |
|
From: Robbie A. <ra...@ci...> - 2001-04-06 23:57:51
|
I'd like to use LDIF.pm for an LDIF parser I'm writing, but one of the biggest problems I've found is that LDIF.pm silently skips LDIF lines that are syntatically wrong. Could an option be specified to error out on such things? Robbie Allen |
7902 messages has been excluded from this view by a project administrator.
