Hallo, dies ist ein Test.

PWD: /www/data-lst1/unixsoft/unixsoft/kaempfer/.public_html

Running in File Mode
Relative path: ././../../../../../../usr/man/man3pam/pam_sm_acct_mgmt.3pam
Real path: /usr/share/man/man3pam/pam_sm_acct_mgmt.3pam
Zurück

'\" te .\" Copyright (c) 1998, 2023, Oracle and/or its affiliates. .TH pam_sm_acct_mgmt 3PAM "15 Mar 2023" "Oracle Solaris 11.4" "PAM Library Functions" .SH NAME pam_sm_acct_mgmt \- service provider implementation for pam_acct_mgmt .SH SYNOPSIS .LP .nf \fBcc\fR [ \fIflag\fR ... ] \fIfile\fR ... \fB-lpam\fR [ \fIlibrary\fR ... ] #include <security/pam_appl.h> #include <security/pam_modules.h> \fBint\fR \fBpam_sm_acct_mgmt\fR(\fBpam_handle_t *\fR\fIpamh\fR, \fBint\fR \fIflags\fR, \fBint\fR \fIargc\fR, \fBconst char **\fR\fIargv\fR); .fi .SH DESCRIPTION .sp .LP In response to a call to \fBpam_acct_mgmt\fR(3PAM), the \fBPAM\fR framework calls \fBpam_sm_acct_mgmt()\fR from the modules listed in the \fBpam.conf\fR(5) file or the relevant \fB/etc/pam.d/\fR\fIservice\fR file. The account management provider supplies the back-end functionality for this interface function. Applications should not call this \fBAPI\fR directly. .sp .LP The \fBpam_sm_acct_mgmt()\fR function determines whether or not the current user's account and password are valid. This includes the following checks: .RS +4 .TP .ie t \(bu .el o The account is not locked or expired .RE .RS +4 .TP .ie t \(bu .el o The user's password is not expired and does not need to be changed .RE .RS +4 .TP .ie t \(bu .el o The user's account has not been inactive for too long .RE .RS +4 .TP .ie t \(bu .el o The \fB/etc/nologin\fR file is not present, unless the user has a uid of 0, has the root role, or is assigned the \fBsolaris.system.maintenance\fR authorization (see \fBnologin\fR(5)) .RE .sp .LP The user in question is specified by a prior call to \fBpam_start\fR(3PAM), and is referenced by the authentication handle, \fIpamh\fR, which is passed as the first argument to \fBpam_sm_acct_mgmt()\fR. The following flags may be set in the \fIflags\fR field: .sp .ne 2 .mk .na \fB\fBPAM_SILENT\fR\fR .ad .RS 29n .rt The account management service should not generate any messages. .RE .sp .ne 2 .mk .na \fB\fBPAM_LOGINS_DISABLED\fR\fR .ad .RS 29n .rt Logins for non-root/maintenance users are disabled due to the presence of the \fB/etc/nologin\fR file. See \fBnologin\fR(5). .RE .sp .ne 2 .mk .na \fB\fBPAM_DISALLOW_NULL_AUTHTOK\fR\fR .ad .RS 29n .rt The account management service should return \fBPAM_NEW_AUTHTOK_REQD\fR if the user has a null authentication token. .RE .sp .LP The \fIargc\fR argument represents the number of module options passed in from the configuration file \fBpam.conf\fR(5) or the relevant \fB/etc/pam.d/\fR\fIservice\fR file. The \fIargv\fR argument specifies the module options, which are interpreted and processed by the account management service. Please refer to the specific module man pages for the various available \fIoptions\fR. If an unknown option is passed to the module, an error should be logged through \fBsyslog\fR(3C) and the option ignored. .sp .LP If an account management module determines that the user password has aged or expired, it should save this information as state in the authentication handle, \fIpamh\fR, using \fBpam_set_data\fR(3PAM). \fBpam_chauthtok\fR(3PAM) uses this information to determine which passwords have expired. .SH RETURN VALUES .sp .LP If there are no restrictions to logging in, \fBPAM_SUCCESS\fR is returned. The following error values may also be returned upon error: .sp .ne 2 .mk .na \fB\fBPAM_USER_UNKNOWN\fR\fR .ad .RS 24n .rt User not known to underlying authentication module. .RE .sp .ne 2 .mk .na \fB\fBPAM_NEW_AUTHTOK_REQD\fR\fR .ad .RS 24n .rt New authentication token required. .RE .sp .ne 2 .mk .na \fB\fBPAM_ACCT_EXPIRED\fR\fR .ad .RS 24n .rt User account has expired. .RE .sp .ne 2 .mk .na \fB\fBPAM_PERM_DENIED\fR\fR .ad .RS 24n .rt User denied access to account at this time. .RE .sp .ne 2 .mk .na \fB\fBPAM_IGNORE\fR\fR .ad .RS 24n .rt Ignore underlying account module regardless of whether the control flag is \fBrequired\fR, \fBoptional\fR, or \fBsufficient\fR. .RE .SH ATTRIBUTES .sp .LP See \fBattributes\fR(7) for descriptions of the following attributes: .sp .TS tab( ) box; cw(2.75i) |cw(2.75i) lw(2.75i) |lw(2.75i) . ATTRIBUTE TYPE ATTRIBUTE VALUE _ Interface Stability Committed _ MT-Level MT-Safe with exceptions .TE .sp .sp .LP The interfaces in \fBlibpam\fR are MT-Safe only if each thread within the multithreaded application uses its own \fBPAM\fR handle. .SH SEE ALSO .sp .LP \fBsyslog\fR(3C), \fBlibpam\fR(3LIB), \fBpam\fR(3PAM), \fBpam_acct_mgmt\fR(3PAM), \fBpam_chauthtok\fR(3PAM), \fBpam_set_data\fR(3PAM), \fBpam_sm\fR(3PAM), \fBpam_start\fR(3PAM), \fBnologin\fR(5), \fBpam.conf\fR(5), \fBattributes\fR(7) .SH NOTES .sp .LP If the \fBPAM_REPOSITORY\fR \fIitem_type\fR is set and a service module does not recognize the type, the service module does not process any information, and returns \fBPAM_IGNORE\fR. If the \fBPAM_REPOSITORY\fR \fIitem_type\fR is not set, a service module performs its default action. .SH HISTORY .sp .LP Support for checking for \fB/etc/nologin\fR in \fBpam_sm_acct_mgmt()\fR and the \fBPAM_LOGINS_DISABLED\fR return value was added in Solaris 11.2.0. .sp .LP The \fBpam_sm_acct_mgmt()\fR \fBAPI\fR was introduced in Solaris 2.6.