- Can I use prayno/casauth-bundle in a Laravel application?
- No, not as-is. This is a Symfony bundle that ships a Bundle subclass, DI extension, and security-firewall factory to wire a CasListener into Symfony's security.firewalls config. Laravel has no equivalent extension points, so adopting it would be a rewrite as a guard or middleware. Use apereo/phpcas directly in Laravel instead.
- What does prayno/casauth-bundle actually do?
- It is a thin Symfony security authenticator over apereo/phpcas that validates CAS tickets against an existing CAS identity provider. It provides a CasListener, a firewall factory, and configuration for CAS host, port, context path, server certificate, protocol version, and service base URL. The hard work lives in phpCAS, not in this bundle.
- Which Symfony and PHP versions does this CAS bundle support?
- The README states Symfony 3, 4, and 5 support, and the last release was 2019-12-17. There is no evidence of Symfony 6 or 7 support, nor of PHP 8.2+ compatibility. Treat it as unmaintained for modern Symfony or PHP stacks.
- How do I install and configure prayno/casauth-bundle in Symfony?
- In a Symfony 3, 4, or 5 app you would composer require prayno/casauth-bundle, enable the bundle, configure CAS host, port, context path, certificate, protocol version, and service URL, then attach the CAS listener to a security firewall. Because the release is old, pin a compatible phpCAS version and test against your IdP before relying on it. Do not expect this install path to work in Laravel.
- Is prayno/casauth-bundle maintained and safe for production authentication?
- Abandonment risk is high: the last release is from 2019, it has around 15 stars and zero dependents, and it appears to be a single-maintainer project. Authentication is security-critical, so an unmaintained auth dependency is a compliance and audit finding even when phpCAS is the real attack surface. The MIT license and small codebase make forking cheap, but the governance risk remains.
- What Laravel CAS authentication approach should I use instead?
- Depend on apereo/phpcas directly and implement native Laravel components: a CAS guard or request guard, a user provider that resolves users from CAS attributes, login and logout controllers, and a middleware group for protected routes. Use this bundle only as a reference checklist for edge cases such as ticket flow and logout behavior. For a PHP developer who knows Laravel auth, this is a few days of work rather than a few weeks.
- Does prayno/casauth-bundle support CAS single logout and attribute release?
- The bundle is described as basic, so assume single logout (SLO) and rich attribute mapping are out of scope. Attribute release for LDAP, JWT, or attribute-based authorization, and logout propagation to the CAS server, will need to be built or handled by phpCAS configuration. Confirm these requirements against your IdP before choosing the package.
- How can I test CAS authentication without hitting the production identity provider?
- Stand up a scratch application with apereo/phpcas against a test or development CAS IdP and validate ticket flow, attribute payload, and logout behavior end-to-end in CI. If no test IdP is available, a two-to-three day spike against the real IdP de-risks most unknowns regardless of package choice. Do not rely on unit tests alone for authentication flow verification.
- Which CAS protocol versions and server products does this bundle interoperate with?
- Protocol support depends on the phpCAS version you pin, since this bundle is a thin adapter over apereo/phpcas. You must confirm whether you need CAS 2.0 or 3.0, proxy or gateway behavior, and which server product you are integrating with, such as Apereo CAS, Shibboleth IdP, or a legacy campus CAS. The bundle exposes a protocol version setting, but you still need to verify interoperability against your IdP.
- What are the alternatives to prayno/casauth-bundle for Laravel or Symfony?
- For Symfony 5.4 or older, direct use is defensible only with a pinned phpCAS version and a documented fork plan; on Symfony 6 or 7 it is a non-starter. For Laravel, use apereo/phpcas with native auth components or a maintained Laravel-native CAS package. Do not introduce Symfony security components into a Laravel application to accommodate this bundle, because that is the expensive path for zero benefit.