Mercurial > prosody-modules
view mod_s2s_never_encrypt_blacklist/README.markdown @ 5425:3b30635d215c
mod_http_oauth2: Support granting zero role-scopes
It seems Very Bad that if you uncheck all roles on the consent page, you
get the default scopes, which seems the opposite of what you probably
intended. Currently, mod_tokenauth will do the same thing, so work is
needed there too to allow issuing tokens without roles.
A token without a role could be used for OIDC login, and not much else.
This seems like a valuable thing to support.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Sun, 07 May 2023 19:29:15 +0200 |
parents | 4d73a1a6ba68 |
children |
line wrap: on
line source
--- labels: - 'Stage-Beta' summary: | Stops prosody from including starttls into available features for specified remote servers. ... Details ------- Let's you stop Prosody from sending \<starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'\> feature to choppy/buggy servers which therefore would fail to re-negotiate and use a secure stream. (e.g. [OpenFire 3.7.0](http://issues.igniterealtime.org/browse/OF-405)) Usage ----- Copy the plugin into your prosody's modules directory. And add it between your enabled modules into the global section (modules\_enabled). Then list each host as follow: tls_s2s_blacklist = { "host1.tld", "host2.tld", "host3.tld" } In the unfortunate case of OpenFire... you can add the Server's ip address directly as it may not send proper rfc6121 requests. tls_s2s_blacklist_ip = { "a.a.a.a", "b.b.b.b", "c.c.c.c" } Compatibility ------------- It's supposed to work with 0.7-0.8.x