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.

---
labels:
summary: Send restricted XML for conformance testing
...

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

This module sends processing instructions, comments, DTDs and a non
predefined entity (defined by the DTD) to the requesting entity.

Usage
=====

Send "PI", "comment", "DTD" or "entity" to
<xmpp:example.com/conformance>, while directly connected to the Prosody
instance.