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.

# About

This module allows using the [mod_csi_simple][doc:modules:mod_csi_simple]
setting `csi_important_payloads` (added in trunk/0.12) in Prosody 0.11.x.

# Config

```
modules_enabled = {
    -- other modules etc
    "csi_simple",
    "csi_simple_compat",
}

csi_important_payloads = {
    -- Anything in this namespace:
    "{urn:example:important-namespace}",
    -- Specific element name and namespace:
    "{urn:example:xmpp:priority}super-important",
}
```

# Example

``` lua
csi_important_payloads = {
    -- XEP-0353: Jingle Message Initiation
    "{urn:xmpp:jingle-message:0}",
}
```