> There are
> several impediments to this happening:
> 1) OpenLDAP uses OpenSSL for crypto, while Mozilla uses NSS. My preference
> would be to have the ability for OpenLDAP to use NSS for crypto, especially if
> running in a Mozilla client app.
That probably makes sense from a Mozilla perspective, but I'm not sure it's worth the overhead of carrying NSPR around everywhere. Also some interesting commentary here:
> 2) Each API has extensions lacking in the other.
Not relevant, since Mozilla's use of LDAP is quite plain-jane.
> 3) The command line tools are incompatible.
I don't see how associated tools are relevant to the Thunderbird/Mozilla apps..
> 4) No one in either of the communities has either the time or the inclination
> to do the work.
Well, out of boredom, I spent 2 hours this afternoon patching my Mozilla build tree to use OpenLDAP. I think the difficulties have been overstated, because it's working fine on my OpenSUSE laptop.
Note that I haven't looked at the necessary autoconf changes, just edited my build tree after configure was already run. As such, edit config/autoconf.mk:
and use the attached patch. A more thorough adaptation would go through and eliminate the use of LDAPv2/deprecated APIs but this was quick and dirty...
(In reply to comment #10)
> What we really need is a unified API between OpenLDAP and Mozilla.
Yes. More to the point, we need a *good* LDAP API. Interested developers are invited to add comments here scratchpad. wikia.com/ wiki/LDAP_ C_API
http://
> There are
> several impediments to this happening:
> 1) OpenLDAP uses OpenSSL for crypto, while Mozilla uses NSS. My preference
> would be to have the ability for OpenLDAP to use NSS for crypto, especially if
> running in a Mozilla client app.
That probably makes sense from a Mozilla perspective, but I'm not sure it's worth the overhead of carrying NSPR around everywhere. Also some interesting commentary here:
http:// markmail. org/message/ z3sf37vnryypdko 4#query: openssl% 20vs%20nss+ page:2+ mid:xvw5nybqrhk w6w7n+state: results
> 2) Each API has extensions lacking in the other.
Not relevant, since Mozilla's use of LDAP is quite plain-jane.
> 3) The command line tools are incompatible.
I don't see how associated tools are relevant to the Thunderbird/Mozilla apps..
> 4) No one in either of the communities has either the time or the inclination
> to do the work.
Well, out of boredom, I spent 2 hours this afternoon patching my Mozilla build tree to use OpenLDAP. I think the difficulties have been overstated, because it's working fine on my OpenSUSE laptop.
Note that I haven't looked at the necessary autoconf changes, just edited my build tree after configure was already run. As such, edit config/autoconf.mk:
#LDAP_CFLAGS = -I${DIST} /public/ ldap local/include -DLDAP_DEPRECATED
#LDAP_LIBS = -L${DIST}/bin -L${DIST}/lib -lldap60 -lprldap60 -lldif60
LDAP_CFLAGS = -I/usr/
LDAP_LIBS= -L/usr/local/lib -lldap_r -llber
and use the attached patch. A more thorough adaptation would go through and eliminate the use of LDAPv2/deprecated APIs but this was quick and dirty...