- Is korotovsky/sso-library a Laravel SSO package or a Symfony2 library?
- The package is described as a Laravel SSO package, but the linked korotovsky/SingleSignOnLibrary repository is described in its own metadata as a Symfony2 library. Treat that mismatch as a blocking compatibility question, not a documentation detail. Confirm which artifact you will install and whether a Laravel adapter or wrapper actually exists before planning work.
- How do I install korotovsky/sso-library in a Laravel application?
- No verified Laravel installation path is provided in the available context. The described package would use Composer and publishable config, but the underlying repository may not install on modern Laravel and PHP runtimes. Run a short Composer install spike on your target runtime and inspect the package requirements before committing to adoption.
- Which Laravel and PHP versions does korotovsky/sso-library support?
- The context does not list supported Laravel versions, and the repository is associated with Symfony2-era code. That likely means PHP 5.x through 7.x targets, with potential failures on PHP 8.2+ from dynamic properties, each(), and interface signature changes. Composer constraints may block installation before any runtime errors surface.
- What SSO protocol does korotovsky/sso-library implement?
- The protocol is never named in the provided assessment. SSO library could mean CAS, SAML 1.1 or 2.0, OAuth or OIDC, or a custom cookie-token broker. Read the source and produce a written protocol note before evaluating conformance, tooling, or identity provider interoperability.
- Does korotovsky/sso-library provision Laravel users and link existing accounts?
- The description claims automatic user provisioning and account linking with Eloquent model and event integration. Those are Laravel-native features, while the repository is described as Symfony2, so the Laravel provisioning layer is unverified. Inspect the actual code or locate a Laravel wrapper before assuming those features exist.
- How do I configure identity providers, SSO routes, and middleware in Laravel?
- The overview advertises publishable config for one or more identity providers, ready-made login and callback routes, and middleware for protecting routes. Those components would normally be registered through a Laravel service provider and applied to protected route groups. Because the repository mismatch is unresolved, verify the config keys, route names, and middleware namespace in the real artifact first.
- Is korotovsky/sso-library safe to use for production authentication?
- Authentication code parses assertions, validates signatures, handles redirects, and establishes sessions, so it has a high blast radius. This package shows zero stars, zero dependents, a composite score of 0, and no visible downstream users, while its Symfony2 and PHP 5.x-era platform is out of support. Unmaintained auth code means future CVEs become yours to find, triage, and patch without upstream guidance.
- How can I test SSO login and callback flows with korotovsky/sso-library?
- The context provides no testing utilities, fake identity provider, or documented callback test path. You would need to mock the identity provider response and assert user provisioning, account linking, and session establishment yourself. First confirm that the validation and assertion code can run outside Symfony Request, Session, and Container access.
- What are maintained alternatives to korotovsky/sso-library for Laravel SSO?
- Maintained alternatives depend on the protocol: Laravel Socialite or league/oauth2-client for OIDC and OAuth, OneLogin or SimpleSAMLphp toolkits for SAML, and apereo/phpcas for CAS. Choosing the abandoned path requires a positive justification beyond inertia. Compare protocol conformance, vendor support, and patch cadence before deciding.
- Is korotovsky/sso-library maintained and licensed for forking?
- The assessment reports zero stars, zero dependents, a composite score of 0, and no visible downstream users, which suggests no active maintenance. It also recommends confirming an explicit license before forking because dormant repositories sometimes lack one. Check the repository license and commit history before adopting, forking, or porting the code.