Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Google+ API Shutdown #1134

Open
rajathms opened this issue Feb 1, 2019 · 1 comment
Open

Google+ API Shutdown #1134

rajathms opened this issue Feb 1, 2019 · 1 comment

Comments

@rajathms
Copy link

rajathms commented Feb 1, 2019

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

@lokeshmeher
Copy link

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:

satellizer/src/config.ts

Lines 37 to 38 in ae28633

scope: ['profile', 'email'],
scopePrefix: 'openid',

which are already the recommend scopes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants