- What is anndro/sentry_ldap used for?
- It provides an LDAP authentication driver for Cartalyst Sentry in Laravel, letting users sign in against LDAP or Active Directory. It is a legacy integration tied to Sentry and PHP 5.3-era conventions, not a modern native Laravel auth driver. Use it only in a constrained legacy app that already depends on Sentry.
- Is anndro/sentry_ldap compatible with Laravel 10 or Laravel 11?
- No, it should not be assumed compatible with modern Laravel versions. The package has had no release since 2015 and targets PHP 5.3-era Laravel and Sentry dependencies. You would need a time-boxed spike, dependency audit, and likely a fork to even evaluate compatibility.
- How do I install anndro/sentry_ldap with Composer?
- Installation is typically via composer require anndro/sentry_ldap, but the legacy dependency constraints are the main obstacle. Expect Composer conflicts with current PHP and Laravel packages, so pin old dependencies or vendor the code. Verify autoloading and service provider registration in an isolated branch before touching production.
- How do I configure LDAP connection details and base DN in SentryLdap?
- The package includes configuration for LDAP connection details, base DN, and user attributes. You will need to supply your directory host, port, bind credentials, base DN, and attribute mappings for users and groups. Validate DN escaping, TLS settings, and schema differences for OpenLDAP versus Active Directory.
- Can anndro/sentry_ldap authenticate against Active Directory?
- Yes, it is intended to let users sign in against LDAP or Active Directory. However, AD behavior around group nesting, DN formats, and TLS certificate validation must be tested explicitly. Do not assume the package handles every AD schema variant correctly.
- How does anndro/sentry_ldap map LDAP groups to Sentry roles?
- The package is meant to support group membership mapping into Sentry's authorization model. Group-to-role mapping defects and nested group behavior are known risk areas for legacy LDAP integrations. Test mapping with real directory groups, including edge cases, before relying on it for access control.
- Is anndro/sentry_ldap still maintained?
- No, it has low adoption with 21 stars, zero dependents, and no release since 2015-06-18. There is no recent community support or security patching. If you use it, your team effectively becomes the maintainer and should budget for fork ownership.
- What are alternatives to anndro/sentry_ldap for Laravel LDAP authentication?
- For modern Laravel, prefer native authentication with a maintained LDAP integration layer or a small internal adapter around php-ldap. If requirements are narrow, a custom LdapAuthenticator that syncs users and roles locally is often safer. Treat the legacy package as an implementation detail to migrate away from, not a strategic identity component.
- What are the security risks of using anndro/sentry_ldap in production?
- Authentication is a security-critical path, and this package is unmaintained with an abandoned Sentry dependency surface. Risks include missing security patches, PHP/Laravel incompatibility, LDAP TLS gaps, and group-to-role mapping defects. Any production use should carry an explicit technical-debt item, security review, and exit plan.
- Can I fork anndro/sentry_ldap and maintain it myself?
- Yes, the BSD-3-Clause license is permissive and lowers legal friction for a fork. You would need to own dependency patching, PHP upgrades, LDAP edge cases, and security review. A fork can be a tactical bridge, but plan a phased migration to a maintained solution.