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: 'Automatically reserve nicknames of MUC users'
...

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

This module automatically reserves the nickname of a user when they first join
a MUC. That's all.

Details
=======

The module doesn't currently update the registration if the user changes their
nick. That could cause flip-flopping if the user has two clients in regular
use with different nicks configured.

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

Requires Prosody trunk (0.12) for the API introduced in commit
[0e7dedd8b18d](https://hg.prosody.im/trunk/rev/0e7dedd8b18d) and
[e0b58717f0c5](https://hg.prosody.im/trunk/rev/e0b58717f0c5).