Repository navigation
fix(auth): use expiring offline tokens - #24
Merged
Merged
Conversation
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.
Summary
expiring: 1) for public apps calling the Admin API.accessTokenwith expiration timestamp (expires) inSession.refreshTokenandrefreshTokenExpiresNULL (zero refresh tokens stored at rest).id_tokenon embedded-admin requests when a session is missing, has NULL expires, or expires within 5 minutes.syncShopProfilewith the newly minted token, logs non-OK response error snippets up to 200 chars, and ensures fallback lookups only use valid tokens.Verified:
npm test: 580 passed, 0 failed across 132 suites.npm run test:all: 591 tests (580 passed, 11 skipped live DB).Unverified: