Relying Party Remote Presentation alignments with standards #400
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…t-wallet-docs into versione-corrente
…t-wallet-docs into versione-corrente
…t-wallet-docs into versione-corrente
…t-wallet-docs into versione-corrente
…t-wallet-docs into versione-corrente
…t-wallet-docs into versione-corrente
…t-wallet-docs into versione-corrente
…t-wallet-docs into versione-corrente
…t-wallet-docs into versione-corrente
…etadata_uri and added clarifications when client_metadata can be used along with openid federation and for ephemeral cryptographic keys provided by RP. Fixes #376
peppelinux
commented
Sep 6, 2024
peppelinux
commented
Sep 6, 2024
Zicchio
reviewed
Sep 9, 2024
FYI in the actual changes you used |
peppelinux
commented
Sep 9, 2024
peppelinux
commented
Sep 9, 2024
grausof
approved these changes
Sep 11, 2024
peppelinux
added
standardization
fmarino-ipzs
approved these changes
Sep 18, 2024
peppelinux
commented
Sep 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR
presentation_submission further clarifications
According to feedbacks ferom the implementers, further clarification abou how to match and decode correctly several credential contained within the vp_token array are included
Removed client_metadata_uri clarification section
since it is not supproted anymore in openid4vp
Added clarifications when client_metadata is present
It can be used along with openid federation and for ephemeral cryptographic keys provided by RP.
This might represent a vulnerability, further checks must be required.
Fixes #376
auth flow fixed for the redirect_uri
RP crossdevice flow without redirect_uri. Fixes #386
The redirect_uri MUST NOT be provided when the cross device flow is used.
further clarification about which key to use for singin a request object
Fixes #292