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-Obsolete'
superseded_by: mod_muc
summary: XEP-0410 Server Optimization (now supported by Prosody mod_muc)
---

This module implements the [Server
Optimization](https://xmpp.org/extensions/xep-0410.html#serveroptimization)
part of [XEP-0410: MUC Self-Ping]

# Usage

The module is loaded on MUC components:

```lua
Component "muc.example.com" "muc"
modules_enabled = {
    "muc_ping";
}
```

# Configuration

No options.

# Compatibility

It should work with Prosody up until 0.10.x.

Prosody 0.11.x and trunk natively supports XEP-0410 so this module is **not** needed.