title: Google OAuth 2.0 and Captive portal with Embedded browser
body: <p>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.</p>
  
  <p>My captive portal allows my guest wifi to use their Google auth credentials in order to allow access to my wifi.</p>
  
  <p>The portal triggers an OAuth 2.0 with Google service and get back the user profile.</p>
  
  <p>All was working fine, unfortunately, Google decided to stop supporting OAuth 2.0 in Embedded browser on April 22nd.</p>
  
  <p><a href="https://developers.googleblog.com/2016/08/modernizing-oauth-interactions-in-native-apps.html" rel="noreferrer">https://developers.googleblog.com/2016/08/modernizing-oauth-interactions-in-native-apps.html</a></p>
  
  <p>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.</p>
  
  <p>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.</p>
  
  <p>Thanks,
  William</p>