File

mod_pep_vcard_avatar/README.markdown @ 5390:f2363e6d9a64

mod_http_oauth2: Advertise the currently supported id_token signing algorithm This field is REQUIRED. The algorithm RS256 MUST be included, but isn't because we don't implement it, as that would require implementing a pile of additional cryptography and JWT stuff. Instead the id_token is signed using the client secret, which allows verification by the client, since it's a shared secret per OpenID Connect Core 1.0 § 10.1 under Symmetric Signatures. OpenID Connect Discovery 1.0 has a lot of REQUIRED and MUST clauses that are not supported here, but that's okay because this is served from the RFC 8414 OAuth 2.0 Authorization Server Metadata .well-known endpoint!
author Kim Alvefur <zash@zash.se>
date Sun, 30 Apr 2023 16:13:40 +0200
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
  ------- --------------------------------