annotate mod_tos/README.md @ 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 |
7f61d89a594d |
children |
|
rev |
line source |
4655
|
1 # mod_tos |
|
2 |
|
3 A very drafty module to implement some kind of Terms of Service acceptance |
|
4 tool. |
|
5 |
|
6 Currently, this only works with clients implementing this very drafty |
|
7 protocol. The result of the experiments will be an update to the |
|
8 [ToS ProtoXEP](https://xmpp.org/extensions/inbox/tos.html), with the goal |
|
9 of acceptance. |