NotLDAP

  NotLDAP

Easy network wide authentication

This is a project developed by HimbeerserverDE.

The other day I was messing around with OpenLDAP and failed completely. That was a problem because Kerberos does not provide the features I need. So I decided to make my own software. It works by synchronizing the client's authentication files with the ones on the server. By the way, now my LDAP setup is working.

Current available version: 1.0

You can download the current version here.

Installing the server

1. Download the project and unpack it. Then open up a terminal and cd into the project folder's sub-directory "server". It's important that you don't run the installer as root.

2. In order for the installer to work, please enter: sudo apt update

3. Run the installer (not as root): ./installer.sh

4. When prompted, enter a password for the new system user "notldap". You will need it when setting up the clients.

5. The server installation should now be done. If it worked, then there will be some files in "/var/notldap/".

Installing a client

1. Download the project and unpack it. Then open up a terminal and cd into the project folder's sub-directory "client". It's important that you don't run the installer as root.

2. In order for the installer to work, please enter: sudo apt update

3. Run the installer (not as root): ./installer.sh

4. When prompted, enter the password for the notldap user.

5. To complete the setup, switch user to "notldap": sudo su notldap

6. Now that you are logged in as "notldap", run the following command: rsync -rav notldap@notldap-server:/tmp/ /tmp/

7. Type "exit".

8. Every client attempts to connect to the server with the hostname "notldap-server" by default. You can use a DNS server or the local hosts file to make it resolve to the correct IP address (IPv6 compatible).

9. Now you have to wait for up to one minute. If the installation was successful, some files will show up in "/var/notldap".

Changing authentication data

If you change the configuration of the server (users, groups, sudoers), the changes will be applied on the clients, too. You may need to relog on the client side to apply changes to your account if you are logged in on a client when the configuration updates.