Mercurial > prosody-modules
view mod_auth_pam/README.markdown @ 5796:93d6e9026c1b
mod_http_oauth2: Do not enforce PKCE on Device and OOB flows
PKCE does not appear to be used with the Device flow. I have found no
mention of any interaction between those standards. Since no data is
delivered via redirects in these cases, PKCE may not serve any purpose.
This is mostly a problem because we reuse the authorization code to
implement the Device and OOB flows.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Fri, 15 Dec 2023 12:10:07 +0100 |
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