Update config.properties with current scopes #13
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Author
|
@racchavan @swathivshenoy @Deeksha-ramesh @Nandhu2303 Could one of you please review this PR? It addresses a common issue people seem to be running into with deprecated OAuth 2.0 scopes in LinkedIn's API. Some examples of the issue being discussed: Stack Overflowexample, OAuth forum example |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
This pull request updates the
config.propertiesfile to replace deprecated OAuth 2.0 scopes with the current scopes supported by LinkedIn.Changes Made:
r_emailaddressr_liteprofilerw_adsrw_organization_adminemailprofilew_member_socialopenidThese scopes are associated with the standard products, "Sign In with LinkedIn using OpenID Connect" and "Share on LinkedIn."
These changes ensure the application is using the latest OAuth 2.0 scopes as recommended by LinkedIn.
Reason for Changes
The previously used scopes (
r_emailaddress,r_liteprofile,rw_ads,rw_organization_admin) are now deprecated and have been replaced with new scopes. Using deprecated scopes results in an authorization error, they can no longer be used.