- Can I use fr3d/ldap-bundle in Laravel?
- No. FR3DLdapBundle is a Symfony bundle and provides no Laravel service provider, Auth guard, or Eloquent binding. For Laravel, use LdapRecord-Laravel or Adldap2-Laravel, or re-implement its attribute-mapping and user-reconciliation logic against those packages.
- What does FR3DLdapBundle do?
- It integrates LDAP authentication into Symfony security firewalls by supplying an authentication provider and a user provider. It maps LDAP attributes such as DN, mail, cn, and memberOf onto a Doctrine-backed user entity. Persistence and registration are delegated to a user manager such as FOSUserBundle.
- Which Symfony and PHP versions does FR3DLdapBundle v4.0.0 support?
- Version 4.0.0 requires PHP >=7.1 and Symfony >=3.4, and it drops Symfony 2.3 through 3.3 support. The constraints are open-ended, so Composer may install it into Symfony 6 or 7 and PHP 8.3 even though it is not targeted there. Treat resolution success as advisory and expect runtime failure in the authentication path on modern stacks.
- How do I install fr3d/ldap-bundle?
- Install it with Composer using fr3d/ldap-bundle, enable the bundle in your Symfony kernel, and configure the LDAP provider and security firewall. This is Symfony wiring only; there is no Laravel package discovery, service provider, or Laravel config file. For v4.0.0, confirm the application is on Symfony 3.4 or plan a careful 4.x spike before installing.
- How do I configure LDAP authentication with FR3DLdapBundle?
- Configure the LDAP connection details such as host, port, base DN, and bind credentials, then wire the LDAP authentication and user providers into your Symfony firewall. Map LDAP attributes like dn, mail, cn, and memberOf to your user entity and configure the user manager for persistence. The bundle supports bind-as-user or bind-then-search-then-rebind flows, so validate your directory contract carefully.
- How does FR3DLdapBundle map LDAP groups to Symfony roles?
- It can map group information from LDAP attributes such as memberOf onto Symfony roles through configuration. You must account for Active Directory versus OpenLDAP schema differences and for nested group depth. Test case sensitivity and group nesting explicitly because mapping defects usually surface as missing or incorrect authorization.
- Is FR3DLdapBundle maintained or safe for production?
- The project is archived, and a single tagged release does not constitute upstream triage, a security response process, or CVE handling. An authentication-path defect can cause a full outage or an authentication bypass, so treat it as a standing audit finding. It is at best a stopgap for a legacy Symfony 3.4 application, not a production choice for new work.
- What are alternatives to FR3DLdapBundle for Laravel?
- For Laravel, use LdapRecord-Laravel or Adldap2-Laravel instead of trying to adapt this Symfony bundle. On modern Symfony, use the framework's built-in form_login_ldap and LdapUserProvider or ldaptools/ldaptools-bundle.
- How should I test an FR3DLdapBundle integration?
- Test against a representative LDAP directory or a controlled mock that covers bind, DN lookup, attribute hydration, group-to-role mapping, and failed-login behavior. Re-test the login flow specifically because v4.0.0 changed the form validator to Symfony 3.4 classes, and a regression there manifests as authentication failures. Include TLS and CA posture checks if your directory requires secure LDAP.
- Does FR3DLdapBundle support Symfony 5, 6, or 7?
- There is no explicit Symfony 5, 6, or 7 targeting in v4.0.0; the open-ended >=3.4 constraint is not a compatibility guarantee. For modern Symfony, use the native form_login_ldap and LdapUserProvider, which stabilize from Symfony 4.4, or use ldaptools/ldaptools-bundle. Do not rely on Composer resolving the bundle as evidence that it works at runtime.