Weave Code
Iam Laravel Package
gdbots/iam
gdbots/iam is a PHP identity and access management package for Gdbots applications, providing users, roles, permissions, and authentication/authorization helpers to manage accounts and enforce access control across services.
Php library that provides implementations for gdbots:iam schemas.
Frequently asked questions about Iam
- Is gdbots/iam a Laravel package?
- No. gdbots/iam is a framework-agnostic PHP identity and access management component from the Gdbots ecosystem, not a Laravel package. It ships schema-generated message classes for users, roles, permissions, and grants rather than Laravel-specific auth tooling. You can use it in a Laravel application, but you must build the Laravel integration yourself.
- How do I install gdbots/iam in a Laravel application?
- Install it with Composer, along with its gdbots/pbj runtime dependency, using composer require gdbots/iam. There is no Laravel service provider, configuration file, facade, or package auto-discovery to rely on. Expect to wire the library into your application manually and verify the resolved version and PHP constraints with Composer.
- Does gdbots/iam provide Laravel auth guards, migrations, or a service provider?
- No. The package has no service provider, no configuration file, no facade, no migrations, no guards, no HTTP surface, and no storage layer. It provides immutable, validated, JSON-serializable IAM value objects generated from gdbots:iam PBJ schemas. Persistence, hydration, caching, and authorization decisions remain your responsibility.
- What PHP and Laravel versions does gdbots/iam support?
- The v3.0.0 release raises the PHP requirement to 8.1. PHP 8.2 and 8.3 support is not verified in the available release information, and there is no declared test matrix or CI visibility. Laravel version support is not declared because this is not a Laravel package; the practical constraint is your application's PHP version and the PBJ runtime.
- What does gdbots/iam actually give me for roles and permissions?
- It gives you a structured IAM domain model covering users, roles, permissions, grants, and related entities. These are schema-generated, strictly typed, validated, JSON-serializable message objects suitable for persistence and cross-service exchange. The package provides the model and authorization concepts, not a ready-made RBAC database or admin UI.
- Can I use gdbots/iam with Eloquent models and a database?
- Yes, but only by writing the mapping layer yourself. There are no Eloquent models, migrations, repositories, or casts included, so you will need repository adapters, custom casts or serializers, and hydration logic between PBJ messages and your application models. Budget this as a small integration project rather than a simple dependency install.
- How do I integrate gdbots/iam authorization checks into Laravel policies or gates?
- There is no built-in Laravel policy or gate bridge. A typical approach is to translate your PBJ user, role, permission, and grant objects into your application's domain model, then perform checks inside Laravel policies or gates. Keep the decision layer in your application so you retain control over caching, tenancy, and resource-scoped authorization.
- Is gdbots/iam production-ready and actively maintained?
- Treat it as high risk for a security-sensitive dependency. It has zero stars and no visible dependents, one release since December 2021, and the v3.0.0 release note is minimal with no enumerated breaking changes or visible CI test matrix. Apache-2.0 licensing helps because it permits a vendored fork, but you should be prepared to own maintenance and security review.
- What changed in gdbots/iam v3.0.0 and is it a breaking change?
- v3.0.0 is a major version bump that adds PHP 8.1 support, but the breaking changes are not enumerated in the release note. Any v2.x prototype or spike must be re-validated against the v3 diff or changelog before pinning. Check whether the schema set or the PBJ runtime contract changed, and run composer why-not gdbots/iam v3.0.0 in your project.
- What are alternatives to gdbots/iam for Laravel RBAC?
- If you want a drop-in Laravel solution, spatie/laravel-permission and Laravel's own gates and policies are common choices. gdbots/iam is a better fit only when you want a canonical, framework-agnostic IAM contract decoupled from Eloquent and are prepared to own persistence and authorization logic. Compare the cost of adopting its foreign schema against defining your own model informed by it.
Weaver
How can I help you explore Laravel packages today?