Weave Code
Ldaptools Bundle Laravel Package
ldaptools/ldaptools-bundle
Symfony bundle integrating LdapTools, a PHP LDAP library for querying and managing Active Directory and OpenLDAP. It adds service configuration and DI integration, making LDAP authentication, lookups, and directory operations easier in Symfony apps.
Provides easy LDAP integration for Symfony via LdapTools.
Frequently asked questions about Ldaptools Bundle
- Can I install ldaptools/ldaptools-bundle in a Laravel application?
- No, not directly. The package is a Symfony bundle whose value is entirely Symfony-specific: a Bundle class, a semantic Configuration tree, compiler-pass service registration, and a security user provider bridge. None of that maps onto Laravel's service container or auth guards, and installing it will drag Symfony components into your dependency graph. For Laravel you should depend on the underlying framework-agnostic library, ldaptools/ldaptools, instead.
- What is the difference between ldaptools/ldaptools and ldaptools/ldaptools-bundle?
- ldaptools/ldaptools is the actual LDAP engine and is framework-agnostic, handling binds, queries, and directory operations against Active Directory and OpenLDAP. The bundle is a thin Symfony integration layer on top of it that adds YAML configuration, dependency injection wiring, a security user provider, and a profiler data collector. A Laravel application wants the library, not the bundle.
- How do I install ldaptools/ldaptools-bundle in a Symfony project?
- Run composer require ldaptools/ldaptools-bundle, register the bundle in config/bundles.php, then create config/packages/ldaptools.yaml with your domain and connection definitions. After that you consume the ldap.manager and ldap.provider services directly. It is a config-only integration that typically takes hours, not days.
- Which PHP and Symfony versions does ldaptools/ldaptools-bundle support?
- You must check the current release's composer.json or Packagist entry before adopting, because the LdapTools family has a slow release cadence and its version constraints have historically lagged current PHP and Symfony releases. PHP version bounds are the likeliest blocker against a modern runtime baseline. Confirm the supported ranges clear your platform before writing any integration code.
- How do I authenticate users against LDAP in Laravel using LdapTools?
- Install ldaptools/ldaptools only, publish an ldap.php config that mirrors the bundle's YAML schema, and bind the LdapTools manager as a singleton in a service provider. Wrap it in a gateway or repository class exposing authenticate(), findByUsername(), and groupsFor() so the rest of the app never touches the library directly. That seam makes a later swap to another LDAP package a one-file change. Budget roughly two to four days plus test harness time.
- Is ldaptools/ldaptools-bundle actively maintained?
- It has very low adoption, around 48 GitHub stars and no dependents, which means little downstream pressure to fix issues. Expect a small bus factor, effectively one maintainer, and a realistic chance that you own any patches you need. The most likely area to go stale is the Symfony security bridge, since that is the fastest-moving part of the framework.
- How do I configure Active Directory or OpenLDAP domains with LdapTools?
- You define one or more domains in configuration, each with a connection type, a list of servers, the base DN, bind credentials, and connection options. The bundle exposes this as YAML under config/packages/ldaptools.yaml, and a Laravel port should reuse that schema verbatim in a PHP config file so both tracks stay aligned. This keeps the LDAP concepts identical even though the wiring differs.
- Does LdapTools support LDAPS, StartTLS, paged results, and referrals?
- LDAP itself is a stable protocol, so the core bind and search paths are low risk, and connection options are where TLS and similar behaviour are configured. Support for StartTLS, LDAPS, paged results, and referral handling depends on the connection type and options you select, so verify each against your actual directory. Test against a real directory replica rather than relying on documentation alone.
- Should I use LdapRecord-Laravel instead of LdapTools for a Laravel app?
- In most Laravel estates, yes. LdapRecord-Laravel is Laravel-native, actively maintained, and has a much larger community, which means less bespoke code and far less risk of owning patches. LdapTools only wins if you already run Symfony services and want one shared directory layer. Even then, keep the library behind a gateway interface so swapping later is cheap.
- How do I test LDAP authentication without a real directory server?
- Put the LDAP calls behind your own gateway or repository interface and mock that seam in unit tests, so feature tests never need a live directory. For integration coverage, run a throwaway OpenLDAP container with a seeded fixture tree during CI. Keep a small spike test that binds and searches against a directory replica to confirm TLS and schema assumptions before you commit to the package.
Weaver
How can I help you explore Laravel packages today?