- Is iter8/ldaprecord-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle, not a Laravel package. It integrates LdapRecord into Symfony via the service container and YAML configuration. Laravel applications should not use this package; they have a dedicated Laravel integration instead.
- Can I use iter8/ldaprecord-bundle in a Laravel application?
- No, it is built specifically for Symfony and relies on Symfony bundle registration and service autowiring. Laravel does not use Symfony bundles in the same way, so this package will not work out of the box in a Laravel app. For Laravel, use directorytree/ldaprecord-laravel, which is the maintained Laravel-specific integration.
- What Laravel package should I use for LDAP authentication and directory queries?
- Use directorytree/ldaprecord-laravel. It wraps the same underlying LdapRecord library but provides Laravel service providers, facades, configuration, and auth integration. The iter8/ldaprecord-bundle is only relevant if you are working in a Symfony project.
- What are the requirements for iter8/ldaprecord-bundle v4.0.0, including Symfony and PHP versions?
- v4.0.0 requires PHP 8.1 or later, Symfony 6.1 or later, and LdapRecord v3. It excludes Symfony 5.4 LTS, so projects still on 5.4 cannot adopt v4.0.0 and must remain on v3.0.0, which uses LdapRecord v2 and is unmaintained. Symfony 7.x support is not explicitly stated, so verify the constraint graph before committing.
- Does iter8/ldaprecord-bundle work with Symfony 5.4 LTS?
- No, v4.0.0 requires Symfony 6.1 or later, so Symfony 5.4 is not supported. If you are on Symfony 5.4, the only option is v3.0.0, which depends on LdapRecord v2 and is now an unmaintained branch. This is a hard constraint to consider before upgrading.
- How do I install and configure iter8/ldaprecord-bundle?
- Install via Composer, register the bundle in config/bundles.php, and configure your LDAP connections in config/packages/*.yaml. The bundle provides service container integration so you can inject directory services and use LdapRecord models and query builders. Note that the bundle namespace changed in v4.0.0, so update your registration and use statements accordingly.
- Does iter8/ldaprecord-bundle provide a Symfony Security user provider or authenticator?
- No, it only provides connection and manager objects. It is not a Symfony Security user provider or authenticator, so you must write the glue code yourself to integrate LDAP authentication with Symfony's security system. The bundle reduces boilerplate for configuration and DI, but it does not handle security integration out of the box.
- Can I use multiple LDAP connections with iter8/ldaprecord-bundle?
- Yes, the bundle supports multiple directory connections through YAML configuration. You can define separate connections and inject the appropriate manager or connection service where needed. Per-connection options such as TLS, protocol, timeouts, and page size should be configurable, though you should verify the exact options supported by LdapRecord v3.
- What breaking changes are in iter8/ldaprecord-bundle v4.0.0?
- The main breaking change is the bundle namespace moving from Iter8\Bundle\LdapRecordBundle\Iter8LdapRecordBundle to Iter8\LdapRecordBundle\Iter8LdapRecordBundle. This affects bundles.php registration, services.yaml aliasing, and any use statements referencing bundle classes. Additionally, v4.0.0 upgrades to LdapRecord v3, which carries its own API breaks from v2, so you may need to update query code as well.
- Is iter8/ldaprecord-bundle actively maintained, tested, and safe for production?
- Maintenance is minimal. There was a release after roughly 20 months, which shows some responsiveness, but adoption is very low (3 stars) and there is no evidence of CI or a test suite. The package is effectively a single-vendor wrapper around LdapRecord, so the bus factor is roughly one. For production, consider forking or inlining the small amount of code instead of tracking the package.