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

---
labels:
- 'Stage-Beta'
summary: Manually override the list of service discovery items
...

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

This Prosody plugin lets you manually override the service discovery
items for a host.

Usage
=====

Simply add `"discoitems"` to your modules\_enabled list. Then add the
`disco_items` option to hosts for which you wish to override the default
response.

Note: mod\_disco in Prosody 0.8+ supports the `disco_items` option; this
plugin changes the behavior from appending items to replacing items

Configuration
=============

The `disco_items` option can be added to relevant hosts:

    disco_items = {
      {"proxy.eu.jabber.org", "Jabber.org SOCKS5 service"};
      {"conference.jabber.org", "The Jabber.org MUC"};
    }

The format for individual items is `{JID, display-name}`. The
display-name can be omitted: `{JID}`.

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

  ----- -------------
  0.8   Works
  0.7   Works
  0.6   Works
  0.5   Should work
  ----- -------------