Weave Code
Ldap Bundle Laravel Package
opensky/ldap-bundle
Symfony bundle that adds LDAP authentication to your application, letting users sign in against an LDAP directory and map directory entries to local user accounts. Simplifies configuring LDAP connections, user providers, and login flows.
LdapBundle is an LDAP-based UserProvider for Symfony2's Security component.
Frequently asked questions about Ldap Bundle
- Is opensky/ldap-bundle a Laravel package?
- No. It is a Symfony 2 bundle that ships a Bundle subclass registered in AppKernel, YAML configuration under an open_sky_ldap root key, a DI extension, and an authentication provider wired into Symfony's security.firewalls chain. There is no Laravel service provider, facade, publishable config, or package auto-discovery entry. Adopting it in Laravel would mean pulling in the Symfony 2 security and kernel surface just to satisfy its type hints.
- Can I install opensky/ldap-bundle with Composer in a Laravel application?
- You cannot install it meaningfully. Its hard dependency is symfony/symfony ~2.x plus the security.context service, which conflicts with the modern Symfony components Laravel ships. Even if dependency resolution succeeded, none of the bundle's registration or configuration wiring has a Laravel analogue. Treat it as a reference implementation, not a dependency.
- Which Laravel and PHP versions does opensky/ldap-bundle support?
- None on the Laravel side, and on the PHP side it targets PHP 5.3+ with code that predates PHP 7 scalar and return type changes. The security.context service it relies on was deprecated in Symfony 2.6 and removed in Symfony 3.0, and the authentication provider interface was reworked in 3.x and replaced by the authenticator system in 5.3. PHP 8.x is out of reach without editing the source.
- What is the best Laravel alternative to opensky/ldap-bundle for LDAP authentication?
- The usual first choice is directorytree/ldaprecord-laravel, which provides a Laravel-native guard, publishable configuration, and an actively maintained LDAP client. If Active Directory group handling is the dominant requirement, adldap2/adldap2-laravel is a reasonable option. For unusual directory semantics, a thin custom user provider over ext-ldap is roughly 150 to 250 lines and avoids dead framework scaffolding.
- Does opensky/ldap-bundle work with Symfony 5 or Symfony 6?
- No. The native symfony/ldap component shipped in 5.1 and a first-class LDAP user provider arrived in 5.2, which supersedes this bundle entirely for Symfony targets. The bundle's provider interface no longer matches modern Symfony security, and its config schema does not translate. On any supported Symfony version, use symfony/ldap directly.
- Is opensky/ldap-bundle still maintained?
- There is no meaningful maintenance signal. The project has roughly 55 stars and zero dependents, with no test suite or CI to lean on, and it targets a Symfony 2 and PHP 5.3 era that has long since passed. That profile is consistent with an abandoned project rather than a niche one. Do not expect an upstream PHP 8 port or interface updates.
- Is opensky/ldap-bundle safe to use for production authentication?
- The technical risk is high and concentrated in the authentication path, where failures are user-visible and security-relevant. The unmaintained LDAP filter construction is a classic injection surface if attribute values reach the filter unescaped, bind credentials live in config files with no secret-management hook, and TLS or STARTTLS enforcement is not a first-class concern in a bundle of this vintage. There is also no test suite or CI to give you confidence before deploying.
- How is LDAP configured in opensky/ldap-bundle?
- Configuration is YAML under an open_sky_ldap root key, loaded by a Symfony DI extension and wired into the security.firewalls chain through a compiler-pass-style setup. Connections, the user provider, and the login flow are all expressed in Symfony service configuration. None of that schema maps to Laravel's config files or service container, so it cannot be reused as-is.
- Can opensky/ldap-bundle map LDAP groups to roles or handle Active Directory?
- The bundle maps directory entries to local user accounts through its LdapManager and LdapClient classes, which are essentially a few hundred lines of ldap_* wrapper code. Group-to-role mapping, nested groups, and paged results are not first-class concerns, so Active Directory setups with complex group structures will need extra work. If those features matter, evaluate LdapRecord or Adldap2 rather than forking this bundle, and if MFA or SSO is on the roadmap, consider SAML or OIDC instead of LDAP bind.
- How do I migrate from opensky/ldap-bundle to a supported Laravel LDAP solution?
- Plan it as a cutover, not an in-place upgrade, because the config schema, the provider interface, and the user object handoff do not translate. Extract the behavioral contract from the existing implementation, then reimplement the guard with LdapRecord or a custom ext-ldap provider. Confirm ext-ldap is present in both the runtime image and CI, and identify who owns the bind service account and how its credentials are rotated before switching over.
Weaver
How can I help you explore Laravel packages today?