Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

clarify what is mutually exclusive (client_metadata and pre-registered clients) #165

Merged
merged 2 commits into from
Jun 14, 2024
Merged

clarify what is mutually exclusive (client_metadata and pre-registered clients) #165

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
effd1e4
clarify what is mutually exclusive
May 3, 2024
33cd6ae
remove updated text and simply remove the current paragraph
Sakurann May 24, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions openid-4-verifiable-presentations-1_0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -767,8 +767,6 @@ The error response follows the rules as defined in [@!RFC6749], with the followi
- `client_metadata` or `client_metadata_uri` parameter defined in (#vp_token_request) is present, but the Wallet recognizes Client Identifier and knows metadata associated with it.
- Verifier's pre-registered metadata has been found based on the Client Identifier, but `client_metadata` parameter is also present.

Usage of `client_metadata` or `client_metadata_uri` parameters with `client_id` that the Wallet might be seeing for the first time is mutually exclusive with the registration mechanism where Self-Issued OP assigns `client_id` to the Verifier after receiving Verifier metadata.

`access_denied`:

- The Wallet did not have the requested Credentials to satisfy the Authorization Request.
Expand Down
Loading