Repository navigation
Obtaining and storing a new access token. #42
Description
Activity
You need to preserve the
refresh_token, you can retrieve it once and need to persist. Even if you don't provide an access token, client will fetch a new one.Okay, so we don't expect the
refresh_tokento change, ever (unless youapproval_promptand get a new one), which is consistent with these docs and this code.So for an ongoing offline task, I see two options:
- Don't store an
access_token, and letOAuth2Clientget a new one on every request. - Store and set
oauth2Client.credentials.access_token, and on the completion of every request (viaexecute) store a (potentially updated)oauth2Client.credentials.access_token.
Where the advantage of the second option is:
If the
access_tokenis still valid, then you'll save a HTTP request (to get a newaccess_token) for every request you make.Looking at the OAuth2 playground an
access_tokenexpires in 4000 seconds. So if you're making more than one request per hour, it's probably worth using option 2, otherwise you'll make just as many requests with option 1 (and you won't need to persistaccess_token).- Don't store an
You're right. If you make more than one request in 4000 secs, it's better to go with the second option.
Building on #14, I see that when you ask for
offline_accessand you haverefresh_tokenthen we get the behavior:Presumably we would be wise to obtain and store the new
access_tokento use in the future?I don't see this mentioned in the existing documentation.