-
Notifications
You must be signed in to change notification settings - Fork 7
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
Clarify the use of Authorization Details (RAR) #93
Comments
the intent was to mandate scopes for the sake of interop. so we should discuss adding RAR, but the first step is probably to remove the examples defined in section 7.2.4 |
yes we should discuss this. as far as I remember, we assumed scopes would be easier to use. From an interop standpoint, I think RAR is the more direct approach as the wallet can directly use the types etc as defined by issuer or standards body for a certain credential without the need to negotiate scopes (in advance or ad-hoc through issuer metadata). |
Dears, |
I was coming from a similar use-case, +1 from me to consider adding RAR |
Section 4.2 states:
which mandates scopes and does not allow RAR to be used. Later on, section 7.2.4 explains Authorization Details to be used with SD-JWT VCs:
We should consider to support RAR (in addition to scopes) which is the path I would prefer or remove the example.
The text was updated successfully, but these errors were encountered: