- Can I use redeye/stormpath-bundle in a Laravel application?
- No. It is a Symfony bundle built around Symfony's kernel and dependency injection container conventions, so a Laravel app would need service providers, facades, and config publishing to bridge it. Even with that work, Stormpath's API and SDKs are no longer operational, so there is nothing to connect to.
- Does redeye/stormpath-bundle still work now that Stormpath has shut down?
- No. Stormpath was acquired by Okta and shut down in 2017, so its API endpoints and SDKs no longer operate. The bundle may still install via Composer, but every runtime call to Stormpath will fail. It is a historical artifact rather than an adoptable dependency.
- What Laravel versions does this package support?
- None. redeye/stormpath-bundle is a Symfony bundle with no Laravel service provider, facade, or Laravel-specific configuration, and it predates current Laravel releases. There is no compatibility matrix for Laravel and no maintainer support for it.
- How do I install and configure redeye/stormpath-bundle?
- Mechanically you would require it via Composer and register it in a Symfony AppKernel or bundles.php, then supply Stormpath credentials and config. However, you cannot provision a Stormpath tenant, so installation never leads to a working integration. Do not schedule adoption of this bundle as a work item.
- What should I use instead of Stormpath for Laravel authentication?
- Start with first-party Laravel options such as Fortify, Breeze, Jetstream, Sanctum, Passport, or Socialite depending on your use case. For hosted identity, use a current provider like Okta, Auth0, Microsoft Entra ID, or Keycloak with an actively maintained OIDC or SAML package. There are maintained Laravel packages that cover these flows.
- Is redeye/stormpath-bundle safe to use in production?
- No. The package touches authentication and credential handling, but its upstream service is gone and there is no maintainer issuing security patches. It has negligible community validation, with roughly 5 stars and 0 dependents. That combination is the highest-severity risk category for an auth dependency.
- Can I fork redeye/stormpath-bundle and point it at Okta or Auth0?
- You technically can, but you would be rewriting the service layer against a different provider's API rather than patching this package. At that point you are no longer using the bundle in any meaningful sense. Use the new provider's official SDK or a maintained framework bundle instead.
- What Symfony versions does redeye/stormpath-bundle support?
- It targets Symfony 2.x and 3.x-era bundle conventions and predates the bundles.php-only workflow in modern Symfony. Compatibility with current Symfony and PHP versions is unverified and likely broken. Check the composer.json constraints before considering it even as reference material.
- How do I test an application that uses redeye/stormpath-bundle?
- You cannot meaningfully integration-test it because the Stormpath service it depends on is offline. You would have to mock every API call, which only tests your mocks rather than a real integration. If you are rebuilding identity, test against a live, maintained identity provider instead.
- Is redeye/stormpath-bundle maintained, and how do I migrate off Stormpath?
- It is not maintained, and the Stormpath service itself no longer exists. Migration is really a rebuild: choose a current identity provider such as Okta, Auth0, Keycloak, or Entra ID, re-provision or import users, and use that provider's maintained SDK. Treat this repository as reference material only and decommission any Stormpath references in your stack.