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.

# https://editorconfig.org/

root = true

[*]
charset = utf-8
end_of_line = lf
indent_style = tab
insert_final_newline = true
trim_trailing_whitespace = true
max_line_length = 150

[*.json]
# json_pp -json_opt canonical,pretty
indent_size = 3
indent_style = space

[{README,COPYING,CONTRIBUTING,TODO}{,.markdown,.md}]
# pandoc -s -t markdown
indent_size = 4
indent_style = space

[*.py]
indent_size = 4
indent_style = space

[*.{xml,svg}]
# xmllint --nsclean --encode UTF-8 --noent --format -
indent_size = 2
indent_style = space

[*.yaml]
indent_size = 2
indent_style = space