TeamDesk Knowledge Base & Support

   Home      FAQ      Forum      Idea Exchange      Ask a Question      My Stuff      Help   
  
Google API Authorize
Is anyone else have issues with Google API Authorization for Call URL's.

We have many Call URL's in our system for Google Calendar integration and they all work great. I was trying to add some additional today and when we try to authorize to Google the authorize button does nothing. Again all of my previously authorized work fine just can't add any additional.

On a side not don't know if it is related or not but sometime in the last day or two I have lost the ability to Cut and Past inside a Call URL as well. the two buttons are gone that are normally up by the Help button. they are still there for all my other types of fields just to on Call URL's

Mike
ID
1286
Category
Integration/API
Author

Mike Nelson
Date Created
6/20/2019 5:01:58 PM
Date Updated
5/5/2025 3:28:40 PM
Comments
basenine 6/20/2019 5:40:19 PM
Apparently Google were having issues yesterday with Calendar

It may be related(?)
Kirill Bondar  Staff  6/21/2019 4:03:58 AM
It was a little glitch on our side. Please try again.
L. C. Parker 5/4/2025 3:24:38 PM
When trying to use 3rd party account and authorizing through Google , receive the following error

The app is requesting access to sensitive info in your Google Account. Until the developer (sales@teamdesk.net) verifies this app with Google, you shouldn't use it.
Kirill Bondar  Staff  5/5/2025 2:17:29 AM
OAuth 2 uses the concept of "application" -- one that requests the data on user's behalf. The application requests the set of privileges and keeps track of user's granted permissions.

To let database library samples work out of the box we registered two OAuth 2 applications -- one with Google and one with Microsoft. Both requesting broadest set of privileges possible and because of that one registered with Google triggers the warning. We even started verification process but were unable to explain properly why our OAuth 2 application wants to access every piece of user's data.

For best results, you should probably register your own OAuth 2 application with Google asking just for privileges you need. By registering an application, you will obtain your very own Client ID and Client Secret, and its security parameters will be under your control.

Here is Google's instructions:
https://developers.google.com/identity/protocols/oauth2/web-server

Redirect URL mentioned in instructions is:
https://www.teamdesk.net/secure/oauth.aspx

Modify your third-party account to use:

Type: OAuth 2
Authorization URL: https://accounts.google.com/o/oauth2/v2/auth?access_type=offline
Token URL: https://oauth2.googleapis.com/token
Client ID: <obtained from application registered at Google>
Client Secret: <obtained from application registered at Google>
Scope: <comma separated list, consult with https://developers.google.com/identity/protocols/oauth2/scopes for a list of available scopes>
L. C. Parker 5/5/2025 3:28:40 PM
Thank you for such a thorough explanation, and solution. I will move forward with your suggestions
Feedback
Back to Search Results