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-Stable'
summary: 'Close idle server-to-server connections'
...

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

Some people find it preferable to close server-to-server connections
after they have been silent for a while.

Configuration
=============

...is trivial. The default timeout is 300 seconds (5 minutes). To change
this simply put in the config:

       s2s_idle_timeout = 60 -- or any other number of seconds

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

  ----- -------
  0.6   Works
  0.7   Works
  ----- -------