LightningCreations / LightningCreations/passman
Server Users and Authentication
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
The Passman Server should store a list of users and provide an authentication flow. A user should be identified by their public key. The server should store their public key, as well as a salt and the user's hashed and salted password.
API endpoint(s) should be provided to enable clients to authenticate a user.
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 locating the Passman Server's existing API entry points and data-storage code, since the issue names no files or tests. Define the user model and authentication endpoints around public-key identity, stored salt, and hashed password; done means clients can authenticate through the provided API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- authentication, backend-api-design, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100