pam_sss(8) [centos man page]

PAM_SSS(8)							 SSSD Manual pages							PAM_SSS(8)

NAME

       pam_sss - PAM module for SSSD

SYNOPSIS

       pam_sss.so [quiet] [forward_pass] [use_first_pass] [use_authtok] [retry=N]

DESCRIPTION

       pam_sss.so is the PAM interface to the System Security Services daemon (SSSD). Errors and results are logged through syslog(3) with the
       LOG_AUTHPRIV facility.

OPTIONS

       quiet
	   Suppress log messages for unknown users.

       forward_pass
	   If forward_pass is set the entered password is put on the stack for other PAM modules to use.

       use_first_pass
	   The argument use_first_pass forces the module to use a previous stacked modules password and will never prompt the user - if no
	   password is available or the password is not appropriate, the user will be denied access.

       use_authtok
	   When password changing enforce the module to set the new password to the one provided by a previously stacked password module.

       retry=N
	   If specified the user is asked another N times for a password if authentication fails. Default is 0.

	   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 sshd with PasswordAuthentication.

MODULE TYPES PROVIDED

       All module types (account, auth, password and session) are provided.

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 pam_sss_pw_reset_message.LOC where LOC stands for a locale string returned by setlocale(3). If there is
       no matching file the content of pam_sss_pw_reset_message.txt 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 /etc/sssd/customize/DOMAIN_NAME/. If no matching file is present a generic message is displayed.

SEE ALSO

       sssd(8), sssd.conf(5), sssd-ldap(5), sssd-krb5(5), sssd-simple(5), sssd-ipa(5), sssd-ad(5), sssd-sudo(5),sss_cache(8), sss_debuglevel(8),
       sss_groupadd(8), sss_groupdel(8), sss_groupshow(8), sss_groupmod(8), sss_useradd(8), sss_userdel(8), sss_usermod(8), sss_obfuscate(8),
       sss_seed(8), sssd_krb5_locator_plugin(8), sss_ssh_authorizedkeys(8), sss_ssh_knownhostsproxy(8),pam_sss(8).

AUTHORS

       The SSSD upstream - http://fedorahosted.org/sssd

SSSD
								    06/17/2014								PAM_SSS(8)

SSS_DEBUGLEVEL(8)						 SSSD Manual pages						 SSS_DEBUGLEVEL(8)

NAME

       sss_debuglevel - change debug level while SSSD is running

SYNOPSIS

       sss_debuglevel [options] NEW_DEBUG_LEVEL

DESCRIPTION

       sss_debuglevel changes debug level of SSSD monitor and providers to NEW_DEBUG_LEVEL while SSSD is running.

OPTIONS

       -c,--config
	   Specify a non-default config file. The default is /etc/sssd/sssd.conf. For reference on the config file syntax and options, consult the
	   sssd.conf(5) manual page.

       NEW_DEBUG_LEVEL
	   SSSD supports two representations for specifying the debug level. The simplest is to specify a decimal value from 0-9, which represents
	   enabling that level and all lower-level debug messages. The more comprehensive option is to specify a hexadecimal bitmask to enable or
	   disable specific levels (such as if you wish to suppress a level).

	   Currently supported debug levels:

	   0, 0x0010: Fatal failures. Anything that would prevent SSSD from starting up or causes it to cease running.

	   1, 0x0020: Critical failures. An error that doesn't kill the SSSD, but one that indicates that at least one major feature is not going
	   to work properly.

	   2, 0x0040: Serious failures. An error announcing that a particular request or operation has failed.

	   3, 0x0080: Minor failures. These are the errors that would percolate down to cause the operation failure of 2.

	   4, 0x0100: Configuration settings.

	   5, 0x0200: Function data.

	   6, 0x0400: Trace messages for operation functions.

	   7, 0x1000: Trace messages for internal control functions.

	   8, 0x2000: Contents of function-internal variables that may be interesting.

	   9, 0x4000: Extremely low-level tracing information.

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

	   Example: To log fatal failures, critical failures, serious failures and function data use 0x0270.

	   Example: To log fatal failures, configuration settings, function data, trace messages for internal control functions use 0x1310.

	   Note: The bitmask format of debug levels was introduced in 1.7.0.

	   Default: 0

SEE ALSO

       sssd(8), sssd.conf(5), sssd-ldap(5), sssd-krb5(5), sssd-simple(5), sssd-ipa(5), sssd-ad(5), sssd-sudo(5),sss_cache(8), sss_debuglevel(8),
       sss_groupadd(8), sss_groupdel(8), sss_groupshow(8), sss_groupmod(8), sss_useradd(8), sss_userdel(8), sss_usermod(8), sss_obfuscate(8),
       sss_seed(8), sssd_krb5_locator_plugin(8), sss_ssh_authorizedkeys(8), sss_ssh_knownhostsproxy(8),pam_sss(8).

AUTHORS

       The SSSD upstream - http://fedorahosted.org/sssd

SSSD
								    06/17/2014							 SSS_DEBUGLEVEL(8)