I am having one wifi captive portal Which asks user for "google plus" login first to continue wifi access. As devices do open embedded browser for this, Google OAuth 2.0 throws 403 error. Error: disallowed_useragent
Is there any way i can check that browsers is embedded or not with useragent string or something? So that in webpage i can put javascript code which will identify browser and eliminate google login option for that devices.
i'm in the same situation, as reported :
Google OAuth 2.0 and Captive portal with Embedded browser
.. we have to drop a message to Nvnagr (Google Team), with client-id and wait until he decide to "whitelist-us"
Hope to be next in whitelist :)
Related
We are getting this Error Title "you can't get there from here" in a webView used for MSA login in a Xamarin iOS app. We are using external login into a ASP.NET WebApi redirecting to the webApi itself.
The detailed error text is as follows:
"You cannot access the resource from this browser on your device. You must use safari or intune managed browser"
The login works for all accounts; personal and work accounts. But the accounts we have problems with, seems to be some kind of restricted work accounts.
We are using UIKit.UIWebView.
Can someone give a hint on what is going wrong here?
Is that a policy problem that can only be solved on account administration side?
Do we miss something in our app/webApi configuration?
Is there an embeddable webView control for iOS that supports that kind of account restrictions?
Many thanks for your help!
"On April 20, 2017, we will start blocking OAuth requests using web-views for all OAuth clients on platforms where viable alternatives exist."
We received this notice. In our iOS app using the Google drive, but google drive sdk no updated. google drive sdk still uses the old way. We need to modify the authorization method?
If you are using the WebView for Google OAuth authentication (i.e. if the user has to type the Gmail address and password in a WebView), yes, you have to update it.
You have two options.
SFSafariViewController: Load the Google login URL in the SFSafariViewController instead of the WebView. If you are accessing any cookies in the WebView, you cannot do that in the SFSafariViewController. For iOS 8 and below, which does not support SFSafariViewController, you can fallback by opening the Safari browser to authenticate.
Google Sign In SDK: Use Google Sign In for iOS SDK. You put a Google Sign In button in your app and use the Google APIs to authenticate.
For more information, refer this presentation from Google devs: https://docs.google.com/presentation/d/1z7bgAqYcEt7EHRmwe3T-vF_iMw9e8Wyxr10wPudypEo/present?slide=id.g135ae23358_0_71
We are using Jawbone API to pull data tracked using jawbone devices.
Our users are successfully able to sign in when they access Jawbone sign in page during OAuth process from our website.
However, they are not able to sign in when they access jawbone authentication page from our android app during OAuth process. This authentication page is launched in webview on andriod.
On log in page after entering correct credentials and clicking on Sign In button does nothing. The page even does not display whether credentials were correct or not.
Is the OAuth authentication user agent (web/app) dependent?
We have started facing this issue just recently and before it used to work perfectly.
Jawbone's OAuth2 flow operates through web login and approval pages, then issues a redirect callback to your server. Jawbone has several partners who do this within their Android apps.
It sounds like your app is not handling the callback half of the OAuth2 flow correctly, but it's hard to say based on this description.
Have you reviewed the Authentication documentation?
Also, consider Jawbone's Android SDK.
I am building a Chrome Extension, that will have specific user setting stored in my own server and communicate with that server via an API.
Server will be running Node.js API built using Express.
I will also have an iPhone app that will pretty much use same API on the same server.
Since my main piece is Chrome Extension, I figured I can use the Google Account authentication instead of my own authentication since I am catering to Google Chrome users mostly.
The way I thought this through is:
User opens chrome extension.
Extension shows a small login popup with a button authenticate via Google Account(or should it show email and password fields? Not sure
how Google authentication works).
User types their email and
password, and Chrome Extension fires an Ajax request to Node.js API
to obtain a token?
Basically, my question is, what is the logistics of such a system? Do I need to store a password in my database? Do I just link users via email only, and Google will handle the password storage and authentication?
I am lost :/
we're developing a wifi hotspot captive portal where users can authenticate with their preferred social network credentials.
Of course before user's login on captive portal he/she can't reach internet, so some urls must be open in order to be able to reach external authentication pages.
Unfortunately for us, facebook's oauth dialog is "https://www.facebook.com/dialog/oauth". Being https we can only open IPs or hostnames, but we have no control on "path" of the request, so we should open all www.facebook.com site. Unfortunately, for legal problems, it's not possible.
The simplest solution would be to have oauth dialog page on a different url (example: http://oauth.facebook.com/dialog/oauth...), is it possible?
Any other suggestion?
I've found some similar questions in this forum (so forgive me for the duplicate question), but none has an answer.