Mercurial > prosody-modules
view mod_cloud_notify_extensions/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 | 5f1120c284c5 |
| children | fed5995180c5 |
line wrap: on
line source
--- summary: "Tigase custom push extensions for iOS" labels: - 'Stage-Beta' rockspec: dependencies: - mod_cloud_notify_encrypted - mod_cloud_notify_priority_tag - mod_cloud_notify_filters ... Introduction ============ This is a meta-module that simply enables all the modules required to support Siskin or Snikket iOS on a Prosody server. These are currently: - mod_cloud_notify_encrypted - mod_cloud_notify_priority_tag - mod_cloud_notify_filters See the individual module pages for more details. In particular, mod_cloud_notify_encrypted depends on [luaossl](http://25thandclement.com/~william/projects/luaossl.html), which must be installed. It is available in Debian via apt as [`lua-luaossl`](https://tracker.debian.org/pkg/lua-luaossl) or via `luarocks install luaossl`. Note: On MUC services you should also load mod_muc_offline_delivery directly under the MUC component in your config file, that is not handled by this module. Configuration ============= There is no configuration for this module, just add it to modules\_enabled as normal. Compatibility ============= ----- ------- 0.12 Works ----- ------- 0.11 Should work ----- ------- trunk Works ----- -------