thefrontside / thefrontside/simulacrum
complete refresh_token rotation functionality
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 117
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
Although #252 added basic refresh_token functionality, there are still a few remaining features to simulate real refresh_token rotation.
- Check whether the token has expired
- With
refresh_tokenrotation, all previous refresh_tokens for that session need to be expired - The rotation number should be incremented concerning the current refresh_token when issuing a new refresh_token for the current session
This article is a good resource.
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 the refresh_token functionality added in issue #252 and the linked Auth0 refresh-token rotation article. Trace how the current session and refresh tokens are represented, then verify expiry checks, expiration of earlier session tokens, and rotation-number increments when a new token is issued.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100