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.

---
labels:
- 'Stage-Alpha'
summary: 'Support XEP-0334: Message Processing Hints for MUC messages'
...

Introduction
============

This module will check for MUC messages with XEP-0334 Message
Processing Hints tags to qualify those messages as "historic"
for later MAM archiving or not.

Usage
=====

First copy the module to the prosody plugins directory.

Then add "muc\_mam\_hints" to your modules\_enabled list in your MUC
component:

``` {.lua}
Component "conference.example.org" "muc"
modules_enabled = {
  "muc_mam",
  "muc_mam_hints",
}
```