Repository navigation
Why does Client configuration data have to be JSON-LD serialized? #199
Description
When a Client Identifier is dereferenced, the resource MUST be serialized as an application/ld+json document unless content negotiation requires a different outcome.
Why does Client configuration data have to be JSON-LD serialized?
OpenID Federation Specification defines Automatic Registration feature that achieves the same goal and the Entity Statement is a signed JWT: https://openid.net/specs/openid-connect-federation-1_0.html#section-10.1
Activity
Sakurann commentedon Oct 3, 2022
Issue #95 seems to be referencing the Federation draft too
acoburn commentedon Oct 4, 2022
We should take a serious look at whether we could replace the use of Solid-OIDC client identifiers with this definition from the OpenID Federation spec