feat(oid4vci): rich authorization requests #110
Draft
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.
Made a start at rich authorization requests for OpenID4VCI:
I think similar to what we have done with scope, requiring the user of this library to actually provide the scope, we should require the user to pass the
authorization_details. However like we did with scope, we can create utils. Currently we have an util to extract for a set of credential configuration ids. We should create a combined method:openid_credential-> use RARThis sill allows full control, while also accomodating the standard flow