sssd - en to unknown language translation catalogue (254 entries)

en: 3. Authentication does not work and syslog contains "No Kerberos credentials available": You don't have any credentials that can be used to obtain the required service ticket. Use kinit or authenticate over SSSD to acquire those credentials.
target: 3. Authentication does not work and syslog contains "No Kerberos credentials available": You don't have any credentials that can be used to obtain the required service ticket. Use kinit, or authenticate over SSSD to acquire those credentials.

en: 4. Authentication does not work and SSSD sssd-pam log contains "User with UPN [$UPN] was not found." or "UPN [$UPN] does not match target user [$username].": You are using credentials that can not be mapped to the user that is being authenticated. Try to use kswitch to select different principal, make sure you authenticated with SSSD or consider disabling <option>pam_gssapi_check_upn</option>.
target: 4. Authentication does not work and SSSD sssd-pam log contains "User with UPN [$UPN] was not found." or "UPN [$UPN] does not match target user [$username].": You are using credentials that can not be mapped to the user that is being authenticated. Try to use kswitch to select a different principal, make sure you authenticated with SSSD or consider disabling <option>pam_gssapi_check_upn</option>.

en: <command>sss_override</command> enables to create a client-side view and allows to change selected values of specific user and groups. This change takes effect only on local machine.
target: <command>sss_override</command> enables to create a client-side view and allows to change selected values of specific users and groups. This change takes effect only on local machine.

en: <emphasis>NOTE:</emphasis> In order to have this feature working as expected SSSD must be running as "root" and not as the unprivileged user.
target: <emphasis>NOTE:</emphasis> In order to have this feature working as expected, SSSD must be running as "root" and not as an unprivileged user.

en: <emphasis>ad</emphasis>: use the value of the 32bit field ldap_user_ad_user_account_control and allow access if the second bit is not set. If the attribute is missing access is granted. Also the expiration time of the account is checked.
target: <emphasis>ad</emphasis>: use the value of the 32bit field ldap_user_ad_user_account_control and allow access if the second bit is not set. If the attribute is missing, access is granted. Also the expiration time of the account is checked.

en: <filename>sssd.conf</filename> must be a regular file, owned by root and only root may read from or write to the file.
target: <filename>sssd.conf</filename> must be a regular file, owned by root and only root may read from, or write to, the file.

en: <placeholder type="programlisting" id="0"/> <phrase condition="have_systemd"> It's important to note that on platforms where systemd is supported there's no need to add the "sudo" provider to the list of services, as it became optional. However, sssd-sudo.socket must be enabled instead.  </phrase>
target: <placeholder type="programlisting" id="0"/> <phrase condition="have_systemd"> It's important to note that on platforms where systemd is supported, there's no need to add the "sudo" provider to the list of services, as it became optional. However, sssd-sudo.socket must be enabled instead.  </phrase>

en: <quote>joe</quote> and <quote>dick</quote> are UNIX user names and <quote>juser</quote> and <quote>richard</quote> are primaries of kerberos principals. For user <quote>joe</quote> resp.  <quote>dick</quote> SSSD will try to kinit as <quote>juser@REALM</quote> resp.  <quote>richard@REALM</quote>.
target: <quote>joe</quote> and <quote>dick</quote> are UNIX usernames and <quote>juser</quote> and <quote>richard</quote> are primaries of kerberos principals. For user <quote>joe</quote> resp.  <quote>dick</quote> SSSD will try to kinit as <quote>juser@REALM</quote> resp.  <quote>richard@REALM</quote>.

en: A <citerefentry> <refentrytitle>printf</refentrytitle> <manvolnum>3</manvolnum> </citerefentry>-compatible format that describes how to compose a fully qualified name from user name and domain name components.
target: A <citerefentry> <refentrytitle>printf</refentrytitle> <manvolnum>3</manvolnum> </citerefentry>-compatible format that describes how to compose a fully qualified name from username and domain name components.

en: A comma separated list of strings which allows to remove (filter) data sent by the PAM responder to pam_sss PAM module. There are different kind of responses sent to pam_sss e.g. messages displayed to the user or environment variables which should be set by pam_sss.
target: A comma-separated list of strings which allows to remove (filter) data sent by the PAM responder to pam_sss PAM module. There are different kind of responses sent to pam_sss e.g. messages displayed to the user or environment variables which should be set by pam_sss.

en: A comma-separated list of users which should have session recording enabled. Matches user names as returned by NSS. I.e. after the possible space replacement, case changes, etc.
target: A comma-separated list of users which should have session recording enabled. Matches usernames as returned by NSS. I.e. after the possible space replacement, case changes, etc.

en: A mapping and matching rule can be added to the SSSD configuration in a section on its own with a name like <quote>[certmap/<replaceable>DOMAIN_NAME</replaceable>/<replaceable>RULE_NAME</replaceable>]</quote>.  In this section the following options are allowed:
target: A mapping and matching rule can be added to the SSSD configuration in a section on its own with a name like <quote>[certmap/<replaceable>DOMAIN_NAME</replaceable>/<replaceable>RULE_NAME</replaceable>]</quote>.  In this section, the following options are allowed:

en: A possible work-around for long running processes which are looking up users and groups only at startup or very rarely is to run them with the environment variable SSS_NSS_USE_MEMCACHE set to "NO" so that they won't use the memory cache at all and not map the memory cache file into the memory. In general a better solution is to tune the cache timeout parameters so that they meet the local expectations and calling <command>sss_cache</command> is not needed.
target: A possible work-around for long running processes which are looking up users and groups only at startup or very rarely is to run them with the environment variable SSS_NSS_USE_MEMCACHE set to "NO" so that they won't use the memory cache at all and not map the memory cache file into the memory. In general, a better solution is to tune the cache timeout parameters so that they meet the local expectations and calling <command>sss_cache</command> is not needed.

en: A special case is long running processes which are doing user or group lookups only at startup, e.g. to determine the name of the user the process is running as. For those lookups the memory cache file is mapped into the memory of the process. But since there will be no further lookups this process would never detect if the memory cache file was invalidated and hence it will be kept in memory and will occupy disk space until the process stops. As a result calling <command>sss_cache</command> might increase the disk usage because old memory cache files cannot be removed from the disk because they are still mapped by long running processes.
target: A special case is long running processes which are doing user or group lookups only at startup, e.g. to determine the name of the user the process is running as. For those lookups, the memory cache file is mapped into the memory of the process. But since there will be no further lookups, this process would never detect if the memory cache file was invalidated and hence it will be kept in memory and will occupy disk space until the process stops. As a result, calling <command>sss_cache</command> might increase the disk usage because old memory cache files cannot be removed from the disk because they are still mapped by long running processes.

en: Add microseconds to the timestamp in debug messages.  If journald is enabled for SSSD debug logging this option is ignored.
target: Add microseconds to the timestamp in debug messages.  If journald is enabled for SSSD debug logging, this option is ignored.

en: All configuration that is needed on SSSD side is to extend the list of <emphasis>services</emphasis> with "sudo" in [sssd] section of <citerefentry> <refentrytitle>sssd.conf</refentrytitle> <manvolnum>5</manvolnum> </citerefentry>. To speed up the LDAP lookups, you can also set search base for sudo rules using <emphasis>ldap_sudo_search_base</emphasis> option.
target: The only configuration that is needed on the SSSD side is to extend the list of <emphasis>services</emphasis> with "sudo" in [sssd] section of <citerefentry> <refentrytitle>sssd.conf</refentrytitle> <manvolnum>5</manvolnum> </citerefentry>. To speed up the LDAP lookups, you can also set search base for sudo rules using <emphasis>ldap_sudo_search_base</emphasis> option.

en: Always prompt the user for credentials. With this option credentials requested by other PAM modules, typically a password, will be ignored and pam_sss will prompt for credentials again. Based on the pre-auth reply by SSSD pam_sss might prompt for a password, a Smartcard PIN or other credentials.
target: Always prompt the user for credentials. With this option, credentials requested by other PAM modules, typically a password, will be ignored and pam_sss will prompt for credentials again. Based on the pre-auth reply by SSSD, pam_sss might prompt for a password, a Smartcard PIN or other credentials.

en: Before performing access control SSSD applies group policy security filtering on the GPOs. For every single user login, the applicability of the GPOs that are linked to the host is checked. In order for a GPO to apply to a user, the user or at least one of the groups to which it belongs must have following permissions on the GPO:
target: Before performing access control, SSSD applies group policy security filtering on the GPOs. For every single user login, the applicability of the GPOs that are linked to the host is checked. In order for a GPO to apply to a user, the user, or at least one of the groups to which it belongs, must have the following permissions on the GPO:

en: By default the ssh responder will use all available certificate matching rules to filter the certificates so that ssh keys are only derived from the matching ones. With this option the used rules can be restricted with a comma separated list of mapping and matching rule names. All other rules will be ignored.
target: By default, the ssh responder will use all available certificate matching rules to filter the certificates, so that ssh keys are only derived from the matching ones. With this option, the used rules can be restricted with a comma-separated list of mapping and matching rule names. All other rules will be ignored.

en: By default, the AD provider will map UID and GID values from the objectSID parameter in Active Directory. For details on this, see the <quote>ID MAPPING</quote> section below. If you want to disable ID mapping and instead rely on POSIX attributes defined in Active Directory, you should set <placeholder type="programlisting" id="0"/> If POSIX attributes should be used, it is recommended for performance reasons that the attributes are also replicated to the Global Catalog. If POSIX attributes are replicated, SSSD will attempt to locate the domain of a requested numerical ID with the help of the Global Catalog and only search that domain. In contrast, if POSIX attributes are not replicated to the Global Catalog, SSSD must search all the domains in the forest sequentially. Please note that the <quote>cache_first</quote> option might be also helpful in speeding up domainless searches.  Note that if only a subset of POSIX attributes is present in the Global Catalog, the non-replicated attributes are currently not read from the LDAP port.
target: By default, the AD provider will map UID and GID values from the objectSID parameter in Active Directory. For details on this, see the <quote>ID MAPPING</quote> section below. If you want to disable ID mapping and instead rely on POSIX attributes defined in Active Directory, you should set <placeholder type="programlisting" id="0"/> If POSIX attributes should be used, it is recommended for performance reasons that the attributes are also replicated to the Global Catalogue. If POSIX attributes are replicated, SSSD will attempt to locate the domain of a requested numerical ID with the help of the Global Catalogue and only search that domain. In contrast, if POSIX attributes are not replicated to the Global Catalogue, SSSD must search all the domains in the forest sequentially. Please note that the <quote>cache_first</quote> option might be also helpful in speeding up domainless searches.  Note that if only a subset of POSIX attributes is present in the Global Catalogue, the non-replicated attributes are currently not read from the LDAP port.

en: By default, the SSSD connects to the Global Catalog first to retrieve users from trusted domains and uses the LDAP port to retrieve group memberships or as a fallback. Disabling this option makes the SSSD only connect to the LDAP port of the current AD server.
target: By default, the SSSD connects to the Global Catalogue first to retrieve users from trusted domains and uses the LDAP port to retrieve group memberships or as a fallback. Disabling this option makes the SSSD only connect to the LDAP port of the current AD server.

en: Certain option defaults do not match their respective backend provider defaults, these option names and IPA provider-specific defaults are listed below:
target: Certain option defaults do not match their respective backend provider defaults. These option names and IPA provider-specific defaults are listed below:

en: Changes the behavior of the ID-mapping algorithm to behave more similarly to winbind's <quote>idmap_autorid</quote> algorithm.
target: Changes the behaviour of the ID-mapping algorithm to behave more similarly to winbind's <quote>idmap_autorid</quote> algorithm.

en: Comma separated list of PAM services that are allowed to try GSSAPI authentication using pam_sss_gss.so module.
target: Comma-separated list of PAM services that are allowed to try GSSAPI authentication using pam_sss_gss.so module.

en: Comma separated list of access control options.  Allowed values are:
target: Comma-separated list of access control options.  Allowed values are:

en: Comma separated list of authentication indicators required to be present in a Kerberos ticket to access a PAM service that is allowed to try GSSAPI authentication using pam_sss_gss.so module.
target: Comma-separated list of authentication indicators required to be present in a Kerberos ticket to access a PAM service that is allowed to try GSSAPI authentication using pam_sss_gss.so module.

