Download the PHP package afbora/oauth2-linkedin-openid without Composer
On this page you can find all versions of the php package afbora/oauth2-linkedin-openid. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download afbora/oauth2-linkedin-openid
More information about afbora/oauth2-linkedin-openid
Files in afbora/oauth2-linkedin-openid
Package oauth2-linkedin-openid
Short Description LinkedIn OAuth 2.0 Client Provider for The PHP League OAuth2-Client using OpenID Connect
License MIT
Informations about the package oauth2-linkedin-openid
LinkedIn Provider for OAuth 2.0 Client
This package provides LinkedIn OAuth 2.0 support for the PHP League's OAuth 2.0 Client.
Before You Begin
The LinkedIn API has been largely closed off and is only available to approved LinkedIn developers. You can request authorization here - https://business.linkedin.com/marketing-solutions/marketing-partners/become-a-partner/marketing-developer-program
You may be able to successfully obtain Access Tokens using this package and still not be authorized to access some resources available in the API.
If you encounter the following, or something similar, this policy is being enforced.
Installation
To install, use composer:
Usage
Usage is the same as The League's OAuth client, using \League\OAuth2\Client\Provider\LinkedIn
as the provider.
Authorization Code Flow
Managing Scopes
When creating your LinkedIn authorization URL, you can specify the state and scopes your application may authorize.
If neither are defined, the provider will utilize internal defaults.
At the time of authoring this documentation, the following scopes are available.
- r_liteprofile (requested by default)
- r_emailaddress (requested by default)
- r_fullprofile
- w_member_social
- rw_company_admin
Retrieving LinkedIn member information
When fetching resource owner details, the provider allows for an explicit list of fields to be returned, so long as they are allowed by the scopes used to retrieve the access token.
A default set of fields is provided. Overriding these defaults and defining a new set of fields is easy using the withFields
method, which is a fluent method that returns the updated provider.
You can find a complete list of fields on LinkedIn's Developer Documentation:
The getResourceOwner
will return an instance of League\OAuth2\Client\Provider\LinkedInResourceOwner
which has some helpful getter methods to access basic member details.
For more customization and control, the LinkedInResourceOwner
object also offers a getAttribute
method which accepts a string to access specific attributes that may not have a getter method explicitly defined.
A note about obtaining the resource owner's email address
The email has to be fetched by the provider in a separate request, it is not one of the profile fields.
When getting the resource owner a second request to fetch the email address will always be attempted. This request will fail silently (and getEmail()
will return null
) if the access token provided was not issued with the r_emailaddress
scope.
You can also attempt to fetch the email in a separate request. This request will fail and throw an exception if the access token provided was not issued with the r_emailaddress
scope.
Refresh Tokens
LinkedIn has introduced Refresh Tokens with OAuth 2.0. This feature is currently available for a limited set of partners. It will be made GA in the near future. Source
If your LinkedIn Client ID is associated with a partner that supports refresh tokens, this package will help you access and work with Refresh Tokens.
Testing
Credits
License
The MIT License (MIT). Please see License File for more information.