Why does Client configuration data have to be JSON-LD serialized?

Open Sakurann opened this issue 3 years ago • 2 comments

When a Client Identifier is dereferenced, the resource MUST be serialized as an application/ld+json document unless content negotiation requires a different outcome.

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

Oct 03 '22 19:10 Sakurann

Issue #95 seems to be referencing the Federation draft too

Oct 03 '22 20:10 Sakurann

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

Oct 04 '22 00:10 acoburn