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.

This module provides two [metrics][doc:statistics]:

`lua_heap_bytes`
:   Bytes of memory as reported by `collectgarbage("count")`{.lua}

`lua_info`
:   Provides the current Lua version as a label

``` openmetrics
# HELP lua_info Lua runtime version
# UNIT lua_info
# TYPE lua_info gauge
lua_info{version="Lua 5.4"} 1
# HELP lua_heap_bytes Memory used by objects under control of the Lua
garbage collector
# UNIT lua_heap_bytes bytes
# TYPE lua_heap_bytes gauge
lua_heap_bytes 8613218
```