When I sent my application to Google oauth team, they said it's a developing or staging application and these are not allowed for oauth login. And the thing is I already published my application a month ago. And also added a download button for it on my website
Here is a pic-
What they mailed me
I am pretty sure the email/reply itself is self-explanatory.
"Google" thinks that your application itself is not complete and is still in development. Please try to contact google support team regarding this. That is all I can say from the amount of information you have given.
Related
I have developed a desktop app that uses the Gmail API to download emails from only my own Gmail account. When I try to make the app "Internal", I am told that I cannot do so, because I am not a Google workspace user. So I started the verification process and went thru the first step - the domain verification process. After this step, I received this email from api-oauth-dev-verification#google.com:
Hi,
Thank you for your patience while we reviewed your project.
It looks like your app is only used by the people in your domain, so your project doesn’t need to be verified.
(Learn more about internal vs. public users).
Note: internal use and personal use are different.
Applications for Internal Use
If this is correct, please let us know by replying to this email. We'll then close your request, and you can update your project from public to internal by following these steps:
Sign-in to Google Cloud Console
Select the project ID: getEmails (id: getemails-354519)
Go to OAuth Consent Screen under APIs & Services
Go to User Type
Select Make Internal
Click Save**
But every time I try to make the app internal, I am prevented from doing so with the same message "Because you are not a Google Workspace user, you can only make your app available to external users".
How do I get around this Catch-22 situation? Any help would be greatly appreciated.
I have developed a desktop app that uses the Gmail API to download emails from only my own Gmail account. When I try to make the app "Internal", I am told that I cannot do so, because I am not a Google workspace user.
To set an app as internal you would need to have created that app on google cloud console using a user on your google worksapce domain. You can not set an app to internal if you have created it on a standard google gmail user.
So I started the verification process and went thru the first step - the domain verification process. After this step, I received this email from api-oauth-dev-verification#google.com:
If this app is being only used by you why would you want to verify it? verification is only needed when your going to have additional users then yourself.
But every time I try to make the app internal, I am prevented from doing so with the same message "Because you are not a Google Workspace user, you can only make your app available to external users".
Again you need to login and create the app from a user on your workspace domain not on a normal gmail user.
How do I get around this Catch-22 situation? Any help would be greatly appreciated.
If its single user, and you don't have a workspace domain. Don't verify it there's no need to.
I have a small personal-use only app that logs into a [throw away] gmail account to pull out an auth-token so it can then run a scheduled job (turning on/off my home cameras). Its dead simple and works, except that the app is in GCP TEST mode and it looks like the gmail auth expires in 7 days.
I highly doubt based on the below requirements that I can promote the app, and I dont want to publish it regardless. I tried GCP Support and wound up here. Im sure Im not the only person that has dealt with the 7 day expiration on a personal project. Any ideas?
If you check the documentation for oauth2#expiration
A Google Cloud Platform project with an OAuth consent screen configured for an external user type and a publishing status of "Testing" is issued a refresh token expiring in 7 days.
The key hear is setting your project into production.
What you are showing in that image are requirements for application verification. You shouldn't have to go though verification for a single user app.
Try just setting it to prodcution and then wait a week and see if it still expires. It shouldn't
I highly doubt based on the below requirements
Unfortunately with the new security restrictions. I wouldn't doubt anything these days. They keep changing the rules.
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.
I am having this error
<"Access Not Configured. Gmail API has not been used in project ********* before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/gmail/overview?project=********* then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.">
I know Im having problem with the product ID. Couple of days ago my friend was running calendar API with my Pycharm and then he verified with his account with all the credentials. But I also created a new project>created new Credential. Downloaded the secret Json file and replaced with previous. I also checked the Json file, and the client ID was mine. But still Pycharm is still looking for that client ID which was my friends client ID. How do I resolve it?
I also tried opening new projects in Pycharm but still having same problem. I am new to python and Google APIs. If my question was too simple/obvious please pardon and help me out with the solutions.
The code I am using is given in this link, quickstart.py by Google developer page.
I finally solved the issue. I didn't enabled the gmail API from the console page. In the console page go to dashboard, next enable API and choose which API you want to enable. In my case it was Gmail.
In 2009, someone asked for 'the best' ColdFusion OpenID solution. I'd like to revisit the question again because it looks like the OpenID projects on RiaForge are getting dated.
Q: Is that because OpenID hasn't changed much?
I signed up for Google oauth, but I think that's more than what I need because oauth has to do with gaining access to someone's calendar or GMail account, and I'm just looking for the same type of login as on StackOverflow.
I watched the cfmeetup video OAuth demystified and got lost in the explanation. Maybe I should watch it again...
I'm actually using the OpenID CFC from RIAForge for a couple of projects, but I'm wondering if OpenID's day has come and gone.
Is your goal to delegate authentication to other services (Google, Yahoo, etc) or to authenticate clients on your site using a local user account? OAuth is more for the latter than the former.
There does appear to be a new player that looks to solve the same problem as OpenID: BrowserID.