en: Comma separated list of domain names the rule should be applied. By default a rule is only valid in the domain configured in sssd.conf. If the provider supports subdomains this option can be used to add the rule to subdomains as well.
target: Comma-separated list of domain names the rule should be applied. By default, a rule is only valid in the domain configured in sssd.conf. If the provider supports subdomains, this option can be used to add the rule to subdomains as well.

en: Comma separated list of domains and subdomains representing the lookup order that will be followed.  The list doesn't have to include all possible domains as the missing domains will be looked up based on the order they're presented in the <quote>domains</quote> configuration option.  The subdomains which are not listed as part of <quote>lookup_order</quote> will be looked up in a random order for each parent domain.
target: Comma-separated list of domains and subdomains representing the lookup order that will be followed.  The list doesn't have to include all possible domains as the missing domains will be looked up based on the order they're presented in the <quote>domains</quote> configuration option.  The subdomains which are not listed as part of <quote>lookup_order</quote> will be looked up in a random order for each parent domain.

en: Comma separated list of groups that are allowed to log in. This applies only to groups within this SSSD domain. Local groups are not evaluated.
target: Comma-separated list of groups that are allowed to log in. This applies only to groups within this SSSD domain. Local groups are not evaluated.

en: Comma separated list of groups that are explicitly denied access. This applies only to groups within this SSSD domain. Local groups are not evaluated.
target: Comma-separated list of groups that are explicitly denied access. This applies only to groups within this SSSD domain. Local groups are not evaluated.

en: Comma separated list of services that are started when sssd itself starts.  <phrase condition="have_systemd"> The services' list is optional on platforms where systemd is supported, as they will either be socket or D-Bus activated when needed.  </phrase>
target: Comma-separated list of services that are started when sssd itself starts.  <phrase condition="have_systemd"> The services' list is optional on platforms where systemd is supported, as they will either be socket or D-Bus activated when needed.  </phrase>

en: Comma separated list of users who are allowed to log in.
target: Comma-separated list of users who are allowed to log in.

en: Comma separated list of users who are explicitly denied access.
target: Comma-separated list of users who are explicitly denied access.

en: Configuring sudo with the SSSD back end
target: Configuring sudo with the SSSD backend

en: Currently SSSD basically only supports LDAP to lookup user information (the exception is the proxy provider which is not of relevance here). Because of this the mapping rule is based on LDAP search filter syntax with templates to add certificate content to the filter. It is expected that the filter will only contain the specific data needed for the mapping and that the caller will embed it in another filter to do the actual search. Because of this the filter string should start and stop with '(' and ')' respectively.
target: Currently SSSD basically only supports LDAP to lookup user information (the exception is the proxy provider which is not of relevance here). Because of this, the mapping rule is based on LDAP search filter syntax with templates to add certificate content to the filter. It is expected that the filter will only contain the specific data needed for the mapping and that the caller will embed it in another filter to do the actual search. Because of this, the filter string should start and stop with '(' and ')' respectively.

en: Currently supported debug levels:
target: Currently-supported debug levels:

en: Default regular expression that describes how to parse the string containing user name and domain into these components.
target: Default regular expression that describes how to parse the string containing username and domain into these components.

en: Default: true on platforms where inotify is supported. False on other platforms.
target: Default: True on platforms where inotify is supported. False on other platforms.

en: Different configuration options are tunable for a trusted domain depending on whether you are configuring SSSD on an IPA server or an IPA client.
target: Different configuration options are tunable for a trusted domain, depending on whether you are configuring SSSD on an IPA server or an IPA client.

en: Directory to store credential caches. All the substitution sequences of krb5_ccname_template can be used here, too, except %d and %P.  The directory is created as private and owned by the user, with permissions set to 0700.
target: Directory in which to store credential caches. All the substitution sequences of krb5_ccname_template can be used here, too, except %d and %P.  The directory is created as private and owned by the user, with permissions set to 0700.

en: Do a binary match with the base64 encoded blob against all otherName SAN components. With this option it is possible to match against custom otherName components with special encodings which could not be treated as strings.
target: Do a binary match with the base64 encoded blob against all otherName SAN components. With this option, it is possible to match against custom otherName components with special encodings which could not be treated as strings.

en: Do certificate based authentication, i.e.  authentication with a Smartcard or similar devices. If a Smartcard is not available the user will be prompted to insert one. SSSD will wait for a Smartcard until the timeout defined by p11_wait_for_card_timeout passed, please see <citerefentry><refentrytitle>sssd.conf</refentrytitle> <manvolnum>5</manvolnum></citerefentry> for details.
target: Do certificate based authentication, i.e.  authentication with a Smartcard or similar devices. If a Smartcard is not available, the user will be prompted to insert one. SSSD will wait for a Smartcard until the timeout defined by p11_wait_for_card_timeout passed, please see <citerefentry><refentrytitle>sssd.conf</refentrytitle> <manvolnum>5</manvolnum></citerefentry> for details.

en: Enable certificate based Smartcard authentication.  Since this requires additional communication with the Smartcard which will delay the authentication process this option is disabled by default.
target: Enable certificate based Smartcard authentication.  Since this requires additional communication with the Smartcard which will delay the authentication process, this option is disabled by default.

en: Failover time outs and tuning
target: Failover timeouts and tuning

en: Following authentication indicators are supported by IPA Kerberos deployments:
target: The following authentication indicators are supported by IPA Kerberos deployments:

en: Following options are usable in more than one configuration sections.
target: The following options are usable in more than one configuration section.

en: For each failover-enabled config option, two variants exist: <emphasis>primary</emphasis> and <emphasis>backup</emphasis>.  The idea is that servers in the primary list are preferred and backup servers are only searched if no primary servers can be reached. If a backup server is selected, a timeout of 31 seconds is set. After this timeout SSSD will periodically try to reconnect to one of the primary servers. If it succeeds, it will replace the current active (backup) server.
target: For each failover-enabled config option, two variants exist: <emphasis>primary</emphasis> and <emphasis>backup</emphasis>.  The idea is that servers in the primary list are preferred and backup servers are only searched if no primary servers can be reached. If a backup server is selected, a timeout of 31 seconds is set. After this timeout, SSSD will periodically try to reconnect to one of the primary servers. If it succeeds, it will replace the current active (backup) server.

en: For example <emphasis>10:0</emphasis> means that up to 10 primary servers will be handed to <citerefentry> <refentrytitle>sssd_krb5_locator_plugin</refentrytitle> <manvolnum>8</manvolnum> </citerefentry> but no backup servers.
target: For example, <emphasis>10:0</emphasis> means that up to 10 primary servers will be handed to <citerefentry> <refentrytitle>sssd_krb5_locator_plugin</refentrytitle> <manvolnum>8</manvolnum> </citerefentry> but no backup servers.

en: For more details about the options see <citerefentry><refentrytitle>sssd.conf</refentrytitle> <manvolnum>5</manvolnum></citerefentry>.
target: For more details about the options, see <citerefentry><refentrytitle>sssd.conf</refentrytitle> <manvolnum>5</manvolnum></citerefentry>.

en: For more details about these options see their individual description in the manual page.
target: For more details about these options, see their individual description in the manual page.

en: For the matching the subject name stored in the certificate in DER encoded ASN.1 is converted into a string according to RFC 4514. This means the most specific name component comes first. Please note that not all possible attribute names are covered by RFC 4514. The names included are 'CN', 'L', 'ST', 'O', 'OU', 'C', 'STREET', 'DC' and 'UID'. Other attribute names might be shown differently on different platform and by different tools. To avoid confusion those attribute names are best not used or covered by a suitable regular-expression.
target: For the matching, the subject name stored in the certificate in DER encoded ASN.1 is converted into a string according to RFC 4514. This means the most specific name component comes first. Please note that not all possible attribute names are covered by RFC 4514. The names included are 'CN', 'L', 'ST', 'O', 'OU', 'C', 'STREET', 'DC' and 'UID'. Other attribute names might be shown differently on different platform and by different tools. To avoid confusion, those attribute names are best not used or covered by a suitable regular-expression.

en: Further, enabling enumeration may increase the time necessary to detect network disconnection, as longer timeouts are required to ensure that enumeration lookups are completed successfully.  For more information, refer to the man pages for the specific id_provider in use.
target: Furthermore, enabling enumeration may increase the time necessary to detect network disconnection, as longer timeouts are required to ensure that enumeration lookups are completed successfully.  For more information, refer to the man pages for the specific id_provider in use.

en: How big can a credential cache be per ccache. Each service ticket accounts into this quota.
target: How big a credential cache can be per ccache. Each service ticket accounts into this quota.

en: How long would SSSD try to resolve a failover service. This service resolution internally might include several steps, such as resolving DNS SRV queries or locating the site.
target: How long SSSD should try to resolve a failover service. This service resolution internally might include several steps, such as resolving DNS SRV queries or locating the site.

en: How many credential caches does the KCM database allow for all users.
target: How many credential caches the KCM database allows for all users.

en: How many credential caches does the KCM database allow per UID. This is equivalent to <quote>with how many principals you can kinit</quote>.
target: How many credential caches the KCM database allows per UID. This is equivalent to <quote>with how many principals you can kinit</quote>.

en: How many seconds should nss_sss cache enumerations (requests for info about all users)
target: How many seconds nss_sss shouldcache enumerations for (requests for info about all users)

en: How many seconds should nss_sss consider entries valid before asking the backend again
target: How many seconds nss_sss should consider entries valid for before asking the backend again

en: How many seconds should nss_sss consider group entries valid before asking the backend again
target: How many seconds nss_sss should consider group entries valid for before asking the backend again

en: How many seconds should nss_sss consider netgroup entries valid before asking the backend again
target: How many seconds nss_sss should consider netgroup entries valid for before asking the backend again

en: How many seconds should nss_sss consider service entries valid before asking the backend again
target: How many seconds nss_sss should consider service entries valid for before asking the backend again

en: How many seconds should nss_sss consider user entries valid before asking the backend again
target: How many seconds nss_sss should consider user entries valid for before asking the backend again

en: How many seconds should sudo consider rules valid before asking the backend again
target: How many seconds sudo should consider rules valid for before asking the backend again

en: How many seconds should the autofs service consider automounter maps valid before asking the backend again
target: How many seconds the autofs service should consider automounter maps valid for before asking the backend again

en: How many seconds to keep a host ssh key after refresh. IE how long to cache the host key for.
target: How many seconds to keep a host ssh key after refresh i.e. how long to cache the host key for.

en: How many seconds will pam_sss wait for p11_child to finish.
target: Number of seconds pam_sss will wait for p11_child to finish.

en: 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.
target: How often should the backend perform periodic DNS update in addition to the automatic update performed when the backend goes online.  This option is optional and applicable only when dyndns_update is true.

en: 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. Note that the lowest possible value is 60 seconds in-case if value is provided less than 60, parameter will assume lowest value only.
target: How often should the backend perform periodic DNS update in addition to the automatic update performed when the backend goes online.  This option is optional and applicable only when dyndns_update is true. Note that the lowest possible value is 60 seconds and any value provided less than 60 will default back to it.

en: If 2-Factor-Authentication (2FA) is used and credentials should be saved this value determines the minimal length the first authentication factor (long term password) must have to be saved as SHA512 hash into the cache.
target: If 2-Factor-Authentication (2FA) is used and credentials should be saved, this value determines the minimal length the first authentication factor (long term password) must have to be saved as SHA512 hash into the cache.

en: If <option>forward_pass</option> is set the entered password is put on the stack for other PAM modules to use.
target: If <option>forward_pass</option> is set, the entered password is put on the stack for other PAM modules to use.

en: If Smartcard authentication is required how many extra seconds in addition to p11_child_timeout should the PAM responder wait until a Smartcard is inserted.
target: If Smartcard authentication is required, how many extra seconds in addition to p11_child_timeout the PAM responder should wait until a Smartcard is inserted.

