Mercurial > prosody-modules
view mod_cloud_notify_encrypted/README.md @ 5682:527c747711f3
mod_http_oauth2: Limit revocation to clients own tokens in strict mode
RFC 7009 section 2.1 states:
> The authorization server first validates the client credentials (in
> case of a confidential client) and then verifies whether the token was
> issued to the client making the revocation request. If this
> validation fails, the request is refused and the client is informed of
> the error by the authorization server as described below.
The first part was already covered (in strict mode). This adds the later
part using the hash of client_id recorded in 0860497152af
It still seems weird to me that revoking a leaked token should not be
allowed whoever might have discovered it, as that seems the responsible
thing to do.
| author | Kim Alvefur <zash@zash.se> |
|---|---|
| date | Sun, 29 Oct 2023 11:30:49 +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.