Support for LinkedIn with OAuth2 authentication #402
Closed
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.
Added support for LinkedIn and its OAuth2 implementation.
LinkedIn has its own subtle interpretation of the OAuth2 standard, and requires a few tricks to work.
It uses POST methods and requires all parameters to be sent as body parameters, and ignores query parameters.
It requires some Http headers like Accept to be defined, so to introduce those parameters I used RequestTuner and changed the signature of OAuthService to accept a variable list of RequestTuners. That new signature should change nothing to users of OAuthService interface, but it will break implementors of that interface or of its concrete classes. Hopefully, that means not many people.
Ludovic