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

Might need to clarify better how authz req parameters are included in PAR #361

Open
Sakurann opened this issue Jul 12, 2024 · 4 comments
Open

Might need to clarify better how authz req parameters are included in PAR #361

Sakurann opened this issue Jul 12, 2024 · 4 comments
Labels
pending close

Comments

@Sakurann
Copy link
Collaborator

got asked if they are top-level.
including example might help
@awoie
Copy link
Contributor

awoie commented Jul 12, 2024

Does this issue belong to OID4VP or to OID4VCI?

@Sakurann Sakurann transferred this issue from openid/OpenID4VP Jul 12, 2024
@bc-pi
Copy link
Member

bc-pi commented Jul 12, 2024

https://www.rfc-editor.org/rfc/rfc9126.html#section-2.1 seems relevant

@jogu
Copy link
Contributor

jogu commented Jul 12, 2024 •
edited
Loading

Was it signed or unsigned PAR requests they were confused about / we should include an example for?

There is already an example for unsigned PAR:

https://openid.github.io/OpenID4VCI/openid-4-verifiable-credential-issuance-wg-draft.html#section-5.1.4

@jogu
Copy link
Contributor

jogu commented Sep 3, 2024

Marking as pending close given we have an example, but it's not clear to me what people were confused about.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
pending close
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@jogu @awoie @Sakurann @bc-pi