Fix credentials refreshment in Google OAuth2 #941
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
All Submissions:
Changes proposed in this Pull Request:
Fixes an issue with Google OAuth, where even though refresh token was stored, it was not used to refresh credentials.
Two scenarios have to be handled here - if a user authorises the app for the first time, they will receive a refresh token (allowing them to connect after the access token expires). Otherwise, they will receive only an access token, which will expire after a certain amount to time.
How to test the changes in this Pull Request:
_newspack_google_oauth
user meta) from the DBOther information: