PingDirectory
PingDirectory is an enterprise directory service that stores and manages user identities, credentials, and profile information for secure authentication and…
Platform availability
Available on 0 of 10 platforms
- Unraid (not listed)
- 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.
49/100 Fair
- Maintained
- No data
- Popular
- No data
- Easy to install
- 250 install platforms, install notes, Docker image
- Light to run
- 801 GB minimum RAM, runs on ARM
Based on 2 of 4 factors.
No GitHub repository data collected yet.
Resources & Compatibility
Minimum requirements: 1 GB RAM. ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Set password, port, and base DN first Before running setup, enter the admin password, the LDAP port clients will use, and the base DN (the top-level folder name for your directory data). If any of these are missing or mistyped, setup can fail and clients won't be able to find or sign in to your directory. source
- Keep SSL certificate files safe Put the keystore/truststore (certificate files) and their password files in a protected folder, then point setup at those paths if you want encrypted LDAP. If they are missing or too easy to read, secure LDAP can fail or your encrypted connection can be exposed. source
- Finish the proxy first-run setup If you are installing the directory proxy, accept the certificate prompt and let setup create the Proxy User. If you skip this, the proxy can't sign in to the real directory and user lookups will fail. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
What values should be entered before basic PingDirectory setup?
Set the admin password, the LDAP port clients will use, and the base DN before running setup. Missing or mistyped values can make setup fail and prevent clients from finding or signing in to the directory.
Where should encrypted LDAP certificate files be stored for PingDirectory Proxy?
Keep the keystore/truststore and their password files in a protected folder and point setup at those paths. If they are missing or too easy to read, secure LDAP can fail or the encrypted connection can be exposed.
Can an Active Directory-to-PingDirectory sync pipe show connectivity without syncing data?
Yes, the reported case had no log errors and successful connectivity, but no data was synchronized between AD and PingDirectory.
What low-level debugging support does the PingDirectory suite provide?
The UBID Suite provides many debugging facilities for diagnosing issues through low-level inspection.
Answers sourced from docs.pingidentity.com, docs.pingidentity.com, support.pingidentity.com, www.reddit.com
Community
Collected 48 days ago - public community threads