d39d3aaff4
This patch adds dovecot support to the chasquid daemon, using the internal dovecot library added in previous patches. Dovecot support is still considered EXPERIMENTAL and may be reverted, or changed in backwards-incompatible ways. The patch also adds the corresponding integration test, which brings up a dovecot server with a custom configuration, and tests chasquid's authentication against it. If dovecot is not installed, the test is skipped.
1.4 KiB
Dovecot integration
As of version 0.04 (2018-02), chasquid has experimental integration with dovecot for authenticating users.
This means that chasquid can ask dovecot to authenticate users, instead/in addition to having its own per-domain user databases.
It is experimental because it was added recently, and the semantics and options are prone to be changed in the future. If you use this feature, please let the authors know, at chasquid@googlegroups.com.
Configuring dovecot
The following needs to be added to the Dovecot configuration, usually in
/etc/dovecot/conf.d/10-master.conf:
service auth {
unix_listener auth-chasquid-userdb {
mode = 0660
user = chasquid
}
unix_listener auth-chasquid-client {
mode = 0660
user = chasquid
}
}
If chasquid is running under a different user, adjust the user = lines
accordingly.
This lets chasquid issue authentication requests to dovecot.
Configuring chasquid
Add the following line to /etc/chasquid/chasquid.conf:
dovecot_auth: true
That should be it, because chasquid will "autodetect" the full path to the dovecot sockets, by looking in the usual places (tested in Debian, Ubuntu, and CentOS).
If chasquid can't find them, the paths can be set with the
dovecot_userdb_path and dovecot_client_path options.