Details
Description
Suggest that users run a test before installing/configuring saslauthd to make sure that the server can already talk to the LDAP server, e.g. with ldapsearch:
ldapsearch -LLL -H ldap://ldapserver:389 -D cn=someuser,ou=users,dc=mydomain,dc=com -w Passw0rd -x -bou=users,dc=mydomain,dc=com cn=someuser
|
Split out correct steps by OS (e.g. different package names).
Remove the chmod - shouldn't be used on any platform. Not needed when I tested on CentOS. On Ubuntu/Debian adding couchbase to the sasl group was enough:
sudo adduser couchbase sasl
The ldap_filter shouldn't have brackets round the parameter.
The first example contains samAccountName which is Windows/AD specific - given that there is a Windows example below this should be changed to uid.
The formatting on all the block quoting has indents after the first line.
The Troubleshooting page could probably be merged in to the saslauthd page - we certainly shouldn't be recommending the chmod or the sym-link. And you should be able to debug with the aforementioned ldapsearch, or by running saslauthd -d.