Mercurial > prosody-modules
view mod_cloud_notify_encrypted/README.md @ 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 | 7f8b0830bf40 |
| children |
line wrap: on
line source
--- labels: - 'Stage-Alpha' summary: 'Support for encrypted payloads in push notifications' rockspec: dependencies: - mod_cloud_notify ... Introduction ============ This module implements support for a [Encrypted Push Notifications](https://xeps.tigase.net//docs/push-notifications/encrypt/), a custom extension to [XEP-0357: Push Notifications](https://xmpp.org/extensions/xep-0357.html). It is planned that this will evolve to a XEP in the near future. Details ======= Add to modules_enabled, there are no configuration options. Depends on [luaossl](http://25thandclement.com/~william/projects/luaossl.html) which is available in Debian as [`lua-luaossl`](https://tracker.debian.org/pkg/lua-luaossl) or via `luarocks install luaossl`. Compatibility ============= Not tested, but hopefully works on 0.11.x and later.