File

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: 'IM-based administration console'
...

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

This module provides a console over XMPP. All the commands of the
mod\_admin\_telnet module are available from an XMPP client.

Only the Prosody admins (see the *admins* list in the Prosody
configuration file) can use this console.

Installation
============

Copy the mod\_admin\_message directory into a directory Prosody will
check for plugins (cf. [Installing
modules](http://prosody.im/doc/installing_modules)) and set up a
component:

    Component "console@example.com" "admin_message"

"console@example.com" is the identifier of the XMPP console.

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

  --------- ---------------
  trunk     Doesn't work (uses is_admin)
  0.9       Works
  \<= 0.8   Not supported
  --------- ---------------