Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
Sakurann opened this issue Oct 3, 2022 · 2 comments
Open

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

Sakurann opened this issue Oct 3, 2022 · 2 comments

Comments

@Sakurann
Copy link

Sakurann commented Oct 3, 2022

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

@Sakurann
Copy link
Author

Sakurann commented Oct 3, 2022

Issue #95 seems to be referencing the Federation draft too

@acoburn
Copy link
Member

acoburn commented 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants