Go to main content

man pages section 7: Standards, Environments, Macros, Character Sets, and Miscellany

Exit Print View

Updated: Wednesday, January 24, 2018



pam_tsol_account - PAM account management module for Trusted Extensions




The Solaris Trusted Extensions service module for PAM, /usr/lib/security/pam_tsol_account.so.1, checks account limitations that are related to labels. The pam_tsol_account.so.1 module is a shared object that can be dynamically loaded to provide the necessary functionality upon demand. Its path is specified in the PAM configuration file.

pam_tsol_account.so.1 contains a function to perform account management, pam_sm_acct_mgmt(). The function checks for the allowed label range for the user. The allowable label range is set by the defaults in the label_encodings(5) file. These defaults can be overridden by entries in the user_attr(5) database.

By default, this module requires that remote hosts connecting to the global zone must have a CIPSO host type. To disable this policy, add the allow_unlabeled keyword as an option to the entry in pam.conf(5), as in:

other  account required    pam_tsol_account allow_unlabeled

The equivalent PAM configuration in /etc/pam.d/ would be the following entry in /etc/pam.d/other:

account required           pam_tsol_account allow_unlabeled


The following options can be passed to the module:


Allows remote connections from hosts with unlabeled template types.


Provides debugging information at the LOG_DEBUG level. See syslog(3C).

Return Values

The following values are returned:


The account is valid for use at this time and label.


The current process label is outside the user's label range, or the label information for the process is unavailable, or the remote host type is not valid.

Other values

Returns an error code that is consistent with typical PAM operations. For information on error-related return values, see the pam(3PAM) man page.


See attributes(7) for description of the following attributes:

Interface Stability
MT Level
MT-Safe with exceptions

The interfaces in libpam(3LIB) are MT-Safe only if each thread within the multi-threaded application uses its own PAM handle.

See Also

keylogin(1), syslog(3C), libpam(3LIB), pam(3PAM), pam_sm_acct_mgmt(3PAM), pam_start(3PAM), label_encodings(5), pam.conf(5), user_attr(5), attributes(7)


The functionality described on this manual page is available only if the system is configured with Trusted Extensions.