This documentation is for Dovecot v2.x, see wiki1 for v1.x documentation.
Differences between revisions 4 and 6 (spanning 2 versions)
Revision 4 as of 2005-01-05 01:28:02
Size: 142
Editor: talvi
Comment:
Revision 6 as of 2005-01-08 23:20:55
Size: 881
Editor: talvi
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
>what about multiple auth (local+vpopmail - users without "@domain" are local)? = Multiple Authentication Databases =
Line 3: Line 3:
Supported in 1.0, but not easy way to do it with 0.99.10. Dovecot 1.0-tests support defining multiple authentication databases, so that if password doesn't match in the first database, it checks the next one. This can be useful if you want to easily support having both local system users in /etc/passwd but also virtual users. This isn't possible in 0.99 releases.

Currently the fallbacking works only with PLAIN authentication mechanism.

This can be configured in the following way:

{{{
auth local {
  mechanisms = plain
  userdb = passwd
  passdb = pam
  user = root
}

auth virtual {
  mechanisms = plain
  userdb = pgsql /etc/dovecot-pgsql.conf
  passdb = pgsql /etc/dovecot-pgsql.conf
  user = dovecot-auth
}
}}}

You should make sure that the same user doesn't exist in multiple password databases. The order in which the authentications are done isn't guaranteed.

Multiple Authentication Databases

Dovecot 1.0-tests support defining multiple authentication databases, so that if password doesn't match in the first database, it checks the next one. This can be useful if you want to easily support having both local system users in /etc/passwd but also virtual users. This isn't possible in 0.99 releases.

Currently the fallbacking works only with PLAIN authentication mechanism.

This can be configured in the following way:

auth local {
  mechanisms = plain
  userdb = passwd
  passdb = pam
  user = root
}

auth virtual {
  mechanisms = plain
  userdb = pgsql /etc/dovecot-pgsql.conf
  passdb = pgsql /etc/dovecot-pgsql.conf
  user = dovecot-auth
}

You should make sure that the same user doesn't exist in multiple password databases. The order in which the authentications are done isn't guaranteed.

None: Authentication/MultipleDatabases (last edited 2019-09-11 14:00:18 by MichaelSlusarz)