pam_allow

- PAM authentication, account, session and password management PAM module to allow operations

Synopsis

pam_allow.so.1

Description

The pam_allow module implements all the PAM service module functions and returns PAM_SUCCESS for all calls. Opposite functionality is available in the pam_deny(5) module.

Proper Solaris authentication operation requires pam_unix_cred(5) be stacked above pam_allow.

The following options are interpreted:

debug

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

Errors

PAM_SUCCESS is always returned.

Examples

Example 1 Allowing ssh none

The following example is a pam.conf fragment that illustrates how to allow the SSHv2 userauth of “none”:

sshd-none  auth    required      pam_unix_cred.so.1
sshd-none  auth    sufficient    pam_allow.so.1
sshd-none  account sufficient    pam_allow.so.1
sshd-none  session sufficient    pam_allow.so.1
sshd-none  password sufficient   pam_allow.so.1

The equivalent configuration using /etc/pam.d/ would be the following entries in /etc/pam.d/sshd-none:

auth    required      pam_unix_cred.so.1
auth    sufficient    pam_allow.so.1
account sufficient    pam_allow.so.1
session sufficient    pam_allow.so.1
password sufficient   pam_allow.so.1

Example 2 Allowing Kiosk Automatic Login Service

The following example is a pam.conf fragment that illustrates how to allow gdm kiosk automatic login:

gdm-autologin auth  required    pam_unix_cred.so.1
gdm-autologin auth  sufficient  pam_allow.so.1

The equivalent configuration using /etc/pam.d/ would be the following entries in /etc/pam.d/gdm-autologin:

auth  required    pam_unix_cred.so.1
auth  sufficient  pam_allow.so.1

Attributes

See attributes(5) for descriptions of the following attributes:

See Also

libpam(3LIB), pam(3PAM), pam_sm(3PAM), syslog(3C), pam.conf(4), attributes(5), pam_deny(5), pam_unix_cred(5)

Notes

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

This module is intended to be used to either allow access to specific services names, or to all service names not specified (by specifying it as the default service stack).