mod_http_oauth2: Implement stateless dynamic client registration Replaces previous explicit registration that required either the additional module mod_adhoc_oauth2_client or manually editing the database. That method was enough to have something to test with, but would not probably not scale easily. Dynamic client registration allows creating clients on the fly, which may be even easier in theory. In order to not allow basically unauthenticated writes to the database, we implement a stateless model here. per_host_key := HMAC(config -> oauth2_registration_key, hostname) client_id := JWT { client metadata } signed with per_host_key client_secret := HMAC(per_host_key, client_id) This should ensure everything we need to know is part of the client_id, allowing redirects etc to be validated, and the client_secret can be validated with only the client_id and the per_host_key. A nonce injected into the client_id JWT should ensure nobody can submit the same client metadata and retrieve the same client_secret

# Introduction

This module closes s2s connections when
[mod_smacks][doc:modules:mod_smacks] reports that a connection has not
received a timely acknowledgement as requested, indicating that the
connection is broken or the remote server is not responding.

With the connection closed, the next stanza to be directed to that
server will trigger Prosody to establish a new connection, instead of
queueing it on the potentially broken connection.

This should prevent messages from being stuck in a queue for a
potentially long time before being bounced back to the sender as
delivery failure reports.

Normally the amount of time it takes for a broken connection to time out
is determined by TCP.

If this is deemed sensible behavior then it will likely be merged into
Prosody itself somewhere.