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
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?
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
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
The text was updated successfully, but these errors were encountered: