Annotate
mod_private_adhoc/README.markdown @ 5705: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 |
| parent |
1803:4d73a1a6ba68 |
| rev |
line source |
|
1803
|
1 ---
|
|
|
2 summary: Retrieve private XML data via adhoc command
|
|
|
3 ...
|
|
|
4
|
|
|
5 Introduction
|
|
|
6 ------------
|
|
|
7
|
|
|
8 This is a very simple module which implements an adhoc commant
|
|
|
9 toretrieves the users private XML data.
|
|
|
10
|
|
|
11 Details
|
|
|
12 -------
|
|
|
13
|
|
|
14 Simple module which adds the adhoc command "Query private data" and will
|
|
|
15 return the users private XML data (typically muc bookmarks,.. ).
|
