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: 'Implement XEP-0328: JID Prep for clients'
...

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

This is a plugin that implements the JID prep protocol defined in
<https://xmpp.org/extensions/xep-0328.html>

Details
=======

JID prep requests can happen over XMPP using the protocol defined in the
document linked above, or alternatively over HTTP. Simply request:

    http://server:5280/jid_prep/USER@HOST

The result will be the stringprepped JID, or a 400 Bad Request if the
given JID is invalid.

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

  ----- -------
  0.9   Works
  ----- -------