linux-credentials / linux-credentials/credentialsd
Use activation token in backend
Open
Nobody has claimed this yet.
ui-consideration
- Dominant language
- Rust
- Stars
- 259
- Forks
- 19
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 12
Description
The portal frontend definition now accepts the activation token, but we don't do anything with it yet. Make sure we forward it and consume it when displaying the backend UI.
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 how the portal frontend definition passes the activation token into the backend UI, then identify where that UI is displayed and where the token should be consumed. Done means the token is forwarded from the portal definition and consumed when displaying the backend UI; verify the relevant portal flow with the project's existing tests or checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100