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

Client identifier and CORS #194

Open
NSeydoux opened this issue Sep 7, 2022 · 0 comments
Open

Client identifier and CORS #194

NSeydoux opened this issue Sep 7, 2022 · 0 comments

Comments

@NSeydoux
Copy link
Contributor

NSeydoux commented Sep 7, 2022

Currently, the spec doesn't say anything about CORS: clients may not configure CORS for their identifiers, preventing cross-domain requests to this document. The main use case for the client identifier is to be dereferenced by the Solid-OIDC provider, which is going to be a backend service, so this has no impact on it. However, the client identifier not being available cross-domain prevents a client-side Solid app to dereference it to discover information about the client. As it stands, making an app that displays information about clients to a user requires a server-side component because there is no guarantee that the client-side request would work. Should there be a note about this in the spec, either recommending that developers configure CORS for the client identifiers, or warning that looking up a client identifier cross-domain may legitimately fail ?

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

1 participant