Refresh reuse interval and reuse detection#117
Conversation
🦋 Changeset detectedLatest commit: a8c3a7f The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
cool! we definitely need to do this. only gave it a cursory look but in my head i imagined rewriting the refresh token back to the store with a new expiry so it would be cleaned up eventually does that make sense at all? |
d4d53dc to
b4cf5b4
Compare
14a8969 to
1cb1837
Compare
Yup, that's currently the way it works. The new expiry is determined by I made some more updates since the previous draft, and think it's good to go now:
|
|
This is an amazing addition, thank you @pverheggen for putting in the work on this. OpenAuth isn't really usable in a SPA without it. |
|
thank you for the contribution! made some minor tweaks to match some naming conventions we have but great |
Refresh tokens can be reused multiple times within a certain window after their first use, configured by the
ttl.refreshReuseoption.Also adds a
ttl.refreshRetentionoption, which sets the number of seconds after the reuse interval to retain for reuse detection.