Tutorials & Integration Guides
Accessing a Firewalled LDAP Server from a Heroku Ruby App
A Ruby app can talk to corporate LDAP easily with net-ldap, until it’s deployed on Heroku and the LDAP server sits behind a firewall. Heroku does not provide a fixed outbound IP, so corporate allowlisting breaks. QuotaGuard solves this by routing outbound traffic through a load-balanced pair of static IPs via a SOCKS5 proxy that supports LDAP. After provisioning QuotaGuard, there are two integration options: 1. SOCKS wrapper script: forces outbound TCP through the SOCKS5 proxy (optionally masked so only AD traffic goes through). It’s quick to set up, but the masking can become maintenance if AD hosts change, and the wrapper is Linux-only so local dev on macOS or Windows is awkward. 2. Patched gems: use QuotaGuard’s patched socksify and net-ldap to route LDAP through the SOCKS proxy directly via Gemfile entries. This works cross-platform and avoids per-host masking work, but it depends on custom forks that may lag upstream updates.