Weave Code
Oauth Bundle Laravel Package
sumocoders/oauth-bundle
A Symfony bundle from SumoCoders that adds OAuth authentication support, helping you integrate OAuth providers and secure your application with minimal configuration.
sumocoders/oauth-bundle is a Symfony bundle that simplifies OAuth integration by connecting OAuth providers to your application’s security and request flow. It reduces boilerplate around authentication, callbacks, token handling, and protected routes.
- Configurable OAuth client/provider setup through bundle configuration
- Integration with Symfony Security for firewalls and access control
- Helpers for authorization callbacks, token exchange, and user data retrieval
- Extensible services for custom providers and OAuth flows
Frequently asked questions about Oauth Bundle
- Can I use sumocoders/oauth-bundle in a Laravel application?
- No, not as a drop-in dependency. Despite being listed among Laravel/PHP packages, sumocoders/oauth-bundle is a Symfony bundle that integrates through Symfony's kernel, service container, and security firewall rather than Laravel's service providers, guards, and config files. In a Laravel app you would be porting the OAuth wiring to Laravel Socialite or league/oauth2-client directly, using this package as a reference implementation rather than a Composer dependency.
- How do I install and register sumocoders/oauth-bundle?
- Installation follows the normal Symfony pattern: require the package with Composer, register the bundle in your kernel or bundles.php, and configure your OAuth providers through the bundle's configuration. There is no Laravel service provider or publishable config, so the standard Laravel installation steps do not apply. Check the repository README for the exact bundle class name and configuration keys before wiring it into a project.
- Which Symfony and PHP versions does sumocoders/oauth-bundle support?
- The supported constraints are not stated in the package overview, so you must read composer.json directly before evaluating it. Confirm the PHP requirement against your runtime and the Symfony major version against your LTS track. Symfony's security firewall factory API is the piece most sensitive to major-version churn, so verify that specifically if you depend on it for authentication.
- Does sumocoders/oauth-bundle use league/oauth2-client under the hood?
- That is very likely, since most Symfony and Laravel OAuth solutions wrap league/oauth2-client for the authorization code flow, token exchange, and refresh handling. Confirm the exact version constraint in composer.json, because the transitive league/oauth2-client version determines your inherited CVE exposure and whether it conflicts with anything else already in your project. This is the most likely compatibility blocker in a larger codebase.
- Does sumocoders/oauth-bundle support PKCE and OpenID Connect?
- This is not confirmed by the available information, and the bundle may only implement plain authorization-code flow with a client secret. If you need PKCE for public clients or OpenID Connect for identity claims, verify support in the source before committing. If those features are missing, league/oauth2-client or a maintained bundle is the better starting point.
- Is sumocoders/oauth-bundle maintained and safe for production?
- Treat it as high risk. It has zero stars and zero dependents, meaning no external consumers have validated it and there are no public bug reports, and no SECURITY.md or disclosure path is apparent for a package that handles client secrets and access tokens. The listed last-release date is future-dated, which looks like a data-quality artifact, so verify the real release history on Packagist directly. Do not depend on an unmaintained, zero-adoption package for authentication.
- What is a better alternative to sumocoders/oauth-bundle for Symfony?
- Use knpuniversity/oauth2-client-bundle. It is the de facto community standard for OAuth in Symfony, is actively maintained, and has far greater adoption than this bundle. Unless you have a specific reason to prefer SumoCoders' implementation, the standard wins on every risk axis, including security response and upgrade support.
- What is the Laravel equivalent of sumocoders/oauth-bundle?
- Laravel Socialite is the first-party equivalent: it is maintained by the Laravel team, ships with a broad provider ecosystem, and integrates natively with Laravel's auth guards. If you need a provider Socialite does not cover, use league/oauth2-client directly behind a small custom service. Either path is a better fit than porting a Symfony bundle.
- Which OAuth providers does sumocoders/oauth-bundle implement?
- The overview mentions provider configuration and integration helpers but does not enumerate supported providers, so check the source for the actual provider classes. Compare that list against the providers your application needs, including any regional or enterprise identity providers. If your provider is not implemented, you would be writing it yourself regardless of which package you choose.
- Should I fork sumocoders/oauth-bundle to use it in Laravel?
- Forking is possible but should be a deliberate decision. Vendor the code into an internal namespace, pin the commit, and own the maintenance, because you cannot rely on upstream releases for an unmaintained zero-adoption package. For Laravel, the effort is effectively a rewrite of the integration layer: keep the provider configuration and flow logic, and reimplement the glue against Socialite or league/oauth2-client.
Weaver
How can I help you explore Laravel packages today?