Weave Code
Linkedin Bundle Laravel Package
happyr/linkedin-bundle
Symfony bundle for LinkedIn integration that provides OAuth authentication and API client wiring, making it easier to add LinkedIn login and profile/data access to PHP applications with configurable services and less boilerplate.
A symfony bundle for happyr/linkedin-api-client
Frequently asked questions about Linkedin Bundle
- Is happyr/linkedin-bundle a Laravel package?
- No. happyr/linkedin-bundle is a Symfony bundle that registers happyr/linkedin-api-client in a Symfony dependency injection container and exposes happyr_linkedin configuration. It contains no Laravel service provider, facade, publishable config, or Illuminate dependency, so installing it in a Laravel app leaves a dead dependency or a Composer conflict. For Laravel, use Laravel Socialite or bind the underlying client library yourself.
- How do I install and configure happyr/linkedin-bundle?
- In a Symfony application you install it with composer require happyr/linkedin-bundle, register the bundle in your kernel or bundles.php, and add happyr_linkedin configuration keys for the client ID, secret, redirect URI, and scopes. The bundle then provides a container-managed LinkedIn client service. This workflow does not apply to Laravel, and the package is effectively unmaintained.
- Does happyr/linkedin-bundle support Laravel 10 or Laravel 11?
- No. It has no Laravel service provider, facade, publishable configuration, or Illuminate dependency, and its Symfony constraints are from the Symfony 2.8 and 3.x era. Installing it in Laravel 10 or 11 will not wire anything useful and may fail dependency resolution. Use laravel/socialite for LinkedIn login or wrap happyr/linkedin-api-client in a custom Laravel provider if you need API calls.
- Which Symfony versions does happyr/linkedin-bundle support?
- The last release was in February 2018 and targets the Symfony 2.8 and 3.x era. It will not resolve against Symfony 5, 6, or 7, or modern PHP 8.x runtimes, without a fork. Treat it as a legacy Symfony-only package rather than something to add to a current application.
- Is happyr/linkedin-bundle still maintained?
- No. Its last release was 2018-02-04, it has roughly 8 stars and zero dependents, and it comes from a single-vendor origin. That makes it effectively abandoned and high risk for production use. If you need the underlying client, plan to fork and maintain happyr/linkedin-api-client yourself.
- What is the difference between happyr/linkedin-bundle and happyr/linkedin-api-client?
- The bundle is only Symfony dependency injection wiring for happyr/linkedin-api-client. The client library is the framework-agnostic PHP package that handles OAuth code exchange, access-token persistence helpers, and typed calls to LinkedIn endpoints. For Laravel or any non-Symfony project, the client library is the reusable asset and the bundle adds nothing.
- Can I use happyr/linkedin-api-client in Laravel?
- Yes, but bind it yourself. Require happyr/linkedin-api-client, create a config file for client ID, secret, redirect URI, and scopes from environment secrets, register a singleton in a service provider, and wrap it behind a gateway interface so the vendor client is swappable. Before writing features, audit endpoint and scope constants against current LinkedIn REST and OpenID Connect documentation.
- Does happyr/linkedin-bundle still work with LinkedIn's current API?
- Probably not without changes. A 2018-era client likely targets retired v1 endpoints and deprecated scopes such as r_basicprofile and r_liteprofile, while LinkedIn now uses versioned REST headers and OpenID Connect for sign-in. You should budget time to rewrite endpoint and scope constants and confirm which products and scopes your LinkedIn app has approved.
- What should I use for LinkedIn login in Laravel instead?
- Use Laravel Socialite's LinkedIn driver for login and basic profile access because it is OIDC-based and avoids adding an abandoned Symfony dependency. If you need publishing, Ads, or messaging APIs beyond identity, wrap happyr/linkedin-api-client in a custom Laravel provider and expose a thin interface. Either path is safer than adopting the Symfony bundle as-is.
- How should I test and harden a Laravel LinkedIn integration if I adopt the client library?
- Test with a mocked HTTP client and a fake token store, and never hit LinkedIn's real OAuth flow in automated tests. For production, keep secrets outside source control, encrypt tokens at rest, validate OAuth state for CSRF, and confirm Marketing Developer Platform approval for the scopes you need. Also assign an owner for the client fork because the bundle itself is unmaintained.
Weaver
How can I help you explore Laravel packages today?