view mod_oidc_userinfo_vcard4/README.md @ 5511:0860497152af

mod_http_oauth2: Record hash of client_id to allow future verification RFC 6819 section 5.2.2.2 states that refresh tokens MUST be bound to the client. In order to do that, we must record something that can definitely tie the client to the grant. Since the full client_id is so large (why we have this client_subset function), a hash is stored instead.
author Kim Alvefur <zash@zash.se>
date Fri, 02 Jun 2023 10:14:16 +0200
parents 320593cf7d90
children
line wrap: on
line source

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

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