This website describes the Rutgers Enterprise-wide LDAP service on ldap.rutgers.edu
and ldap2.rutgers.edu. These servers are intended for use by Units throughout Rutgers
to do authentication and authorization, i.e. to check passwords, and to verify whether users are valid
members of the Rutgers community. It can also verify information such as whether they are in a certain
department or registered for a certain course.
The LDAP servers may also be used as an email address directory, for mail software that supports LDAP. Most current mail software does.
For questions, please contact ldap-support@rutgers.edu
The LDAP servers run on the usual ports, 389 for normal services, and 636 for SSL service. Anyone that supplies passwords must use SSL or TLS.
There are two LDAP servers, ldap.rutgers.edu and ldap2.rutgers.edu.
The services and machines are identical and both have their data continuously replicated from a master LDAP server.
We suggest setting up applications to use ldap as their primary server and ldap2 as a
backup in case ldap can't be reached or fails.
ldap and ldap2 are in separate locations in New Brunswick/Piscataway, on
different sides of the River. If you use only one server, it should be ldap. ldap2
may be down from time to time for software maintenance, so software that uses it should be capable of failing
over to ldap. If we take ldap down intentionally, we will provide an alternate at
the same IP address, with a few seconds of downtime for the changeover. We still recommend configuring systems
to fail over to ldap2 to protect against failures of the primary. In case of
a failure, ldap could be down for several hours.