Mercurial > prosody-modules
view mod_auth_pam/README.markdown @ 4260:c539334dd01a
mod_http_oauth2: Rescope oauth client config into users' storage
This produces client_id of the form owner@host/random and prevents
clients from being deleted by registering an account with the same name
and then deleting the account, as well as having the client
automatically be deleted when the owner account is removed.
On one hand, this leaks the bare JID of the creator to users. On the
other hand, it makes it obvious who made the oauth application.
This module is experimental and only for developers, so this can be
changed if a better method comes up.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Sat, 21 Nov 2020 23:55:10 +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