en: If True, SSSD will require that the Kerberos user principal that successfully authenticated through GSSAPI can be associated with the user who is being authenticated. Authentication will fail if the check fails.
target: If True, SSSD will require that the Kerberos user principal that successfully authenticated through GSSAPI be able to be associated with the user who is being authenticated. Authentication will fail if the check fails.

en: If a special file (<filename>/var/lib/sss/pubconf/pam_preauth_available</filename>)  exists SSSD's PAM module pam_sss will ask SSSD to figure out which authentication methods are available for the user trying to log in.  Based on the results pam_sss will prompt the user for appropriate credentials.
target: If a special file (<filename>/var/lib/sss/pubconf/pam_preauth_available</filename>)  exists, SSSD's PAM module pam_sss will ask SSSD to figure out which authentication methods are available for the user trying to log in.  Based on the results, pam_sss will prompt the user for appropriate credentials.

en: If enabled, SSSD will store only rules that can be applied to this machine. This means rules that contain one of the following values in <emphasis>sudoHost</emphasis> attribute:
target: If enabled, SSSD will store only rules that can be applied to this machine. This refers to rules that contain one of the following values in <emphasis>sudoHost</emphasis> attribute:

en: If multiple rules have the same priority and only one of the related matching rules applies, this rule will be chosen. If there are multiple rules with the same priority which matches, one is chosen but which one is undefined. To avoid this undefined behavior either use different priorities or make the matching rules more specific e.g. by using distinct &lt;ISSUER&gt; patterns.
target: If multiple rules have the same priority and only one of the related matching rules applies, this rule will be chosen. If there are multiple rules with the same priority which matches, one is chosen but which one is undefined. To avoid this undefined behaviour, either use different priorities or make the matching rules more specific e.g. by using distinct &lt;ISSUER&gt; patterns.

en: If no Smartcard is available after the timeout or certificate based authentication is not allowed for the current service PAM_AUTHINFO_UNAVAIL is returned.
target: If no Smartcard is available after the timeout or certificate based authentication is not allowed for the current service, PAM_AUTHINFO_UNAVAIL is returned.

en: If no Smartcard is available or certificate based authentication is not allowed for the current service PAM_AUTHINFO_UNAVAIL is returned.
target: If no Smartcard is available or certificate based authentication is not allowed for the current service, PAM_AUTHINFO_UNAVAIL is returned.

en: If no rules are configured using 'all_rules' will enable a default rule which enables all certificates suitable for client authentication.  This is the same behavior as for the PAM responder if certificate authentication is enabled.
target: If no rules are configured using 'all_rules' will enable a default rule which enables all certificates suitable for client authentication.  This is the same behaviour as for the PAM responder if certificate authentication is enabled.

en: If no servers are specified, the back end automatically uses service discovery to try to find a server. Optionally, the user may choose to use both fixed server addresses and service discovery by inserting a special keyword, <quote>_srv_</quote>, in the list of servers. The order of preference is maintained. This feature is useful if, for example, the user prefers to use service discovery whenever possible, and fall back to a specific server when no servers can be discovered using DNS.
target: If no servers are specified, the backend automatically uses service discovery to try to find a server. Optionally, the user may choose to use both fixed server addresses and service discovery by inserting a special keyword, <quote>_srv_</quote>, in the list of servers. The order of preference is maintained. This feature is useful if, for example, the user prefers to use service discovery whenever possible, and fall back to a specific server when no servers can be discovered using DNS.

en: If service discovery is used in the back end, specifies the domain part of the service discovery DNS query.
target: If service discovery is used in the backend, specifies the domain part of the service discovery DNS query.

en: If set to 0 the user cannot authenticate offline if offline_failed_login_attempts has been reached. Only a successful online authentication can enable offline authentication again.
target: If set to 0, the user cannot authenticate offline if offline_failed_login_attempts has been reached. Only a successful online authentication can enable offline authentication again.

en: If set to TRUE, the group membership attribute is not requested from the ldap server, and group members are not returned when processing group lookup calls, such as <citerefentry> <refentrytitle>getgrnam</refentrytitle> <manvolnum>3</manvolnum> </citerefentry> or <citerefentry> <refentrytitle>getgrgid</refentrytitle> <manvolnum>3</manvolnum> </citerefentry>.  As an effect, <quote>getent group $groupname</quote> would return the requested group as if it was empty.
target: If set to TRUE, the group membership attribute is not requested from the ldap server, and group members are not returned when processing group lookup calls, such as <citerefentry> <refentrytitle>getgrnam</refentrytitle> <manvolnum>3</manvolnum> </citerefentry> or <citerefentry> <refentrytitle>getgrgid</refentrytitle> <manvolnum>3</manvolnum> </citerefentry>.  As an effect, <quote>getent group $groupname</quote> would return the requested group as if it were empty.

en: If set to true the <command>sss_ssh_authorizedkeys</command> will return ssh keys derived from the public key of X.509 certificates stored in the user entry as well. See <citerefentry> <refentrytitle>sss_ssh_authorizedkeys</refentrytitle> <manvolnum>1</manvolnum> </citerefentry> for details.
target: If set to true, the <command>sss_ssh_authorizedkeys</command> will return ssh keys derived from the public key of X.509 certificates stored in the user entry as well. See <citerefentry> <refentrytitle>sss_ssh_authorizedkeys</refentrytitle> <manvolnum>1</manvolnum> </citerefentry> for details.

en: If set to true, the LDAP library would perform a reverse lookup to canonicalize the host name during a SASL bind.
target: If set to true, the LDAP library would perform a reverse lookup to canonicalise the host name during a SASL bind.

en: If specified the user is asked another N times for a password if authentication fails. Default is 0.
target: If specified, the user is asked another N times for a password if authentication fails. Default is 0.

en: If the backend supports sub-domains the value of ldap_sasl_mech is automatically inherited to the sub-domains. If a different value is needed for a sub-domain it can be overwritten by setting ldap_sasl_mech for this sub-domain explicitly.  Please see TRUSTED DOMAIN SECTION in <citerefentry><refentrytitle>sssd.conf</refentrytitle> <manvolnum>5</manvolnum></citerefentry> for details.
target: If the backend supports sub-domains, the value of ldap_sasl_mech is automatically inherited to the sub-domains. If a different value is needed for a sub-domain, it can be overwritten by setting ldap_sasl_mech for this sub-domain explicitly.  Please see TRUSTED DOMAIN SECTION in <citerefentry><refentrytitle>sssd.conf</refentrytitle> <manvolnum>5</manvolnum></citerefentry> for details.

en: If the domain list is not empty users mapped to a given certificate are not only searched in the local domain but in the listed domains as well as long as they are know by SSSD. Domains not know to SSSD will be ignored.
target: If the domain list is not empty, users mapped to a given certificate are not only searched in the local domain but in the listed domains as well, so long as they are known by SSSD. Domains not known to SSSD will be ignored.

en: If the environment variable SSSD_KRB5_LOCATOR_DEBUG is set to any value debug messages will be sent to stderr.
target: If the environment variable SSSD_KRB5_LOCATOR_DEBUG is set to any value, debug messages will be sent to stderr.

en: If the environment variable SSSD_KRB5_LOCATOR_DISABLE is set to any value the plugin is disabled and will just return KRB5_PLUGIN_NO_HANDLE to the caller.
target: If the environment variable SSSD_KRB5_LOCATOR_DISABLE is set to any value, the plugin is disabled and will just return KRB5_PLUGIN_NO_HANDLE to the caller.

en: If the environment variable SSSD_KRB5_LOCATOR_IGNORE_DNS_FAILURES is set to any value plugin will try to resolve all DNS names in kdcinfo file. By default plugin returns KRB5_PLUGIN_NO_HANDLE to the caller immediately on first DNS resolving failure.
target: If the environment variable SSSD_KRB5_LOCATOR_IGNORE_DNS_FAILURES is set to any value, the plugin will try to resolve all DNS names in kdcinfo file. By default, the plugin returns KRB5_PLUGIN_NO_HANDLE to the caller immediately on first DNS resolving failure.

en: If the environment variable SSS_LOCKFREE is set to "NO", requests from multiple threads of a single application will be serialized.
target: If the environment variable SSS_LOCKFREE is set to "NO", requests from multiple threads of a single application will be serialised.

en: If the files provider is configured to monitor other files it makes sense to set this option to 'False' to avoid inconsistent behavior because in general there would be no other NSS module which can be used as a fallback.
target: If the files provider is configured to monitor other files, it makes sense to set this option to 'False' to avoid inconsistent behaviour because in general there would be no other NSS module which could be used as a fallback.

en: 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.
target: If there are no more machines to try, the backend as a whole switches to offline mode, and then attempts to reconnect every 30 seconds.

en: 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
target: 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 backup servers

en: If true then SSSD will download every rule that contains a netgroup in sudoHost attribute.
target: If true, then SSSD will download every rule that contains a netgroup in sudoHost attribute.

en: If true then SSSD will download every rule that contains a wildcard in sudoHost attribute.
target: If true, then SSSD will download every rule that contains a wildcard in sudoHost attribute.

en: If using access_provider = ldap and ldap_access_order = filter (default), this option is mandatory. It specifies an LDAP search filter criteria that must be met for the user to be granted access on this host. If access_provider = ldap, ldap_access_order = filter and this option is not set, it will result in all users being denied access.  Use access_provider = permit to change this default behavior. Please note that this filter is applied on the LDAP user entry only and thus filtering based on nested groups may not work (e.g. memberOf attribute on AD entries points only to direct parents). If filtering based on nested groups is required, please see <citerefentry> <refentrytitle>sssd-simple</refentrytitle><manvolnum>5</manvolnum> </citerefentry>.
target: If using access_provider = ldap and ldap_access_order = filter (default), this option is mandatory. It specifies an LDAP search filter criteria that must be met for the user to be granted access on this host. If access_provider = ldap, ldap_access_order = filter and this option is not set, it will result in all users being denied access.  Use access_provider = permit to change this default behaviour. Please note that this filter is applied on the LDAP user entry only and thus filtering based on nested groups may not work (e.g. memberOf attribute on AD entries points only to direct parents). If filtering based on nested groups is required, please see <citerefentry> <refentrytitle>sssd-simple</refentrytitle><manvolnum>5</manvolnum> </citerefentry>.

en: In contrast to the SID based ID mapping which is used if ldap_id_mapping is set to true the allowed ID range for ldap_user_uid_number and ldap_group_gid_number is unbound. In a setup with sub/trusted-domains this might lead to ID collisions. To avoid collisions ldap_min_id and ldap_max_id can be set to restrict the allowed range for the IDs which are read directly from the server. Sub-domains can then pick other ranges to map IDs.
target: In contrast to the SID based ID mapping which is used if ldap_id_mapping is set to true, the allowed ID range for ldap_user_uid_number and ldap_group_gid_number is unbound. This might lead to ID collisions in a setup with sub/trusted-domains. To avoid collisions, ldap_min_id and ldap_max_id can be set to restrict the allowed range for the IDs which are read directly from the server. Sub-domains can then pick other ranges to map IDs.

en: In environments with read-only and read-write KDCs where clients are expected to use the read-only instances for the general operations and only the read-write KDC for config changes like password changes a <filename>kpasswdinfo.REALM</filename> is used as well to identify read-write KDCs. If this file exists for the given realm the content will be used by the plugin to reply to requests for a kpasswd or kadmin server or for the MIT Kerberos specific master KDC. If the address contains a port number the default KDC port 88 will be used for the latter.
target: In environments with read-only and read-write KDCs, where clients are expected to use the read-only instances for the general operations and only the read-write KDC for config changes like password changes, a <filename>kpasswdinfo.REALM</filename> is used as well to identify read-write KDCs. If this file exists for the given realm, the content will be used by the plugin to reply to requests for a kpasswd or kadmin server, or for the MIT Kerberos specific master KDC. If the address contains a port number, the default KDC port 88 will be used for the latter.

en: In general it is recommended to use attributes from the certificate and add them to special attributes to the LDAP user object. E.g. the 'altSecurityIdentities' attribute in AD or the 'ipaCertMapData' attribute for IPA can be used.
target: In general, it is recommended to use attributes from the certificate and add them to special attributes to the LDAP user object. E.g. the 'altSecurityIdentities' attribute in AD or the 'ipaCertMapData' attribute for IPA can be used.

