Copyright (c) 1998, Sun Microsystems, Inc. All Rights Reserved
The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
cc [ flag ... ] file ... -lpam [ library ... ] #include <security/pam_appl.h> int pam_acct_mgmt(pam_handle_t *pamh, int flags);
The pam_acct_mgmt() function is called to determine if the current user's account is valid. It checks for password and account expiration, and verifies access hour restrictions. This function is typically called after the user has been authenticated with pam_authenticate(3PAM).
The pamh argument is an authentication handle obtained by a prior call to pam_start(). The following flags may be set in the flags field:
PAM_SILENT
The account management service should not generate any messages.
PAM_DISALLOW_NULL_AUTHTOK
The account management service should return PAM_NEW_AUTHTOK_REQD if the user has a null authentication token.
Upon successful completion, PAM_SUCCESS is returned. In addition to the error return values described in pam(3PAM), the following values may be returned:
PAM_USER_UNKNOWN
User not known to underlying account management module.
PAM_AUTH_ERR
Authentication failure.
PAM_NEW_AUTHTOK_REQD
New authentication token required. This is normally returned if the machine security policies require that the password should be changed because the password is NULL or has aged.
PAM_ACCT_EXPIRED
User account has expired.
See attributes(5) for description of the following attributes:
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
| Interface Stability | Stable |
| MT-Level | MT-Safe with exceptions |
pam(3PAM), pam_authenticate(3PAM), pam_start(3PAM), libpam(3LIB), attributes(5)
The interfaces in libpam are MT-Safe only if each thread within the multithreaded application uses its own PAM handle.