Weave Code
Ldap Bundle Laravel Package
gepur-it/ldap-bundle
gepur-it/ldap-bundle is a PHP/Symfony bundle that integrates LDAP directory services with your application, offering configuration for connections, user authentication, and directory queries. It helps wire LDAP-backed login and user lookup into Symfony services with minimal setup.
Authorisation bundle fot gepur apps
Frequently asked questions about Ldap Bundle
- Can I use gepur-it/ldap-bundle in a Laravel application?
- Not without an adapter. The package name and convention (ldap-bundle) identify it as a Symfony bundle, so it bootstraps through a Bundle class, a DI Extension, and compiler passes, none of which Laravel executes. Composer will install it fine, but in a Laravel app it stays inert at runtime until you write a service provider that wires the connection and user provider into Laravel's container and auth layer yourself. Treat it as an LDAP implementation you integrate, not a drop-in Laravel package.
- How do I install gepur-it/ldap-bundle with Composer?
- Installation is a standard Composer require against the public GitHub repository; there is no Packagist-focused documentation or install guide in the release. Before committing, read the composer.json to confirm the PHP constraint, the Symfony framework constraint, and whether it depends on ext-ldap directly or on symfony/ldap. Also check for any transitive dependencies on private gepur packages, which would make the install unresolvable outside their organisation.
- What PHP and Symfony versions does ldap-bundle v5.1.0 support?
- The only stated constraint in the v5.1.0 release note is php >=7.4 with no upper bound, which is a compatibility red flag rather than a guarantee. An unbounded constraint means the package will resolve happily on PHP 8.2, 8.3, 8.4, and future majors even though nothing indicates it was tested there. No framework-version constraint is mentioned in the changelog, so verify the Symfony requirement in composer.json before relying on it.
- Does this bundle work as a Laravel auth guard or user provider?
- No. The bundle supplies an LDAP user provider for Symfony's security firewall, and Laravel's guard and user-provider contracts are a different abstraction. Bridging them means implementing Illuminate\Contracts\Auth\UserProvider on top of the bundle's lookup helpers, or bypassing the security integration and calling the directory search services directly. Because authentication code carries a large blast radius, test the bridge thoroughly before shipping it.
- How do I configure LDAP connections such as host, port, base DN, and bind credentials?
- The bundle exposes declarative configuration for connections, including host, port, base DN, and bind credentials, plus sensible defaults and overridable services in the container. In Symfony that configuration is loaded through the bundle's extension in your config directory. In a Laravel adapter you would have to instantiate and populate the connection service yourself, since Laravel's config repository is not read by a Symfony DI extension.
- What changed between older versions and ldap-bundle v5.1.0, and were there breaking changes?
- The v5.1.0 changelog entry consists solely of a PHP constraint line, so there is no record of what actually changed. It is unclear whether a v4 to v5 major transition occurred, and whether bind behaviour or group mapping changed in ways that would break existing integrations. Because intent cannot be diffed from the note, review the source or a repository diff rather than trusting the version number.
- Does gepur-it/ldap-bundle support LDAPS, StartTLS, paged results, and Active Directory?
- This is not documented. The package has no README, no tests, and no usage examples, so protocol-level behaviour has to be read directly from the source. The description only claims configurable connections, a security user provider, directory search and lookup helpers, and extensible attribute mapping and filters. Confirm LDAPv3 handling, StartTLS versus LDAPS, referral chasing, paged results, and AD versus OpenLDAP differences before depending on any of them.
- How do I map LDAP attributes and groups to application roles?
- The bundle advertises an extensible design for custom attribute mapping and filters, but the mapping model itself is not documented anywhere in the release. It is also unclear whether the package implements simple bind, search-and-bind, group-to-role mapping, or a gepur-internal RBAC layer, and the description's framing suggests the latter. Read the source to determine which model applies before designing your role mapping around it.
- Are there tests, documentation, or usage examples for this bundle?
- None are shipped. The release provides no README, no docs, no tests, and no usage examples, and the changelog is a single line, so the discovery cost is effectively reading every file. Maintenance is minimally attended at best: a tag after roughly four years of silence shows the repository is not dead, but there is no visible community catching regressions and no documented security contact. Forking, adding tests, and pinning the tag is the safer path for production use.
- What are the alternatives to gepur-it/ldap-bundle for LDAP authentication?
- For Symfony, the official symfony/ldap component plus a small custom user provider is the better-supported route, and it gives you real framework version constraints. For Laravel specifically, packages such as LdapRecord or Adldap2 provide native guards, query builders, and documented attribute and group handling. Those options trade some of this bundle's prebuilt wiring for maintained code, tests, and a support community, which matters most in authentication paths.
Weaver
How can I help you explore Laravel packages today?