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

Non-default scopes #55

Open
Arepo opened this issue Jun 21, 2019 · 0 comments
Open

Non-default scopes #55

Arepo opened this issue Jun 21, 2019 · 0 comments

Comments

@Arepo
Copy link

Arepo commented Jun 21, 2019

Hi all,

I just got the email below from LinkedIn, and was wondering whether 'default' means something different in their context than it does in the context of your Readme. Ie, if we haven't configured the scope option in our Rails project, will the project still work come September?

LinkedIn email:

Dear LinkedIn Developers, 

What's happening?

As of September 15, 2019, we will no longer be supporting default scopes. Default scopes allow apps to make calls to /oauth/v2/authorization without explicitly requesting scopes in the scope parameter. If your apps rely on default scopes, they must now request scopes explicitly in their OAuth flow

Additionally, requests to v1 specific scopes will not be permitted after September 15, 2019. The set of v1 scopes includes:

  • r_basicprofile (only permitted if your app has been granted v2 Basic Profile)
  • w_share
  • rw_company_admin

What you'll need to do:

  1. Determine if your app is using default scopes by inspecting your code. If your call to request an authorization code includes a scope parameter explicitly requesting permissions, your app is not using default scopes and you do not need to take any action. Important: If your call does not include a scope parameter, proceed with the rest of the steps below.
  2. Initiate OAuth flow from your app as a user.
  3. Proceed to the LinkedIn authentication screen describing what access is being requested
  4. Map the access request descriptions to their corresponding scopes using the table in our migration guide.

Timeframe:

You will need to complete the migration steps above by September 15, in order to prevent any interruption of your access. Requests to obtain an access token while using default scopes after this date will return an HTTP 400 error from our API.

Resources:

For further assistance, please reference our migration guide.

If you need additional support while migrating your default scopes, or have general questions regarding these updates you can open a support ticket here.

Thank you,
LinkedIn Developers Program Team

--

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

1 participant