Is there support for Google OAuth 2.0 ?
See original GitHub issueHi there, recently we received an email from Google at work saying that one of the apps we develop may be blocked from signing in because Google is making an effort to block sign in from inside embedded browsers.
Our app uses react-native-webview to render a web page that has html form to login using email and password or social login with Google and others
Here is the link that came in the email https://developers.googleblog.com/2020/08/guidance-for-our-effort-to-block-less-secure-browser-and-apps.html
And here is the key point from that link
If you're an app developer and use CEF or other clients for authorization on devices,
use browser-based OAuth 2.0 flows.
Alternatively, you can use a compatible full native browser for sign-in.
For limited-input device applications, such as applications that do not have access to
a browser or have limited input capabilities, use limited-input device OAuth 2.0 flows.
I’m gathering information about this and I wonder if you guys can help me understand if react-native-webview qualifies as one of the cases that will be blocked by Google in their security efforts
Here are two more links that may be helpful understanding Google’s pre requisites https://developers.google.com/identity/protocols/oauth2/native-app https://security.googleblog.com/2018/10/announcing-some-security-treats-to.html
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:17
Top GitHub Comments
I’m interested in the same question. Did you figure anything out @gabriel-tentaculo ?
Hello 👋, this issue has been opened for more than 2 months with no activity on it. If the issue is still here, please keep in mind that we need community support and help to fix it! Just comment something like still searching for solutions and if you found one, please open a pull request! You have 7 days until this gets closed automatically