this browser or app may not be secure что делать
question
Cannot add Gmail to Outlook: This browser or app may not be secure.
Try using a different browser. If you’re already using a supported browser, you can refresh your screen and try again to sign in.
We’ve modified a lot of Windows Internet Settings, but I can access Gmail through IE and my default Edge Chromium browser. So why doesn’t it work when accessed through Outlook? Outlook appears to be using some version of IE instead of my default Edge browser. Does anyone know why that is, or exactly what setting needs to be enabled for this to work?
I was able to go here: https://myaccount.google.com/u/0/security and turn on access to less secure apps while I signed in. Once sign in completed and Outlook started populating with data, I closed Outlook, turned off access to less secure apps, and I still had my gmail syncing.
5 Answers
In order to avoid the interference of this Outlook profile, it’s suggested to create a new profile and re-add your account to check if you could add it normally there:
enable «prmpt for a profile to be used» : Control Panel > Mail>Show profiles > choose «prompt for a profile to be used »
restart your Outlook>Options>New>type a new profile name and add your gmail account
If the issue still exists there, based on my research, the less secure app access for your gmail account may also affect it, it’s recommended to log into your gmail account in browser and turn on the less secure app acess to check if the issue has any difference after that. For more information, please refer to : Less secure apps & your Google Account
Update:
The big question here is why does Outlook use IE instead of the default system browser and is there a way to configure it to do so?
Based on my research, I couldn’t find any related information that shows/explain Outlook use IE when configured gmail account as you mentioned. But based on my test on Outlook 365, I could add Gmail account normally in this system: 
So for your issue itself, did it occur on your client only? In order to further confirm if your issue is related to Outlook or your account itself, it’s suggested to log into your account on Windows Mail or other Outlook client that could work normally to check if you could configure your account normally there.
If you could add the account normally on other client, the issue may be related to your client itself, in order to avoid the interference of corrupted Outlook client, please try to repair your Outlook to check.
If your issue has any update, please feel free to post back.
If the response is helpful, please click «Accept Answer» and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Comments
Migacz85 commented Dec 14, 2019 •
Edit by @The-Compiler: See #5182 for a more detailed explanation and fix/workaround for this.
So I’m unable to log in to google services, including gmail, youtube etc. And have this message while trying to login:
This browser or app may not be secure. Learn more
Try using a different browser. If you’re already using a supported browser, you can refresh your screen and try again to sign in.
version of qutebrowser:
qutebrowser v1.8.3
Git commit:
Backend: QtWebEngine (Chromium 73.0.3683.105)
CPython: 3.8.0
Qt: 5.13.2
PyQt: 5.13.2
sip: 4.19.19
colorama: 0.4.1
pypeg2: 2.15
jinja2: 2.10.3
pygments: 2.5.2
yaml: 5.1.2
cssutils: no
attr: 19.3.0
PyQt5.QtWebEngineWidgets: yes
PyQt5.QtWebEngine: 5.13.2
PyQt5.QtWebKitWidgets: yes
pdf.js: 2.3.200 (/usr/share/pdf.js/build/pdf.js)
sqlite: 3.30.1
QtNetwork SSL: OpenSSL 1.1.1d 10 Sep 2019
Style: Qt5CTProxyStyle
Platform: Linux-5.3.15-1-MANJARO-x86_64-with-glibc2.2.5, 64bit
Linux distribution: Manjaro Linux (manjaro)
Frozen: False
Imported from /usr/lib/python3.8/site-packages/qutebrowser
Using Python from /usr/bin/python3
Qt library executable path: /usr/lib/qt/libexec, data path: /usr/share/qt
Paths:
cache: /home/migacz/.cache/qutebrowser
config: /home/migacz/.config/qutebrowser
data: /home/migacz/.local/share/qutebrowser
runtime: /run/user/1000/qutebrowser
system data: /usr/share/qutebrowser
Autoconfig loaded: no
Config.py: /home/migacz/.config/qutebrowser/config.py has been loaded
Uptime: 0:02:29
The text was updated successfully, but these errors were encountered:
Trying to login to Gmail with Selenium but «This browser or app may not be secure»
After a lot of Google searching, I got my python script to login with Selenium, but now the page is telling me that:
Is there anyway around this? Here is my current script.
Sending keys directly to the password field wasn’t working so I tried sending keys to the browser itself and now I’m getting this error. I don’t know how to proceed further.
Edit: Toggling Less secure app access did not work: https://stackoverflow.com/a/59607923/11343425
3 Answers 3
This Google Support page states that sign in via browsers that «Use automation testing frameworks» is being disabled for the following security reasons and Google advices to do «Sign in with Google» using browser-based OAuth 2.0 authentication service.
As some websites, like stackoverflow.com allow you to sign in to their services using «Sign in with Google» it must happen via Google OAuth 2.0 authentication. This implicates that doing so you are also indirectly signing in to your Google account and therefore you can use all the Google services.
So you can fully automatically sign in to your Google account, e.g. by using a Python script, by performing these actions in your code:
This way you land down in your Gmail mailbox without performing any manual actions.
Please remember to add some 5s delays between different actions as doing it too quickly or too frequently can be recognized by StackOverflow as malicious automated actions and you can get blocked and you will need to make the manual I’m not a robot verification
Electron application using Google OAuth: «this browser or app may not be secure»
A user of my app reported an issue today about authorizing the user with Google (using OAuth 2.0). So far the application was opening a new BrowserWindow (node integration disabled, session is separated from the main application). You can see the implementation here since the library is OSS. I am using this to authorize the user to access application data on Google Drive. Today after logging in I see the following message:
This browser or app may not be secure.
Try using a different browser. If you’re already using a supported browser, you can refresh your screen and try again to sign in.
The learn more link has a section for developers. This section has 2 links. One is how to upgrade the application to PWA. Because the application is an API testing tool it won’t be possible to run it in a web browser. The second link points to a document describing how to migrate to authorization for native application. However described flow requires authorization_code grant. This means I need to include OAuth secret into my application. Electron application, however, is still web application and there’s no notion of compiling sources. I would expose client secret to the public which is not secured. Potentially I could build a server application to support it but the app is OSS project. It does not have funding to run a server for authorization.
My question is now how should I implement OAuth 2 for Electron application then. I can’t use PWA’s and server authorization flow (code grant) is far from ideal in this case.
3 Answers 3
As Paweł explained, changing the user agent will do the trick. However, you can easily set the user agent by passing an object when loading the URL
I have tested it and it worked like a charm
Warning: This answer relies on changing the browser’s user-agent. As of Jan. 2021, Google disapproves of this and warns not to do this (see EDIT4). Use at your own risk!
The other answers didn’t work for me (in Electron 9.0.5), but I eventually found this, which worked:
EDIT: Two other approaches, which I haven’t tested, but which may also work:
EDIT2: Trying again sometime later, approach #2 did not work, but #1 still did. Haven’t tried #3 yet.
EDIT3: Trying again later still, it seems that none of these workarounds are needed anymore! Google appears to accept sign-in popups from Electron apps again, without modifications to the user-agent. (odd that they’d revert this; perhaps I just did something wrong in my re-attempt)
EDIT4: While approach #1 still works atm, I recently found this blog post: https://developers.googleblog.com/2020/08/guidance-for-our-effort-to-block-less-secure-browser-and-apps.html Apparently Google is restricting usage of Google sign-in in non-standard browsers (which presumably includes Electron) starting in Jan. 2021, and warns developers not to modify their browser’s user-agent (which all three of the possibilities I mention do). Use at your own risk! (they don’t make clear what outcome will result, but for my own use, I’m opting to use the alternative shown below from now on)
This browser or app may not be secure что делать
But why doesn’t Steam have a secure browser? People should be able to link their videos without having to download another browser. Sort of rediculous that the base client does not offer this functionality. Shouldn’t it be updated or something, so that it works?
The Steam client interface obviously does not work very well, if they cannot even do this without having to download another program.
But why doesn’t Steam have a secure browser? People should be able to link their videos without having to download another browser, imho. Sort of rediculous that the base client does not offer this functionality. Shouldn’t it be updated or something, so that it works?
The Steam client obviously does not work very well, if they cannot even do this without having to download another program.
But why doesn’t Steam have a secure browser? People should be able to link their videos without having to download another browser.
It was Google’s decision last year to make it act this way.
so what are you even on about.
I am talking about age-restricted videos.
I suppose we have wait for a solution, because this is not working very well, if people cannot age-restrict their own videos anymore, without blocking themselves from viewing those videos through Steam. This decision results in causing age-restricted videos to be completely inaccessible through Steam, unless Steam updates their browser to enable their users to access those videos.
For instance, you want to watch a video that happens to be age-restricted, because there is bad language, blood, explicit graphics, or violence in the video, and you want to access that through the interface, by using the Steam in-game overlay. Right now, that is not possible, it seems.
Just imagine how impractical this is for walkthroughs and such, that happen to show a video of a game that is already age-gated on Steam.
This answer does not solve anything in that regard, because the issue is still there, and this is not a solution for everyone.
I am guessing they authenticate the Steam app at Google once more?
What I think is a good solution is that the Steam user gets an age gate for age-restricted videos, sort of in the same way as it get done on YouTube. So that they can just put in their age and then it loads, and if they are too young, the app sends them to another place.
Currently, this situation only handicaps the users who properly set age-gates on their videos, because the users who don’t care, do not receive any restrictions at all, and can watch their videos regardless.
Right now, they are encouraging us to remove the age-gates, but I do not want to do that, because otherwise I would not have age-gated them in the first place. If I remove the age-gates, those videos pop-up in everyone playlists on YouTube, and they start auto-playing, etcetera, and I do not want that to happen, because some videos aren’t appropriate to just pop-up in everyone’s playlist on YouTube. That would only draw a lot of unwanted attention, because those videos aren’t supposed to pop-up in someone’s playlist, if they are just casually watching some videos, and therefor I need to have them age-gated.
I should not just remove the age-gates from those videos, because that wouldn’t be proper. Right now, if the Steam user wants to watch some of those videos, they are encouraged to make an entire YouTube account, which is an extreme measure, if a simple age-gate would also suffice. They have to jump through a lot of hoops.
Anyway, I’ll figure out a way around this. It’s no problem. I’ll figure something out. It’s just, that the age restricted videos become pretty difficult to access now through Steam, and I have to make a lot of extra steps, and the users end up having to see them on YouTube, instead of being able to stay on Steam. So they end up on the YouTube website, in order to view the videos, while my idea was for them to be able to see them in the Steam client, as I originally intended. So, that the Steam community could stay on Steam, and the YouTube community could stay on YouTube.
Long story short: It seems impossible now to see age-restricted videos through Steam.