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'
rockspec:
  dependencies:
  - mod_spam_reporting
summary: 'Notify admins about incoming XEP-0377 spam reports'
---

This module sends a message to the server admins for incoming
[XEP-0377][1] spam reports. It depends on [mod\_spam\_reporting][2] 
and doesn't require any configuration.

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

  ----- -----------
  trunk Works
  0.11  Works
  ----- -----------


[1]:https://xmpp.org/extensions/xep-0377.html
[2]:https://modules.prosody.im/mod_spam_reporting.html