Ubuntu Manpage: sssd-ipa - SSSD IPA provider

name
description
configuration options
subdomains provider
failover
service discovery
example
see also
authors

Provided by: sssd-ipa_1.13.4-1ubuntu1.15_amd64

NAME

       sssd-ipa - SSSD IPA provider

DESCRIPTION

       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 with some exceptions described below.

       However, it is neither necessary nor recommended to set these options. IPA provider can also be used as
       an access and chpass provider. As an access provider it uses HBAC (host-based access control) rules.
       Please refer to freeipa.org for more information about HBAC. No configuration of access provider is
       required on the client side.

       The IPA provider will use the PAC responder if the Kerberos tickets of users from trusted realms contain
       a PAC. To make configuration easier the PAC responder is started automatically if the IPA ID provider is
       configured.

CONFIGURATION OPTIONS

Refer to the section “DOMAIN SECTIONS” of the sssd.conf(5) manual page for details on the configuration
of an SSSD domain.

ipa_domain (string)
Specifies the name of the IPA domain. This is optional. If not provided, the configuration domain
name is used.

ipa_server, ipa_backup_server (string)
The comma-separated 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. For more information on service
discovery, refer to the “SERVICE DISCOVERY” section.

ipa_hostname (string)
Optional. May be set on machines where the hostname(5) does not reflect the fully qualified name used
in the IPA domain to identify this host.

dyndns_update (boolean)
Optional. This option tells SSSD to automatically update the DNS server built into FreeIPA v2 with
the IP address of this client. The update is secured using GSS-TSIG. The IP address of the IPA LDAP
connection is used for the updates, if it is not otherwise specified by using the “dyndns_iface”
option.

NOTE: On older systems (such as RHEL 5), for this behavior to work reliably, the default Kerberos
realm must be set properly in /etc/krb5.conf

NOTE: While it is still possible to use the old ipa_dyndns_update option, users should migrate to
using dyndns_update in their config file.

Default: false

dyndns_ttl (integer)
The TTL to apply to the client DNS record when updating it. If dyndns_update is false this has no
effect. This will override the TTL serverside if set by an administrator.

NOTE: While it is still possible to use the old ipa_dyndns_ttl option, users should migrate to using
dyndns_ttl in their config file.

Default: 1200 (seconds)

dyndns_iface (string)
Optional. Applicable only when dyndns_update is true. Choose the interface or a list of interfaces
whose IP addresses should be used for dynamic DNS updates. Special value “*” implies that IPs from
all interfaces should be used.

NOTE: While it is still possible to use the old ipa_dyndns_iface option, users should migrate to
using dyndns_iface in their config file.

Default: Use the IP addresses of the interface which is used for IPA LDAP connection

Example: dyndns_iface = em1, vnet1, vnet2

ipa_enable_dns_sites (boolean)
Enables DNS sites - location based service discovery.

If true and service discovery (see Service Discovery paragraph at the bottom of the man page) is
enabled, then the SSSD will first attempt location based discovery using a query that contains
"_location.hostname.example.com" and then fall back to traditional SRV discovery. If the location
based discovery succeeds, the IPA servers located with the location based discovery are treated as
primary servers and the IPA servers located using the traditional SRV discovery are used as back up
servers

Default: false

dyndns_refresh_interval (integer)
How often should the back end perform periodic DNS update in addition to the automatic update
performed when the back end goes online. This option is optional and applicable only when
dyndns_update is true.

Default: 0 (disabled)

dyndns_update_ptr (bool)
Whether the PTR record should also be explicitly updated when updating the client's DNS records.
Applicable only when dyndns_update is true.

This option should be False in most IPA deployments as the IPA server generates the PTR records
automatically when forward records are changed.

Default: False (disabled)

dyndns_force_tcp (bool)
Whether the nsupdate utility should default to using TCP for communicating with the DNS server.

Default: False (let nsupdate choose the protocol)

dyndns_server (string)
The DNS server to use when performing a DNS update. In most setups, it's recommended to leave this
option unset.

Setting this option makes sense for environments where the DNS server is different from the identity
server.

Please note that this option will be only used in fallback attempt when previous attempt using
autodetected settings failed.

Default: None (let nsupdate choose the server)

ipa_hbac_search_base (string)
Optional. Use the given string as search base for HBAC related objects.

Default: Use base DN

ipa_host_search_base (string)
Optional. Use the given string as search base for host objects.