- Is korotovsky/sso-idp-bundle compatible with Laravel?
- No. korotovsky/sso-idp-bundle is a Symfony 2 bundle that relies on Symfony's DependencyInjection extension, compiler passes, and XML/YAML service definitions, none of which Laravel's container can load. It has no Laravel service provider, facade, config file, or extra.laravel composer metadata, so a Laravel app will fail during autoload or bootstrap rather than at runtime logic.
- Can I use korotovsky/sso-idp-bundle to turn my Laravel app into an SSO identity provider?
- Not directly. The bundle implements the identity provider role for Symfony applications using league/oauth2-server, but it is not packaged for Laravel and its Symfony security integration cannot be reused by Laravel guards. Standing up an IdP from a Laravel monolith is a major architectural decision, and this abandoned Symfony 2 codebase is a poor foundation for authentication.
- How do I install korotovsky/sso-idp-bundle in a Laravel project?
- You should not attempt a normal Composer install for Laravel. The package has no Laravel service provider or auto-discovery, and its Symfony bundle classes will not register with Illuminate\Container. Installing it would only add dead dependencies unless you plan a full fork and rewrite for Laravel and PHP 8.2+.
- What Laravel and PHP versions does korotovsky/sso-idp-bundle support?
- It targets Symfony 2.x and PHP 5.x, both of which are end-of-life and not supported on modern Laravel 10 or 11 stacks. There is no declared Laravel version support and no compatibility layer for PHP 8.2+. Running this code on a current Laravel runtime would require significant porting before any feature could work.
- Does korotovsky/sso-idp-bundle provide OAuth2 and OIDC endpoints?
- Yes, the bundle is designed to expose Authorization Code and Client Credentials grants with refresh tokens, plus OIDC discovery, JWKS, and userinfo endpoints on top of league/oauth2-server. That feature set is relevant to identity provider work, but the implementation is Symfony-specific and not usable as-is in Laravel. You would need to rebuild the endpoint wiring and security integration for Laravel.
- What grants and token features does korotovsky/sso-idp-bundle support?
- It supports the Authorization Code grant and Client Credentials grant with refresh tokens, and it includes configurable signing keys and token lifetimes. It also provides a pluggable ClaimSet and user resolver to control token and userinfo payloads. These are useful IdP concepts, but they are delivered through Symfony services and Doctrine entities, not Laravel components.
- Is korotovsky/sso-idp-bundle maintained and safe for production authentication?
- No. The repository shows zero stars, empty star metadata, zero dependents, and no visible maintainer activity, which is a strong signal of an abandoned or archived project. Because an identity provider mints bearer credentials, unaudited token formats, weak signing algorithms, missing replay protection, or non-constant-time comparisons could become account-takeover primitives. There is also no visible security review, CVE history, or test suite to justify using it in an auth path.
- What are good alternatives to korotovsky/sso-idp-bundle for Laravel SSO?
- If your Laravel app needs to be an OAuth2/OIDC identity provider, evaluate maintained options such as Laravel Passport with an OIDC layer, Ory Hydra, Keycloak, or a commercial identity platform. If your Laravel app is actually a service provider that needs to log users in through an existing IdP, use Socialite or socialiteproviders for OAuth/OIDC and a maintained SAML package for SAML. Match the tool to whether you need to be the IdP or the SP before choosing a package.
- Why doesn't Symfony security integration work in Laravel?
- The bundle plugs into Symfony's security layer so existing users and firewalls become the identity source for the SSO ecosystem. Laravel uses guards, middleware, and its own authentication manager instead, and it cannot load Symfony bundle DI extensions or compiler passes. Porting would mean replacing Symfony request/response and security context with Illuminate\Http and Laravel guards, which is a rewrite rather than an integration.
- Should I fork korotovsky/sso-idp-bundle to port it to Laravel?
- Only if you treat the repository as a requirements specification rather than a codebase to reuse. A Laravel port would require rewriting DI wiring, replacing Symfony HTTP and security components, migrating sessions and guards, and revalidating every cryptographic primitive on PHP 8.2+. With no maintainer activity and zero dependents, your team would own that fork forever, so compare the cost against maintained IdP products or a scoped build first.