Weave Code
Adldap Laravel Package
adldap/adldap
Adldap2 is a PHP LDAP library for integrating Active Directory and OpenLDAP into applications. It offers fluent querying, authentication, and management of users, groups, and organizational units, with a separate Laravel integration available.
Adldap is a Laravel package for integrating LDAP and Active Directory authentication and directory management into PHP applications. It provides an expressive, Eloquent-like API for querying and managing directory entries, letting Laravel apps authenticate users against LDAP and work with users, groups, and organizational units without writing raw LDAP code.
- Laravel-native configuration and service provider
- Authentication against LDAP/Active Directory
- Fluent query builder for searching directory records
- CRUD operations for users, groups, and OUs
- Support for multiple LDAP connections
Frequently asked questions about Adldap
- Is adldap/adldap compatible with Laravel 11?
- adldap/adldap is a 2014-era PHP LDAP utility, not a modern Laravel package, and it has had no release for more than a decade. Expect no service provider, facade, publishable config, dependency injection, or Laravel-native testing support. For Laravel 9, 10, or 11 on PHP 7.4/8.x, assume incompatibility until proven otherwise with a compatibility spike.
- How do I install adldap/adldap with Composer?
- You may be able to add it with Composer, but the repository is unknown in this assessment and the package is effectively vendored legacy code. Mirror the source into private VCS, review it, and pin the exact commit or version rather than trusting a floating constraint. Also confirm the PHP ldap extension and your Composer and PHP constraints before any spike.
- What is adldap/adldap used for?
- It is a PHP class for LDAP authentication and Active Directory integration, including bind authentication and querying directory entries, groups, and organizational units. It is a general PHP utility rather than a Laravel-native package. Your application must define its own configuration boundary, error mapping, credential handling, and security controls.
- Should I use adldap/adldap or LdapRecord-Laravel in a new Laravel project?
- For greenfield Laravel, do not adopt adldap/adldap; use native PHP LDAP or a maintained package such as LdapRecord-Laravel after verifying current support. adldap/adldap has high technical risk due to age, unknown provenance, and missing security patches. It is only defensible as a short-lived adapter for a legacy PHP 5.x-era application.
- How do I integrate adldap/adldap without leaking it into my Laravel codebase?
- Wrap it behind an application-owned anti-corruption layer, such as an AdAuthenticator interface with authenticate, findUser, and groupsForUser methods. Keep package classes out of controllers, models, jobs, and domain logic. Load secrets from environment variables or a secret manager, use redacted logging, timeouts, rate limits, and a feature flag with rollback.
- Does adldap/adldap support LDAPS, StartTLS, and certificate validation?
- The package is old and its TLS and LDAP defaults are a known concern, so you must verify LDAPS, StartTLS, certificate validation, referral handling, and error codes against a real test Active Directory. Do not assume secure defaults. Test TLS failure scenarios explicitly before any production use.
- What are the production security risks of adldap/adldap?
- Key risks include unsupported PHP versions, missing security patches, unknown repository provenance, old TLS and LDAP defaults, unclear LDAP filter escaping, credential handling, and AD account-lockout behavior. LGPL-2.1 distribution obligations may also require legal review. Treat it as high risk and require explicit security and license sign-off if proceeding.
- Is adldap/adldap still maintained?
- No release has shipped for more than a decade, the repository is unknown in this assessment, and support is community-only and effectively nonexistent. Documentation and examples are old, and online guidance may not match current PHP or Laravel versions. Your team would own vulnerability triage, compatibility patches, and security review.
- How should I test adldap/adldap authentication and LDAP failures?
- Spike in a disposable environment against a non-production Active Directory. Test bind success and failure, wrong password, expired password, locked account, TLS failure, AD timeout, group lookup, and nested groups. Confirm error codes and referral handling, then roll out behind a feature flag with a documented rollback.
- What license does adldap/adldap use, and does it affect distribution?
- The assessment flags LGPL-2.1 distribution obligations, so legal and license review is required if the application will be distributed. Because repository provenance is unknown, mirror and review the code and pin an exact version. Do not assume the license or supply chain has been vetted.
Weaver
How can I help you explore Laravel packages today?