divviup-api could manage collector auth tokens for subscribers
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 10
- Forks
- 5
- Avg merge
- 2h 41m
- Merged PRs (30d)
- 66
Description
We generate a unique collector auth token for each task and then expect subscribers to get them from divviup-api and subsequently use them to authenticate requests to the Leader's collection API.
It would be nice if divviup-api had a wrapper around the DAP layer collection API. It could verify that the client is logged in as a user who has appropriate privileges on the task and then make a collection request to the leader on their behalf.
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
No files, tests, or entry points are named. Start by tracing how divviup-api exposes task access and how the DAP layer collection API handles Leader requests; define the authentication and privilege boundaries before determining what a completed wrapper should support.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, authentication, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100