Weave Code
Oauth2 Server Client Manager Supervisor Bundle Laravel Package
spomky-labs/oauth2-server-client-manager-supervisor-bundle
A Symfony bundle that provides a client manager supervisor for OAuth2 servers, helping you register, organize, and oversee OAuth2 clients within your Symfony application.
Symfony2 OAuth2 Server Client Manager Supervisor Bundle
Frequently asked questions about Oauth2 Server Client Manager Supervisor Bundle
- Is this package compatible with Laravel?
- No. spomky-labs/oauth2-server-client-manager-supervisor-bundle is a Symfony 2 bundle built on Bundle classes, DI extensions, compiler passes, and XML service definitions, none of which exist in Laravel. There is no Laravel service provider and no compatible integration seam, so it cannot be installed and used in a Laravel application as shipped.
- What does this package actually do?
- It provides a supervisor client manager that aggregates several underlying OAuth2 client managers and resolves a client by consulting them in order, a chain-of-responsibility lookup. The reusable domain logic is roughly 100 lines; everything else is Symfony 2 bundle wiring. Its whole value proposition is the composite-resolver pattern, not the shipped code.
- Can I install it with Composer in a modern Laravel app?
- Realistically no. The spomky-labs OAuth2 stack from this era is pinned to PHP versions well behind current runtimes, so Composer resolution is expected to fail on PHP 8.x. Even if it resolved, you would need a shim provider that manually constructs Symfony services, which is high effort with no payoff.
- How do I implement multiple OAuth2 client sources in Laravel instead?
- Bind a CompositeClientRepository, or a decorator around Laravel Passport's ClientRepository, that holds an ordered list of sub-repositories each implementing League\OAuth2\Server\Repositories\ClientRepositoryInterface. Resolve getClientEntity by iterating in configured precedence order and returning the first non-null hit, or null if none match. Drive the ordering from config/oauth2.php so precedence is environment-controllable without code changes, and keep the composite behind an interface so a Passport upgrade stays a single-file change.
- Does it work with Laravel Passport or league/oauth2-server?
- No. The package targets a Symfony 2 OAuth2 server implementation of a different vintage and does not implement or target Passport's repository contracts. Verify the League ClientRepositoryInterface version you are on (getClientEntity, validateClient, and on newer majors isClientConfidential) and implement the composite against that interface directly.
- Is it safe to use on the authentication-critical path in production?
- Not recommended. Client identification drives redirect-URI validation and grant eligibility, so an unmaintained dependency there is a standing audit finding. The package has zero dependents, zero stars, no security patching, no CVE response, and its underlying spomky-labs OAuth2 dependency chain is itself superseded.
- Which Symfony version does this bundle target?
- Symfony 2. That means the Symfony bundle, kernel, and compiler-pass model, which Laravel does not have. The only transferable asset is the composite-resolver design, which you would re-implement natively in Laravel.
- How should client lookup precedence and duplicate client_id conflicts be resolved?
- Write the precedence rules down before coding, then enforce them with a deterministic ordered list of sub-repositories. On a duplicate client_id across sources, the first source in configuration order wins and returns immediately; a full miss must return null rather than throw. Cover determinism with a test asserting the same winner regardless of iteration side effects.
- What are the alternatives for managing multiple OAuth2 client sources in Laravel?
- Use Laravel Passport for OAuth2 client resolution and Sanctum for first-party token issuance. For static or first-party clients, prefer a config-backed repository over seeding the database, but have it implement the same ClientRepositoryInterface so the composite can mix DB-backed dynamic clients, environment-defined M2M clients, and tenant-partitioned stores. No new production dependency is required.
- How do I test a composite client repository?
- Cover a hit in the first source, a hit in the second, and a miss in all sources expecting null rather than an exception. Add a duplicate client_id case asserting the deterministic winner, plus a redirect-URI mismatch rejection to prove validation still fails closed. Before removing any legacy Symfony 2 OAuth2 surface, confirm the multi-source requirement is real and not a single-table need Passport already covers.
Weaver
How can I help you explore Laravel packages today?