SSSD/sssd-manpage — Dutch @ Fedora Weblate: <command>pam_sss_gss.so</command> <arg choice='opt'> <replaceable>debug</replaceable> </arg>

Translation

Source change

English type: Content of: <reference><refentry><refsynopsisdiv><cmdsynopsis>

Dutch

Needs editing

Skip

	English	Dutch	Actions
	Conversation failure.
	PAM_AUTHTOK_LOCK_BUSY
	No KDC suitable for password change is available.
	PAM_ABORT
	Unknown PAM call.
	PAM_MODULE_UNKNOWN
	Unsupported PAM task or command.
	PAM_BAD_ITEM
	The authentication module cannot handle Smartcard credentials.
	FILES
	If a password reset by root fails, because the corresponding SSSD provider does not support password resets, an individual message can be displayed. This message can e.g. contain instructions about how to reset a password.
	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.
	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.
	pam_sss_gss
	PAM module for SSSD GSSAPI authentication
	<command>pam_sss_gss.so</command> <arg choice='opt'> <replaceable>debug</replaceable> </arg>	<command>sss_groupmod</command> <arg choice='opt'> <replaceable>opties</replaceable> </arg> <arg choice='plain'><replaceable>GROEP</replaceable></arg>
	<command>pam_sss_gss.so</command> authenticates user over GSSAPI in cooperation with SSSD.
	This module will try to authenticate the user using the GSSAPI hostbased service name host@hostname which translates to host/hostname@REALM Kerberos principal. The <emphasis>REALM</emphasis> part of the Kerberos principal name is derived by Kerberos internal mechanisms and it can be set explicitly in configuration of [domain_realm] section in /etc/krb5.conf.
	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.
	If <option>pam_gssapi_check_upn</option> is True (default) then SSSD requires that the credentials used to obtain the service tickets can be associated with the user. This means that the principal that owns the Kerberos credentials must match with the user principal name as defined in LDAP.
	To enable GSSAPI authentication in SSSD, set <option>pam_gssapi_services</option> option in [pam] or domain section of sssd.conf. The service credentials need to be stored in SSSD's keytab (it is already present if you use ipa or ad provider). The keytab location can be set with <option>krb5_keytab</option> option. See <citerefentry> <refentrytitle>sssd.conf</refentrytitle> <manvolnum>5</manvolnum> </citerefentry> and <citerefentry> <refentrytitle>sssd-krb5</refentrytitle> <manvolnum>5</manvolnum> </citerefentry> for more details on these options.
	Some Kerberos deployments allow to associate authentication indicators with a particular pre-authentication method used to obtain the ticket granting ticket by the user. <command>pam_sss_gss.so</command> allows to enforce presence of authentication indicators in the service tickets before a particular PAM service can be accessed.
	If <option>pam_gssapi_indicators_map</option> is set in the [pam] or domain section of sssd.conf, then SSSD will perform a check of the presence of any configured indicators in the service ticket.
	<option>debug</option>
	Print debugging information.
	Only the <option>auth</option> module type is provided.
	The user is not known to the authentication service or the GSSAPI authentication is not supported.
	Authentication failure.
	The main use case is to provide password-less authentication in sudo but without the need to disable authentication completely. To achieve this, first enable GSSAPI authentication for sudo in sssd.conf:
	[domain/MYDOMAIN] pam_gssapi_services = sudo, sudo-i
	And then enable the module in desired PAM stack (e.g. /etc/pam.d/sudo and /etc/pam.d/sudo-i).

Loading…

None

Source string changed

English 75 characters edited

3 years ago

Browse all string changes

Things to check

XML markup

XML tags in translation do not match source

Reset

Glossary

English	Dutch
No related strings found in the glossary.

String information

Source string description

type: Content of: <reference><refentry><refsynopsisdiv><cmdsynopsis>

Source string location

pam_sss_gss.8.xml:22

String age

3 years ago

Last updated

a week ago

Source string age

3 years ago

Translation file

src/man/po/nl.po, string 1222