File

mod_muc_auto_reserve_nicks/README.md @ 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 4772:85d4ab318d66
line wrap: on
line source

---
labels:
- 'Stage-Alpha'
summary: 'Automatically reserve nicknames of MUC users'
...

Introduction
============

This module automatically reserves the nickname of a user when they first join
a MUC. That's all.

Details
=======

The module doesn't currently update the registration if the user changes their
nick. That could cause flip-flopping if the user has two clients in regular
use with different nicks configured.

Compatibility
=============

Requires Prosody trunk (0.12) for the API introduced in commit
[0e7dedd8b18d](https://hg.prosody.im/trunk/rev/0e7dedd8b18d) and
[e0b58717f0c5](https://hg.prosody.im/trunk/rev/e0b58717f0c5).