Software /
code /
prosody-modules
File
mod_bookmarks2/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 |
parent | 5051:2718652c18ca |
line wrap: on
line source
--- labels: - 'Stage-Merged' summary: Synchronise bookmarks between Private XML, legacy PEP, and PEP ... ::: {.alert .alert-info} **Deprecatation notice:** This module has been merged into Prosody as [mod_bookmarks][doc:modules:mod_bookmarks]. Users of Prosody **0.12** and later should switch to that. ::: Introduction ------------ This module fetches users’ bookmarks from Private XML (or legacy PEP) and pushes them to PEP on login, and then redirects any Private XML query (or legacy PEP) to PEP. This allows interoperability between older clients that use [XEP-0048](https://xmpp.org/extensions/xep-0048.html) and recent clients which use [XEP-0402](https://xmpp.org/extensions/xep-0402.html). Configuration ------------- Simply [enable it like most other modules](https://prosody.im/doc/installing_modules#prosody-modules), no further configuration is needed. Compatibility ------------- ------- ----------------------------------------- 0.12 [Use the official mod_bookmarks module instead][doc:modules:mod_bookmarks] 0.11 Works 0.10 Does not work 0.9 Does not work ------- -----------------------------------------