This documentation is for Dovecot v1.x, see wiki2 for v2.x documentation.
Differences between revisions 12 and 13
Revision 12 as of 2009-03-15 22:35:09
Size: 2941
Editor: localhost
Comment: converted to 1.6 markup
Revision 13 as of 2010-04-14 00:47:30
Size: 2936
Editor: unknown
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
Line 8: Line 7:
Line 18: Line 16:
Line 19: Line 18:
Line 33: Line 31:
  * Dovecot supports reading all [[Authentication/PasswordSchemes|password schemes]] from passwd and shadow databases (if prefix is specified), but that is of course incompatible with all other tools using/modifying the passwords.   * Dovecot supports reading all [[Authentication/PasswordSchemes|password schemes]] from passwd and shadow databases (if prefix is specified), but that is of course incompatible with all other tools using/modifying the passwords.

Password Databases

Dovecot authenticates users against password databases. It can also be used to configure things like proxies.

You can use multiple databases, so if the password doesn't match in the first database, Dovecot checks the next one. This can be useful if you want to easily support having both virtual users and also local system users (see Authentication/MultipleDatabases).

Success/failure databases

These databases simply verify if the given password is correct for the user. Dovecot doesn't get the correct password from the database, it only gets a "success" or a "failure" reply. This means that these databases can't be used with non-plaintext authentication mechanisms.

Databases that belong to this category are:

  • PAM: Pluggable Authentication Modules.

  • BSDAuth: BSD authentication.

  • CheckPassword: External checkpassword program.

Lookup databases

Dovecot does a lookup based on the username and possibly other information (e.g. IP address) and verifies the password validity itself. Fields that the lookup can return:

  • password: User's password.

    • password_noscheme: Like "password", but if a password begins with "{", assume it belongs to the password itself instead of treating it as a scheme prefix. This is usually needed only if you use plaintext passwords. v1.0.8+ only.

  • user: Returning a user field can be used to change the username. Typically used only for case changes (e.g. "UseR" -> "user").

    • username: Like user, but doesn't drop existing domain name (e.g. "username=foo" for "user@domain" gives "foo@domain"). v1.1+ only.
    • domain: Updates the domain part of the username. v1.1+ only.
  • Other special extra fields.

Databases that support looking up only passwords, but no user or extra fields:

  • Passwd: System users (NSS, /etc/passwd, or similiar).

  • Shadow: Shadow passwords for system users (NSS, /etc/shadow or similiar).

    • Dovecot supports reading all password schemes from passwd and shadow databases (if prefix is specified), but that is of course incompatible with all other tools using/modifying the passwords.

  • VPopMail: External software used to handle virtual domains.

Databases that support looking up everything:

  • Passwd-file: /etc/passwd-like file in specified location.

  • LDAP: Lightweight Directory Access Protocol.

  • SQL: SQL database (PostgreSQL, MySQL, SQLite).

None: PasswordDatabase (last edited 2010-04-14 00:47:30 by unknown)