Mercurial > prosody-modules
view mod_http_dir_listing2/resources/template.html @ 5682:527c747711f3
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.
| author | Kim Alvefur <zash@zash.se> |
|---|---|
| date | Sun, 29 Oct 2023 11:30:49 +0100 |
| parents | c91c9b87929e |
| children |
line wrap: on
line source
<html> <head> <title>Index of {path}</title> <meta charset="utf-8"/> <style>{style}</style> </head> <body> <h1>Index of {path}</h1> <ul class="filelist">{filelist# <li class="{item.class}"><a href="{item.href}"{item.rel& rel="{item.rel}"}>{item.text}</a></li>} </ul> <footer>{footer}</footer> </body> </html>