en: In order to change the default of one of the configuration attributes of the <emphasis>sss</emphasis> plugin listed below you will need to create a config section for it, named <quote>[sss]</quote>.
target: In order to change the default of one of the configuration attributes of the <emphasis>sss</emphasis> plugin listed below, you will need to create a config section for it, named <quote>[sss]</quote>.

en: Internally the priority is treated as unsigned 32bit integer, using a priority value larger than 4294967295 will cause an error.
target: Internally, the priority is treated as unsigned 32bit integer, and using a priority value larger than 4294967295 will cause an error.

en: Invalidate all autofs maps. This option overrides invalidation of specific map if it was also set.
target: Invalidate all autofs maps. This option overrides invalidation of a specific map if it was also set.

en: Invalidate all cached sudo rules. This option overrides invalidation of specific sudo rule if it was also set.
target: Invalidate all cached sudo rules. This option overrides invalidation of a specific sudo rule if it was also set.

en: Invalidate all group records. This option overrides invalidation of specific group if it was also set.
target: Invalidate all group records. This option overrides invalidation of a specific group if it was also set.

en: Invalidate all netgroup records. This option overrides invalidation of specific netgroup if it was also set.
target: Invalidate all netgroup records. This option overrides invalidation of a specific netgroup if it was also set.

en: Invalidate all service records. This option overrides invalidation of specific service if it was also set.
target: Invalidate all service records. This option overrides invalidation of a specific service if it was also set.

en: Kerberos local authorization plugin
target: Kerberos local authorisation plugin

en: Lifetime of the PAC entry in seconds. As long as the PAC is valid the PAC data can be used to determine the group memberships of a user.
target: Lifetime of the PAC entry, in seconds. As long as the PAC is valid, the PAC data can be used to determine the group memberships of a user.

en: Maximal number of secondary slices that is tried when performing mapping from UNIX id to SID.
target: Maximum number of secondary slices to try when performing mapping from UNIX id to SID.

en: Maximum number of expired rules that can be refreshed at once. If number of expired rules is below threshold, those rules are refreshed with <quote>rules refresh</quote> mechanism. If the threshold is exceeded a <quote>full refresh</quote> of sudo rules is triggered instead. This threshold number also applies to IPA sudo command and command group searches.
target: Maximum number of expired rules that can be refreshed at once. If number of expired rules is below threshold, those rules are refreshed with <quote>rules refresh</quote> mechanism. If the threshold is exceeded, a <quote>full refresh</quote> of sudo rules is triggered instead. This threshold number also applies to IPA sudo command and command group searches.

en: NOTE: It is not possible to mix units.  To set the lifetime to one and a half hours please use '90m' instead of '1h30m'.
target: NOTE: It is not possible to mix units.  To set the lifetime to one and a half hours, please use '90m' instead of '1h30m'.

en: 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
target: NOTE: On older systems (such as RHEL 5), for this behaviour to work reliably, the default Kerberos realm must be set properly in /etc/krb5.conf

en: NOTE: This option has no effect on netgroup lookups due to their tendency to include nested netgroups without qualified names. For netgroups, all domains will be searched when an unqualified name is requested.
target: NOTE: This option has no effect on netgroup lookups, due to their tendency to include nested netgroups without qualified names. For netgroups, all domains will be searched when an unqualified name is requested.

en: Name of the LDAP attribute containing the email address of the user.
target: Name of the LDAP attribute containing the e-mail address of the user.

en: Normally when no applicable GPOs are found the users are allowed access. When this option is set to True users will be allowed access only when explicitly allowed by a GPO rule. Otherwise users will be denied access. This can be used to harden security but be careful when using this option because it can deny access even to users in the built-in Administrators group if no GPO rules apply to them.
target: Normally, when no applicable GPOs are found, the users are allowed access. When this option is set to True, users will be allowed access only when explicitly allowed by a GPO rule. Otherwise, users will be denied access. This can be used to harden security, but be careful when using this option because it can deny access even to users in the built-in Administrators group if no GPO rules apply to them.

en: Normally when some group policy containers (AD object) of applicable group policy objects are not readable by SSSD then users are denied access.  This option allows to ignore group policy containers and with them associated policies if their attributes in group policy containers are not readable for SSSD.
target: Normally when some group policy containers (AD object) of applicable group policy objects are not readable by SSSD then users are denied access.  This option allows to ignore group policy containers, and with them associated policies, if their attributes in group policy containers are not readable for SSSD.

en: Not all Kerberos implementations support the use of plugins. If <command>sssd_krb5_locator_plugin</command> is not available on your system you have to edit /etc/krb5.conf to reflect your Kerberos setup.
target: Not all Kerberos implementations support the use of plugins. If <command>sssd_krb5_locator_plugin</command> is not available on your system, you have to edit /etc/krb5.conf to reflect your Kerberos setup.

en: Note: Additional secondary slices might be generated when SID is being mapped to UNIX id and RID part of SID is out of range for secondary slices generated so far. If value of ldap_idmap_helper_table_size is equal to 0 then no additional secondary slices are generated.
target: Note: Additional secondary slices might be generated when both the SID is being mapped to UNIX id and the RID part of SID is out of range for secondary slices generated so far. If value of ldap_idmap_helper_table_size is equal to 0 then no additional secondary slices are generated.

en: Note: Cron service name may differ depending on Linux distribution used.
target: Note: Cron service name may differ, depending on Linux distribution used.

en: Note: First, a new connection is established to verify current password by binding as the user that requested password change. If successful, this connection is used to change the password therefore the user must have write access to userPassword attribute.
target: Note: First, a new connection is established to verify current password by binding as the user that requested password change. If successful, this connection is used to change the password, therefore the user must have write access to userPassword attribute.

en: Note: If an email address of a user conflicts with an email address or fully qualified name of another user, then SSSD will not be able to serve those users properly. If for some reason several users need to share the same email address then set this option to a nonexistent attribute name in order to disable user lookup/login by email.
target: Note: If an e-mail address of a user conflicts with an e-mail address or fully qualified name of another user, then SSSD will not be able to serve those users properly. If for some reason several users need to share the same e-mail address then set this option to a nonexistent attribute name in order to disable user lookup/login by e-mail.

en: Note: It is unsupported to have multiple search bases which reference identically-named objects (for example, groups with the same name in two different search bases). This will lead to unpredictable behavior on client machines.
target: Note: It is unsupported to have multiple search bases which reference identically-named objects (for example, groups with the same name in two different search bases). This will lead to unpredictable behaviour on client machines.

en: Note: Please be aware that message is only printed for the SSH service unless pam_verbosity is set to 3 (show all messages and debug information).
target: Note: Please be aware that the message is only printed for the SSH service when pam_verbosity is not set to 3 (show all messages and debug information).

en: Note: Using the Group Policy Management Editor this value is called "Access this computer from the network" and "Deny access to this computer from the network".
target: Note: Using the Group Policy Management Editor, this value is called "Access this computer from the network" and "Deny access to this computer from the network".

en: Note: Using the Group Policy Management Editor this value is called "Allow log on as a batch job" and "Deny log on as a batch job".
target: Note: Using the Group Policy Management Editor, this value is called "Allow log on as a batch job" and "Deny log on as a batch job".

en: Note: this option will have no effect on platforms where inotify is unavailable. On these platforms, polling will always be used.
target: Note: This option will have no effect on platforms where inotify is unavailable. On these platforms, polling will always be used.

en: Number of days entries are left in cache after last successful login before being removed during a cleanup of the cache. 0 means keep forever.  The value of this parameter must be greater than or equal to offline_credentials_expiration.
target: Number of days that entries are left in cache after last successful login before being removed during a cache cleanup. 0 means keep forever.  The value of this parameter must be greater than or equal to offline_credentials_expiration.

en: Overrides data are stored in the SSSD cache. If the cache is deleted, all local overrides are lost. Please note that after the first override is created using any of the following <emphasis>user-add</emphasis>, <emphasis>group-add</emphasis>, <emphasis>user-import</emphasis> or <emphasis>group-import</emphasis> command. SSSD needs to be restarted to take effect.  <emphasis>sss_override</emphasis> prints message when a restart is required.
target: Overrides data are stored in the SSSD cache. If the cache is deleted, all local overrides are lost. Please note that after the first override is created, using any of the following <emphasis>user-add</emphasis>, <emphasis>group-add</emphasis>, <emphasis>user-import</emphasis> or <emphasis>group-import</emphasis> command. SSSD needs to be restarted to take effect.  <emphasis>sss_override</emphasis> prints message when a restart is required.

en: PKCS#11 URI (see RFC-7512 for details) which can be used to restrict the selection of devices used for Smartcard authentication. By default SSSD's p11_child will search for a PKCS#11 slot (reader)  where the 'removable' flags is set and read the certificates from the inserted token from the first slot found. If multiple readers are connected p11_uri can be used to tell p11_child to use a specific reader.
target: PKCS#11 URI (see RFC-7512 for details) which can be used to restrict the selection of devices used for Smartcard authentication. By default, SSSD's p11_child will search for a PKCS#11 slot (reader)  where the 'removable' flags is set and read the certificates from the inserted token from the first slot found. If multiple readers are connected, p11_uri can be used to tell p11_child to use a specific reader.

en: Please note that UID 0 is always allowed to access the PAM responder even in case it is not in the pam_trusted_users list.
target: Please note that UID 0 is always allowed to access the PAM responder, even when it is not in the pam_trusted_users list.

en: Please note that although the UID 0 is used as the default it will be overwritten with this option. If you still want to allow the root user to access the InfoPipe responder, which would be the typical case, you have to add 0 to the list of allowed UIDs as well.
target: Please note that although the UID 0 is used as the default, it will be overwritten with this option. If you still want to allow the root user to access the InfoPipe responder, which would be the typical case, you have to add 0 to the list of allowed UIDs as well.

en: Please note that although the UID 0 is used as the default it will be overwritten with this option. If you still want to allow the root user to access the PAC responder, which would be the typical case, you have to add 0 to the list of allowed UIDs as well.
target: Please note that although the UID 0 is used as the default, it will be overwritten with this option. If you still want to allow the root user to access the PAC responder, which would be the typical case, you have to add 0 to the list of allowed UIDs as well.

en: Please note that disabling Global Catalog support does not disable retrieving users from trusted domains. The SSSD would connect to the LDAP port of trusted domains instead. However, Global Catalog must be used in order to resolve cross-domain group memberships.
target: Please note that disabling Global Catalogue support does not disable retrieving users from trusted domains. The SSSD would connect to the LDAP port of trusted domains instead. However, Global Catalogue must be used in order to resolve cross-domain group memberships.

en: Please note that if <quote>cached_auth_timeout</quote> is longer than <quote>pam_id_timeout</quote> then the back end could be called to handle <quote>initgroups.</quote>
target: Please note that if <quote>cached_auth_timeout</quote> is longer than <quote>pam_id_timeout</quote> then the backend could be called to handle <quote>initgroups.</quote>

en: Please note that it is an configuration error if both, simple_allow_users and simple_deny_users, are defined.
target: Please note that it is a configuration error if both simple_allow_users and simple_deny_users are defined.

en: Please note that this option might not work as expected if the application calling PAM handles the user dialog on its own. A typical example is <command>sshd</command> with <option>PasswordAuthentication</option>.
target: Please note that this option might not work as expected if the application calling PAM handles the user dialogue on its own. A typical example is <command>sshd</command> with <option>PasswordAuthentication</option>.

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

en: Please note, the home directory from a specific override for the user, either locally (see <citerefentry><refentrytitle>sss_override</refentrytitle> <manvolnum>8</manvolnum></citerefentry>) or centrally managed IPA id-overrides, has a higher precedence and will be used instead of the value given by override_homedir.
target: Please note that the home directory from a specific override for the user, whether locally (see <citerefentry><refentrytitle>sss_override</refentrytitle> <manvolnum>8</manvolnum></citerefentry>) or centrally managed IPA id-overrides, has a higher precedence and will be used instead of the value given by override_homedir.

