- Can I use riper/security-active_directory for Active Directory authentication in Laravel?
- No. Despite the Laravel-oriented package description, riper/security-active_directory is a Symfony security bundle for Active Directory authentication, not a Laravel package. It does not provide a Laravel auth guard, service provider integration, or published Laravel configuration out of the box. For Laravel AD/LDAP authentication, evaluate LdapRecord-Laravel or php-ldap instead.
- Which Symfony versions does riper/security-active_directory support?
- Version 2.0.0 requires Symfony >=2.6 and targets the Symfony 2.6–2.8 era. It does not declare support for Symfony 3.x, 4.x, or modern Symfony 5/6/7. Installation on newer Symfony versions is unsupported even if it happens to work in practice.
- What changed in riper/security-active_directory v2.0.0?
- Version 2.0.0 raises the minimum Symfony version to 2.6 and replaces the deprecated Security context with the token_storage service. That is a backward-compatibility break in service wiring and in any custom authentication provider or factory code. Existing 1.x integrations cannot be upgraded in place without configuration and code changes.
- Is riper/security-active_directory actively maintained and production-ready?
- Adoption is thin, with roughly 16 stars and zero dependents, and there is no evidence of a maintained security-patch cadence, test suite, or CI. Authentication is a security-critical path, so that is a high-risk profile for production use. Treat it as a reference implementation or a legacy-only dependency rather than a greenfield choice.
- How do I migrate from riper/security-active_directory 1.x to 2.0?
- You must account for the move from the Security context to token_storage, which changes the dependency graph for the bundle's services and any custom authentication provider or factory. Existing 1.x integrations need configuration and code changes and cannot be upgraded in place. Because field usage is near zero, the upgrade path is largely untested beyond the author. Prototype the migration on your exact target stack and pin dependencies.
- What are the alternatives to riper/security-active_directory for Laravel AD authentication?
- For Laravel, use LdapRecord-Laravel or php-ldap. Outside Laravel, options include the Symfony LDAP component, Adldap2, and FreeDSx LDAP. If you are on legacy Symfony 2.6–2.8 and need simple AD bind authentication, this bundle might be evaluated with a fork and pinned dependencies. For modern Symfony, prefer Symfony's LDAP component or a maintained bundle.
- Does riper/security-active_directory support group and role mapping for Active Directory?
- The package description mentions configurable group and role mapping to translate directory membership into application permissions, plus automatic user synchronization on login. However, because it is a Symfony security bundle and not Laravel-native, you should not expect Laravel guards, Eloquent user mapping, or published Laravel configuration out of the box. Verify the actual feature set in the bundle code before relying on it.
- What are the security risks of using riper/security-active_directory in production?
- Risks include PHP 8 behavior, deprecated Symfony 2.x APIs, weak TLS/AD defaults, credential handling, and absent observability. AD environment risks are unchanged: domain controller discovery, LDAP versus LDAPS, referral chasing, nested groups, Kerberos/SSO, and account lockout semantics. The token_storage change carries regression risk in token and session handling, where mistakes are hardest to detect.
- Can I use riper/security-active_directory with PHP 8 or modern Symfony?
- It is not declared compatible with modern Symfony 3.x/4.x or 5/6/7; v2.0.0 targets Symfony >=2.6 in the 2.x era. PHP 8 behavior is a listed risk, and there is no evidence of CI or a test suite to validate it. For modern stacks, use maintained LDAP/AD components instead.
- Should I fork riper/security-active_directory or replace it?
- Fork only if you are maintaining a legacy Symfony 2.6–2.8 application that already uses Symfony Security and needs simple AD bind authentication; assume you own security patching and dependency pinning. Otherwise replace it with a maintained alternative such as Symfony LDAP component, LdapRecord, Adldap2, or FreeDSx LDAP. For Laravel specifically, do not integrate this package. Have an exit and rollback plan if AD authentication fails in production.