[stub] make sure the use of an old refresh token invalidates all refresh tokens and is audited/logged
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 739
- Forks
- 85
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 1
Description
We give you a new refresh token on every refresh flow. Thus if an attacker steals your refresh token and uses it, they will invalidate your token. We should make sure that if you then try to use your (now invalid) refresh token, the whole session is terminated (because we have detected that it was stolen). This event should be audited / logged as a potential compromise.
Contributor guide
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
The issue does not name files, tests, or entry points. Start by locating the refresh flow and how refresh-token reuse is detected and invalidated. Done means reuse terminates the whole session and records an auditable or logged potential-compromise event, with tests covering that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100