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.

---
summary: 'Block remote servers via ad-hoc command'
...

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

This module provides the *Edit Blacklist* ad-hoc command described in
[XEP-0133](http://xmpp.org/extensions/xep-0133.html#edit-blacklist) and
also performs the actual blocking of incoming and outgoing
server-to-server connections.

Using
=====

In your client, simply select the Edit Blacklist command from the list
of adhoc commands. E.g. in Pidgin, this is under *Accounts -\> (your
account)* in the menu.