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
An issue we've ran into with the DCQL implementation from the PR in credo is that it encodes the dcql_query as string. For presentation_definition it encodes it as JSON object when doing JAR.
I think the agreement for OID4VP is to use string when encoding as url query, but if using JAR we can keep it as json. When parsing we should support both to increate interoperability.
@auer-martin could you take this into account with the oid4vp impementation?
The text was updated successfully, but these errors were encountered:
TimoGlastra
changed the title
Support both string and JSON encoded variant of presentation_definition and dcql_query
[OID4VP] Support both string and JSON encoded variant of presentation_definition and dcql_queryFeb 6, 2025
TimoGlastra
changed the title
[OID4VP] Support both string and JSON encoded variant of presentation_definition and dcql_query
Support both string and JSON encoded variant of presentation_definition and dcql_queryFeb 6, 2025
An issue we've ran into with the DCQL implementation from the PR in credo is that it encodes the
dcql_query
as string. Forpresentation_definition
it encodes it as JSON object when doing JAR.I think the agreement for OID4VP is to use string when encoding as url query, but if using JAR we can keep it as json. When parsing we should support both to increate interoperability.
See openid/OpenID4VP#378
@auer-martin could you take this into account with the oid4vp impementation?
The text was updated successfully, but these errors were encountered: