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-Merged'
- 'Type-Storage'
- ArchiveStorage
summary: 'Simple memory-only storage module'
...

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

This module acts as a normal storage module for Prosody, but saves all
data in memory only. All data is lost when the server stops. This makes
it useful for testing, or certain specialized applications.

Details
=======

Because the accounts store will always begin empty, it is mostly useful
combined with an authentication plugin which doesn't use Prosody's
storage API, or with [mod\_auth\_any](mod_auth_any.html), or you can
create user accounts manually each time the server starts.

Compatibility
=============

  ----- -------
  0.9   Works
  ----- -------