Same Client ID can be used by server-side and on-device components of the client
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 26
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
This comes out of https://github.com/solid/notifications/issues/35
Even if this doesn't affect spec we should probably show how it can be done in the primer.
For the End-user it should be transparent that the client has two separate components. I think both of them using the same Client ID should be sufficient. If both components share the refresh token, issues may come up around rotating them. I think one of the components would be responsible for refreshing tokens and the other component would just get current access token from it.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the repository's primer and the linked solid/notifications issue #35 to understand the proposed server-side and on-device client arrangement. Document how both components can use one Client ID, including the refresh-token and current-access-token responsibilities, and make the separation transparent to end users.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100