is a daemon process that handles plaintext authentication requests
on behalf of the SASL library.
The server fulfills two roles: it isolates all code requiring superuser
privileges into a single process, and it can be used to provide
authentication services to clients that do not understand
SASL based authentication.
started from the system boot scripts when going to
multi-user mode. When running against a protected authentication
database (e.g. the
it must be run as the superuser.
Options named by lower-case letters configure the server itself.
Upper-case options control the behavior of specific authentication
mechanisms; their applicability to a particular authentication
mechanism is described in the
Sx AUTHENTICATION MECHANISMS
as the authentication mechanism. (See the
Sx AUTHENTICATION MECHANISMS
section below.) This parameter is mandatory.
A mechanism specific option (e.g. rimap hostname or config file path)
The remote host to be contacted by the
authentication mechanism. (Depricated, use -O instead)
as the pathname to the named socket to listen on for
connection requests. This must be an absolute pathname, and MUST NOT
include the trailing "/mux". Note that the default for this value
is "/var/state/saslauthd" (or what was specified at compile time)
and that this directory must exist for saslauthd to function.
processes for responding to authentication queries. (default: 5) A
value of zero will indicate that saslauthd should fork an individual
process for each connection. This can solve leaks that occur in some
as the table size of the hash table (in kilobytes)
as the expiration time of the authentication cache (in seconds)
Honour time-of-day login restrictions.
Show usage information
Enable cacheing of authentication credentials
Disable the use of a lock file for controlling access to accept().
Combine the realm with the login (with an '@' sign in between). e.g.
login: "foo" realm: "bar" will get passed as login: "foo@bar". Note that
the realm will still be passed, which may lead to unexpected behavior.
Print the version number and available authentication
mechanisms on standard error, then exit.
logs it's activities via
supports one or more
Qq authentication mechanisms ,
dependent upon the facilities provided by the underlying operating system.
The mechanism is selected by the
flag from the following list of choices:
Authenticate using the DCE authentication environment.
Authenticate using the
library function. Typically this authenticates against the
local password file. See your systems
man page for details.
Authenticate against the local Kerberos 4 realm. (See the
section for caveats about this driver.)
Authenticate against the local Kerberos 5 realm.
Authenticate using Pluggable Authentication Modules (PAM).
Forward authentication requests to a remote IMAP server. This driver
connects to a remote IMAP server, specified using the -O flag,
and attempts to login (via an IMAP
command) using the credentials
supplied to the local
server. If the remote authentication succeeds the local connection
is also considered to be authenticated. The remote connection is closed
as soon as the tagged response from the
command is received from the remote
parameter to the
flag describes the remote server to forward
authentication requests to.
can be a hostname (imap.example.com) or a dotted-quad IP address
(192.168.0.1). The latter is useful if the remote server is
multi-homed and has network interfaces that are unreachable from
the local IMAP server. The remote host is contacted on the
service port. A non-default port can be specified by appending
a slash and the port name or number
flag and argument are mandatory when using the
(AIX, Irix, Linux, Solaris)
Authenticate against the local
Qq shadow password file .
The exact mechanism is system dependent.
currently understands the
library routines. Some systems
Authenticate against the
SASL authentication database. Note that this is probabally not what you
want to be using, and is even disabled at compile-time by default.
If you want to use sasldb with the SASL library, you probably want to
use the pwcheck_method of "auxprop" along with the sasldb auxprop plugin
(All platforms that support OpenLDAP 2.0 or higher)
Authenticate against an ldap server. The ldap configuration parameters are
read from /etc/saslauthd.conf. The location of this file can be
changed with the -O parameter. See the LDAP_SASLAUTHD file included with the
distribution for the list of available parameters.
Authenticate using the Digital
Security Integration Architecture
Qq enhanced security ) .
authentication driver consumes considerable resources. To perform an
authentication it must obtain a ticket granting ticket
from the TGT server
on every authentication request.
The Kerberos library routines that obtain the TGT also create a
local ticket file, on the reasonable assumption that you will want
to save the TGT for use by other Kerberos applications. These ticket
files are unusable by
however there is no way not to create them. The overhead of creating
these ticket files can cause serious performance degradation on busy
was never intended to be used in this manner, anyway.)