PAM_USERDB(8) Linux-PAM Manual PAM_USERDB(8)NAME
pam_userdb - PAM module to authenticate against a db database
SYNOPSIS
pam_userdb.so db=/path/database [debug] [crypt=[crypt|none]] [icase] [dump] [try_first_pass] [use_first_pass] [unknown_ok] [key_only]
DESCRIPTION
The pam_userdb module is used to verify a username/password pair against values stored in a Berkeley DB database. The database is indexed
by the username, and the data fields corresponding to the username keys are the passwords.
OPTIONS
crypt=[crypt|none]
Indicates whether encrypted or plaintext passwords are stored in the database. If it is crypt, passwords should be stored in the
database in crypt(3) form. If none is selected, passwords should be stored in the database as plaintext.
db=/path/database
Use the /path/database database for performing lookup. There is no default; the module will return PAM_IGNORE if no database is
provided.
debug
Print debug information.
dump
Dump all the entries in the database to the log. Don't do this by default!
icase
Make the password verification to be case insensitive (ie when working with registration numbers and such). Only works with plaintext
password storage.
try_first_pass
Use the authentication token previously obtained by another module that did the conversation with the application. If this token can
not be obtained then the module will try to converse. This option can be used for stacking different modules that need to deal with the
authentication tokens.
use_first_pass
Use the authentication token previously obtained by another module that did the conversation with the application. If this token can
not be obtained then the module will fail. This option can be used for stacking different modules that need to deal with the
authentication tokens.
unknown_ok
Do not return error when checking for a user that is not in the database. This can be used to stack more than one pam_userdb module
that will check a username/password pair in more than a database.
key_only
The username and password are concatenated together in the database hash as 'username-password' with a random value. if the
concatenation of the username and password with a dash in the middle returns any result, the user is valid. this is useful in cases
where the username may not be unique but the username and password pair are.
MODULE TYPES PROVIDED
The auth and account module types are provided.
RETURN VALUES
PAM_AUTH_ERR
Authentication failure.
PAM_AUTHTOK_RECOVERY_ERR
Authentication information cannot be recovered.
PAM_BUF_ERR
Memory buffer error.
PAM_CONV_ERR
Conversation failure.
PAM_SERVICE_ERR
Error in service module.
PAM_SUCCESS
Success.
PAM_USER_UNKNOWN
User not known to the underlying authentication module.
EXAMPLES
auth sufficient pam_userdb.so icase db=/etc/dbtest.db
SEE ALSO crypt(3), pam.conf(5), pam.d(5), pam(7)AUTHOR
pam_userdb was written by Cristian Gafton >gafton@redhat.com<.
Linux-PAM Manual 06/04/2011 PAM_USERDB(8)
Check Out this Related Man Page
PAM_UNIX(8) BSD System Manager's Manual PAM_UNIX(8)NAME
pam_unix -- UNIX PAM module
SYNOPSIS
[service-name] module-type control-flag pam_unix [options]
DESCRIPTION
The UNIX authentication service module for PAM provides functionality for two PAM categories: authentication and account management. In
terms of the module-type parameter, they are the ``auth'' and ``account'' features. It also provides a null function for session management.
UNIX Authentication Module
The UNIX authentication component provides functions to verify the identity of a user (pam_sm_authenticate()), which obtains the relevant
passwd(5) entry. It prompts the user for a password and verifies that this is correct with crypt(3).
The following options may be passed to the authentication module:
debug syslog(3) debugging information at LOG_DEBUG level.
use_first_pass If the authentication module is not the first in the stack, and a previous module obtained the user's password, that password
is used to authenticate the user. If this fails, the authentication module returns failure without prompting the user for a
password. This option has no effect if the authentication module is the first in the stack, or if no previous modules
obtained the user's password.
try_first_pass This option is similar to the use_first_pass option, except that if the previously obtained password fails, the user is
prompted for another password.
auth_as_self This option will require the user to authenticate himself as the user given by getlogin(2), not as the account they are
attempting to access. This is primarily for services like su(1), where the user's ability to retype their own password might
be deemed sufficient.
nullok If the password database has no password for the entity being authenticated, then this option will forgo password prompting,
and silently allow authentication to succeed.
UNIX Account Management Module
The UNIX account management component provides a function to perform account management, pam_sm_acct_mgmt(). The function verifies that the
authenticated user is allowed to login to the local user account by checking the password expiry date.
The following options may be passed to the management module:
debug syslog(3) debugging information at LOG_DEBUG level.
UNIX Password Management Module
The UNIX password management component provides a function to perform account management, pam_sm_chauthtok(). The function changes the
user's password.
The following options may be passed to the password module:
debug syslog(3) debugging information at LOG_DEBUG level.
no_warn suppress warning messages to the user. These messages include reasons why the user's authentication attempt was declined.
passwd_db=name Change the user's password only the specified password database. Valid password database names are:
files local password file
nis NIS password database
FILES
/etc/master.passwd default UNIX password database.
SEE ALSO passwd(1), getlogin(2), crypt(3), getpwent(3), syslog(3), nsswitch.conf(5), passwd(5), nis(8), pam(8)BSD February 26, 2005 BSD