- Is stgbundle/cas-bundle a Laravel package?
- No. It is a Symfony bundle that integrates CAS single sign-on with Symfony Security, and its 8.0 release targets Symfony 7.4. It depends on Symfony's kernel, DI container compiler passes, bundle extensions, and security authenticator abstractions, so it is not a drop-in Laravel dependency.
- Can I install stgbundle/cas-bundle in a Laravel app with Composer?
- Composer may resolve the package, but it will not function as a Laravel package. There is no Laravel service provider, auth guard, or middleware, and the bundle expects Symfony's container and firewall. Installing it would add dead weight unless you extract the CAS protocol logic.
- How do I integrate CAS single sign-on into Laravel?
- You need a Laravel-native CAS client that validates service tickets against the CAS /serviceValidate endpoint, parses the response, and wraps the flow in a custom auth guard and login/logout middleware. Use this bundle as a reference for the CAS protocol flow, but replace Symfony HTTP client usage with Guzzle and register the logic through a Laravel service provider. Scope the work as building a CAS client for Laravel rather than adopting the bundle.
- Does stgbundle/cas-bundle support Laravel 10, 11, or 12?
- No. The package tracks Symfony releases, not Laravel, and release 8.0 is described as a CAS bundle for Symfony 7.4. There are no Laravel version constraints or framework integrations. For Laravel projects, treat it as a protocol reference rather than a supported dependency.
- What PHP version does stgbundle/cas-bundle require?
- The Symfony 7.4 target likely imposes PHP 8.2 or newer, and the code may use newer PHP syntax. The technical assessment recommends checking composer.json and the source for PHP 8.3 or 8.4-only features before planning any extraction. Laravel teams should also verify compatibility with their own PHP floor.
- Is stgbundle/cas-bundle safe to use in production?
- The assessment flags high risk: three stars, zero dependents, a single maintainer, no changelog, and no migration guide for 8.0. A security-adjacent package with no downstream users has little external review or vulnerability discovery surface. If you extract code, pin a tag, review the diff from 7.x, and add your own tests.
- What changed in stgbundle/cas-bundle 8.0?
- The release note says it is a CAS bundle for Symfony 7.4, suggesting a port to that Symfony release train. There is no changelog or breaking-change list, so you must read the diff against 7.x, especially around ticket validation and XML parsing. Pin a tag rather than tracking main.
- Does stgbundle/cas-bundle implement a CAS client or a CAS server?
- The description points to a client that authenticates users against an external CAS server through login and logout flows. The assessment says the durable value is the client-side protocol logic: service ticket validation, proxy ticket handling, and attribute extraction. Confirm by reading the code, because server-side CAS support would roughly triple porting cost.
- What CAS protocol features does stgbundle/cas-bundle support?
- The overview mentions gateway mode, ticket validation, configurable server settings, and protocol options, but it does not specify CAS 1.0, 2.0, or 3.0 support, proxy granting tickets, or SAML 1.1 attribute release. The assessment lists these as open questions. Verify each feature against the source before relying on it for a Laravel integration.
- What are the alternatives to stgbundle/cas-bundle for Laravel CAS SSO?
- You can wrap apereo/phpCAS in a Laravel guard and middleware, or build a small CAS client with Guzzle and Laravel's authentication contracts. The bundle itself is only useful as a reference implementation, and you should confirm its license before copying code. Prefer maintained packages with explicit Laravel support when they exist, and otherwise keep the extraction small and well tested.