DevExpress
Google logins no longer work through Testcafe
It looks like, as of a few days ago, Google has started detecting testcafe-hammerhead (or something it does) and rejecting log-in attempts. Fails on testcafe-hammerhead 17.1.17, but tested various previous versions too and have the same issue, so it does not appear to be a regression on the testcafe-hammerhead side.
To reproduce:
- Chrome 85.0.4183.102, Mac OS X 10.15.6 but seems to happen on all Chrome versions I have been able to test with, and also Safari (but does not seem to happen every time)
- Start testcafe-hammerhead playground
- Enter: https://accounts.google.com
- When prompted for user ID, enter: abc123
- Get 'This browser or app may not be secure' warning, before even being prompted for password
Since the proxy should be invisible to the visited site, I am not sure why this now breaks (it has worked for the past 12 months). This would affect any testing that involves authenticating via Google, which is quite commonplace. Any ideas?
UPD: Sign in with a supported browser
@adriancable
Hello,
I reproduced the "This browser or app may not be secure" error.
I am not sure why this now breaks (it has worked for the past 12 months)
I suppose this issue relates to the update of the Google login mechanism. We'll need some time to research this behavior.
Related issue: https://github.com/DevExpress/testcafe-hammerhead/issues/2423.
@Farfurix - thanks, I appreciate it very much. Since a lot of sites use Google OAuth or "Sign in with Google" I think this may be something that potentially will begin to affect many people.
@LavrovArtem - unfortunately, the problem is still there, just the same. It does not happen with every account, every time, so if you do not see it sometimes please do not think the problem has fixed itself.
If you would like instructions on how to reproduce the issue 100% of the time, please email me at [email protected] (as I do not want to post credentials in a public place), but even if not, since other people have reported the same issue (e.g. DevExpress/testcafe#5596) you may not wish to close it until it is resolved.
Sure. We need to see how to reproduce this issue and then fix it. I actually was able to reproduce it once, but now everything works as expected for me. Would you please send an email with your credentials to [email protected].
@adriancable
Hello,
I reproduced the issue with your email address. Could you please try turning on the "Allow less secure apps" Google account setting to workaround this security check? Please tell us if it works in your case.
@Farfurix - unfortunately, according to Google this setting is not available accounts with two-factor authentication enabled. So my account does not have this setting.
Hi @Farfurix - I note that this was assigned to Sprint DevExpress/testcafe-hammerhead#68, which was completed a while back even though this issue was not resolved. Do we need to reassign this to a new sprint, so it does not get forgotten?
@adriancable
Hello,
We are researching this issue. We haven't planned our next sprint yet. Watch for our updates in this thread.
Hi - note @AndreyBelym modify the tags a few hours back. Do you have any update on identifying the cause of this issue? Thanks!
@adriancable @Farfurix Hello, My test had the same thing.
When I created a new Google accout and tested it, this issue did not occur. But the existing Google account didn't solve the problem.
@Farfurix - we understand that, if you had updates on progress, you would post them here, and because there is nothing, there are no updates.
However, we are certain that you have investigative work at least planned and scheduled in your development roadmap, so we would appreciate if you can share that schedule with us those of us impacted by this issue know when to expect results.
We think this is a serious issue, higher priority than many others for which PRs have been created, because it affects the testing of any web site or web app that uses Google SSO.
Thank you!
@adriancable
Hello,
We can only say that a lot of resources will be required to implement and maintain this functionality. Any changes to the TestCafe/hammerhead/Google authorization mechanism may have a bad effect on it. At the moment, I cannot give you any estimates on when we will return to this issue.
I believe that the simplest way to resolve this issue is to mock the Google (or any other) authorization at the web app development stage.
@Farfurix - are you able to email me on [email protected]? I have an idea around this issue which you and your team might find interesting and attractive.
@adriancable
Feel free to share your idea in this thread. We will take it into account.
@Farfurix - my idea is a commercial one.
My idea is that we discuss a potential consultancy project to scope out the work and cost required to address this issue, and if it looks good we execute on that project. I am happy for the results to be given back to the community under the MIT license. The idea of this is win-win-win:
- Win for you, since you get $$$ from me which you can invest in other development areas of your choice.
- Win for other DevExpress customers, since they get full access to the results of the work.
- Win for me, since I get development time from you on an issue which is important to me, which otherwise you cannot tell me when you will work on.
I acknowledge you request discussing in this thread, but Github is not the right vehicle for commercial discussions, hence my request for you to email me privately. If you want to continue this discussion, my suggestion again is that in the first instance, email is the best approach.
@adriancable
Hello,
TestCafe is an open-source framework. We don't accept commercial ideas. You might want to find proper specialists on LinkedIn or similar web sites.
We use all our resources to address priority tasks. At the moment, this issue is not on our priority list based on the information we have.
@Farfurix - sorry if I wasn't clear. Under my suggestion, any work you would do under this arrangement would be fully open-source and would be available to everyone. So, it would benefit not just me but the entire Testcafe community, specifically the other people in this thread who are also coming up against the Google login issue.
FYI: I'm still running into this issue also and I have set the "Allow less secure apps" Google account setting to On. Thanks!
Hi @adriancable,
This issue is not reproduced with combination of [email protected] and the Google Chrome browser. Feel free to reopen this issue if you encounter it in other browsers.
