• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 600
  • Last Modified:

LDAP server on Linux Redhat 6

I need to create an LDAP server Master/Slave configuration (Where, when the client updates, it updates the Master...and viceversa).

I've come across these 3 links:


(this link has sublinks, -adding users -creating client -creating TSL)


I'm thinking I need to follow the last one, since I'm running rhel 6.5. I'm not too familiar with 389. The first two install the standard openldap packages, but the last installs a 389 package

I am not wanting to integrate it (at this time) with active directory. I would just add users manually, to test that the LDAP seemless works across clients.

I'd like a suggestion on what link I should follow, and any experience and/or input you all have with 389.

Thanks for any information/advice
2 Solutions
Zephyr ICTCloud ArchitectCommented:
Well, it depends on what you will be more comfortable with, there's positives and negatives with all the choices.

389 is actually a product from Redhat, so you'll stay in the same group if you'd go with that, there's plenty of sources on the web that explain on how to install it, choose the one that seems best and go with it ...

Than there's OpenDJ Directory as an alternative as well as ApacheDS which is LDAPv3 compatible among other things ...

I'd go over all of them to see what seems most interesting to you, I've dabbled with OpenLDAP and ApacheDS (I like the latter a lot), I haven't played with 389 Directory yet though...
José MéndezCommented:
I have been looking for a good LDAP option myself. The 389 is praised all over, and even has a nice GUI


I don't like the fact that ApacheDS is Java based, I immediately link that to extra labor setting up the environment properly, am I right?
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now