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: 'Ad-hoc interface to Message Archive Management Settings'
...

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

This module complements mod\_mam by allowing clients to change archiving
preferences through an Ad-hoc command.

Details
=======

When enabled, an "Archive Settings" command should appear in the list of
Ad-hoc commands available. This allows the user to change default policy
(always, never, roster) and which JIDs to always store or never store.

Usage
=====

First copy the module to the prosody plugins directory.

Then add "mam\_adhoc" to your modules\_enabled list:

``` {.lua}
modules_enabled = {
  -- ...
    "mam",
  "mam_adhoc",
  -- ...
}
```