On Google Cloud Platform I created a project and OAuth 2.0 Client IDs. Everything works fine (register/login with Google Account) but I have a concern with the following screen at "OAuth consent screen"
It says that it needs verification, and that I should prepare my app to submit such a request. Everything is okay but when I click on "prepare your app" (from the picture above) it gives me the following screen
Would you please be so kind and let me know what are my next steps to verify my app and how can I do that?
Related
We are using Google Sheets API in our product.
To use API, we configured OAuth consent screen described in the doc below, and we passed the valification process by Google.
So, functions using the Sheets API have now been released and are already in working order.
Configure the OAuth consent screen:
However, due to the change of our company name and product logo, we have to change the infomation shown in OAuth consent screen.
We will not change scope of API access.
After some research, I found that if I tried to change that information, it would trigger Google's validation process again.
My question is, can we use Sheets API while Google's revalidation process?
We must run our production app with no down, even if our OAuth app under validation process.
I cannot find any document about that.
Someone please tell me the availability of API under validation process, or tell me the document about that.
After getting the Google Fit API to authenticate user and read data on the phone I use for debugging, I sent the debug.apk to my friend's phone to test it. I checked the Cloud Platform console, the API dashboard shows the requests.
However, it is not working on any device except mine. I tried with testing mode on google cloud(all the emails were added as testers), it did not worked. When I publish the app on google cloud, nothing changes, same problem again, getting result code 0.
I would like to know if problem is with google cloud platform or I should wait some time...
I tried different official tutorials but they all ended up to be misleading.
The last one was this: https://cloud.google.com/iap/docs/cloud-run-sign-in -- it ​says:
Enable external identities, and select the Host a sign-in page for me option during setup.
But there was no such option. No new Cloud Run instance was created and so nothing has happened. Then after a while I've updated the source code of my application, redeployed and the blue login button appeared on the Cloud Run instance URL instead. NO documentation tell that "on this step you'll now see the blue button" so I don't know for sure what it is. When I went through the dialog it said I should add the Cloud Run instance URL to the "allowed origins" in the OAuth app I created a week ago by trying different tutorials I mentioned in the first place. Aha! I add the URL as allowed but this does nothing -- it just loops, the dialog leaves me on the same page with the same blue button instead of my Cloud Run instance response that now I effectively have no access to. I am the GCP Project owner and I want this all to check that it's me to invoke the Cloud Run. How does this specific OAuth app blocks this specific Cloud Run instance at all? I have multiple apps made in months or years and multiple Cloud Run instances but only now this blue button appeared.
Being unable to make it work I decided to roll it all back. I allowed the Unauthenticated calls to my Cloud Run instance, disabled the IAP API, deleted the OAuth app, redeployed several times, but the blue button is still there with dialog saying: "The OAuth client was deleted." And I see nothing like my current problem to be described on https://cloud.google.com/run/docs/troubleshooting
So now not only the whole thing didn't work (the "sign-in page" does not deploy, not even if I disable and enable the IAP API again) but I've lost the access to the Cloud Run instance at all -- it's blocked by the blue button that is nowhere to disable. Even when I deploy new services they are behind this broken thing.
UPD: after a while I've realised that I didn't really lose any access -- the "blue button" was an artifact of the failed tryings to setup the auth, a my own copypasted htm page that didn't work, and I was just visiting the wrong path appended to the service URL. So the question is half-invalid. Though the problem of the "create a sign-in page for me" persists.
Currently, IAP is only supported with App Engine, Compute Engine and HTTPs Load balancers. Cloud Run isn't yet supported. It is planned to be supported in the near future.
As a workaround you can check those two options in order to implement with your application:
1 - A similar stackoverflow post where is stated and answer about how to Google Sign in for Cloud Run
2 - A Cloud Run hosted version of an IAP in Terraform config made by the community
Also you can try to Setup a Load Balancer with Cloud Run and see if that solves the issue you're facing.
Enable external identities, and select the Host a sign-in page for me option during setup.
I believe this is referring to - when you turn on IAP and choose 'use external identities for authorization', there is an option that says - 'Create a sign-in page for me' with a note which says - IAP will create a sign-in page for you using Cloud Run and Firebase UI
2.
I tried following the steps and after checking the option to 'create a sign-in page for me', it showed me a popup window with a message that it was creating a Cloud Run instance for me. After about 3 minutes, it said it was done and showed me url for the Cloud Run instance and a link to the page settings
3.
Regarding access to the Cloud Run instance, I think it's best to just delete it from the UI (Google Cloud Console). Redeploying will then recreate the Cloud Run service and you should no longer have the 'blue button' since you say you have disabled it
I have created a Youtube API application to enable access to Youtube API for Integromat. All my Youtube API application does it gives access to my Youtube channel videos for Integromat. Integromat grabs the links to videos and uploads the links to my Airtable. So the only user for the Youtube API is going to be myself and my own Integromat workflow.
The Youtube API app is in development. I want to verify the app to get rid of the 1-hour deactivation of the authorization (Integromat connection to Youtube API breaks after 1 hour).
To get verified, I looked the steps here https://support.google.com/cloud/answer/7454865?hl=en. The first step it tells me to do is "Update the OAuth consent screen details" and I go to that screen and shows the publishing status. Do I click to "publish to production"?
When I click that, it tells me:
Your app will be available to any user with a Google Account.
Screenshot showing the step to publish my app
That's sounds scary. What does it mean?
I do not need (nor want) have other users logging to my Youtube API. I am the only user and Integromat is the only app that will access the Youtube API.
I am novice in this and don't have much idea about programming so I don't even know what questions I should be asking here.
Thanks.
Here are more details about what I am trying to do in Integromat:
Youtube API Integromat testing app - connection getting disabled
It means that you will be able to share your app via that link with anyone you please. The whole point of an API is that it's available publicly, at least on a technical level. Whether you're actively soliciting users is an entirely other matter, naturally.
Ive set up my google cloud platform credentials because i want my app to use cloud saves. Everything works perfect when testing, whenever i build from unity to my phone everything works fine.
But then i uploaded my app to google play as closed testing, changed the sha1 keys on oauth on google clouds platform to the App signing key certificate and only the emails that are added as test users on the OAuth consent screen get and infinite loading. All other accounts work fine and are able to connect to google services just fine. Ive also change the key on oauth to Upload key certificate and the problem persists.