Weave Code
Laravel Passport Social Grant Laravel Package
coderello/laravel-passport-social-grant
Laravel Passport Social Grant lets API clients exchange social network access tokens (such as Facebook, Google, or Apple) for Laravel Passport OAuth tokens, enabling passwordless social login for mobile and SPA apps.
🔒 API authentication via social networks for your Laravel application
Frequently asked questions about Laravel Passport Social Grant
- What is coderello/laravel-passport-social-grant used for?
- It lets API clients exchange social network access tokens, such as Facebook, Google, or Apple tokens, for Laravel Passport OAuth tokens. This enables passwordless social login for mobile and SPA applications without building a custom Passport grant. It fits Laravel apps that already use Passport for OAuth token issuance and want provider-based user resolution.
- How do I install coderello/laravel-passport-social-grant in a Laravel app?
- Install it with Composer using composer require coderello/laravel-passport-social-grant. Then configure Laravel Passport and register the social grant or provider credential flow according to the package repository instructions. Before upgrading, check the package composer.json and release notes for Laravel, Passport, and PHP constraints.
- Is version 5.0.0 a breaking change for resolveUserByProviderCredentials?
- Likely yes. Version 5.0.0 adds a $client argument to resolveUserByProviderCredentials, which can break any application or package that overrides or implements that method. Search your codebase for the method and related overrides, update the signatures, and retest token issuance. Teams without a custom override may have a lower-effort upgrade.
- How do I migrate from 4.x to 5.x of laravel-passport-social-grant?
- Treat 5.0.0 as a planned major upgrade rather than a patch. Inventory custom grant and resolver code, update resolveUserByProviderCredentials signatures to accept $client, align any custom contracts, and run the full authentication and token-issuance test suite. Keep 4.x pinned until the migration is verified, and review the linked PR and package source for the intended client behavior.
- Which Laravel, Passport, PHP, and social provider versions are supported?
- The release notes do not publish a full compatibility matrix or migration guide. Check the package composer.json and repository documentation for Laravel, Passport, PHP, and social-provider package constraints. Validate those constraints against your exact framework version and provider integrations before upgrading.
- Does the $client argument change token client binding or runtime behavior?
- The $client argument adds OAuth client context to user resolution, which can affect which client is associated with token issuance in multi-client setups. Incorrect handling of $client could change validation or client-binding behavior, so review the package source and linked PR. Test token issuance, refresh flows, and client binding explicitly after upgrading.
- Can I use this package with multiple Passport clients or multi-tenant applications?
- It can fit multi-client Passport applications, but version 5.0.0 requires explicit verification that $client is resolved and propagated correctly. Add tests confirming the resolver returns the right user and that tokens are bound to the expected OAuth client. Incorrect client handling is the main risk in multi-client or multi-tenant scenarios.
- How should I test social grant authentication before production?
- Create a branch and run the full authentication and token-issuance test suite, including custom resolver overrides if you have them. Test against real or sandbox social providers, refresh flows, and multi-client token binding scenarios. Stage the upgrade and roll out to production only after confirming token issuance and client behavior.
- Is laravel-passport-social-grant actively maintained and supported?
- It is a community dependency with no vendor SLA implied. Support depends on the package maintainers, GitHub issues, and your internal Laravel and Passport expertise. Because 5.0.0 is a major release with a short changelog, your team should own upgrade validation and retain the ability to fork or replace the grant if maintenance slows.
- What alternatives should I consider instead of laravel-passport-social-grant?
- This package is best for Laravel services already using Passport and needing social grant support. It is less attractive for teams standardizing on Sanctum, external identity providers, or custom OAuth implementations unless they explicitly need Passport grant integration. If you are not on Passport, evaluate Sanctum or a provider SDK and custom flow instead.
Weaver
How can I help you explore Laravel packages today?