view mod_oidc_userinfo_vcard4/README.md @ 5447:aa4828f040c5

mod_http_oauth2: Enforce client scope restrictions in authorization When registering a client, a scope field can be included as a promise to only ever use those. Here we enforce that promise, if given, ensuring a client can't request or be granted a scope it didn't provide in its registration. While currently there is no restrictions at registration time, this could be changed in the future in various ways.
author Kim Alvefur <zash@zash.se>
date Thu, 11 May 2023 19:33:44 +0200
parents f8ec43db580b
children 320593cf7d90
line wrap: on
line source

---
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