Problem using https://www.googleapis.com/auth/photoslibrary.readonly with the OAuth 2.0 Playground - oauth

When using the Google Developer OAuth 2.0 Playground, when I enter the oath scope "https://www.googleapis.com/auth/photoslibrary.readonly" and press the "Authorise" button, it asks me to sign in with my Google Account which I do without any issues and then takes me to this error page ... This app is blocked This app tried to access sensitive info in your Google Account. To keep your account safe, Google blocked this access.

Related

OAuth consent screen not showing permissions

I have a google login in my app when I try to click on sign in with google I do not see the permission it needs to access
My app uses users contacts and so I have added it to scope in consent screen settings but it do not show any permission. Can someone help me if there is anything else that needs to be configured as I need to verify my app from google
I want permission to display like this(sample image)
Scopes that I am using
this is the api
Lets use the Google Oauth Playground to test a little.
test 1 requesting authorization to Oauth2 scopes.
I am going to select Google contacts really there is not much point in selecting this one using google People api is a much better choice.
And everything under Google People API
This is the consent screen shown me
test two authenticating with open id connect
I am going to only request
Now profile and email are special they are related to Open Id connect, which is out side of the Oauth2 because of that i was not actually shown a consent screen. Because i am Authenticating to Google that this is me logging in.
I am not Authorizing any Oauth2 scopes because none were really requested. Now this make confuse you because by requesting profile you are automatically given access to the users profile data which means that you can access the Google people api and do people/me and get the information about the person.
conclusion
Only Oauth2 scopes appear to the user requesting access. not open id scopes.

iOS App How to Submit Google OAuth Verification to Use Google Calendar

Hi While using Google Calendar in my iOS APP, the screen prompts a warning like as bellow
This app isn't verified by google yet...
only proceed if you know and trust the developer
To avoid this warning I need to submit my iOS App to Google OAuth Verification
I searched in different sites but i didn't get a clear doc to Submit An iOS App for Google OAuth Verification.
Could someone help to provide the steps/guidelines link to Submit An iOS App for Google OAuth Verification.
Thanks in advance...
Go to the google developer console Under credentials
You will find the consent screen tab
At the very bottom of this page you will find a button
Before submiting you should read though the information provided on that page along with the links
OAuth verification
To protect you and your users, your consent screen
and application may need to be verified by Google. Verification is
required if your app is marked as Public and at least one of the
following is true:
Your app uses a sensitive and/or restricted scope
Your app displays an icon on its OAuth consent screen
Your app has a large number of
authorized domains
You have made changes to a previously-verified
OAuth consent screen The verification process may take up to several
weeks, and you will receive email updates as it progresses. Learn more
about verification.
Before your consent screen and application are verified by Google, you
can still test your application with limitations. Learn more about how
your app will behave before it's verified.

Sign in with google prevents the user to sign in again with different account - iOS

I'm using google authentication to sign in with firebase.
The authentication process works well and I'm able to create the credentials and authenticate.
My problem is when, after signing out from firebase and google, the user tries to sign in using google again. At this point google will automatically authenticate with the account used previously.
I tried both sign-out and disconnect option from google api but the result is the same.
I partially found what my problem was, here steps to reproduce:
Not signed in with google in app and not signed-in in safari on the device with a google account
Sign in with the application using a google account
Now I am signed-in in app AND in safari as well with the same account
When I sign-out from the application, safari is still authenticated with this user
I'm not able to see the account choice in app until I sign-out the google account from safari on the device
This problem doesn't show up if safari (point 1) was already signed-in with a different google account. In this case I will always have a choice between the two accounts in app.
Is there a way to sign out from the app and always shows the account choice when signing in with google again?
There are many Authentication URI parameters. One of them is "prompt" which could have a "select_account" value. It helped me to resolve the same issue for Auth0-service Google integration. Maybe could be useful for your issue if the SDK allows setting parameters for sign in.
See docs here: https://developers.google.com/identity/protocols/OpenIDConnect#authenticationuriparameters

Issue : Connecting using OAuth to Jawbone from android app

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.

GMail API iOS Authorization

I am using the Gmail API in iOS with the code that is given on the link
https://developers.google.com/gmail/api/quickstart/ios?ver=swift
and I tried running the application on an iPhone but every time, when I start the application it is asking for a Google login for authorization.
The page at Google Developers says that:
Authorization information is stored in your Keychain, so subsequent executions will not prompt for authorization.
So my question is that for my application is the Keychain value not being stored, if so how can I correct it and if not what can be the possible error in the code that is in the link provided above?

Resources