-
Notifications
You must be signed in to change notification settings - Fork 75
VC Presentation Request Configuration could rather be an OAuth2 Pushed Authorization Request #136
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.
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
Comments
Thank you for the links. I see the spec is still in draft, so it might be wise to wait until it is formalized to implement it, but it looks like a good path moving forward. Currently, the endpoint is well defined, but having an arbitrary If you have time to put together a PR we would be happy to review and evaluate it 🙂 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Pinning issue for re-assessment. |
In the current protocol the OP is required to provide an unspecified endpoint for managing request configurations
(see https://github.com/bcgov/vc-authn-oidc/blob/master/docs/README.md#vc-presentation-request-configuration).
This could be refined based on Pushed Authorization Requests so that management of this request configuration is well-defined.
The text was updated successfully, but these errors were encountered: