- What is subfission/cas used for in Laravel?
- subfission/cas adds Central Authentication Service single sign-on to Laravel applications by wrapping the phpCAS client in a Laravel service provider and facade. It is intended for apps that must delegate login to an institutional CAS server, including login and logout redirects, ticket validation, and authenticated session setup. It does not provide application user records or authorization by itself.
- How do I install and configure subfission/cas in a Laravel app?
- Install the package with Composer, then publish and edit its configuration for the CAS host, port, context, and certificate options. Register the service provider and facade as described in the README, or rely on Laravel package discovery where supported. Protect the routes that require SSO with the package middleware and verify the CAS callback flow in a non-production environment first.
- Does subfission/cas work with Laravel authentication guards and user providers?
- No. The package authenticates a session against CAS and exposes CAS attributes, but it is not a Laravel authentication guard or user provider. It does not handle Auth::attempt, password resets, remember-me tokens, or guard composition. You must build the mapping from CAS attributes to your users table, first-login provisioning, roles, and authorization policies.
- Which Laravel and PHP versions does subfission/cas support?
- The exact Laravel and PHP version window depends on the release, so check the package composer.json and README before adopting it. The evaluation notes that illuminate/* constraints can eventually pin the host application to an aging Laravel release unless new releases continue. Verify that your target stack is inside the supported window today.
- How does CAS login, logout, and ticket validation work in this package?
- The package wraps phpCAS, so login helpers redirect the user to the CAS server and logout helpers integrate with the CAS logout flow. On return, the package handles ticket validation and sets up the authenticated Laravel session. Configuration controls the CAS host, port, context, and certificate settings used for those operations.
- Is subfission/cas maintained and safe for production use?
- Treat maintenance as a production risk: the package was assessed as archived, has a single-maintainer bus factor, and the v5.1.0 release is a narrow proxy-signature fix rather than proof of a renewed support commitment. Re-verify the archived status with security, review the phpCAS advisory history, and put the dependency through normal review. The MIT license permits forking, but you should record accepted risk and a contingency plan.
- What changed in subfission/cas v5.1.0?
- v5.1.0 widened the PhpCasProxy::client() and PhpCasProxy::proxy() signatures to match the corresponding phpCAS package because the previous types were overly restricted. This affects CAS proxy-mode applications that request proxy or service tickets and is inert for plain SSO plus logout. The upstream phpCAS lockfile change matters more than the wrapper change, so review it with the dependency bump. Widened types can also move previously fast TypeErrors into phpCAS redirect or exit behavior, and any subclass overriding those methods must be rebased.
- Can I use subfission/cas for CAS proxy mode and service tickets?
- Yes, proxy mode is the surface touched by v5.1.0 through PhpCasProxy::client() and PhpCasProxy::proxy(). It is relevant only when your Laravel app requests CAS proxy or service tickets to call downstream services. Plain SSO plus logout does not use this surface, so the release is effectively inert for those teams.
- How should I test CAS authentication in Laravel with subfission/cas?
- The provided context does not describe built-in testing helpers for this package. You can mock the Cas facade or phpCAS boundary in unit tests, and use a controlled CAS test server for end-to-end login and ticket-validation checks. Because phpCAS relies on static state, session handling, redirects, and exits, keep CAS integration tests isolated and assert the Laravel session and user-mapping behavior separately.
- What are alternatives to subfission/cas for Laravel CAS SSO?
- The context does not name specific alternatives, but the realistic options are integrating phpCAS directly or choosing another maintained Laravel CAS or SSO wrapper. Compare maintenance activity, Laravel version constraints, phpCAS advisory handling, and whether you need proxy-mode support. If your needs are plain SSO plus logout, this package is a thin wrapper and the surrounding user-provisioning work will dominate either choice.