Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

As a follow-up to my previous question, which I've resolved part of, what we're trying to do now is take an exported .ldif file of the "Users" container on our OS X Server and import it into a separate OpenLDAP server on an EC2 instance. This we'll use for LDAP user authentication of other apps without having to open our internal network to LDAP traffic.

The exported .ldif file thinks the DN of the "Users" container is cn=users,dc=server,dc=domain,dc=com. Is it easiest to configure the EC2 OpenLDAP server to think that it's domain is the same so the container is imported to the proper place? Or should we edit the text of the .ldif file to change the DN to match the external naming?

Hopefully that makes sense... but I'm confused as to the best way to accomplish this.

share|improve this question
up vote 0 down vote accepted

Just do a find and replace on the LDIF file to change the DN to match the external naming.

share|improve this answer
Of course, be sure to backup the LDAP before doing this in case you need to restore. – user31775 Jan 15 '10 at 16:05
A great tool to use for this stuff is Apache Directory Studio. – user31775 Jan 15 '10 at 16:07

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.