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
Starting from the example Client ID Document in 5.1, when expanding with the context and then compacting the result again, the "redirect_uris": ["https://app.example/callback"] statement becomes:
This is obviously not what we want, in order to be compatible with OIDC Dynamic Registration syntax. It is due to redirect_uris being configured as a JSON-LD ID Map in the context, as follows.
That data structure is meant for maps, both the key and the value of which are (named) nodes. A set of redirect URIs, however, is just a set of nodes, not a map. I therefore believe the @id annotation of @container should be removed, leaving just "@container": "@set", which results in the correct expansion.
The text was updated successfully, but these errors were encountered:
While experimenting in the JSON-LD Playground, I stumbled upon the following issue, which I could only solve by diverting from the mandated JSON-LD context.
Starting from the example Client ID Document in 5.1, when expanding with the context and then compacting the result again, the
"redirect_uris": ["https://app.example/callback"]
statement becomes:This is obviously not what we want, in order to be compatible with OIDC Dynamic Registration syntax. It is due to
redirect_uris
being configured as a JSON-LD ID Map in the context, as follows.That data structure is meant for maps, both the key and the value of which are (named) nodes. A set of redirect URIs, however, is just a set of nodes, not a map. I therefore believe the
@id
annotation of@container
should be removed, leaving just"@container": "@set"
, which results in the correct expansion.The text was updated successfully, but these errors were encountered: