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: "XEP-0198 integration with SASL2"
rockspec:
  dependencies:
  - mod_sasl2
---

Add support for inlining stream management negotiation into the SASL2 process.

**Note: At the time of writing (November 2022), this module implements a
version of XEP-0198 that is still working its way through the XSF standards
process. For more information and current status, see [PR #1215](https://github.com/xsf/xeps/pull/1215).**

This module depends on [mod_sasl2] and [mod_sasl2_bind2]. It exposes no
configuration options.