Menu

MariaDB PAM Mapping: One Password, Several Identity Boundaries
📰

MariaDB PAM Mapping: One Password, Several Identity Boundaries

DEV Community: cybersecurity·SorrelThorncroft·10 days ago
#AHlFyGyo
#devtocybersecurity#devto#dev#mariadb#account
Reading 0:00
15s threshold

MariaDB PAM Mapping: One Password, Several Identity Boundaries

Delegating MariaDB authentication to PAM can remove a separate database password from the workflow. It also introduces several identities that must agree: the Unix account, the PAM service and policy, the mapped MariaDB account, and the database grants attached to that account. A successful password check is only the first part of authorization.

PAM authenticates; MariaDB still authorizes

MariaDB's PAM authentication plugin hands credential verification to the host's Pluggable Authentication Module stack. The database account still must exist and have privileges. The documentation makes this separation clear: PAM answers an authentication question, while MariaDB evaluates account privileges after the connection is associated with a principal.

The mapping layer matters when the Unix name does not match the database account. MariaDB documents pam_user_map for mapping Unix users and groups to MariaDB users.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.