File

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.

---
summary: OIDC group membership in UserInfo
labels:
- Stage-Alpha
rockspec:
  dependencies:
  - mod_http_oauth2 >= 200
  - mod_groups_internal
---

This module exposes [mod_groups_internal] groups to
[OAuth 2.0][mod_http_oauth2] clients via a `groups` scope/claim.