-
Pavel Borzenkov authored
connector/linkedin implements authorization strategy via LinkedIn's OAuth2 endpoint + profile API. It doesn't implement RefreshConnector as LinkedIn doesn't provide any refresh token at all (https://developer.linkedin.com/docs/oauth2, Step 5 — Refresh your Access Tokens) and recommends ordinary AuthCode exchange flow when token refresh is required. Signed-off-by:
Pavel Borzenkov <pavel.borzenkov@gmail.com>
ab061194
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| bitbucket-icon.svg | ||
| coreos-icon.svg | ||
| email-icon.svg | ||
| github-icon.svg | ||
| gitlab-icon.svg | ||
| google-icon.svg | ||
| ldap-icon.svg | ||
| linkedin-icon.svg | ||
| saml-icon.svg |
