Provided by: sssd_1.0.5-0ubuntu1_i386
sssd-ipa - the configuration file for SSSD
This manual page describes the configuration of the IPA provider for
sssd(8). For a detailed syntax reference, refer to the “FILE FORMAT”
section of the sssd.conf(5) manual page.
The IPA provider is a back end used to connect to an IPA server. (Refer
to the freeipa.org web site for information about IPA servers.) This
provider requires that the machine be joined to the IPA domain;
configuration is almost entirely self-discovered and obtained directly
from the server.
The IPA provider accepts the same options used by the sssd-ldap(5)
identity provider and the sssd-krb5(5) authentication provider.
However, it is neither necessary nor recommended to set these options.
Refer to the section “DOMAIN SECTIONS” of the sssd.conf(5) manual page
for details on the configuration of an SSSD domain.
Specifies the name of the IPA domain. This is optional. If not
provided, the configuration domain name is used.
The list of IP addresses or hostnames of the IPA servers to which
SSSD should connect in the order of preference. For more
information on failover and server redundancy, see the “FAILOVER”
section. This is optional if autodiscovery is enabled.
Optional. May be set on machines where the hostname(5) does not
reflect the fully qualified name used in the IPA domain to identify
Verify with the help of krb5_keytab that the TGT obtained has not
Note that this default differs from the traditional Kerberos
provider back end.
The failover feature allows back ends to automatically switch to a
different server if the primary server fails.
The list of servers is given as a comma-separated list; any number of
spaces is allowed around the comma. The servers are listed in order of
preference. The list can contain any number of servers.
The Failover Mechanism
The failover mechanism distinguishes between a machine and a service.
The back end first tries to resolve the hostname of a given machine; if
this resolution attempt fails, the machine is considered offline. No
further attempts are made to connect to this machine for any other
service. If the resolution attempt succeeds, the back end tries to
connect to a service on this machine. If the service connection attempt
fails, then only this particular service is considered offline and the
back end automatically switches over to the next service. The machine
is still considered online and might still be tried for another
Further connection attempts are made to machines or services marked as
offline after a specified period of time; this is currently hard coded
to 30 seconds.
If there are no more machines to try, the back end as a whole switches
to offline mode, and then attempts to reconnect every 30 seconds.
The following example assumes that SSSD is correctly configured and
example.com is one of the domains in the [sssd] section. This examples
shows only the ipa provider-specific options.
id_provider = ipa
ipa_server = ipaserver.example.com
ipa_hostname = myhost.example.com
sssd.conf(5), sssd-ldap(5), sssd-krb5(5), sssd(8)
The SSSD upstream - http://fedorahosted.org/sssd