Mercurial > prosody-modules
view mod_couchdb/README.markdown @ 5264:d3ebaef1ea7a
mod_http_oauth2: Correctly verify OAuth client credentials on revocation
Makes no sense to validate against username and password here, or using
a token to revoke another token, or itself?
In fact, upon further discussion, why do you need credentials to revoke
a token? If you are not supposed to have the token, revoking it seems
the most responsible thing to do with it, so it should be allowed, while
if you are supposed to have it, you should be allowed to revoke it.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Tue, 21 Mar 2023 21:57:18 +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