-
Notifications
You must be signed in to change notification settings - Fork 800
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to log into PSN account using ungoogled chromium #1139
Comments
What is the difference between the request made by UC and the one made by official Chromium? Sounds like the request is somehow malformed. |
AFAICT only the post form content and cookie header is different (from copied curl command line). |
Can you post the details of those two requests so we can know what are the differences? |
cURL cmdline with ungoogled chromium in incognito mode with only two extensions:
with google chrome:
|
The major difference comes from
and
However this seems to be some encoded binary data and I am not sure what I am looking at. @Eloston Any ideas? |
Unfortunately not, it looks pretty application-specific. Could there be other requests and responses that are different? Perhaps the authentication state spans multiple requests. |
From the descriptions of what was done, the request made by One possiblity I am thinking is maybe anti-fingerprinting messed up something? But they should be disabled by default I believe? |
It seems there was indeed another request after submitting only the email address:
It returns 201 Created and sets a new value to cookie |
@wchen342 You are right, the issue comes from flag #fingerprinting-client-rects-noise. It seems that Sony is somehow using that info to identify clients, but that flag is interfering with the detection. |
it may be they are using the information somehow, or maybe it is because of the reCAPTCHA they are using. Google is known to use more than JS (including other browser properties+machine learning) to identify activities. |
Yeah it's disabled by default. I think this is the first case I've seen where these anti-fingerprinting flags actually breaks a site. Interesting. Closing unless there are still problems here. |
@Eloston it was already reported here: bromite/bromite#402 I believe it is the same issue |
Describe the bug
This is a rather strange issue which I still can't figure out the reason.
I was trying to log into my PSN account to collect PS Plus games, but I'm unable to login using ungoogled chromium. On the login page, the request to
https://ca.account.sony.com/api/v1/ssocookie
always return 403 (which is then blocked by the browser as 403 responses doesn't have CORS headers).Tried using secret mode with only two extensions: BitWarden and Proxy SwitchyOmega with "system proxy" mode. Also tried with no extensions enabled.
Tried using official Google Chrome 84.0.4147.125 and Safari with no issues logging in.
Tried to copy the requests as cURL, the requests sent by ungoogled chromium also return 403 while the ones sent by official Chrome work.
Tried to copy everything under
Application Support/Chromium
toApplication Support/Google/Chrome
and running official Chrome then login, and it works. (Extensions don't work as expected as they are installed by Chromium Web Store.)I'm quite confident this is caused by ungoogled chromium at this point, but unable to pinpoint the exact issue.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Should have no issues logging in.
Screenshots
N/A
Environment (please complete the following information):
Additional context
Built using official
depot_tools
withgclient sync
and default args plus following entries:The text was updated successfully, but these errors were encountered: