Google Connect warning on Instagram-App

[n1c0]

Hello Everybody!

We have discovered a problem. When users click on our registration via an Instagram add or our page there and want to connect to Google Connect, they get an error message.

“Access blocked, the request from Holistic violates Google’s guidelines: Use Secure Browsers”

The message comes after the user typed in his credentials. It seems that the internal Instagram browser does not appear to be secure for Google. Makes sense, too.

The question is: Can I hide the GoogleConnect only in the Instagram context? Or is there an other solution?

[dawid.matuszczyk]

Hi @n1c0

Welcome to the Auth0 Community!

You are right; Google OAuth does not work with embedded web views per policy. → Modernizing OAuth interactions in Native Apps for Better Usability and Security - Google Developers Blog

You can utilize the GET /authorize endpoint to direct the user to the specific ODIC connection by specifying the connection parameter. This should bypass the Universal Login prompt. Authentication API Explorer

Google SSO in app browsers (webviews)

Problem statement We’re constrained to use the universal login page on our site within a webview in a 3rd party product, which causes a 403 for Google SSO. We can’t conditionally hide Google because existing users need to use Google to log in. The 3rd party product can’t just not use the webview because this is fundamental to their dapp browser feature, and other similar products use the same. Is there a way for auth0 to open an external user agent from within an embedded user agent in a native…

Google Social error for web login from embedded browsers

Problem statement We have users that can’t log in through Instagram or TikTok embedded browser. Symptoms 403: disallowed_useragent for web login from embedded browsers (Instagram / TikTok embedded browser) Cause Google OAuth does not work in embedded web views per policy. See Modernizing OAuth interactions in Native Apps for Better Usability and Security — Google for Developers Blog - News about Web, Mobile, AI and Cloud Solution The workaround is to use one of the alternatives recommend…

I hope this will help you!

Dawid

[n1c0]

@dawid.matuszczyk

You can utilize the GET /authorize endpoint to direct the user to the specific ODIC connection by specifying the connection parameter. This should bypass the Universal Login prompt. Authentication API Explorer

Hey Dawid!

Thank you for your quick response and the idea to fix it

It would be great to set a parameter to get only the “email/password” registration-form without connections. Can I achieve this with the authorize endpoint?