Open rajathms opened 5 years ago
Short answer: No, satellizer doesn't need to be updated for the Google+ API shutdown.
Long answer:
Because satellizer defaults already use the recommend scopes, it won't need to be updated. But your application might get affected depending on the additional scopes you are requesting during the OAuth flow. For example, one of my applications was using the https://www.googleapis.com/auth/plus.business.manage
scope which is now deprecated. So, I updated it to recommended replacement scope https://www.googleapis.com/auth/business.manage
.
The defaults scopes used by satellizer are: https://github.com/sahat/satellizer/blob/ae2863338ab7214e8f3be7b5fae6373a18d7a11b/src/config.ts#L37-L38 which are already the recommend scopes.
Google+ APIs will be shut down on March 7, 2019. This includes Google+ Sign-in and OAuth token requests with Google+ scopes. How it affecting satellizer, if it is, what are the necessary changes have to take by the end user of satellizer, if satellizer is being updated for this change, does satellizer pushing any patch for this.
Need some explanation, whether it is affecting satellizer users or not.
Ref: https://developers.google.com/+/api-shutdown
@sahat