- Can I use smurfy/crowd-bundle in a Laravel application?
- No, not out of the box. smurfy/crowd-bundle is a Symfony bundle built around Symfony's security.firewall and authentication-provider system, service container, and Symfony DI configuration. Laravel uses a different Guard and AuthManager abstraction, so dropping this package into a Laravel app is effectively a rewrite rather than an integration. Treat it as reference material for Crowd API calls, not as a Composer dependency for Laravel.
- How do I install smurfy/crowd-bundle?
- You install it with Composer and then register the bundle in a Symfony kernel, which means it assumes a Symfony application structure. It also ships Symfony service definitions and event listeners that have no Laravel equivalent, so Laravel package auto-discovery will not wire it up for you. If you are evaluating it for a Laravel project, installation alone will not produce a working Crowd login flow.
- Does smurfy/crowd-bundle support Laravel 10 or Laravel 11?
- There is no Laravel version support because the package is a Symfony bundle, not a Laravel package. It predates modern Symfony and Laravel conventions, so its PHP version constraints, PSR compliance, and dependency tree are likely incompatible with a current application. Do not expect Laravel 10 or 11 compatibility without a substantial port.
- How do you configure Crowd as a security provider with this bundle?
- In Symfony you would register the bundle's services and configure Crowd as a security firewall authentication provider, pointing it at your Crowd server endpoints. The bundle then handles username and password validation plus user and group lookups against Crowd. In Laravel there is no equivalent firewall provider configuration, so you would need a custom user provider and auth guard instead.
- Which Crowd API does this bundle use, REST or SOAP?
- Historically the bundle works against Crowd's REST endpoints and, in older versions, SOAP. Crowd's REST API is more limited than SOAP, and group and attribute behaviour varies across Crowd versions, so the bundle's assumptions may not match your deployed Crowd release. Confirm which API and Crowd version your environment exposes before relying on its request and response handling.
- Is smurfy/crowd-bundle safe to use for production authentication?
- Treat it with caution. It has roughly one star, zero dependents, a single-maintainer history, and no meaningful test coverage or community validation, which means no CVE watchers and no incident reports to learn from. Authentication code that has not been reviewed or patched against modern TLS and certificate handling is a security risk on a critical path. For production, prefer a maintained client or a small reviewed implementation you own.
- How do I authenticate Laravel users against Atlassian Crowd without this package?
- Implement a thin native Laravel integration using a Guzzle-based CrowdClient service that calls Crowd's authentication, token validation, and group lookup endpoints. Then build a custom UserProvider and a custom Guard or auth driver and register them in AuthServiceProvider. This preserves the useful Crowd domain knowledge from the bundle without inheriting an abandoned Symfony dependency.
- What are the alternatives to smurfy/crowd-bundle for Crowd authentication?
- You have three realistic paths. Fork the bundle and modernise it for Laravel's contracts, which is more work but preserves any edge-case handling; write a clean-room adapter against Crowd's documented REST API using the bundle only as behavioural reference; or wrap a maintained community Crowd PHP client if one exists in your stack. Also check whether Crowd is a hard requirement or whether SAML or OIDC to a modern identity provider could replace it.
- How should I test a Crowd authentication integration in Laravel?
- Never hit a live Crowd server in CI. Mock the HTTP layer with Laravel's Http::fake or a Guzzle mock handler, then assert your CrowdClient sends the expected endpoints and payloads and handles success, invalid credentials, and error codes correctly. Add feature tests around your custom guard and user provider for token validation, group sync, and failure paths. Also test that no Crowd credentials or tokens leak into logs.
- Is Atlassian Crowd still a good platform to build authentication on?
- Crowd is a legacy identity product, and Atlassian has been steering organisations toward Atlassian Guard and cloud SSO. Building on it is a bet on a contracting platform, so clarify your organisation's Crowd exit timeline before investing. If this is a short bridge, a minimal adapter may be enough; if it is a multi-year commitment, push for a modern identity provider instead.