Repository navigation
Sec/refresh tokens - #2849
Open
nhoening wants to merge 5 commits into
Open
Sec/refresh tokens#2849nhoening wants to merge 5 commits into
nhoening wants to merge 5 commits into
Conversation
Context: - Refresh-token rotation needs durable state and protection against concurrent use. Change: - Add the tracker model and migration, lock user and family rows consistently, and revoke families on credential changes or deactivation.
Context: - Integrations need renewable credentials without changing existing access-token clients. Change: - Add JSON refresh and revocation endpoints with kebab-case fields, lifetime reporting, replay protection and immediate revocation. - Preserve legacy response fields and token lifetime; reject inactive users and prevent caching token responses.
Context: - Authentication lifecycle changes need regression coverage using real token validation. Change: - Cover rotation, concurrent reuse, expiry, revocation and credential changes. - Correct naming checks for the existing auth_token and user_id response contract without allowing new snake-case fields.
Context: - Issue #2229 adds renewable API credentials. Change: - Describe refresh-token rotation, expiry and revocation while retaining legacy access-token authentication.
Context: - New clients need a complete flow and guidance for safe rotation and recovery. Change: - Document opt-in authentication, exchange, revocation, expiry and deployment requirements with curl and Python examples. - Update generated OpenAPI definitions to match the actual authentication responses.
Documentation build overview
14 files changed ·
|
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Closes #2229
The
auth_token,user_id, and access-token lifetime remain compatible.documentation/changelog.rstLook & Feel
Check the new documentation and API endpoints.
How to test
Here is a bash script:
Future work
The client needs to support this, as well.