Menu
https://console.developers.google.com/project/*/apiui/credential
The credentials panel on repeatedly clicking also does not load ( keeps loading )
I need to access the Oauth 2.0 and I am unable to because nothing is being displayed.
I have done the following activated - google analytics api ( enabled it)
Now i need to access Oauth 2.0 and My internet connection is fast yet the credential section does not laod and all other section in the google developers age is loading .
What should I do to get this resolved ?
514
To enable the credentials click on API Console after clicking on Enable the Gmail API . You will travel to a filled form on the Credentials menu on Google APIs . You can change there the name and/or restrictions to better suit your project. Finally, you can click on Generate key to finish the process.
All credentials have a token that is used for authentication and may also optionally set an expiry to indicate when the token will no longer be valid. Most credentials will be invalid until refresh() is called. Credentials can do this automatically before the first HTTP request in before_request() .
To create a credentialIn Object Explorer, expand the Security folder. Right-click the Credentials folder and select New Credential.... In the New Credential dialog box, in the Credential Name box, type a name for the credential.
For me, it was the Disconnect chrome plugin.
146
[late edit: Other answers imply that this can be caused by browser extensions and / or security proxies (which often come with anti virus or firewall software). Please check whether you have an adblocker/privacy tool/etc. enabled - disable temporary and then try again. If this doesn't help, continue reading...]
Sounds to me like this could be resolved by filling the OAuth consent screen
https://console.developers.google.com/project/<yourprojectid>/apiui/consent
You'll need at least a product name and the email address filled. Google recently made a change so that you cannot create credentials as long as the consent screen is not filled. Before that change one often got cryptic errors during oauth, so this change actually makes sense.
If that doesn't help i recommend setting up another project and do a quick test with that project. Sometimes a project is not properly setup at Google in which case you'd need to contact Google's customer support.
41
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
