Mercurial > prosody-modules
view mod_muc_ping/README.markdown @ 5264:d3ebaef1ea7a
mod_http_oauth2: Correctly verify OAuth client credentials on revocation
Makes no sense to validate against username and password here, or using
a token to revoke another token, or itself?
In fact, upon further discussion, why do you need credentials to revoke
a token? If you are not supposed to have the token, revoking it seems
the most responsible thing to do with it, so it should be allowed, while
if you are supposed to have it, you should be allowed to revoke it.
| author | Kim Alvefur <zash@zash.se> |
|---|---|
| date | Tue, 21 Mar 2023 21:57:18 +0100 |
| parents | 59bedf167910 |
| children |
line wrap: on
line source
--- labels: - 'Stage-Obsolete' superseded_by: mod_muc summary: XEP-0410 Server Optimization (now supported by Prosody mod_muc) --- This module implements the [Server Optimization](https://xmpp.org/extensions/xep-0410.html#serveroptimization) part of [XEP-0410: MUC Self-Ping] # Usage The module is loaded on MUC components: ```lua Component "muc.example.com" "muc" modules_enabled = { "muc_ping"; } ``` # Configuration No options. # Compatibility It should work with Prosody up until 0.10.x. Prosody 0.11.x and trunk natively supports XEP-0410 so this module is **not** needed.