Blazam vs LTB Self Service Password

Blazam is a free, open-source web interface for delegating Active Directory administration to non-IT staff. It manages users, groups, organizational units, computers, and printers, including account unlocks, password resets, group assignments, and attribute changes. Administrators can create reusable access levels for groups or individuals, with controls for individual attributes and actions. Rules can trigger Active Directory actions in response to events or on schedules, using filters, ordered processing, conditional stops, and expiration settings. Blazam also lists a REST API and webhook notifications, and offers MFA through Cisco DUO or Google Authenticator-compatible TOTP. Its documentation says passwords are encrypted at rest and in transit, connections support TLS/SSL, and the app is designed to run as an unprivileged account. Windows installation can use IIS or a standalone service; Linux installation supports Apache, nginx, or a standalone service. Blazam requires Active Directory and a domain-joined Windows host. A well-defined OU structure is needed for granular delegation, and the documentation advises against installing it on a Domain Controller. The free plan is free and is MIT licensed for personal and commercial use.

LTB Self Service Password is a PHP web application that lets users change or reset passwords in LDAP directories, including standard LDAPv3 directories and Active Directory. Password resets can rely on security questions, an emailed token, or SMS through an external Email 2 SMS service or SMS API. Administrators can configure checks for length, character classes, forbidden characters and words, password reuse, entropy and breached-password status using the Have I been pwned API. Other features include CAPTCHA, password-change email notices, and scripts that run before or after a password change. Users can also update their SSH key, email address and phone number in LDAP. A REST API is available. The free, GPL-3.0-licensed software is self-hosted. Documented installation routes include a tarball, Debian or Ubuntu packages, CentOS or Red Hat packages, Docker and Git for developers. Prerequisites include PHP 7.4 or later, required PHP extensions, Smarty 3 or later, configured mail and sessions, and LDAP connectivity. The project directs software questions to its mailing lists and bug reports to GitHub issues.