Mercurial > prosody-modules
view mod_profile/README.markdown @ 5416:2393dbae51ed
mod_http_oauth2: Add option for specifying TTL of registered clients
Meant to simplify configuration, since TTL vs ignoring expiration is
expected to be the main thing one would want to configure.
Unsure what the implications of having unlimited lifetime of clients
are, given no way to revoke them currently, short of rotating the
signing secret.
On one hand, it would be annoying to have the client expire.
On the other hand, it is trivial to re-register it.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Thu, 04 May 2023 18:41:33 +0200 |
parents | 89226fb1af67 |
children |
line wrap: on
line source
--- labels: - 'Stage-Obsolete' summary: 'Replacement for mod\_vcard with vcard4 support and PEP integration' superseded_by: mod_vcard_legacy --- ::: {.alert .alert-warning} [mod\_vcard\_legacy][doc:modules:mod_vcard_legacy] and [mod\_vcard4][doc:modules:mod_vcard4] included with Prosody 0.11.x provide equivalent functionality. ::: # Introduction This module was an experimental replacement for [mod\_vcard]. In addition to the ageing protocol defined by [XEP-0054], it also supports the [new vCard 4 based protocol][xep0292] and integrates with [Personal Eventing Protocol][xep0163]. Also supports [XEP-0398: User Avatar to vCard-Based Avatars Conversion]. The vCard 4, [User Avatar][xep0084] and [User Nickname][xep0172] PEP nodes are updated when the vCard is changed.. # Configuration modules_enabled = { -- "vcard"; -- This module must be removed "profile"; } # Compatibility Requires Prosody **trunk** as of 2014-05-29. Won't work in 0.10.x. It depends on the trunk version of [mod\_pep][doc:modules:mod_pep] for PEP support, previously known as [mod\_pep\_plus][doc:modules:mod_pep_plus].