- Is fm/keystone-bundle compatible with Laravel?
- No. fm/keystone-bundle is a Symfony2 bundle for the OpenStack Identity Service API, not a Laravel package. It does not follow Laravel service-provider, facade, config-publishing, or package-discovery conventions, and its Symfony container assumptions do not map cleanly to Laravel. Treat any integration as a port or adapter effort rather than a normal Composer dependency.
- Can I install fm/keystone-bundle in a Laravel application via Composer?
- Composer may install the package, but that does not make it Laravel-compatible. The bundle is archived, depends on old Symfony/PHP assumptions, and has no Laravel bootstrapping or package discovery. Expect container or bootstrapping failures unless you isolate it behind an adapter layer.
- What is fm/keystone-bundle used for?
- It is a Symfony2 implementation of the OpenStack Identity Service API, also known as Keystone. It provides bundle configuration, service wiring, and convenience helpers for Symfony/PHP applications that need Keystone support. It is not intended for Laravel applications.
- Is fm/keystone-bundle maintained or abandoned?
- It is effectively abandoned. The package is archived, its last release was 2014-03-18, it has zero dependents, and the evaluation notes explicit supersession by treehouselabs/keystone-bundle. There are no security releases, bug fixes, or upstream support signals.
- Which Laravel and PHP versions does fm/keystone-bundle support?
- The context does not list official Laravel or PHP version support, and the package predates modern Laravel releases. Its Symfony2-era assumptions and 2014 release date make compatibility with current Laravel and PHP versions unlikely without a fork or adapter. Validate PHP constraints, Symfony component versions, PSR compliance, and autoloading before any proof of concept.
- What is a good Laravel alternative to fm/keystone-bundle for OpenStack Keystone?
- The context does not name a specific Laravel-native Keystone package. For Laravel, prefer a maintained PHP SDK or a thin internal HTTP client around the required Keystone/OpenStack Identity API surface. Evaluate treehouselabs/keystone-bundle only as a migration reference or for Symfony contexts, not as a Laravel drop-in.
- How do I integrate OpenStack Keystone authentication in Laravel without a Symfony bundle?
- Define the required behavior first, then build a small internal client around the Keystone API endpoints you need. Put configuration in Laravel config and environment variables, bind an internal contract through a service provider, and keep token handling behind that contract. Add contract tests and dependency/security scans before production exposure.
- Does fm/keystone-bundle work with Laravel service providers, facades, or package discovery?
- No. It is built around Symfony bundle conventions, so it does not expose Laravel service providers, facades, publishable configuration, migrations, or package discovery. Adopting it would introduce framework-bound abstractions that need a Laravel-native interface or an anti-corruption layer. Otherwise, Laravel domain code would depend directly on Symfony-specific wiring.
- Is fm/keystone-bundle safe to use in production?
- The technical risk is high. It is archived, has no upstream patching, relies on stale PHP/Symfony assumptions, and may introduce unpatched security issues, especially on identity or authentication paths. Avoid production use in Laravel; if a short-lived proof of concept is approved, pin dependencies, isolate the package, and plan a rollback path.
- What should I check before using fm/keystone-bundle or its successor in a Laravel project?
- First document the exact capability needed: identity, authentication, Keystone API access, or CMS behavior. Then evaluate a Laravel-native package, maintained PHP SDK, or thin internal client, and check PHP/Symfony/PSR constraints, dependency age, autoloading, and security scans. If you proceed, isolate the integration behind a Laravel-native contract with tests and a rollback plan.