带有嵌入式浏览器的Google OAuth 2.0和Captive门户 [英] Google OAuth 2.0 and Captive portal with Embedded browser

问题描述

Android和IOS设备都有一种机制来检测Guest Wifi网络上的强制网络门户。
每当检测到强制网络门户时，这些设备都会启动嵌入式浏览器以显示强制网络门户。

Both Android and IOS devices have a mechanism to detect captive portal on Guest Wifi networks. Whenever a captive portal is detected, these devices start an embedded browser in order to show up the captive portal.

我的强制网络门户允许我的访客wifi使用他们的Google身份验证凭据是为了允许访问我的wifi。

My captive portal allows my guest wifi to use their Google auth credentials in order to allow access to my wifi.

门户网站通过Google服务触发OAuth 2.0并取回用户个人资料。

The portal triggers an OAuth 2.0 with Google service and get back the user profile.

一切正常，不幸的是，谷歌决定在4月22日停止在嵌入式浏览器中支持OAuth 2.0。

All was working fine, unfortunately, Google decided to stop supporting OAuth 2.0 in Embedded browser on April 22nd.

https://developers.googleblog.com/2016/08/modernizing -oauth-interactions-in-native-apps.html

据我所知，没有办法强迫IOS或Android设备启动强制门户网站检测过程中的真实浏览器。

As far as I know, there is no way to force IOS or Android devices to start a real browser during the captive portal detection process.

由于无法控制嵌入式浏览器，我有什么选择允许我的访客使用他们的Google凭据？
如果没有其他选择，我将不得不迁移到今天没有此限制的Facebook身份验证模块。

Since this embedded browser can't be controlled, what option do I have to allow my guests to use their Google credentials? If there is no alternative option, I will have to migrate to Facebook auth modules which doesn't have this restriction as of today.

谢谢，
William

Thanks, William

推荐答案

感谢William关于Captive portal的这一说明。我们（Google身份小组）需要进行一些调查，以确定如何最好地支持您的用例。我会回复这个帖子。请继续关注。

Thanks William for this note regarding Captive portal. We (Google Identity team) need to do some investigation to decide how to best support your use case. I'll reply back on this thread. Stay tuned.

更新（4/7/2017）：目前我们已经决定不会破坏谷歌在专属门户网站内的登录。如果您的客户端确实坏了，请将客户端ID发给我。

Update (4/7/2017): For now we have decided that we'll not break the Google sign-ins within captive portals. If you do have a client that is broken, send me the client id.

这篇关于带有嵌入式浏览器的Google OAuth 2.0和Captive门户的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！