Mercurial > prosody-modules
view mod_sasl2/README.md @ 5367:93d445b26063
mod_http_oauth2: Validate redirect URI depending on application type
Per https://openid.net/specs/openid-connect-registration-1_0.html
require that web applications use https:// and native applications must
use either http://localhost or a custom (non-https) URI.
Previous requirement that hostname matches that of client_uri is kept
for web applications.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Tue, 25 Apr 2023 19:49:41 +0200 |
parents | 5b77f4720bfe |
children | da942a3f3660 |
line wrap: on
line source
--- labels: - Stage-Beta summary: "XEP-0388: Extensible SASL Profile" --- Implementation of [XEP-0388: Extensible SASL Profile]. **Note: At the time of writing (Nov 2022) the version of the XEP implemented by this module is still working its way through the XSF standards process. See [PR #1214](https://github.com/xsf/xeps/pull/1214) for the current status.** ## Configuration This module honours the same configuration options as Prosody's existing [mod_saslauth](https://prosody.im/doc/modules/mod_saslauth). ## Developers mod_sasl2 provides some events you can hook to affect aspects of the authentication process: - `advertise-sasl-features` - `sasl2/c2s/success` - Priority 1000: Session marked as authenticated, success response created (`event.success`) - Priority -1000: Success response sent to client - Priority -1500: Updated <stream-features/> sent to client - `sasl2/c2s/failure` - `sasl2/c2s/error`