linux-credentials / linux-credentials/credentialsd
Implement Linked Devices
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 259
- Forks
- 19
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 12
Description
Having linked devices can make it a little bit easier for users to start the hybrid flow. This is useful if a user has two devices, but credentials are not synchronized between them.
In order to do this, we'd need to send a message to the UI session after the credential is completed. There are a couple of ways to do this:
- the UI can wait a little bit after the credential is received for an event that has device linking information.
- CredentialService can wait a little bit after the credential is received, but before sending the CredentialCompleted event.
Contributor guide
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 tracing CredentialService from credential receipt through the CredentialCompleted event and the UI session message described in the issue. Decide how the UI should receive device-linking information and whether the wait belongs in the UI or CredentialService; done means the linked-device data reaches the UI session after credential completion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100