Mercurial > prosody-modules
view mod_auth_pam/README.markdown @ 5366:db4c66a1d24b
mod_http_oauth2: Fill in some client metadata defaults
Explicit > Implicit
Maybe we should actually use these for something as well? :)
It's is somewhat an open question of how strictly we should enforce
things in the client metadata given that it is somewhat extensible.
Especially some of these enum fields which have corresponding IANA
registries.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Tue, 25 Apr 2023 18:09:08 +0200 |
parents | d407397d05ca |
children |
line wrap: on
line source
--- labels: - 'Stage-Alpha' - 'Type-Auth' summary: PAM authentication module --- Introduction ============ This module makes Prosody authenticate users against PAM (Linux Pluggable Authentication Modules) Dependencies ============ The module depends on [lua-pam](https://github.com/devurandom/lua-pam) and [LuaPosix](https://github.com/luaposix/luaposix). Setup ===== Create a `/etc/pam.d/xmpp` with something like this: auth [success=1 default=ignore] pam_unix.so obscure sha512 nodelay auth requisite pam_deny.so auth required pam_permit.so And switch authentication provider in the Prosody config: authentication = "pam" Compatibility ============= Compatible with 0.9 and up