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

Is OpenID Federation supported for DC API requests? #436

Open
TimoGlastra opened this issue Feb 24, 2025 · 1 comment · May be fixed by #458
Open

Is OpenID Federation supported for DC API requests? #436

TimoGlastra opened this issue Feb 24, 2025 · 1 comment · May be fixed by #458

Comments

@TimoGlastra
Copy link
Member

The spec mentions for OpenID Federation client id scheme, that the request MAY contain a trust_chain parameter.

However Appendix A.2. does not include the trust_chain parameter in the supported parameters.

Should Appendix A.2. also include the trust_chain parameter?
@Sakurann
Copy link
Collaborator

Sakurann commented Mar 4, 2025 •
edited
Loading

signed openid4vp request over DC API works with any client_id_scheme :)

The signed request allows the Wallet to authenticate the Verifier using a trust framework other than the Web PKI utilized by the browser.

we could add a text saying that any additional parameters bound to a specific client identifier scheme can be used over the DC API? Could you propose text/do a PR?

@TimoGlastra TimoGlastra linked a pull request Mar 15, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

add small note about client id parameters for dc api TimoGlastra/OpenID4VP
2 participants
@TimoGlastra @Sakurann