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!

---
summary: OIDC UserInfo profile details from vcard4
labels:
- Stage-Alpha
rockspec:
  dependencies:
  - mod_http_oauth2
---

This module extracts profile details from the user's [vcard4][XEP-0292]
and provides them in the [UserInfo] endpoint of [mod_http_oauth2] to
clients the user grants authorization.

Whether this is really needed is unclear at this point. When logging in
with an XMPP client, it could fetch the actual vcard4 to retrieve these
details, so the UserInfo details would probably primarily be useful to
other OAuth 2 and OIDC clients.

[UserInfo]: https://openid.net/specs/openid-connect-core-1_0.html#UserInfoResponse