en: Regular expression for this domain that describes how to parse the string containing user name and domain into these components.  The "domain" can match either the SSSD configuration domain name, or, in the case of IPA trust subdomains and Active Directory domains, the flat (NetBIOS) name of the domain.
target: Regular expression for this domain that describes how to parse the string containing username and domain into these components.  The "domain" can match either the SSSD configuration domain name, or, in the case of IPA trust subdomains and Active Directory domains, the flat (NetBIOS) name of the domain.

en: Resolving a server to connect to can be as simple as running a single DNS query or can involve several steps, such as finding the correct site or trying out multiple host names in case some of the configured servers are not reachable. The more complex scenarios can take some time and SSSD needs to balance between providing enough time to finish the resolution process but on the other hand, not trying for too long before falling back to offline mode. If the SSSD debug logs show that the server resolution is timing out before a live server is contacted, you can consider changing the time outs.
target: Resolving a server to connect to can be as simple as running a single DNS query or can involve several steps, such as finding the correct site or trying out multiple host names in case some of the configured servers are not reachable. The more complex scenarios can take some time and SSSD needs to balance between providing enough time to finish the resolution process but on the other hand, not trying for too long before falling back to offline mode. If the SSSD debug logs show that the server resolution is timing out before a live server is contacted, you can consider changing the timeouts.

en: SSSD can handle views and overrides which are offered by FreeIPA 4.1 and later version. Since all paths and objectclasses are fixed on the server side there is basically no need to configure anything. For completeness the related options are listed here with their default values.  <placeholder type="variablelist" id="0"/>
target: SSSD can handle views and overrides which are offered by FreeIPA 4.1 and later version. Since all paths and objectclasses are fixed on the server side there is basically no need to configure anything. For completeness, the related options are listed here with their default values.  <placeholder type="variablelist" id="0"/>

en: SSSD is used to provide desired service name and to validate the user's credentials using GSSAPI calls. If the service ticket is already present in the Kerberos credentials cache or if user's ticket granting ticket can be used to get the correct service ticket then the user will be authenticated.
target: SSSD is used to provide desired service name and to validate the user's credentials using GSSAPI calls. If the service ticket is already present in the Kerberos credentials cache, or if user's ticket granting ticket can be used to get the correct service ticket, then the user will be authenticated.

en: SSSD supports to look up the names of Well-Known SIDs, i.e. SIDs with a special hardcoded meaning. Since the generic users and groups related to those Well-Known SIDs have no equivalent in a Linux/UNIX environment no POSIX IDs are available for those objects.
target: SSSD supports to look up the names of Well-Known SIDs, i.e. SIDs with a special hardcoded meaning. Since the generic users and groups related to those Well-Known SIDs have no equivalent in a Linux/UNIX environment, no POSIX IDs are available for those objects.

en: SSSD uses different kinds of mechanisms with more or less complex LDAP filters to keep the cached sudo rules up to date. The default configuration is set to values that should satisfy most of our users, but the following paragraphs contain few tips on how to fine- tune the configuration to your requirements.
target: SSSD uses different kinds of mechanisms with more or less complex LDAP filters to keep the cached sudo rules up to date. The default configuration is set to values that should satisfy most of our users, but the following paragraphs contain a few tips on how to fine- tune the configuration to your requirements.

en: Similar to <quote>--genconf</quote>, but only refresh a single section from the configuration file.  This option is useful mainly to be called from systemd unit files to allow socket-activated responders to refresh their configuration without requiring the administrator to restart the whole SSSD.
target: Similar to <quote>--genconf</quote>, but only refresh a single section from the configuration file.  This option is useful mainly to be called from systemd unit files, allowing socket-activated responders to refresh their configuration without requiring the administrator to restart the whole SSSD.

en: Space separated list of IPv4 or IPv6 host/network addresses that should be used to filter the rules.
target: Space-separated list of IPv4 or IPv6 host/network addresses that should be used to filter the rules.

en: Space separated list of hostnames or fully qualified domain names that should be used to filter the rules.
target: Space-separated list of hostnames or fully qualified domain names that should be used to filter the rules.

en: Specifies a list of configuration parameters that should be inherited by a subdomain. Please note that only selected parameters can be inherited.  Currently the following options can be inherited:
target: Specifies a list of configuration parameters that should be inherited by a subdomain. Please note that only selected parameters can be inherited.  Currently, the following options can be inherited:

en: Specifies a timeout (in seconds) that a connection to an LDAP server will be maintained. After this time, the connection will be re-established. If used in parallel with SASL/GSSAPI, the sooner of the two values (this value vs. the TGT lifetime)  will be used.
target: Specifies a timeout (in seconds) that a connection to an LDAP server will be maintained. After this time, the connection will be re-established. If used in parallel with SASL/GSSAPI, the sooner of the two values (this value vs. the TGT lifetime) will be used.

en: Specifies acceptable cipher suites.  Typically this is a colon separated list.  See <citerefentry><refentrytitle>ldap.conf</refentrytitle> <manvolnum>5</manvolnum></citerefentry> for format.
target: Specifies acceptable cipher suites.  Typically this is a colon-separated list.  See <citerefentry><refentrytitle>ldap.conf</refentrytitle> <manvolnum>5</manvolnum></citerefentry> for format.

en: Specifies for how many seconds nss_sss should cache negative cache hits (that is, queries for invalid database entries, like nonexistent ones)  before asking the back end again.
target: Specifies for how many seconds nss_sss should cache negative cache hits (that is, queries for invalid database entries, like nonexistent ones)  before asking the backend again.

en: Specifies for how many seconds nss_sss should keep local users and groups in negative cache before trying to look it up in the back end again. Setting the option to 0 disables this feature.
target: Specifies for how many seconds nss_sss should keep local users and groups in negative cache before trying to look it up in the backend again. Setting the option to 0 disables this feature.

en: Specifies for how many seconds should the autofs responder negative cache hits (that is, queries for invalid map entries, like nonexistent ones) before asking the back end again.
target: Specifies for how many seconds  the autofs responder should cache negative hits (that is, queries for invalid map entries, like nonexistent ones) before asking the backend again.

en: Specifies how many seconds SSSD has to wait before triggering a background refresh task which will refresh all expired or nearly expired records.
target: Specifies how many seconds SSSD has to wait before triggering a background refresh task which will refresh all expired, or nearly expired, records.

en: Specifies if the SSSD should instruct the Kerberos libraries what realm and which KDCs to use. This option is on by default, if you disable it, you need to configure the Kerberos library using the <citerefentry> <refentrytitle>krb5.conf</refentrytitle> <manvolnum>5</manvolnum> </citerefentry> configuration file.
target: Specifies if the SSSD should instruct the Kerberos libraries what realm and which KDCs to use. This option is on by default. If you disable it, you need to configure the Kerberos library using the <citerefentry> <refentrytitle>krb5.conf</refentrytitle> <manvolnum>5</manvolnum> </citerefentry> configuration file.

en: Specifies if the host and user principal should be canonicalized. This feature is available with MIT Kerberos 1.7 and later versions.
target: Specifies if the host and user principal should be canonicalised. This feature is available with MIT Kerberos 1.7 and later versions.

en: Specifies if the host principal should be canonicalized when connecting to LDAP server. This feature is available with MIT Kerberos >= 1.7
target: Specifies if the host principal should be canonicalised when connecting to LDAP server. This feature is available with MIT Kerberos >= 1.7

en: Specifies the comma-separated list of UID values or user names that are allowed to access the InfoPipe responder. User names are resolved to UIDs at startup.
target: Specifies the comma-separated list of UID values or usernames that are allowed to access the InfoPipe responder. Usernames are resolved to UIDs at startup.

en: Specifies the comma-separated list of UID values or user names that are allowed to access the PAC responder. User names are resolved to UIDs at startup.
target: Specifies the comma-separated list of UID values or usernames that are allowed to access the PAC responder. Usernames are resolved to UIDs at startup.

en: Specifies the comma-separated list of UID values or user names that are allowed to run PAM conversations against trusted domains.  Users not included in this list can only access domains marked as public with <quote>pam_public_domains</quote>.  User names are resolved to UIDs at startup.
target: Specifies the comma-separated list of UID values or usernames that are allowed to run PAM conversations against trusted domains.  Users not included in this list can only access domains marked as public with <quote>pam_public_domains</quote>.  Usernames are resolved to UIDs at startup.

en: Specifies the file that contains certificates for all of the Certificate Authorities that <command>sssd</command> will recognize.
target: Specifies the file that contains certificates for all of the Certificate Authorities that <command>sssd</command> will recognise.

en: Specifies to use subdomains realms for the authentication of users from trusted domains. This option can be set to 'true' if enterprise principals are used with upnSuffixes which are not known on the parent domain KDCs. If the option is set to 'true' SSSD will try to send the request directly to a KDC of the trusted domain the user is coming from.
target: Specifies to use subdomain realms for the authentication of users from trusted domains. This option can be set to 'true' if enterprise principals are used with upnSuffixes which are not known on the parent domain KDCs. If the option is set to 'true' SSSD will try to send the request directly to a KDC of the trusted domain the user is coming from.

en: Specify file to read user's password from. (if not specified password is prompted for)
target: Specify file to read user's password from. (If not specified, password is prompted for).

en: Specify the SASL authorization id to use.  When GSSAPI/GSS-SPNEGO are used, this represents the Kerberos principal used for authentication to the directory.  This option can either contain the full principal (for example host/myhost@EXAMPLE.COM) or just the principal name (for example host/myhost).  By default, the value is not set and the following principals are used: <placeholder type="programlisting" id="0"/> If none of them are found, the first principal in keytab is returned.
target: Specify the SASL authorisation id to use.  When GSSAPI/GSS-SPNEGO are used, this represents the Kerberos principal used for authentication to the directory.  This option can either contain the full principal (for example host/myhost@EXAMPLE.COM) or just the principal name (for example host/myhost).  By default, the value is not set and the following principals are used: <placeholder type="programlisting" id="0"/> If none of them are found, the first principal in keytab is returned.

en: Specify the number of group members that must be missing from the internal cache in order to trigger a dereference lookup. If less members are missing, they are looked up individually.
target: Specify the number of group members that must be missing from the internal cache in order to trigger a dereference lookup. If fewer members are missing, they are looked up individually.

en: SystemTap Probe points have been added into various locations in SSSD code to assist in troubleshooting and analyzing performance related issues.
target: SystemTap Probe points have been added into various locations in SSSD code to assist in troubleshooting and analysing performance related issues.

en: The <emphasis>full refresh</emphasis> simply deletes all sudo rules stored in the cache and replaces them with all rules that are stored on the server. This is used to keep the cache consistent by removing every rule which was deleted from the server. However, full refresh may produce a lot of traffic and thus it should be run only occasionally depending on the size and stability of the sudo rules.
target: The <emphasis>full refresh</emphasis> simply deletes all sudo rules stored in the cache and replaces them with all rules that are stored on the server. This is used to keep the cache consistent by removing every rule which was deleted from the server. However, a full refresh may produce a lot of traffic and thus it should be run only occasionally, depending on the size and stability of the sudo rules.

en: The <emphasis>rules refresh</emphasis> ensures that we do not grant the user more permission than defined. It is triggered each time the user runs sudo. Rules refresh will find all rules that apply to this user, check their expiration time and redownload them if expired.  In the case that any of these rules are missing on the server, the SSSD will do an out of band full refresh because more rules (that apply to other users) may have been deleted.
target: The <emphasis>rules refresh</emphasis> ensures that we do not grant the user more permission than defined. It is triggered each time the user runs sudo. Rules refresh will find all rules that apply to this user, check their expiration time, and redownload them if expired.  In the case that any of these rules are missing on the server, the SSSD will do an out of band full refresh because more rules (that apply to other users) may have been deleted.

en: The AD provider automatically sets "fallback_homedir = /home/%d/%u" to provide personal home directories for users without the homeDirectory attribute. If your AD Domain is properly populated with Posix attributes, and you want to avoid this fallback behavior, you can explicitly set "fallback_homedir = %o".
target: The AD provider automatically sets "fallback_homedir = /home/%d/%u" to provide personal home directories for users without the homeDirectory attribute. If your AD Domain is properly populated with Posix attributes, and you want to avoid this fallback behaviour, you can explicitly set "fallback_homedir = %o".

