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: 'HTTP-based account data import/export using XEP-0227'
...

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

This module allows a user to import or export account data using a simple
HTTP API. The data is expected to be in the format described by [XEP-0227:
Portable Import/Export Format for XMPP-IM Servers](https://xmpp.org/extensions/xep-0227.html).

Note that this module does not provide any UI for direct interaction from
users - it is expected that any UI will be provided elsewhere. For example,
this module is used by the [Snikket web portal](https://github.com/snikket-im/snikket-web-portal/).

For Developers
==========

TBD.

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

Requires Prosody trunk (270047afa6af).