Nelson B wrote:
Questions about the status of perLDAP in the mozilla source repository:
Is it still being maintained?
Yes. Leif and I are working on what will become version 1.5. One of
the problems is that I have made it more difficult to build, because the
latest version of the ldap c sdk does not include nspr and nss, so you
have to download, unpack, and install them separately.
Will client auth support ever be added?
Eventually, probably in the next major release.
Can we get the documentation fixed for the "certdb" argument to new?
Sure. Please file a bug in bugzilla.mozilla.org against Directory ->
Perldap.
According to http://www.mozilla.org/directory/csdk.html the LDAP C SDK
is still being actively maintained. I'm glad to see that!
Yes. We just released v5.17, and the mozilla/seamonkey/thunderbird team
are going to use that as their new branch point. Binaries are available
at ftp://ftp.mozilla.org/pub/mozilla.org/directory/c-sdk/releases/v5.17/
According to http://www.mozilla.org/directory/perldap.html the latest
perLDAP code is ~60 days old, suggesting that this code is still being
maintained. That's encouraging, if true. But the FAQ is about 5 years old.
So, what's the status of perLDAP?
Sporadically maintained. We use perldap in Netscape/Red Hat/Fedora
Directory Server, so we have a vested interest in maintaining it.
http://www.perldap.org/docs/Conn.html#item_new (a.k.a.,
http://lxr.mozilla.org/mozilla/source/directory/perldap/Conn.pm#1041 ) says:
new
This creates and initialized a new LDAP connection and object. The required
arguments are host name, port number, bind DN and the bind password. An
optional argument is a certificate (public key), which causes the LDAP
connection to be established over an SSL channel.
It's actually the path name of the directory containing NSS's cert & key DBs.
Currently we do not support Client Authentication, so you still have to
use the simple authentication method (i.e. with a password).
LDAP C SDK supports client auth. Will PerLDAP ever do so?
At some point. We are trying to figure out the future direction for
perldap. We think that for the next major release, we may just use SWIG
to generate the perl wrapper around the Mozilla LDAP C SDK rather than
the current hand tuned XS code. The SWIG approach would allow use to
easily expose all of the functionality of the LDAP C SDK, including
support for client auth, and also allow us to support other languages
such as python.
_______________________________________________
dev-tech-ldap mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-ldap
