Mercurial > prosody-modules
view mod_sasl2/README.md @ 5185:09d6bbd6c8a4
mod_http_oauth2: Fix treatment of 'redirect_uri' parameter in code flow
It's optional and the one stored in the client registration should
really be used instead. RFC 6749 says an URI provided as parameter MUST
be validated against the stored one but does not say how.
Given that the client needs their secret to proceed, it seems fine to
leave this for later.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Thu, 02 Mar 2023 22:00:42 +0100 |
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`