An OmniAuth strategy for LinkedIn OAuth2 authentication in Ruby applications.
omniauth-linkedin-oauth2 is a Ruby gem that provides a LinkedIn OAuth2 strategy for the OmniAuth authentication framework. It enables Ruby applications, particularly Rails apps, to authenticate users via their LinkedIn accounts by handling the OAuth2 flow and returning standardized user profile data. It simplifies integration with LinkedIn's API, though note that LinkedIn has deprecated this OAuth2 method in favor of OpenID Connect.
Ruby developers, especially those using Rails, who need to add LinkedIn-based authentication to their applications using the OmniAuth framework. It is suited for projects currently relying on LinkedIn's OAuth2 API before its deprecation.
Developers choose this gem for a straightforward, standardized way to integrate LinkedIn OAuth2 into OmniAuth-based authentication systems, with features like configurable permission scoping and profile fields. It offers a clean upgrade path from older OAuth1 LinkedIn strategies and is specifically updated for LinkedIn API v2 compatibility.
A LinkedIn OAuth2 strategy for OmniAuth.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Integrates directly into OmniAuth's middleware, allowing straightforward addition of LinkedIn authentication to Rails apps with minimal configuration, as shown in the example initializer.
Updated to support LinkedIn's API v2, ensuring compatibility with current LinkedIn standards and the required r_liteprofile permission.
Enables customization of OAuth scopes and profile fields via configuration options, giving developers control over data access and user consent.
Provides a clean upgrade path from older OAuth1 strategies by simplifying provider names and adapting to API changes, easing transitions for existing apps.
LinkedIn has deprecated OAuth2 for Sign In with LinkedIn, making this gem less future-proof and recommending OpenID Connect for new projects.
The shift to r_liteprofile significantly reduces available user data, which may not suffice for applications requiring detailed profile information.
Upgrading from previous versions requires changes to provider names and scopes, potentially disrupting existing configurations without careful updates.