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

I am running 10 Linux machines that is doing different types of work. The machines are configured to use LDAP authentication so when one user is configured in slapd he can login on all the machines. To make maintenance easier i want to create a root account in slapd so i can use this instead of the local root accounts when installing applications etc. but i am not sure on how to do this. Is it enough to create a user with the name root and gid/uid 0? should the local root be disabled somehow?

I am fully aware that this is normally not a good idea from a security perspective, but as mentioned before this is a special case.

share|improve this question
up vote 2 down vote accepted

Having a UID=0/GID=0 account should be sufficient.

Leave the local root user account alone, as if something happens to the LDAP server or the network you'll want "emergency access". Also, I would recommend that the LDAP server itself not be dependent on LDAP for authentication (chicken-and-egg situations).

Make sure you're using SSL/TLS as well.

I would also strongly recommend against doing this.

share|improve this answer

Use sudo instead of a root account in LDAP. That'll also give you logging of what they did as root.

And +1 on using puppet to manage the servers and have puppet maintain the local copies of /etc/sudoers on all of your servers.

share|improve this answer

With 10 servers I would look into setting up Puppet and use it manage the applications and configurations.

This is much less error prone and creates repeatable configurations.

share|improve this answer

Your Answer


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