Software /
code /
prosody-modules
Annotate
mod_require_otr/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 | 1803:4d73a1a6ba68 |
rev | line source |
---|---|
1803 | 1 --- |
2 labels: | |
3 - 'Stage-Stable' | |
4 summary: 'Enforce a policy for OTR-encrypted messages' | |
5 ... | |
6 | |
7 Introduction | |
8 ------------ | |
9 | |
10 [OTR, "Off The Record"](https://otr.cypherpunks.ca/), encryption allows | |
11 clients to encrypt messages such that the server cannot read/modify | |
12 them. | |
13 | |
14 This module allows the server admin to require that all messages are | |
15 OTR-encrypted. | |
16 | |
17 Configuration | |
18 ------------- | |
19 | |
20 Just enable the module by adding it to your global `modules_enabled`, or | |
21 if you only want to load it on a single host you can load it only for | |
22 one host like this: | |
23 | |
24 VirtualHost "example.com" | |
25 modules_enabled = { "require_otr" } | |
26 | |
27 #### Compatibility | |
28 | |
29 ------ ------- | |
30 0.10 Works | |
31 0.9 Works | |
32 0.8 Works | |
33 ------ ------- |