I was just curious what the status was on ejabberd's support for LDAPS (LDAP over SSL). I did a search of the forums, and other than this thread:
http://www.ejabberd.im/node/613
(to which I no less wrote an entry), there's not much on the subject. Noting badlop's response in that thread where he wrote "ejabberd uses a library to get LDAP support: ELDAP. The port is hard coded on the file ejabberd_auth_ldap.erl, line 39", and as Google is your friend, decided to do a little searching.
In no time flat I ran across this thread dating back to Nov 2003 which SEEMS to indicate that ELDAP has had support for LDAPS for a few years now:
And as the person in that particular thread was none other than Alexey himself, I figured it's quite likely that adding LDAPS support such that it just requires an adjustment of the configuration file might not be too far off.
So are there currently any plans in the works for adding LDAPS support? And if not, where is the most appropriate place to log such a feature request? :-)
Re: Status of LDAPS support in ejabberd
I figured it's quite likely that adding LDAPS support such that it just requires an adjustment of the configuration file might not be too far off.
ejabberd includes a modified version of eldap on directory ejabberd/src/eldap/. That version seems architecturally improved (better fault-tolerance etc) but lacks at least one feature included on the original eldap: LDAPS support.
So are there currently any plans in the works for adding LDAPS support? And if not, where is the most appropriate place to log such a feature request? :-)
No known plans on short term from known developers. Submit it to Bugzilla.
After you submit the feature request, you can give this a try if you have much, much spare time. I just looked at the original code and the modified one. I have no idea of LDAP/LDAPS but tried to port some code. It's such a quick, dirty and untested code that I give you a guarantee 99.9% that:
The patch is against SVN, and you need to change the options on eldap.erl lines 80..93 manually and recompile: use_tls=true, port=686, etc.