You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by thomasrutger November 5, 2024
I noticed that the MvdScopeTransformer is very similar to the default EdcScopeToCriterionTransformer, with the exception of the list of knownCredentialTypes. In particular, if a scope string is not recognized as a "known credential" it returns the Criterion
The purpose of this fallback behavior is unclear to me. Does this relate to an MVD-specific scope alias, or is there another reason behind it? Why not return a failure if the scope is unrecognized?
The text was updated successfully, but these errors were encountered:
Discussed in #382
Originally posted by thomasrutger November 5, 2024
I noticed that the
MvdScopeTransformer
is very similar to the defaultEdcScopeToCriterionTransformer
, with the exception of the list ofknownCredentialTypes
. In particular, if a scope string is not recognized as a "known credential" it returns the Criterion"verifiableCredential.credential.credentialSubject.claims.level"=credentialType
The purpose of this fallback behavior is unclear to me. Does this relate to an MVD-specific scope alias, or is there another reason behind it? Why not return a failure if the scope is unrecognized?
The text was updated successfully, but these errors were encountered: