On Thu, 12 Jan 2006, Cap wrote:
One more thing about this...
Is it possible to configure cyrus to contact SASL in a non
standard way, let's say through a domain socket specified
by an explicit path?
sasl_saslauthd_path
See $cyrus-sasl/doc/options.html
This works great so far, although I do need two different
saslauthd.conf files to be able to define two different ldap
filters.
How come ldap_filter is not implemented as an overridable
option, just like sql_select? It would be so nice to set
sasl_ldap_filter in imapd.conf and never have the need for two
parallel saslauthds at all.
sasl_ options in imapd.conf set parameters for the sasl library that cyrus
is using. Communication with saslauthd happens over a socket and is very
basic (send user and password, get OK response). saslauthd is a
standalone daemon, so it's never going to see any of the options set in
imapd.conf.
Andy
----
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
