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.

Generate a DNS UPDATE order in format suitable for `nsupdate` based on
current port configuration.

Example output:

```
$ prosodyctl mod_dnsupdate -d example.com -t xmpp.example.com example.com
zone example.com
server ns1.example.com
ttl 3600
add _xmpp-client._tcp.example.com IN SRV 1 1 5222
add _xmpp-server._tcp.example.com IN SRV 1 1 5269
```