File

mod_http_oauth2: Advertise the currently supported id_token signing algorithm This field is REQUIRED. The algorithm RS256 MUST be included, but isn't because we don't implement it, as that would require implementing a pile of additional cryptography and JWT stuff. Instead the id_token is signed using the client secret, which allows verification by the client, since it's a shared secret per OpenID Connect Core 1.0 § 10.1 under Symmetric Signatures. OpenID Connect Discovery 1.0 has a lot of REQUIRED and MUST clauses that are not supported here, but that's okay because this is served from the RFC 8414 OAuth 2.0 Authorization Server Metadata .well-known endpoint!

---
labels:
- 'Stage-Alpha'
summary: 'Implement XEP-0328: JID Prep for clients'
...

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

This is a plugin that implements the JID prep protocol defined in
<https://xmpp.org/extensions/xep-0328.html>

Details
=======

JID prep requests can happen over XMPP using the protocol defined in the
document linked above, or alternatively over HTTP. Simply request:

    http://server:5280/jid_prep/USER@HOST

The result will be the stringprepped JID, or a 400 Bad Request if the
given JID is invalid.

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

  ----- -------
  0.9   Works
  ----- -------