File

mod_compliance_latest: using module:log_status diff --git a/mod_compliance_latest/mod_compliance_latest.lua b/mod_compliance_latest/mod_compliance_latest.lua --- a/mod_compliance_latest/mod_compliance_latest.lua +++ b/mod_compliance_latest/mod_compliance_latest.lua @@ -1,6 +1,6 @@ local success, err = pcall(function() module:depends("compliance_2023") end) if not success then - module:log("error", "Error, can't load module: mod_compliance_2023. Is this module downloaded in a folder readable by prosody?") - return 1, "Error: Couldn't load dependency mod_compliance_2023." +module:log_status( "error", "Error, can't load module: mod_compliance_2023. Is this module downloaded into a folder readable by prosody?" ) +return false end

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