Installation of RCDevs Directory Server System requirements:
RCDevs Directory Server (DS) runs on Linux with GLIBC ≥ 2.5. The package contains the required dependencies allowing DS to run on any Linux system without other requirements.
1. Install DS 1.1 Using the Repository 1.1.1 CentOS/RHEL On a RedHat, CentOS or Fedora system, you can use our repository, which simplifies updates.
Add the repository:
[root@ldap ~]# yum install https://repos.rcdevs.com/redhat/base/rcdevs_release-1.1.1-1.noarch.rpm Clean yum cache:
1. Overview This guide intends to explain how to install and configure WebADM in docker containers.
The following items will be covered:
Slapd MariaDB WebADM WAProxy 2. Before you start All steps were tested in CentOS 7/CentOS 8 and docker version 19. But it should work in any system running a modern version of docker.
In this guide, I assume you already have a working docker installation. In case you need help to setup a docker environment, you can check the docker website documentation.
1. Overview Generally, WebADM is configured to connect with a remote AD/LDAP domain for two reasons:
For an admin to be able to browse (and optionally modify) remote domain contents such as user objects via a web browser (and optionally delegate that work to sub-administrators).
To act as a gateway to allow the OpenOTP server to read and use remote user data for authentication purposes (i.e. fetch user mobile phone number from AD account).
Test Double Authentication with a User 1. User Activation Once WebADM is installed and configured, we can connect to it with a web browser.
We select the user to activate in the LDAP tree on the left, for example, Admin, or we create a new user by clicking on Create. Once the user is selected, we click on Activate Now!:
If present, we fill mandatory attributes and Proceed:
We click on Extend Object:
1. Product Overview The main use-case of OpenOTP LDAP Bridge is enabling enterprise applications that use LDAP as an external authentication mechanism to work with OpenOTP. LDAP Bridge allows authentication to be delegated to an OpenOTP server transparently, without changing the LDAP back-end. From the client applications perspective, the main change is that it will use the LDAP Bridge as an LDAP server, instead of the backend-end LDAP server.