en: The AD provider can be used to get user information and authenticate users from trusted domains. Currently only trusted domains in the same forest are recognized. In addition servers from trusted domains are always auto-discovered.
target: The AD provider can be used to get user information and authenticate users from trusted domains. Currently, only trusted domains in the same forest are recognised. In addition, servers from trusted domains are always auto-discovered.

en: The AD provider enables SSSD to use the <citerefentry> <refentrytitle>sssd-ldap</refentrytitle> <manvolnum>5</manvolnum> </citerefentry> identity provider and the <citerefentry> <refentrytitle>sssd-krb5</refentrytitle> <manvolnum>5</manvolnum> </citerefentry> authentication provider with optimizations for Active Directory environments. The AD provider accepts the same options used by the sssd-ldap and sssd-krb5 providers with some exceptions. However, it is neither necessary nor recommended to set these options.
target: The AD provider enables SSSD to use the <citerefentry> <refentrytitle>sssd-ldap</refentrytitle> <manvolnum>5</manvolnum> </citerefentry> identity provider and the <citerefentry> <refentrytitle>sssd-krb5</refentrytitle> <manvolnum>5</manvolnum> </citerefentry> authentication provider with optimisations for Active Directory environments. The AD provider accepts the same options used by the sssd-ldap and sssd-krb5 providers, with some exceptions. However, it is neither necessary nor recommended to set these options.

en: The AD provider is a back end used to connect to an Active Directory server. This provider requires that the machine be joined to the AD domain and a keytab is available. Back end communication occurs over a GSSAPI-encrypted channel, SSL/TLS options should not be used with the AD provider and will be superseded by Kerberos usage.
target: The AD provider is a backend used to connect to an Active Directory server. This provider requires that the machine be joined to the AD domain and a keytab is available. Backend communication occurs over a GSSAPI-encrypted channel, SSL/TLS options should not be used with the AD provider and will be superseded by Kerberos usage.

en: The IPA provider enables SSSD to use the <citerefentry> <refentrytitle>sssd-ldap</refentrytitle> <manvolnum>5</manvolnum> </citerefentry> identity provider and the <citerefentry> <refentrytitle>sssd-krb5</refentrytitle> <manvolnum>5</manvolnum> </citerefentry> authentication provider with optimizations for IPA environments. The IPA provider accepts the same options used by the sssd-ldap and sssd-krb5 providers with some exceptions. However, it is neither necessary nor recommended to set these options.
target: The IPA provider enables SSSD to use the <citerefentry> <refentrytitle>sssd-ldap</refentrytitle> <manvolnum>5</manvolnum> </citerefentry> identity provider and the <citerefentry> <refentrytitle>sssd-krb5</refentrytitle> <manvolnum>5</manvolnum> </citerefentry> authentication provider with optimisations for IPA environments. The IPA provider accepts the same options used by the sssd-ldap and sssd-krb5 providers, with some exceptions. However, it is neither necessary nor recommended to set these options.

en: 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.
target: The IPA provider is a backend 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.

en: The Kerberos local authorization plugin <command>sssd_krb5_localauth_plugin</command> is used by libkrb5 to either find the local name for a given Kerberos principal or to check if a given local name and a given Kerberos principal relate to each other.
target: The Kerberos local authorisation plugin <command>sssd_krb5_localauth_plugin</command> is used by libkrb5 to either find the local name for a given Kerberos principal or to check if a given local name and a given Kerberos principal relate to each other.

en: The Kerberos local authorization plugin must be enabled explicitly in the Kerberos configuration, see <citerefentry> <refentrytitle>krb5.conf</refentrytitle> <manvolnum>5</manvolnum> </citerefentry>.  SSSD will create a config snippet with the content like e.g.  <placeholder type="programlisting" id="0"/> automatically in the SSSD's public Kerberos configuration snippet directory. If this directory is included in the local Kerberos configuration the plugin will be enabled automatically.
target: The Kerberos local authorisation plugin must be enabled explicitly in the Kerberos configuration, see <citerefentry> <refentrytitle>krb5.conf</refentrytitle> <manvolnum>5</manvolnum> </citerefentry>.  SSSD will create a config snippet with the content like e.g.  <placeholder type="programlisting" id="0"/> automatically in the SSSD's public Kerberos configuration snippet directory. If this directory is included in the local Kerberos configuration the plugin will be enabled automatically.

en: The Kerberos locator plugin <command>sssd_krb5_locator_plugin</command> is used by libkrb5 to find KDCs for a given Kerberos realm. SSSD provides such a plugin to guide all Kerberos clients on a system to a single KDC. In general it should not matter to which KDC a client process is talking to.  But there are cases, e.g. after a password change, where not all KDCs are in the same state because the new data has to be replicated first. To avoid unexpected authentication failures and maybe even account lockings it would be good to talk to a single KDC as long as possible.
target: The Kerberos locator plugin <command>sssd_krb5_locator_plugin</command> is used by libkrb5 to find KDCs for a given Kerberos realm. SSSD provides such a plugin to guide all Kerberos clients on a system to a single KDC. In general, it should not matter which KDC a client process is talking to, but there are cases, e.g. after a password change, where not all KDCs are in the same state because the new data has to be replicated first. To avoid unexpected authentication failures and maybe even account lockings, it would be good to talk to a single KDC as long as possible.

