-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
[Desktop] Can't sign in with firebase website with shields up #5075
Comments
Seems to have fixed itself |
Closed, fixed by above commit. |
Just a followup @ericelliott enabling all cookies helps. |
The issue is still reproducible with default shields settings. Note: Allowing all cookies fixes the issue. Tested on
|
Reproduced on
|
@ryanbr Can you give this another look? Looks like an issue with something more than firebaseapp |
Not sure if this is the same but I've got error "The popup has been closed by the user before finalizing the operation." on https://terminal.jcubic.pl#chat when I try to login with GitHub using Firebase, I don't see anything in console. |
Can you test in Brave-beta @jcubic ? |
Not sure what causes it, but I could login via /login github in Brave-beta |
Tested on Brave beta, got the same error. But this time the popup was closed, in original brave (on Fedora) the popup remained open but without any visible stuff. |
Okay, Just allow all cookies in sheilds on https://terminal.jcubic.pl/#chat Related to blocking of cookies on coveralls.io. |
coveralls.io is just code coverage report, it's not related. The issue it with GitHub and Firebase. Only those, maybe some other domains from Firebase. Allowing 3rd party cookies is working, but it's not related to coveralls.io. Google use lot of domains in their infrastructure. Is it possible to enable 3rd party cookies for single domain? I've only seen one dropdown where you can enable or disable all or only 3rd party. |
For reference, maybe something will be able to rewrite Firebase login with this: SO: Use Google Firebase Authentication without 3rd Party Cookies I will try when I have time. |
Any updates on the issue? I started getting this issue today when trying to login with Google auth with firebase. Works on Chrome. |
@indreklasn I think you need to enable 3rd party cookies for that page. The only solution I can think of is to have one global allow 3rd party cookie place where you can enable cookies from Google and/or Firebase. This may request to investigate what base domain firebase use that need 3rd party cookies, visit that domain and then enable 3rd party cookies so it will enable to use on all firebase websites. Maybe some extension (if brave allow extensions) that will enable Firebase login on any new website, without any other 3rd party cookie. |
@jcubic I have already enabled cookies and disabled shields. :/ This answer fixed the issue for me: https://stackoverflow.com/a/51277982/5073961 |
Just installed and tried it with Brave Version 0.70.121 Chromium: 78.0.3904.70 (Official Build) (64-bit)
|
Facing the same issue here. I just want to link this issue from firebase-js-sdk repo. |
No idea if this helps, but here's a specific error message I recently got showing that seemingly all requests from 'googleapis.com' are blocked when shields are up. The site in question does use Firebase for authentication.
I've recently been unable to sign in using google sign-in everywhere I've tried, and the browser even kicks me out of things I'm already signed into sometimes. :sad: |
@aormsby do you have |
ah ok - that feature is only on 1.3 and newer (which is on our Beta channel) |
I just ran into this today, discovered that Brave changes the |
No longer works, here's a project you can test on as well to get the web-page's source code: https://github.com/armand1m/react-firebase-authentication-medium |
We've just made a change to how we modify the referrer on cross-origin Would anybody be able to test again using Brave Nightly? |
Only works for me if I change the default "Only block cross-site cookies" to "Allow cookies" in the brave://settings/shields settings. Obviously not ideal. |
Thanks for the testing. It looks like aside from the referrer problems (now fixed), there is also a problem due to third-party cookies: #10367 |
closed with brave/brave-core#5952 |
Verification passed on
Reproduced issue in 1.11.x
|
Description
We use Firebase for sign in with GitHub on EricElliottJS.com. I'm unable to sign in with shields up in Brave. It works great with shields down.
Steps to Reproduce
Actual result:
Sign in fails and an error object is logged to the console:
Expected result:
Delegated authentication is a common way to improve security and user privacy by reducing the available attack surface for nefarious collectors of usernames and passwords. I hope we can figure out how to enable commonly used authentication methods and still protect user privacy.
Reproduces how often:
Easily reproduced.
Brave version (brave://version info)
0.65.120 Chromium: 75.0.3770.90 (Official Build) (64-bit)
Revision | a6dcaf7e3ec6f70a194cc25e8149475c6590e025-refs/branch-heads/3770@{#1003}
OS | Mac OS X
Version/Channel Information:
Don't know. Don't have time to check.
Other Additional Information:
Does the issue resolve itself when disabling Brave Shields?
Yes.
Does the issue resolve itself when disabling Brave Rewards?
Don't know.
Is the issue reproducible on the latest version of Chrome?
No.
Miscellaneous Information:
P.S. Using Brave as my default browser. Looking good. I have high hopes for the future of Brave and the BAT ecosystem.
The text was updated successfully, but these errors were encountered: