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:
- 'Type-S2SAuth'
---

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

[PKIX over Secure HTTP (POSH)][rfc7711] describes a method of
securely delegating a domain to a hosting provider, without that hosting
provider needing keys and certificates covering the hosted domain.

# Validating

This module performs POSH validation of other servers. It is *not*
needed to delegate your own domain.

# Delegation

You can generate the JSON delegation file from a certificate by running
`prosodyctl mod_s2s_auth_posh /path/to/example.crt`. This file needs to
be served at `https://example.com/.well-known/posh/xmpp-server.json`.