Add support for tokens from the Mobile SDK#39
Open
ushu wants to merge 1 commit intoemorikawa:masterfrom
ushu:is_mobile_sdk
Open
Add support for tokens from the Mobile SDK#39ushu wants to merge 1 commit intoemorikawa:masterfrom ushu:is_mobile_sdk
ushu wants to merge 1 commit intoemorikawa:masterfrom
ushu:is_mobile_sdk
Conversation
ushu
changed the title
is_mobile_sdk options
Adds `is_mobile_sdk` option that changes how the token is handled to the sdk, to allow authentication using the tokens retreived with the mobile SDK.
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
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.
Hello,
this PR adds a new option called
is_mobile_sdkto the contructor ofLinkedIn::API.When turned on, this allows to contact LinkedIn with the tokens obtained through the Mobile SDK.
Basically, the usual approach to provide credentials (
oauth2_access_token) does not work with these tokens, and you have to provide an "Authorization" header (+ a set of additional headers) to authenticate with the service.We have this code running in Production with no issue.