File

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.

Over the years, some servers stop working for various reasons, and leave
behind broken roster subscriptions that trigger failing s2s connections.
This module allows cleaning up such cases by unsubscribing local users
from their contacts on those servers. Also works for typos and the like.
Use with care.

```lua
Component "gmail.com" "unsubscriber"
```