Fix login 403 by persisting captured SLAS cookies - #2
Open
ludmoncada wants to merge 1 commit into
Open
Conversation
www.asda.com token refresh is Cloudflare-fronted and returns 403 to plain HTTP clients, which is issue MarkDunne#1. The access JWT is already in SLAS.AUTH_TOKEN after browser login; store it and refresh later from the same Chrome profile. Co-authored-by: Cursor <cursoragent@cursor.com>
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
1 participant
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.
Fixes #1.
After browser login, AsdaBot discarded
SLAS.AUTH_TOKENand immediately POSTed the refresh token with httpx towww.asda.com/.../oauth2/token. That host is Cloudflare-fronted and returns HTTP 403 to a bare HTTP client.This change:
SLAS.AUTH_TOKEN(plusADB2C.AUTH_TOKENwhen present)fetchin the existing Chrome profileNo TLS impersonation or Cloudflare bypass.
Made with Cursor