LDAP-Sync
LDAP-Sync is an extension for AuthPortal that supports LDAP, the Lightweight Directory Access Protocol, for which OpenLDAP is an open-source implementation.
Platform availability
Available on 1 of 10 platforms
- Unraid
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
11/100 Low
- Maintained
- 0last commit 4247 days ago
- Popular
- 102 GitHub stars
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- No data
Based on 3 of 4 factors.
Availability: platform listings confirmed today, links checked 27 days ago
- GitHub stars
- 2
- Open issues
- 0
- Last commit
- 2015-04-06
- Activity
- stale
Checked 9 days ago - source: GitHub (syadykin/ldap-sync)
Resources & Compatibility
ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Configure your LDAP login details Replace the example LDAP address, login name, and password with the real values for your LDAP directory server. If you leave them as samples, LDAP-Sync will not be able to connect or authenticate. source
- Keep the LDAP port reachable The example uses port 389, the standard LDAP port. If your firewall blocks that port, the app cannot reach the LDAP server. source
- Use StartTLS if required If your LDAP server requires StartTLS (encrypted traffic after connecting), enable it in your settings. Without it, the secure handshake can fail and syncing may not work. source
- Config file location Place the configuration file at /etc/ldap-sync/config.json with connection, bind, sync, and log sections; an invalid file causes the app to raise an error on start. source
Fetched 39 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Where does ldap-sync look for its configuration file, and what happens if loading fails?
It searches for /etc/ldap-sync/config.json and raises an error if the config import fails.
What connection settings are needed for the Redmine backend plugin?
Configure url, key, auth_source_id, and domain; the key is an admin API key and auth_source_id is the LDAP authentication source number shown in Redmine admin.
How should firewall and TLS settings be handled for the LDAP server connection?
Keep the standard LDAP port, such as 389, reachable, and enable StartTLS if the LDAP server requires encrypted traffic after connecting.
Can ldap-sync log errors to email, and what should I use if Gmail has two-factor authentication enabled?
The log section supports file and mail; for mail you provide SMTP fields such as host, port, SSL, username, password, subject, from, to, and level, and Gmail two-factor requires an application password.
Answers sourced from github.com, pkg.go.dev
Community
- ldap - Openldap sync issue in multi-master replication - Stack Overflow (forum)
- Recommended Frequency - LDAP Sync process — Cloud Customer Connect (other)
- LDAP sync issues - OpenText - Forums (forum)
- What is LDAP Synchronization and how does it work? - CyberArk (other)
- Do you have an LDAP server setup? : r/selfhosted - Reddit (reddit)
Collected 48 days ago - public community threads