- Can I use gregoryeple/oauth-server-bundle in a Laravel application?
- No. It is a Symfony bundle built on Symfony SecurityBundle, EventDispatcher, HttpKernel, and typically Doctrine ORM, not a Laravel package. It ships no Laravel service provider, facade, config publishing, migrations, or Eloquent bindings. Adopting it in Laravel would mean re-platforming or running a separate Symfony service, not a normal Composer integration.
- Is gregoryeple/oauth-server-bundle a Laravel OAuth2 server package?
- No. It is a server-side OAuth2 bundle for Symfony 6 and a fork of FOSOAuthServerBundle. For Laravel, use laravel/passport for a full OAuth2 authorization server or laravel/sanctum for first-party SPA and mobile tokens.
- How do I install gregoryeple/oauth-server-bundle?
- You would install it with Composer into a Symfony application and register it as a Symfony bundle. There is no supported Laravel installation path because the package lacks Laravel package discovery, configuration merging, and database migrations. Do not expect a Laravel service provider or publishable config.
- Does gregoryeple/oauth-server-bundle support Laravel 10 or Laravel 11?
- There is no verified Laravel 10 or Laravel 11 support. The package is architecturally tied to Symfony security and HTTP kernel primitives, and its compatibility with current Laravel PHP runtimes is unverified. Treat it as incompatible with Laravel until proven otherwise.
- What Laravel package should I use instead for OAuth2?
- Use laravel/passport when you need a full OAuth2 authorization server with standard grants and token issuance. Use laravel/sanctum when you only need API tokens for first-party SPAs or mobile apps. Both are native Laravel packages and avoid introducing Symfony security layers.
- Is gregoryeple/oauth-server-bundle maintained and safe for production?
- It is a personal fork of FOSOAuthServerBundle with zero stars, zero dependents, and a last release from June 2023. An OAuth authorization server is a high-value attack surface, so a single-maintainer unvetted fork is a poor security choice. Prefer league/oauth2-server-bundle in Symfony or laravel/passport in Laravel.
- What OAuth2 grant flows does this Symfony bundle support?
- As a fork of FOSOAuthServerBundle it typically targets authorization code, client credentials, refresh token, and password-style flows. Exact PKCE and modern OAuth 2.1 behavior would need verification against the fork. These details do not change the fact that it is not a Laravel integration.
- Can I run gregoryeple/oauth-server-bundle as a separate OAuth2 service for my Laravel app?
- You could stand up an isolated Symfony service running this bundle and call it over HTTP from Laravel. That is a new service boundary and a re-platforming exercise, not a Laravel package integration. A better Symfony choice would be league/oauth2-server-bundle, or use laravel/passport directly inside Laravel.
- How does gregoryeple/oauth-server-bundle compare to laravel/passport?
- They live in different ecosystems. laravel/passport wraps league/oauth2-server and integrates natively with Laravel guards, Eloquent, migrations, and configuration. gregoryeple/oauth-server-bundle is Symfony-only and provides no Laravel bindings, so it is not a like-for-like alternative for Laravel developers.
- Why would a Laravel developer evaluate this package?
- Most likely by mistaken search results for an OAuth2 server package. Laravel developers should route the requirement to laravel/passport or laravel/sanctum depending on whether they need a full OAuth2 server or simple API tokens. If a Symfony service is genuinely in scope, evaluate league/oauth2-server-bundle rather than this personal fork.