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

+
−This module compares the memory usage reported by Lua before and after
+
−each event and reports it to the log if it exceeds the configuration
+
−setting `log_memory_threshold` (in bytes).
+
−
+
−``` lua
+
−log_memory_threshold = 20*1024
+
−```
+
−
+
−If you are looking to identify memory leaks, please first read [Three
+
−kinds of memory
+
−leaks](https://blog.nelhage.com/post/three-kinds-of-leaks/).
+
−
+
−Prosody runs on Lua which uses automatic memory management with garbage
+
−collection, so the numbers reported by this module are very likely to be
+
−useless for the purpose of identifying memory leaks. Large, but
+
−temporary, increases in memory usage can however highlight other kinds
+
−of performance problems and sometimes even provide hits for where to
+
−look for memory leaks.