Digest HTTP authentication
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.5k
- Forks
- 178
- Avg merge
- 15d 9h
- Merged PRs (30d)
- 2
Description
Output of rest-server --version
rest-server 0.9.7 (v0.9.8-25-g924f6c9) compiled with go1.14.2 on linux/amd64
What should rest-server do differently?
It'll be cool to support Digest or some other HTTP authentication scheme without transmitting plaintext login/password.
What are you trying to do? What is your use case?
I've just found that using TLS causes pretty observable overhead. Most of data is already encrypted except file paths and authentication credentials. So once non-plaintext authentication is implemented, it should be pretty safe to use it without TLS.
May be related: https://github.com/golang/go/issues/29409
Did rest-server help you today? Did it make you happy in any way?
Yes :)
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 reviewing rest-server's existing HTTP authentication behavior and the REST backend API, then read the linked Go issue about authentication support. Done means the project has agreed on and implemented a non-plaintext authentication scheme with documented behavior and coverage for its authentication flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, backend-api-design, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100