The main authentication section works fine via tls and 636, but when I add mod_shared_roster_ldap, I have to specifically turn those off inside the mod_shared_roster_ldap spec, which seems strange, with:
{ldap_encrypt, none},
{ldap_port, 389},
... otherwise the whole ejabberd server fails to properly start, instead it keeps trying and failing to connect to AD.
Does this module use its own connection code?
Does it insist on verifying the cert presented by the AD server?
Thanks for any help.
Brian
