Mercurial > prosody-modules
view mod_couchdb/README.markdown @ 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 | 4d73a1a6ba68 |
| children |
line wrap: on
line source
--- labels: - 'Stage-Alpha' - 'Type-Storage' summary: A CouchDB backend for Prosody ... ***Note:** This module needs updating to the 0.8 storage module API.* Introduction ============ This is an experimental Prosody backend for CouchDB. Configuration ============= In your config file, under the relevant host, add: datastore = "couchdb"; couchdb_url = "http://127.0.0.1:5984/database-name"; Compatibility ============= This module was developed as a prototype during development of the storage provider API in Prosody 0.8. The final storage provider API is different, so this module needs updates to work. Quirks ====== This implementation is a work in progress. - The data stored in couchdb is limited to: account data, rosters, private XML and vCards