Weave Code
Iam Bundle Laravel Package
gdbots/iam-bundle
Identity and access management bundle for Laravel/PHP apps, integrating the Gdbots IAM service for authentication, user accounts, roles, and permissions. Provides configurable guards, middleware, and service bindings to wire IAM into your application quickly.
Gdbots IAM Bundle integrates the Gdbots IAM library with Symfony to provide a ready-to-use identity and access management layer. It wires configuration, services, and security components so applications can model users, roles, and permissions without repetitive boilerplate.
- Symfony integration through bundle configuration and service definitions
- Role-based access control for users and protected resources
- Extensible contracts for custom identity providers and authorization logic
- Security-aware integration with Symfony’s firewall and service container
- Composer-ready installation and straightforward configuration
Frequently asked questions about Iam Bundle
- Does gdbots/iam-bundle work with Laravel?
- No. gdbots/iam-bundle is a Symfony bundle that integrates gdbots/iam with Symfony's Security component, so it does not provide native Laravel authentication or authorization. Laravel teams would need a different package or a custom bridge, and adopting it would still mean adopting the Gdbots ecosystem.
- Which Symfony and PHP versions does gdbots/iam-bundle support?
- The bundle is intended for Symfony applications and is typically evaluated on Symfony 6 or 7 with PHP 8.1 or newer, but you must confirm the actual support matrix in the repository and CI. The technical assessment warns that Symfony Security has changed significantly since 5.3, so verify which Symfony majors are truly tested rather than claimed.
- How do I install gdbots/iam-bundle?
- Install it with Composer using the package name gdbots/iam-bundle, then register the bundle in your Symfony application and configure its services for your identity store. Because it depends on gdbots/iam and the broader Gdbots message and PBJ stack, installation in a non-Gdbots application is not a simple single-package add.
- What backing stores does gdbots/iam require?
- The bundle delegates persistence to gdbots/iam, so the required backing store is whatever the parent library is configured to use. The assessment flags this as a key unknown: confirm whether your deployment needs DynamoDB, MySQL, Elasticsearch, or only an event store before committing. If your platform does not already run that store, adoption becomes a platform decision.
- Does gdbots/iam-bundle provide a user provider and authenticator for login?
- The bundle's narrow job is to wire gdbots/iam users, roles, and permission checks into Symfony Security, including user providers and authenticators. The assessment explicitly asks whether session, token, OAuth or OIDC, and API key login methods are covered, so check the documented authenticators before assuming your flows are supported.
- How are roles and permissions modeled in gdbots/iam-bundle?
- Roles and permissions come from gdbots/iam and are surfaced through Symfony Security, likely as role strings, voters, or PBJ permission nodes. The assessment recommends mapping this model against your existing authorization scheme before adoption. Because the parent library owns the model, changes there can affect how the bundle enforces access checks.
- Is gdbots/iam-bundle production-ready?
- It has a January 2026 release and appears actively maintained internally, but the zero-star and zero-dependent profile means there is almost no public evidence of production use. Treat production readiness as unproven until you run a spike and characterize failure modes, version skew, and consistency behavior. Apache-2.0 licensing and forkability are the main mitigations.
- How do I integrate gdbots/iam-bundle with an existing Symfony app that uses Doctrine users?
- You will need a compatibility layer: a UserProviderInterface implementation backed by IAM, a one-time backfill of users and roles into the IAM store, and a transitional dual-read period where legacy roles are honored until parity is confirmed. The assessment describes this path as feasible but costly. Plan the migration before writing integration code.
- What are alternatives to gdbots/iam-bundle?
- If you are not already on the Gdbots platform, alternatives include native Symfony Security with Doctrine users and voters, or a dedicated Symfony IAM bundle that does not pull in an event-sourcing substrate. The real alternative is often to keep your current authorization model and evaluate this bundle only if you are committed to Gdbots. Treat the package as an ecosystem lock-in decision rather than a drop-in library.
- How do I test authorization and handle eventual consistency with gdbots/iam-bundle?
- Test authorization checks at the Symfony voter and user-provider boundaries, and include spike tests for version skew and storage behavior. Because IAM roles and permissions may be projected from an event stream, authorization decisions can lag behind administrative intent, so characterize and cache that read path. The assessment recommends proving feasibility with a spike rather than relying on documentation review.
Weaver
How can I help you explore Laravel packages today?