I am developing a web application that needs to access 100 or more different Google Calendars using OAuth2. All calendars are on different accounts with the corresponding users. I stumbled upon this paragraph from Google:
"Note that there are limits on the number of refresh tokens that will be issued; one limit per client/user combination, and another per user across all clients. You should save refresh tokens in long-term storage and continue to use them as long as they remain valid. If your application requests too many refresh tokens, it may run into these limits, in which case older refresh tokens will stop working."
My application reportedly uses access tokens and then stores the update tokens in the database for later use. I am wondering if I have reached the limit on the number of calendars my update tokens will work with. Someone had difficulty before the updated tokens stop working after reaching the limit. There are two limitations mentioned in the paragraph, but I'm not sure if my application will be affected, since each calendar is a different user. I'm not sure what Google means "and another user on all clients"?
Anyone who has experience or knowledge in this, please help.
Thanks in advance.
source
share