prosody-modules
527c747711f3
mod_pep_vcard_avatar/README.markdown
Software / code / prosody-modules
File
mod_pep_vcard_avatar/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 | 3421:41dd405efb5a |
line wrap: on
line source
--- labels: - 'Stage-Alpha' summary: Sync avatars between vCards and PEP --- ## Introduction This module pushes the users nickname and avatar from vCards into PEP, or into vCards from PEP. This allows interop between older clients that use [XEP-0153: vCard-Based Avatars] to see the avatars of clients that use [XEP-0084: User Avatar] and vice versa. Also see [XEP-0398: User Avatar to vCard-Based Avatars Conversion]. ## Configuration Simply [enable it like most other modules][doc:installing_modules#prosody-modules], no further configuration needed. ## Compatibility ------- -------------------------------- trunk Use mod\_vcard\_legacy instead 0.11 Use mod\_vcard\_legacy instead 0.10 Works 0.9 Does not work 0.8 Does not work ------- --------------------------------
