- What is sebius77/cas-bundle used for?
- sebius77/cas-bundle is a Symfony bundle that adds Central Authentication Service (CAS) single sign-on to a Symfony application. It integrates CAS login and logout with Symfony Security so users can authenticate through a central CAS server. It is aimed at Symfony projects, not Laravel applications, and supports configurable CAS server URL, service endpoint, and protocol settings.
- Does sebius77/cas-bundle work with Laravel?
- No, it is not a Laravel package. sebius77/cas-bundle is a Symfony bundle that hooks into Symfony Security and does not provide a Laravel service provider or package discovery. Laravel developers should use a Laravel-specific CAS package or build a custom bridge instead of expecting drop-in installation.
- How do I install sebius77/cas-bundle with Composer?
- Install it with Composer using composer require sebius77/cas-bundle, then enable the bundle in your Symfony application. Configure the CAS server URL, service endpoint, and protocol settings to match your CAS environment. Use v2.0.7 or a later 2.0.x patch as the baseline and clear Symfony caches after installation.
- Which PHP and Symfony versions are supported by sebius77/cas-bundle?
- The provided context does not list an exact PHP and Symfony version matrix, so check the package's composer.json constraints before upgrading. v2.0.7 is a 2.0.x patch release, so semver suggests it should be non-breaking within that line. Validate against your PHP and Symfony versions and run composer validate in CI.
- How do I configure the CAS server URL and service settings?
- Configure the bundle with your CAS server URL, service endpoint, and protocol options, then align those values with your CAS server administrator. Exact configuration keys should be taken from the package documentation, which may be primarily French. Test login, logout, and redirect behavior in staging before production rollout.
- What changed in sebius77/cas-bundle v2.0.7 and should I upgrade?
- The v2.0.7 release note is 'Correction erreur de syntaxe,' which indicates a syntax error fix. If your application pinned an affected 2.0.x release, make ^2.0.7 the minimum accepted patch and refresh the Composer lockfile. No application-code migration is expected, but verify autoloading and Symfony boot after upgrading.
- How should I test CAS login and logout in a Symfony app using this bundle?
- Test CAS login and logout against a staging or dedicated CAS test server, including SSO redirects and session handling. Run PHP lint and your full test suite, clear Symfony cache and opcache, and smoke-test application bootstrap. Because the v2.0.7 fix is syntactic, focus on proving that the framework boots and authentication flows work.
- What production deployment concerns apply to sebius77/cas-bundle v2.0.7?
- For production, upgrade in a branch, run composer validate, lint, and the full test suite, then deploy to staging first. Clear Composer, Symfony, and opcache caches so stale files do not preserve a parse error. Keep a rollback to the last known-good release if bootstrap or CAS login fails.
- What are alternatives to sebius77/cas-bundle for CAS SSO in PHP?
- Alternatives include other Symfony CAS bundles, the phpCAS library, or Laravel-specific CAS packages if you are working in Laravel. Evaluate protocol support, maintenance activity, documentation language, and compatibility with your framework version. For a Laravel app, a Laravel-native package is usually a better fit than a Symfony bundle.
- How is sebius77/cas-bundle maintained and what support should I expect?
- Maintenance impact for v2.0.7 is expected to be low because it is a patch-style syntax fix, but the terse French release note limits auditability. Ask for an English changelog, affected-version details, and an issue reference for internal records. Monitor the repository and require CI bootstrap and lint checks before adopting future patches.