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-Beta'
summary: |
    COMPAT Module for old clients using wrong namespaces in MUC's
    affiliation manipulations.
...

Details
=======

Adds compatibility for old clients/libraries attempting to change
affiliations and retrieve 'em sending the \<
http://jabber.org/protocol/muc\#owner \> xmlns instead of \<
http://jabber.org/protocol/muc\#admin \>.

Usage
=====

Copy the plugin into your prosody's modules directory.

And add it between the enabled muc component's modules

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

-   0.7-0.8.x