Tech debt: OAuth sign-in
- Dominant language
- Go
- Stars
- 0
- Forks
- 0
- Avg merge
- 3h 1m
- Merged PRs (30d)
- 29
Description
Tracked in `roadmap.md` *Tech debts* as: **"Oauth"**
Third-party OAuth sign-in (Google, GitHub, etc.) alongside the existing Argon2id + opaque cookie session flow.
*Published Contract Candidates* already records the verdict: **already covered** — this is another `auth.Resolver`, or a sibling port inside `auth/`. No new module needed.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with roadmap.md and the existing auth/Resolver described in the issue, then review the current Argon2id and opaque-cookie session flow. Confirm which OAuth providers and acceptance cases are in scope before changing auth/. Done means third-party sign-in works alongside the existing session flow without introducing a new module.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100