The pam authentication plugin allows MariaDB to offload user authentication to the system's Pluggable Authentication Module (PAM) framework. PAM is an authentication framework used by Linux, FreeBSD, Solaris, and other Unix-like operating systems.
Note: Windows does not support PAM, so the pam authentication plugin does not support Windows. However, one can use a MariaDB client on Windows to connect to MariaDB server that is installed on a Unix-like operating system and that is configured to use the pam authentication plugin. For an example of how to do this, see the blog post: MariaDB: Improve Security with Two-Step Verification.
PAM makes it possible to implement various authentication scenarios of different complexity. For example,
/etc/shadow (indeed, this is what a default PAM configuration usually does). See the pam_unix PAM module. pam_ldap PAM module. pam_lsass, pam_winbind, and pam_centrifydc PAM modules. pam_google_authenticator and pam_securid PAM modules. pam_ssh PAM module. pam_user_map PAM module. pam_time PAM module. The pam authentication plugin's library is provided in binary packages in all releases on Linux.
Although the plugin's shared library is distributed with MariaDB by default, the plugin is not actually installed by MariaDB by default. There are two methods that can be used to install the plugin with MariaDB.
The first method can be used to install the plugin without restarting the server. You can install the plugin dynamically by executing INSTALL SONAME or INSTALL PLUGIN. For example:
INSTALL SONAME 'auth_pam';
The second method can be used to tell the server to load the plugin when it starts up. The plugin can be installed this way by providing the --plugin-load or the --plugin-load-add options. This can be specified as a command-line argument to mysqld or it can be specified in a relevant server option group in an option file. For example:
[mariadb] ... plugin_load_add = auth_pam
Starting in MariaDB 10.4.0, the auth_pam shared library actually refers to version 2.0 of the pam authentication plugin. MariaDB 10.4.0 and later also provides version 1.0 of the plugin as the auth_pam_v1 shared library.
In MariaDB 10.4.0 and later, if you need to install version 1.0 of the authentication plugin instead of version 2.0, then you can do so. For example, with INSTALL SONAME or INSTALL PLUGIN:
INSTALL SONAME 'auth_pam_v1';
Or by specifying in a relevant server option group in an option file:
[mariadb] ... plugin_load_add = auth_pam_v1
You can uninstall the plugin dynamically by executing UNINSTALL SONAME or UNINSTALL PLUGIN. For example:
UNINSTALL SONAME 'auth_pam';
If you installed the plugin by providing the --plugin-load or the --plugin-load-add options in a relevant server option group in an option file, then those options should be removed to prevent the plugin from being loaded the next time the server is restarted.
If you installed version 1.0 of the authentication plugin, then you can uninstall that by executing a similar statement for auth_pam_v1. For example:
UNINSTALL SONAME 'auth_pam_v1';
The pam authentication plugin tells MariaDB to delegate the authentication to the PAM authentication framework. How exactly that authentication is performed depends on how PAM was configured.
PAM is divided into services. PAM services are configured by PAM configuration files. Typically, the global PAM configuration file is located at /etc/pam.conf and PAM directory-based configuration files for individual services are located in /etc/pam.d/.
If you want to use a PAM service called mariadb for your MariaDB PAM authentication, then the PAM configuration file for that service would also be called mariadb, and it would typically be located at /etc/pam.d/mariadb.
For example, here is a minimal PAM service configuration file that performs simple password authentication with UNIX passwords:
auth required pam_unix.so audit account required pam_unix.so audit
Let's breakdown this relatively simple PAM service configuration file.
Each line of a PAM service configuration file has the following general format:
type control module-path module-arguments
The above PAM service configuration file instructs the PAM authentication framework that for successful authentication (i.e. type=auth), it is required that the pam_unix.so PAM module returns a success.
The above PAM service configuration file also instructs the PAM authentication framework that for an account (i.e. type=account) to be valid, it is required that the pam_unix.so PAM module returns a success.
PAM also supports session and password types, but MariaDB's pam authentication plugin does not support those.
The above PAM service configuration file also provides the audit module argument to the pam_unix PAM module. The pam_unix manual says that this module argument enables extreme debug logging to the syslog.
On most systems, you can find many other examples of PAM service configuration files in your /etc/pam.d/ directory.
If you configure PAM to use the pam_unix PAM module (as in the above example), then you might notice on some systems that this will fail by default with errors like the following:
Apr 14 12:56:23 localhost unix_chkpwd[3332]: check pass; user unknown Apr 14 12:56:23 localhost unix_chkpwd[3332]: password check failed for user (alice) Apr 14 12:56:23 localhost mysqld: pam_unix(mysql:auth): authentication failure; logname= uid=991 euid=991 tty= ruser= rhost= user=alice
The problem is that on some systems, the pam_unix PAM module needs access to /etc/shadow in order to function, and most systems only allow root to access that file by default.
Newer versions of PAM do not have this limitation, so you may want to try upgrading your version of PAM to see if that fixes the issue.
If that does not work, then you can work around this problem by giving the user that runs mysqld access to /etc/shadow. For example, if the mysql user runs mysqld, then you could do the following:
sudo groupadd shadow sudo usermod -a -G shadow mysql sudo chown root:shadow /etc/shadow sudo chmod g+r /etc/shadow
And then you would have to restart the server.
At that point, the server should be able to read /etc/shadow.
Starting in MariaDB 10.4.0, the pam authentication plugin uses a setuid wrapper to perform its PAM checks, so it should not need any special workarounds to perform privileged operations, such as reading /etc/shadow when using the pam_unix PAM module. See MDEV-7032 for more information.
Similar to all other authentication plugins, to create a user in MariaDB which uses the pam authentication plugin, you would execute CREATE USER while specifying the name of the plugin in the IDENTIFIED VIA clause. For example:
CREATE USER username@hostname IDENTIFIED VIA pam;
If SQL_MODE does not have NO_AUTO_CREATE_USER set, then you can also create the user this way with GRANT. For example:
GRANT SELECT ON db.* TO username@hostname IDENTIFIED VIA pam;
You can also specify a PAM service name for MariaDB to use by providing it with the USING clause. For example:
CREATE USER username@hostname IDENTIFIED VIA pam USING 'mariadb';
This line creates a user that needs to be authenticated via the pam authentication plugin using the PAM service name mariadb. As mentioned in a previous section, this service's configuration file will typically be present in /etc/pam.d/mariadb.
If no service name is specified, then the plugin will use mysql as the default PAM service name.
For clients that use the libmysqlclient or MariaDB Connector/C libraries, MariaDB provides two client authentication plugins that are compatible with the pam authentication plugin:
dialog mysql_clear_password When connecting with a client or utility to a server as a user account that authenticates with the pam authentication plugin, you may need to tell the client where to find the relevant client authentication plugin by specifying the --plugin-dir option. For example:
mysql --plugin-dir=/usr/local/mysql/lib64/mysql/plugin --user=alice
Both the dialog and the mysql_clear_password client authentication plugins transmit the password to the server in clear text. Therefore, when you use the pam authentication plugin, it is incredibly important to encrypt client connections using TLS to prevent the clear-text passwords from being seen by unauthorized users.
dialogUsually the pam authentication plugin uses the dialog client authentication plugin to communicate with the user. This client authentication plugin allows MariaDB to support arbitrarily complex PAM configurations with regular or one-time passwords, challenge-response, multiple questions, or just about anything else. When using a MariaDB client library, there is no need to install or enable anything — the dialog client authentication plugin is loaded by the client library completely automatically and transparently for the application.
The dialog client authentication plugin was developed by MariaDB, so MySQL's clients and client libraries as well as third party applications that bundle MySQL's client libraries do not support the dialog client authentication plugin out of the box. If the server tells an unsupported client to use the dialog client authentication plugin, then the client is likely to throw an error like the following:
ERROR 2059 (HY000): Authentication plugin 'dialog' cannot be loaded: /usr/lib/mysql/plugin/dialog.so: cannot open shared object file: No such file or directory
For some libraries or applications, this problem can be fixed by copying dialog.so or dialog.dll from a MariaDB client installation that is compatible with the system into the system's MySQL client authentication plugin directory. However, not all clients are compatible with the dialog client authentication plugin, so this may not work for every client.
If your client does not support the dialog client authentication plugin, then you may need to use the mysql_clear_password client authentication plugin instead.
The dialog client authentication plugin transmits the password to the server in clear text. Therefore, when you use the pam authentication plugin, it is incredibly important to encrypt client connections using TLS to prevent the clear-text passwords from being seen by unauthorized users.
mysql_clear_passwordThe mysql_clear_password client authentication plugin and the pam_use_cleartext_plugin system variable were first added in MariaDB 5.5.32 and MariaDB 10.1.1.
Users can instruct the pam authentication plugin to use the mysql_clear_password client authentication plugin instead of the dialog client authentication plugin by configuring the pam_use_cleartext_plugin system variable on the server. It can be set in a relevant server option group in an option file. For example:
[mariadb] ... pam_use_cleartext_plugin
It is important to note that the mysql_clear_password plugin has very limited functionality.
mysql_clear_password client authentication plugin only supports PAM services that require password-based authentication. mysql_clear_password client authentication plugin also only supports PAM services that ask the user a single question. mysql_clear_password client authentication plugin. In that case, the dialog client authentication plugin will have to be used instead. The mysql_clear_password client authentication plugin transmits the password to the server in clear text. Therefore, when you use the pam authentication plugin, it is incredibly important to encrypt client connections using TLS to prevent the clear-text passwords from being seen by unauthorized users.
The mysql_clear_password client authentication plugin is similar to MySQL's mysql_clear_password client authentication plugin.
The mysql_clear_password client authentication plugin is compatible with MySQL clients and most MySQL client libraries, while the dialog client authentication plugin is not always compatible with them. Therefore, the mysql_clear_password client authentication plugin is most useful if you need some kind of MySQL compatibility in your environment, but you still want to use the pam authentication plugin.
Even though the mysql_clear_password client authentication plugin is compatible with MySQL clients and most MySQL client libraries, the mysql_clear_password client authentication plugin may be disabled by default by these clients and client libraries. For example, MySQL's version of the mysql command-line client has the --enable-cleartext-plugin option that must be set in order to use the mysql_clear_password client authentication plugin. For example:
mysql --enable-cleartext-plugin --user=alice -p
Other clients may require other methods to enable the authentication plugin. For example, MySQL Workbench has a checkbox titled Enable Cleartext Authentication Plugin under the Advanced tab on the connection configuration screen.
For applications that use MySQL's libmysqlclient, the authentication plugin can be enabled by setting the MYSQL_ENABLE_CLEARTEXT_PLUGIN option with the mysql_options() function. For example:
mysql_options(mysql, MYSQL_ENABLE_CLEARTEXT_PLUGIN, 1);
For MySQL compatibility, MariaDB Connector/C also allows applications to set the MYSQL_ENABLE_CLEARTEXT_PLUGIN option with the mysql_optionsv function. However, this option does not actually do anything in MariaDB Connector/C, because the mysql_clear_password client authentication plugin is always enabled for MariaDB clients and client libraries.
MariaDB Connector/C supports pam authentication using the client authentication plugins mentioned in the previous section since MariaDB Connector/C 2.1.0, regardless of the value of the pam_use_cleartext_plugin system variable.
MariaDB Connector/ODBC supports pam authentication using the client authentication plugins mentioned in the previous section since MariaDB Connector/ODBC 1.0.0, regardless of the value of the pam_use_cleartext_plugin system variable.
MariaDB Connector/J supports pam v1 authentication since MariaDB Connector/J 1.4.0, regardless of the value of the pam_use_cleartext_plugin system variable.
MariaDB Connector/J supports pam v2 authentication since MariaDB Connector/J 2.4.4, regardless of the value of the pam_use_cleartext_plugin system variable.
MariaDB Connector/Node.js supports pam authentication since MariaDB Connector/Node.js 0.7.0, regardless of the value of the pam_use_cleartext_plugin system variable.
MySqlConnector for ADO.NET supports pam authentication since MySqlConnector 0.20.0, but only if the pam_use_cleartext_plugin system variable is enabled on the server.
Errors and messages from PAM modules are usually logged using the syslog daemon with the authpriv facility. To determine the specific log file where the authpriv facility is logged, you can check rsyslog.conf.
On RHEL, CentOS, Fedora, and other similar Linux distributions, the default location for these messages is usually /var/log/secure.
On Debian, Ubuntu, and other similar Linux distributions, the default location for these messages is usually /var/log/auth.log.
For example, the syslog can contain messages like the following when MariaDB's pam authentication plugin is configured to use the pam_unix PAM module, and the user enters an incorrect password:
Jan 9 05:35:41 ip-172-30-0-198 unix_chkpwd[1205]: password check failed for user (foo) Jan 9 05:35:41 ip-172-30-0-198 mysqld: pam_unix(mariadb:auth): authentication failure; logname= uid=997 euid=997 tty= ruser= rhost= user=foo
MariaDB's pam authentication plugin can also log additional verbose debug logging to the error log. This is only done if the plugin is a debug build and if pam_debug is set.
The output looks like this:
PAM: pam_start(mariadb, alice) PAM: pam_authenticate(0) PAM: conv: send(Enter PASSCODE:) PAM: conv: recv(123456789) PAM: pam_acct_mgmt(0) PAM: pam_get_item(PAM_USER) PAM: status = 0 user = ��\>
The pam_exec PAM module can be used to implement some custom logging. This can be very useful when debugging certain kinds of issues.
For example, first, create a script that writes the log output:
tee /tmp/pam_log_script.sh <<EOF
#!/bin/bash
echo "\${PAM_SERVICE}:\${PAM_TYPE} - \${PAM_RUSER}@\${PAM_RHOST} is authenticating as \${PAM_USER}"
EOF
chmod 0775 /tmp/pam_log_script.sh
And then change the PAM service configuration to execute the script using the pam_exec PAM module. For example:
auth optional pam_exec.so log=/tmp/pam_output.txt /tmp/pam_log_script.sh auth required pam_unix.so audit account optional pam_exec.so log=/tmp/pam_output.txt /tmp/pam_log_script.sh account required pam_unix.so audit
Whenever the above PAM service is used, the output of the script will be written to /tmp/pam_output.txt. It may look similar to this:
*** Tue May 14 14:53:23 2019 mariadb:auth - @ is authenticating as alice *** Tue May 14 14:53:25 2019 mariadb:account - @ is authenticating as alice *** Tue May 14 14:53:28 2019 mariadb:auth - @ is authenticating as alice *** Tue May 14 14:53:31 2019 mariadb:account - @ is authenticating as alice
Even when using the pam authentication plugin, the authenticating PAM user account still needs to exist in MariaDB, and the account needs to have privileges in the database. Creating these MariaDB accounts and making sure the privileges are correct can be a lot of work. To decrease the amount of work involved, some users would like to be able to map a PAM user to a different MariaDB user. For example, let’s say that alice and bob are both DBAs. It would be nice if each of them could log into MariaDB with their own PAM username and password, while MariaDB sees both of them as the same dba user. That way, there is only one MariaDB account to keep track of. See User and Group Mapping with PAM for more information on how to do this.
There are many PAM modules. The ones described below are the ones that have been seen most often by MariaDB.
The pam_unix PAM module provides support for Unix password authentication. It is the default PAM module on most systems.
For a tutorial on setting up PAM authentication and user or group mapping with Unix authentication, see Configuring PAM Authentication and User Mapping with Unix Authentication.
The pam_user_map PAM module was developed by MariaDB to support user and group mapping.
The pam_ldap PAM module provides support for LDAP authentication.
For a tutorial on setting up PAM authentication and user or group mapping with LDAP authentication, see Configuring PAM Authentication and User Mapping with LDAP Authentication.
This can also be configured for Active Directory authentication.
The pam_sss PAM module provides support for authentication with System Security Services Daemon (SSSD).
This can be configured for Active Directory authentication.
The pam_lsass PAM module provides support for Active Directory authentication. It is provided by PowerBroker Identity Services – Open Edition.
The pam_winbind PAM module provides support for Active Directory authentication. It is provided by winbindd from the samba suite.
This PAM module converts all provided user names to lowercase. There is no way to disable this functionality. If you do not want to be forced to use all lowercase user names, then you may need to configure the pam_winbind_workaround system variable. See MDEV-18686 for more information.
The pam_centrifydc PAM module provides support for Active Directory authentication. It integrates with the commercial Active Directory Bridge from Centrify.
The pam_krb5 PAM module provides support for Kerberos authentication.
This can be configured for Active Directory authentication.
The pam_google_authenticator PAM module provides two-factor identification with Google Authenticator. It is from Google's google-authenticator-libpam open-source project. The PAM module should work with the open-source mobile apps built by Google's google-authenticator and google-authenticator-android projects as well as the the closed source Google Authenticator mobile apps that are present in each mobile app store.
For an example of how to use this PAM module, see the blog post: MariaDB: Improve Security with Two-Step Verification.
The pam_securid PAM module provides support for multi-factor authentication. It is part of the commercial RSA SecurID Suite.
Note that current versions of this module are not safe for multi-threaded environments, and the vendor does not officially support the product on MariaDB. See MDEV-10361 about that. However, the module may work with MariaDB 10.4.0 and above.
The pam_ssh PAM module provides authentication using SSH keys.
The pam_time PAM module provides time-controlled access.
MariaDB is a multi-threaded program, which means that different connections concurrently run in different threads. Current versions of MariaDB's pam authentication plugin execute PAM module code in the server address space. This means that any PAM modules used with MariaDB must be safe for multi-threaded environments. Otherwise, if multiple clients try to authenticate with the same PAM module in parallel, undefined behavior can occur. For example, the pam_fprintd PAM module is not safe for multi-threaded environments, and if you use it with MariaDB, you may experience server crashes.
Starting in MariaDB 10.4.0, the pam authentication plugin isolates PAM module code from the server address space, so even PAM modules that are known to be unsafe for multi-threaded environments should not cause issues with MariaDB. See MDEV-15473 for more information.
When a password validation plugin is enabled, MariaDB won't allow an account to be created if the password validation plugin says that the account's password is too weak. This creates a problem for accounts that authenticate with the pam authentication plugin, since MariaDB has no knowledge of the user's password. When a user tries to create an account that authenticates with the pam authentication plugin, the password validation plugin would throw an error, even with strict_password_validation=OFF set.
The workaround is to uninstall the password validation plugin with UNINSTALL PLUGIN, and then create the account, and then reinstall the password validation plugin with INSTALL PLUGIN.
For example:
INSTALL PLUGIN simple_password_check SONAME 'simple_password_check'; Query OK, 0 rows affected (0.002 sec) SET GLOBAL strict_password_validation=OFF; Query OK, 0 rows affected (0.000 sec) CREATE USER ''@'%' IDENTIFIED VIA pam USING 'mariadb'; ERROR 1819 (HY000): Your password does not satisfy the current policy requirements UNINSTALL PLUGIN simple_password_check; Query OK, 0 rows affected (0.000 sec) CREATE USER ''@'%' IDENTIFIED VIA pam USING 'mariadb'; Query OK, 0 rows affected (0.000 sec) INSTALL PLUGIN simple_password_check SONAME 'simple_password_check'; Query OK, 0 rows affected (0.001 sec)
Starting in MariaDB 10.4.0, accounts that authenticate with the pam authentication plugin should be exempt from password validation checks. See MDEV-12321 and MDEV-10457 for more information.
SELinux may cause issues when using the pam authentication plugin. For example, using pam_unix with the pam authentication plugin while SELinux is enabled can sometimes lead to SELinux errors involving unix_chkpwd, such as the following::
Apr 14 12:37:59 localhost setroubleshoot: Plugin Exception restorecon_source Apr 14 12:37:59 localhost setroubleshoot: SELinux is preventing /usr/sbin/unix_chkpwd from execute access on the file . For complete SELinux messages. run sealert -l c56fe6e0-c78c-4bdb-a80f-27ef86a1ea85 Apr 14 12:37:59 localhost python: SELinux is preventing /usr/sbin/unix_chkpwd from execute access on the file . ***** Plugin catchall (100. confidence) suggests ************************** If you believe that unix_chkpwd should be allowed execute access on the file by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # grep unix_chkpwd /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp
Sometimes issues like this can be fixed by updating the system's SELinux policies. You may be able to update the policies using audit2allow. See SELinux: Generating SELinux Policies with audit2allow for more information.
If you can't get the pam authentication plugin to work with SELinux at all, then it can help to disable SELinux entirely. See SELinux: Changing SELinux's Mode for information on how to do this.
You may find the following PAM-related tutorials helpful:
| Version | Status | Introduced |
|---|---|---|
| 2.0 | Beta | MariaDB 10.4.0 |
| 1.0 | Stable | MariaDB 10.0.10 |
| 1.0 | Beta | MariaDB 5.2.10 |
pam_debug--pam-debug boolean OFF pam_use_cleartext_pluginmysql_clear_password client authentication plugin instead of the dialog client authentication plugin. This may be needed for compatibility reasons, but it only supports simple PAM configurations that don't require any input besides a password. --pam-use-cleartext-plugin boolean OFF pam_winbind_workaroundpam_winbind PAM module, which is known to convert all user names to lowercase, and which does not allow this behavior to be disabled. --pam-winbind-workaround boolean OFF pamOFF - Disables the plugin without removing it from the mysql.plugins table. ON - Enables the plugin. If the plugin cannot be initialized, then the server will still continue starting up, but the plugin will be disabled. FORCE - Enables the plugin. If the plugin cannot be initialized, then the server will fail to start with an error. FORCE_PLUS_PERMANENT - Enables the plugin. If the plugin cannot be initialized, then the server will fail to start with an error. In addition, the plugin cannot be uninstalled with UNINSTALL SONAME or UNINSTALL PLUGIN while the server is running. --pam=value enumerated ON OFF, ON, FORCE, FORCE_PLUS_PERMANENT
© 2019 MariaDB
Licensed under the Creative Commons Attribution 3.0 Unported License and the GNU Free Documentation License.
https://mariadb.com/kb/en/authentication-plugin-pam/