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:
- Statistics
summary: Measure process resource use metrics (cpu, memory, file descriptors)
---

Description
===========

This module exposes process resource use metrics similar to those exposed by
default when using a Prometheus client library. Specifically, the following
metrics are exposed:

- CPU use
- Resident set and virtual memory size
- Number of open file descriptors and their limit

This module uses the new OpenMetrics API and thus requires a recent version
of Prosody trunk (0.12+).

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

  ------- -------------
  trunk   Works
  0.11    Does not work
  ------- -------------