ComputerScienceHouse / ComputerScienceHouse/csh-auth
Give better feedback for bad secrets
Open
- Dominant language
- Go
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
IDK, even just "failed to exchange code, are your secrets valid?" would go so far
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the code-exchange error path in the Go service and inspect how invalid secrets are currently reported. Reproduce the failure with bad secrets, then verify that the resulting feedback clearly indicates that the secrets may be invalid.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100