en: The LDAP attribute that corresponds to the user name (or UID, group name or user's netgroup)
target: The LDAP attribute that corresponds to the username (or UID, group name or user's netgroup)

en: The LDAP attribute that corresponds to the user name that commands may be run as.
target: The LDAP attribute that corresponds to the username that commands may be run as.

en: The PAC responder works together with the authorization data plugin for MIT Kerberos sssd_pac_plugin.so and a sub-domain provider. The plugin sends the PAC data during a GSSAPI authentication to the PAC responder. The sub-domain provider collects domain SID and ID ranges of the domain the client is joined to and of remote trusted domains from the local domain controller. If the PAC is decoded and evaluated some of the following operations are done:
target: The PAC responder works together with the authorisation data plugin for MIT Kerberos sssd_pac_plugin.so and a sub-domain provider. The plugin sends the PAC data during a GSSAPI authentication to the PAC responder. The sub-domain provider collects domain SID and ID ranges of the domain the client is joined to and of remote trusted domains from the local domain controller. If the PAC is decoded and evaluated, some of the following operations are done:

en: The SSSD POSIX-type domain the application domain inherits all settings from. The application domain can moreover add its own settings to the application settings that augment or override the <quote>sibling</quote> domain settings.
target: The SSSD POSIX-type domain the application domain inherits all settings from. The application domain can also add its own settings to the application settings that augment or override the <quote>sibling</quote> domain settings.

en: 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.
target: 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.

en: The administrator might want to use the SSSD local users instead of traditional UNIX users in cases where the group nesting (see <citerefentry> <refentrytitle>sss_groupadd</refentrytitle> <manvolnum>8</manvolnum> </citerefentry>) is needed. The local users are also useful for testing and development of the SSSD without having to deploy a full remote server. The <command>sss_user*</command> and <command>sss_group*</command> tools use a local LDB storage to store users and groups.
target: The administrator might want to use the SSSD local users instead of traditional UNIX users, in cases where the group nesting (see <citerefentry> <refentrytitle>sss_groupadd</refentrytitle> <manvolnum>8</manvolnum> </citerefentry>) is needed. The local users are also useful for testing and development of the SSSD without having to deploy a full remote server. The <command>sss_user*</command> and <command>sss_group*</command> tools use a local LDB storage to store users and groups.

en: The capitalized version of these names are used as domain names when returning the fully qualified name of a Well-Known SID.
target: The capitalised version of these names are used as domain names when returning the fully qualified name of a Well-Known SID.

en: The cleartext password is read from standard input or entered interactively.  The obfuscated password is put into <quote>ldap_default_authtok</quote> parameter of a given SSSD domain and the <quote>ldap_default_authtok_type</quote> parameter is set to <quote>obfuscated_password</quote>. Refer to <citerefentry> <refentrytitle>sssd-ldap</refentrytitle> <manvolnum>5</manvolnum> </citerefentry> for more details on these parameters.
target: The cleartext password is read from standard input, or entered interactively.  The obfuscated password is put into <quote>ldap_default_authtok</quote> parameter of a given SSSD domain and the <quote>ldap_default_authtok_type</quote> parameter is set to <quote>obfuscated_password</quote>. Refer to <citerefentry> <refentrytitle>sssd-ldap</refentrytitle> <manvolnum>5</manvolnum> </citerefentry> for more details on these parameters.

en: The configuration snippets from <filename>conf.d</filename> have higher priority than <filename>sssd.conf</filename> and will override <filename>sssd.conf</filename> when conflicts occur. If several snippets are present in <filename>conf.d</filename>, then they are included in alphabetical order (based on locale).  Files included later have higher priority. Numerical prefixes (<filename>01_snippet.conf</filename>, <filename>02_snippet.conf</filename> etc.) can help visualize the priority (higher number means higher priority).
target: The configuration snippets from <filename>conf.d</filename> have higher priority than <filename>sssd.conf</filename> and will override <filename>sssd.conf</filename> when conflicts occur. If several snippets are present in <filename>conf.d</filename>, then they are included in alphabetical order (based on locale).  Files included later have higher priority. Numerical prefixes (<filename>01_snippet.conf</filename>, <filename>02_snippet.conf</filename> etc.) can help visualise the priority (higher number means higher priority).

en: The current use case are login managers which can monitor a Smartcard reader for card events. In case a Smartcard is inserted the login manager will call a PAM stack which includes a line like <placeholder type="programlisting" id="0"/> In this case SSSD will try to determine the user name based on the content of the Smartcard, returns it to pam_sss which will finally put it on the PAM stack.
target: The current use case involves login managers which can monitor a Smartcard reader for card events. If a Smartcard is inserted, the login manager will call a PAM stack which includes a line like <placeholder type="programlisting" id="0"/> In this case, SSSD will try to determine the username based on the content of the Smartcard, and return it to pam_sss which will finally put it on the PAM stack.

en: The detailed instructions for configuration of sudo_provider are in the manual page <citerefentry> <refentrytitle>sssd-sudo</refentrytitle> <manvolnum>5</manvolnum> </citerefentry>.  There are many configuration options that can be used to adjust the behavior. Please refer to "ldap_sudo_*" in <citerefentry> <refentrytitle>sssd-ldap</refentrytitle> <manvolnum>5</manvolnum> </citerefentry>.
target: The detailed instructions for configuration of sudo_provider are in the manual page <citerefentry> <refentrytitle>sssd-sudo</refentrytitle> <manvolnum>5</manvolnum> </citerefentry>.  There are many configuration options that can be used to adjust the behaviour. Please refer to "ldap_sudo_*" in <citerefentry> <refentrytitle>sssd-ldap</refentrytitle> <manvolnum>5</manvolnum> </citerefentry>.

en: The failover feature allows back ends to automatically switch to a different server if the current server fails.
target: The failover feature allows backends to automatically switch to a different server if the current server fails.

en: 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 service.
target: The failover mechanism distinguishes between a machine and a service. The backend 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 backend 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 backend automatically switches over to the next service.  The machine is still considered online and might still be tried for another service.

en: The filter must be a valid LDAP search filter as specified by http://www.ietf.org/rfc/rfc2254.txt
target: The filter must be a valid LDAP search filter as specified by https://www.ietf.org/rfc/rfc2254.txt

en: The following example illustrates the use of an application domain. In this setup, the POSIX domain is connected to an LDAP server and is used by the OS through the NSS responder. In addition, the application domain also requests the telephoneNumber attribute, stores it as the phone attribute in the cache and makes the phone attribute reachable through the D-Bus interface.
target: The following example illustrates the use of an application domain. In this setup, the POSIX domain is connected to an LDAP server and is used by the OS through the NSS responder. In addition, the application domain also requests the telephoneNumber attribute, stores it as the phone attribute in the cache, and makes the phone attribute reachable through the D-Bus interface.

en: The following krb5 options can be configured in the [kcm] section to control renewal behavior, these options are described in detail below <placeholder type="programlisting" id="0"/>
target: The following krb5 options can be configured in the [kcm] section to control renewal behaviour, these options are described in detail below <placeholder type="programlisting" id="0"/>

en: The idmap_sss module provides a way to call SSSD to map UIDs/GIDs and SIDs. No database is required in this case as the mapping is done by SSSD.
target: The idmap_sss module provides a way to call SSSD to map UIDs/GIDs and SIDs. No database is required in this case, as the mapping is done by SSSD.

en: The list of mappings is given as a comma-separated list of pairs <quote>username:primary</quote> where <quote>username</quote> is a UNIX user name and <quote>primary</quote> is a user part of a kerberos principal. This mapping is used when user is authenticating using <quote>auth_provider = krb5</quote>.
target: The list of mappings is given as a comma-separated list of pairs <quote>username:primary</quote> where <quote>username</quote> is a UNIX username and <quote>primary</quote> is a user part of a kerberos principal. This mapping is used when user is authenticating using <quote>auth_provider = krb5</quote>.

en: The main purpose of this option is to let SSSD determine the user name based on additional information, e.g. the certificate from a Smartcard.
target: The main purpose of this option is to let SSSD determine the username based on additional information, e.g. the certificate from a Smartcard.

en: The message is read from the file <filename>pam_sss_pw_reset_message.LOC</filename> where LOC stands for a locale string returned by <citerefentry> <refentrytitle>setlocale</refentrytitle><manvolnum>3</manvolnum> </citerefentry>. If there is no matching file the content of <filename>pam_sss_pw_reset_message.txt</filename> is displayed. Root must be the owner of the files and only root may have read and write permissions while all other users must have only read permissions.
target: The message is read from the file <filename>pam_sss_pw_reset_message.LOC</filename> where LOC stands for a locale string returned by <citerefentry> <refentrytitle>setlocale</refentrytitle><manvolnum>3</manvolnum> </citerefentry>. If there is no matching file, the content of <filename>pam_sss_pw_reset_message.txt</filename> is displayed. Root must be the owner of the files and only root may have read and write permissions, while all other users must only have read permissions.

en: The plugin reads the information about the KDCs of a given realm from a file called <filename>kdcinfo.REALM</filename>. The file should contain one or more DNS names or IP addresses either in dotted-decimal IPv4 notation or the hexadecimal IPv6 notation.  An optional port number can be added to the end separated with a colon, the IPv6 address has to be enclosed in squared brackets in this case as usual. Valid entries are:
target: The plugin reads the information about the KDCs of a given realm from a file called <filename>kdcinfo.REALM</filename>. The file should contain one or more DNS names or IP addresses, either in dotted-decimal IPv4 notation or the hexadecimal IPv6 notation.  An optional port number can be added to the end, separated with a colon; the IPv6 address has to be enclosed in squared brackets in this case as usual. Valid entries are:

en: The rules are processed by priority while the number '0' (zero)  indicates the highest priority. The higher the number the lower is the priority. A missing value indicates the lowest priority. The rules processing is stopped when a matched rule is found and no further rules are checked.
target: The rules are processed by priority while the number '0' (zero)  indicates the highest priority. The higher the number, the lower the priority. A missing value indicates the lowest priority. The processing of rules is stopped when a matching rule is found and no further rules are checked.

en: The service discovery feature allows back ends to automatically find the appropriate servers to connect to using a special DNS query. This feature is not supported for backup servers.
target: The service discovery feature allows backends to automatically find the appropriate servers to connect to using a special DNS query. This feature is not supported for backup servers.

en: The sssd-kcm service is typically socket-activated <citerefentry> <refentrytitle>systemd</refentrytitle> <manvolnum>1</manvolnum> </citerefentry>. To generate debug logs, add the following either to the <filename>/etc/sssd/sssd.conf</filename> file directly or as a configuration snippet to <filename>/etc/sssd/conf.d/</filename> directory: <placeholder type="programlisting" id="0"/> Then, restart the sssd-kcm service: <placeholder type="programlisting" id="1"/> Finally, run whatever use-case doesn't work for you. The KCM logs will be generated at <filename>/var/log/sssd/sssd_kcm.log</filename>. It is recommended to disable the debug logs when you no longer need the debugging to be enabled as the sssd-kcm service can generate quite a large amount of debugging information.
target: The sssd-kcm service is typically socket-activated <citerefentry> <refentrytitle>systemd</refentrytitle> <manvolnum>1</manvolnum> </citerefentry>. To generate debug logs, add the following either to the <filename>/etc/sssd/sssd.conf</filename> file directly or as a configuration snippet to <filename>/etc/sssd/conf.d/</filename> directory: <placeholder type="programlisting" id="0"/> Then, restart the sssd-kcm service: <placeholder type="programlisting" id="1"/> Finally, run whatever use-case doesn't work for you. The KCM logs will be generated at <filename>/var/log/sssd/sssd_kcm.log</filename>. It is recommended to disable the debug logs when you no longer need the debugging to be enabled, as the sssd-kcm service can generate quite a large amount of debugging information.

en: The user is not known to the authentication service or the GSSAPI authentication is not supported.
target: The user is not known to the authentication service, or the GSSAPI authentication is not supported.

en: The validation is the benefit of using X.509 certificates instead of SSH keys directly because e.g. it gives a better control of the lifetime of the keys. When the ssh client is configured to use the private keys from a Smartcard with the help of a PKCS#11 shared library (see <citerefentry><refentrytitle>ssh</refentrytitle> <manvolnum>1</manvolnum></citerefentry> for details) it might be irritating that authentication is still working even if the related X.509 certificate on the Smartcard is already expired because neither <command>ssh</command> nor <command>sshd</command> will look at the certificate at all.
target: The validation is the benefit of using X.509 certificates instead of SSH keys directly because e.g. it gives a better control of the lifetime of the keys. When the ssh client is configured to use the private keys from a Smartcard with the help of a PKCS#11 shared library (see <citerefentry><refentrytitle>ssh</refentrytitle> <manvolnum>1</manvolnum></citerefentry> for details), it might be irritating that authentication is still working even if the related X.509 certificate on the Smartcard is already expired because neither <command>ssh</command> nor <command>sshd</command> will look at the certificate at all.

en: There are many configuration options that can be used to adjust the behavior. Please refer to "ldap_sudo_*" in <citerefentry> <refentrytitle>sssd-ldap</refentrytitle> <manvolnum>5</manvolnum> </citerefentry> and "sudo_*" in <citerefentry> <refentrytitle>sssd.conf</refentrytitle> <manvolnum>5</manvolnum> </citerefentry>.
target: There are many configuration options that can be used to adjust the behaviour. Please refer to "ldap_sudo_*" in <citerefentry> <refentrytitle>sssd-ldap</refentrytitle> <manvolnum>5</manvolnum> </citerefentry> and "sudo_*" in <citerefentry> <refentrytitle>sssd.conf</refentrytitle> <manvolnum>5</manvolnum> </citerefentry>.

en: These files are searched in the directory <filename>/etc/sssd/customize/DOMAIN_NAME/</filename>. If no matching file is present a generic message is displayed.
target: These files are searched in the directory <filename>/etc/sssd/customize/DOMAIN_NAME/</filename>. If no matching file is present, a generic message is displayed.

en: This attribute is currently only used by the AD provider to determine if a group is a domain local groups and has to be filtered out for trusted domains.
target: This attribute is currently only used by the AD provider to determine if a group is a domain local group and has to be filtered out for trusted domains.

en: This option can be used to specify which extended key usage the certificate should have. The following value can be used in a comma separated list:
target: This option can be used to specify which extended key usage the certificate should have. The following value can be used in a comma-separated list:

en: This option can be used to specify which key usage values the certificate should have. The following values can be used in a comma separated list:
target: This option can be used to specify which key usage values the certificate should have. The following values can be used in a comma-separated list:

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

en: This option specifies the DN of password policy entry on LDAP server. Please note that absence of this option in sssd.conf in case of enabled account lockout checking will yield access denied as ppolicy attributes on LDAP server cannot be checked properly.
target: This option specifies the DN of password policy entry on LDAP server. Please note that an absence of this option in sssd.conf in the case of enabled account lockout checking will yield access denied as ppolicy attributes on LDAP server cannot be checked properly.

en: This option was named <quote>krb5_kdcip</quote> in earlier releases of SSSD. While the legacy name is recognized for the time being, users are advised to migrate their config files to use <quote>krb5_server</quote> instead.
target: This option was named <quote>krb5_kdcip</quote> in earlier releases of SSSD. While the legacy name is recognised for the time being, users are advised to migrate their config files to use <quote>krb5_server</quote> instead.

en: This parameter controls the value of the random offset used for the above equation. Final random_offset value will be random number in range:
target: This parameter controls the value of the random offset used for the above equation. Final random_offset value will be a random number in range:

en: This parameter will replace spaces (space bar)  with the given character for user and group names.  e.g. (_). User name &quot;john doe&quot; will be &quot;john_doe&quot; This feature was added to help compatibility with shell scripts that have difficulty handling spaces, due to the default field separator in the shell.
target: This parameter will replace spaces (space bar)  with the given character for user and group names.  e.g. (_). Username &quot;john doe&quot; will be &quot;john_doe&quot; This feature was added to help compatibility with shell scripts that have difficulty handling spaces, due to the default field separator in the shell.

en: This should avoid that the short PINs of a PIN based 2FA scheme are saved in the cache which would make them easy targets for brute-force attacks.
target: This should avoid having short PINs of a PIN based 2FA scheme saved in the cache which would otherwise make them easy targets for brute-force attacks.

en: This should be preferred to read user specific data from the certificate like e.g. an email address and search for it in the LDAP server. The reason is that the user specific data in LDAP might change for various reasons would break the mapping. On the other hand it would be hard to break the mapping on purpose for a specific user.
target: This should be preferred to read user specific data from the certificate like e.g. an e-mail address and search for it in the LDAP server. The reason is that the user-specific data in LDAP might change for various reasons and would break the mapping. On the other hand,  it would be hard to break the mapping on purpose for a specific user.

en: This string will be used as a default domain name for all names without a domain name component. The main use case is environments where the primary domain is intended for managing host policies and all users are located in a trusted domain.  The option allows those users to log in just with their user name without giving a domain name as well.
target: This string will be used as a default domain name for all names without a domain name component. The main use case is environments where the primary domain is intended for managing host policies and all users are located in a trusted domain.  The option allows those users to log in just with their username without giving a domain name as well.

en: This template will add the Kerberos principal which is taken either from the SAN used by pkinit or the one used by AD. The 'short_name' component represents the first part of the principal before the '@' sign.
target: This template will add the Kerberos principal which is taken either from the SAN used by pkinit, or the one used by AD. The 'short_name' component represents the first part of the principal before the '@' sign.

en: This template will add the full issuer DN converted to a string according to RFC 4514. If X.500 ordering (most specific RDN comes last) an option with the '_x500' prefix should be used.
target: This template will add the full issuer DN converted to a string according to RFC 4514. If X.500 ordering (most specific RDN comes last), an option with the '_x500' prefix should be used.

en: This template will add the string which is stored in the rfc822Name component of the SAN, typically an email address. The 'short_name' component represents the first part of the address before the '@' sign.
target: This template will add the string which is stored in the rfc822Name component of the SAN, typically an e-mail address. The 'short_name' component represents the first part of the address before the '@' sign.

en: This template will add the whole DER encoded certificate as a string to the search filter. Depending on the conversion option the binary certificate is either converted to an escaped hex sequence '\xx' or base64.  The escaped hex sequence is the default and can e.g. be used with the LDAP attribute 'userCertificate;binary'.
target: This template will add the whole DER encoded certificate as a string to the search filter. Depending on the conversion option, the binary certificate is either converted to an escaped hex sequence '\xx' or base64.  The escaped hex sequence is the default and can e.g. be used with the LDAP attribute 'userCertificate;binary'.

en: Time in seconds to tell how long would SSSD try to resolve single DNS query (e.g. resolution of a hostname or an SRV record) before trying the next hostname or discovery domain.
target: Time in seconds SSSD should try to resolve a single DNS query (e.g. resolution of a hostname or an SRV record) before trying the next hostname or discovery domain.

en: Timeout in seconds between heartbeats for this service. This is used to ensure that the process is alive and capable of answering requests. Note that after three missed heartbeats the process will terminate itself.
target: Timeout in seconds between heartbeats for this service. This is used to ensure that the process is alive and capable of answering requests. Note that after three missed heartbeats, the process will terminate itself.

en: To allow authentication with Smartcards and certificates SSSD must be able to map certificates to users. This can be done by adding the full certificate to the LDAP object of the user or to a local override. While using the full certificate is required to use the Smartcard authentication feature of SSH (see <citerefentry> <refentrytitle>sss_ssh_authorizedkeys</refentrytitle> <manvolnum>8</manvolnum> </citerefentry> for details) it might be cumbersome or not even possible to do this for the general case where local services use PAM for authentication.
target: To allow authentication with Smartcards and certificates, SSSD must be able to map certificates to users. This can be done by adding the full certificate to the LDAP object of the user or to a local override. While using the full certificate is required to use the Smartcard authentication feature of SSH, (see <citerefentry> <refentrytitle>sss_ssh_authorizedkeys</refentrytitle> <manvolnum>8</manvolnum> </citerefentry> for details) it might be cumbersome or not even possible to do this for the general case where local services use PAM for authentication.

en: To be compatible with the usage of MIT Kerberos this option will match the Kerberos principals in the PKINIT or AD NT Principal SAN as &lt;SAN:Principal&gt; does.
target: To be compatible with the usage of MIT Kerberos, this option will match the Kerberos principals in the PKINIT or AD NT Principal SAN as &lt;SAN:Principal&gt; does.

en: To disable the creation of the configuration snippets set the parameter to 'none'.
target: To disable the creation of the configuration snippets, set the parameter to 'none'.

en: To enable service discovery ldap_chpass_dns_service_name must be set.
target: To enable service discovery, ldap_chpass_dns_service_name must be set.

en: To enable this the <quote>ssh_use_certificate_keys</quote> option must be set to true (default) in the [ssh] section of <filename>sssd.conf</filename>. If the user entry contains certificates (see <quote>ldap_user_certificate</quote> in <citerefentry><refentrytitle>sssd-ldap</refentrytitle> <manvolnum>5</manvolnum></citerefentry> for details) or there is a certificate in an override entry for the user (see <citerefentry><refentrytitle>sss_override</refentrytitle> <manvolnum>8</manvolnum></citerefentry> or <citerefentry><refentrytitle>sssd-ipa</refentrytitle> <manvolnum>5</manvolnum></citerefentry> for details) and the certificate is valid SSSD will extract the public key from the certificate and convert it into the format expected by sshd.
target: To enable this, the <quote>ssh_use_certificate_keys</quote> option must be set to true (default) in the [ssh] section of <filename>sssd.conf</filename>. If the user entry contains certificates (see <quote>ldap_user_certificate</quote> in <citerefentry><refentrytitle>sssd-ldap</refentrytitle> <manvolnum>5</manvolnum></citerefentry> for details) or there is a certificate in an override entry for the user (see <citerefentry><refentrytitle>sss_override</refentrytitle> <manvolnum>8</manvolnum></citerefentry> or <citerefentry><refentrytitle>sssd-ipa</refentrytitle> <manvolnum>5</manvolnum></citerefentry> for details) and the certificate is valid, SSSD will extract the public key from the certificate and convert it into the format expected by sshd.

en: To list all available commands run <command>sssctl</command> without any parameters. To print help for selected command run <command>sssctl COMMAND --help</command>.
target: To list all available commands, run <command>sssctl</command> without any parameters. To print help for a selected command, run <command>sssctl COMMAND --help</command>.

en: To log required bitmask debug levels, simply add their numbers together as shown in following examples:
target: To log required bitmask debug levels, simply add their numbers together as shown in the following examples:

en: To make the configuration simple and reduce the amount of configuration options the <quote>files</quote> provider has some special properties:
target: To make the configuration simple and reduce the amount of configuration options, the <quote>files</quote> provider has some special properties:

en: To make the mapping more flexible mapping and matching rules were added to SSSD (see <citerefentry> <refentrytitle>sss-certmap</refentrytitle> <manvolnum>5</manvolnum> </citerefentry> for details).
target: To make the mapping more flexible, mapping and matching rules were added to SSSD (see <citerefentry> <refentrytitle>sss-certmap</refentrytitle> <manvolnum>5</manvolnum> </citerefentry> for details).

en: Treat user and group names as case sensitive.  Possible option values are: <placeholder type="variablelist" id="0"/>
target: Treat user and group names as case-sensitive.  Possible option values are: <placeholder type="variablelist" id="0"/>

en: Try to use certificate based authentication, i.e.  authentication with a Smartcard or similar devices. If a Smartcard is available and the service is allowed for Smartcard authentication the user will be prompted for a PIN and the certificate based authentication will continue
target: Try to use certificate based authentication, i.e.  authentication with a Smartcard or similar devices. If a Smartcard is available and the service is allowed for Smartcard authentication, the user will be prompted for a PIN and the certificate based authentication will continue

en: Unsigned integer value defining the priority of the rule. The higher the number the lower the priority.  <quote>0</quote> stands for the highest priority while <quote>4294967295</quote> is the lowest.
target: Unsigned integer value defining the priority of the rule. The higher the number, the lower the priority.  <quote>0</quote> stands for the highest priority while <quote>4294967295</quote> is the lowest.

en: When SSSD switches to offline mode the amount of time before it tries to go back online will increase based upon the time spent disconnected.  By default SSSD uses incremental behaviour to calculate delay in between retries.  So, the wait time for a given retry will be longer than the wait time for the previous ones.  After each unsuccessful attempt to go online, the new interval is recalculated by the following:
target: When SSSD switches to offline mode, the amount of time before it tries to go back online will increase based upon the time spent disconnected.  By default, SSSD uses incremental behaviour to calculate delay in between retries.  So, the wait time for a given retry will be longer than the wait time for the previous ones.  After each unsuccessful attempt to go online, the new interval is recalculated by the following:

en: When a user or group is looked up by name in the proxy provider, a second lookup by ID is performed to "canonicalize" the name in case the requested name was an alias. Setting this option to true would cause the SSSD to perform the ID lookup from cache for performance reasons.
target: When a user or group is looked up by name in the proxy provider, a second lookup by ID is performed to "canonicalise" the name in case the requested name was an alias. Setting this option to true would cause the SSSD to perform the ID lookup from cache for performance reasons.

en: When password changing enforce the module to set the new password to the one provided by a previously stacked password module.
target: When password changing, enforce the module to set the new password to the one provided by a previously-stacked password module.

en: Whether the nsupdate utility should use GSS-TSIG authentication for secure updates with the DNS server, insecure updates can be sent by setting this option to 'none'.
target: Whether the nsupdate utility should use GSS-TSIG authentication for secure updates with the DNS server; insecure updates can be sent by setting this option to 'none'.

en: While the first two correspond to the general default the third one is introduced to allow easy integration of users from Windows domains.
target: While the first two correspond to the general default, the third one is introduced to allow easy integration of users from Windows domains.

en: While updating the internal data SSSD will return an error and let the client continue with the next NSS module. This helps to avoid delays when using the default system files <filename>/etc/passwd</filename> and <filename>/etc/group</filename> and the NSS configuration has 'sss' before 'files' for the 'passwd' and 'group' maps.
target: While updating the internal data, SSSD will return an error and let the client continue with the next NSS module. This helps to avoid delays when using the default system files <filename>/etc/passwd</filename> and <filename>/etc/group</filename> and the NSS configuration has 'sss' before 'files' for the 'passwd' and 'group' maps.

en: With the growing number of authentication methods and the possibility that there are multiple ones for a single user the heuristic used by pam_sss to select the prompting might not be suitable for all use cases. The following options should provide a better flexibility here.
target: With the growing number of authentication methods and the possibility that there are multiple ones for a single user, the heuristic used by pam_sss to select the prompting might not be suitable for all use cases. The following options should provide better flexibility here.

en: With this a part or the whole issuer name of the certificate can be matched. All comments for &lt;SUBJECT&gt; apply her as well.
target: With this, a part of or the whole issuer name of the certificate can be matched. All comments for &lt;SUBJECT&gt; apply her as well.

en: With this a part or the whole subject name of the certificate can be matched. For the matching POSIX Extended Regular Expression syntax is used, see regex(7)  for details.
target: With this, a part of or the whole subject name of the certificate can be matched. For the matching POSIX Extended Regular Expression syntax is used, see regex(7)  for details.

en: With this option a client side evaluation of access control attributes can be enabled.
target: With this option, a client side evaluation of access control attributes can be enabled.

en: With this parameter the PAM certificate verification can be tuned with a comma separated list of options that override the <quote>certificate_verification</quote> value in <quote>[sssd]</quote> section.  Supported options are the same of <quote>certificate_verification</quote>.
target: With this parameter, the PAM certificate verification can be tuned with a comma-separated list of options that override the <quote>certificate_verification</quote> value in <quote>[sssd]</quote> section.  Supported options are the same of <quote>certificate_verification</quote>.

en: With this parameter the certificate verification can be tuned with a comma separated list of options. Supported options are: <placeholder type="variablelist" id="0"/>
target: With this parameter, the certificate verification can be tuned with a comma-separated list of options. Supported options are: <placeholder type="variablelist" id="0"/>

en: [General]
    Verbosity = 2
    # domain must be synced between NFSv4 server and clients
    # Solaris/Illumos/AIX use "localdomain" as default!
    Domain = default
    
    [Mapping]
    Nobody-User = nfsnobody
    Nobody-Group = nfsnobody
    
    [Translation]
    Method = sss
target: [General]
    Verbosity = 2
    # domain must be synched between NFSv4 server and clients
    # Solaris/Illumos/AIX use "localdomain" as default!
    Domain = default
    
    [Mapping]
    Nobody-User = nfsnobody
    Nobody-Group = nfsnobody
    
    [Translation]
    Method = sss

en: boolean value, if True there will be only a single prompt using the value of first_prompt where it is expected that both factors are entered as a single string. Please note that both factors have to be entered here, even if the second factor is optional.
target: boolean value; if True, there will be only a single prompt using the value of first_prompt where it is expected that both factors are entered as a single string. Please note that both factors have to be entered here, even if the second factor is optional.

en: fully qualified user name (user@domain)
target: fully qualified username (user@domain)

en: get OpenSSH authorized keys
target: get OpenSSH authorised keys

en: if maprule is not set the RULE_NAME name is assumed to be the name of the matching user
target: if maprule is not set, the RULE_NAME name is assumed to be the name of the matching user

en: libkrb5 will search the locator plugin in the libkrb5 sub-directory of the Kerberos plugin directory, see plugin_base_dir in <citerefentry> <refentrytitle>krb5.conf</refentrytitle> <manvolnum>5</manvolnum> </citerefentry> for details. The plugin can only be disabled by removing the plugin file. There is no option in the Kerberos configuration to disable it. But the SSSD_KRB5_LOCATOR_DISABLE environment variable can be used to disable the plugin for individual commands. Alternatively the SSSD option krb5_use_kdcinfo=False can be used to not generate the data needed by the plugin. With this the plugin is still called but will provide no data to the caller so that libkrb5 can fall back to other methods defined in krb5.conf.
target: libkrb5 will search the locator plugin in the libkrb5 sub-directory of the Kerberos plugin directory, see plugin_base_dir in <citerefentry> <refentrytitle>krb5.conf</refentrytitle> <manvolnum>5</manvolnum> </citerefentry> for details. The plugin can only be disabled by removing the plugin file. There is no option in the Kerberos configuration to disable it, but the SSSD_KRB5_LOCATOR_DISABLE environment variable can be used to disable the plugin for individual commands. Alternatively, the SSSD option krb5_use_kdcinfo=False can be used to not generate the data needed by the plugin. With this, the plugin is still called but will provide no data to the caller so that libkrb5 can fall back to other methods defined in krb5.conf.

en: user name
target: username
