Auth: Allow enabling/disabling OpenID4VP and OpenID4VCI independently#4119
Auth: Allow enabling/disabling OpenID4VP and OpenID4VCI independently#4119
Conversation
…arately Co-authored-by: reinkrul <1481228+reinkrul@users.noreply.github.com> Agent-Logs-Url: https://github.com/nuts-foundation/nuts-node/sessions/97962131-050a-4a34-9f6d-efe01eef57ac
reinkrul
left a comment
There was a problem hiding this comment.
Log error when deprecated AuthorizationEndpoint is used, telling to use the other properties.
Co-authored-by: reinkrul <1481228+reinkrul@users.noreply.github.com> Agent-Logs-Url: https://github.com/nuts-foundation/nuts-node/sessions/c497969e-5b23-418a-82f4-5e6af4be6b6e
Done in 2c4ddd5. When Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
|
Coverage Impact ⬆️ Merging this pull request will increase total coverage on Modified Files with Diff Coverage (4)
🤖 Increase coverage with AI coding...🚦 See full report on Qlty Cloud » 🛟 Help
|
|
@copilot the openid4vp e2e tests still specify auth.authorizationendpoint in the YAML files, replace this with the new property |
Co-authored-by: reinkrul <1481228+reinkrul@users.noreply.github.com> Agent-Logs-Url: https://github.com/nuts-foundation/nuts-node/sessions/eace0514-6d68-46f9-9c5c-b1a1b5b9532e
2 new issues
|
…e2e test configs Co-authored-by: reinkrul <1481228+reinkrul@users.noreply.github.com> Agent-Logs-Url: https://github.com/nuts-foundation/nuts-node/sessions/9decfe7c-69e1-48c8-9fb4-02d1217789f2
Updated in 3e6f62c. All three e2e test configs now use
|
- Add integrating/openid4vci.rst: how-to guide for requesting credentials over OpenID4VCI (wallet-initiated flow) - Regenerate server_options.rst: replace deprecated auth.authorizationendpoint.enabled with auth.openid4vci.enabled and auth.openid4vp.enabled - Update recommended-deployment.rst to reference the new config keys - Register openid4vci.rst in the docs index Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Previously,
auth.authorizationendpoint.enabledenabled both OpenID4VP and OpenID4VCI together, making it impossible to use OpenID4VCI without also enabling OpenID4VP.New configuration
Two separate flags replace the combined flag:
The old
auth.authorizationendpoint.enabledis deprecated but remains functional — it still enables both protocols for backward compatibility. A deprecation warning is logged at startup when this flag is set, directing users to the new flags.Changes
auth/config.go: AddedOpenID4VPConfigandOpenID4VCIConfigstructs; keptAuthorizationEndpointConfigas deprecatedauth/interface.go: ReplacedAuthorizationEndpointEnabled()withOpenID4VPEnabled()andOpenID4VCIEnabled()auth/auth.go: Both new methods OR with the deprecated flag for backward compat; logs aWARNwhen the deprecated flag is in useauth/api/iam/api.go:HandleAuthorizeRequestgated onOpenID4VPEnabled()Callbackenabled when either protocol is enabledauthorization_endpointomitted from AS metadata when OpenID4VP is disabledauth/api/iam/openid4vci.go:RequestOpenid4VCICredentialIssuancegated onOpenID4VCIEnabled()auth/cmd/cmd.go: New flags registered; old flag marked deprecated with migration hintOriginal prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.