Proof of Concept: user authentication through OpenID Connect #3793
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PoC verifies the feasibility of using the Nuts Node as OpenID Connect Provider to authenticate users from other care organizations. This can be used to log remote users into the organization's applications using generic OpenID Connect client libraries.
PoC setup can be found here: https://github.com/Zorgbijjou/nuts-openid-poc
Changes:
/authorize
with GET parameters (this disables the JAR requirement): client app might not be able to support JAR (e.g. MSAL.js)aud
claim verify if not set (need to solve this differently).id_token
in access token when requested scope isopenid
login_hint
, which contains the authorization server URL at which to perform OpenID4VP. If not set, it falls back to using the clientID (party who started the flow).TODO:
id_token
claims from user auth