The formal release of the Reopenldap 1.2.0 LDAP server, formed to resurrect the project after blocking its repository on GitHub. In April, GitHub deleted the accounts and repositories of many Russian developers related to companies that have fallen under the sanctions of the United States, including the ReopenLDAP repository. In connection with the revival of the interest of users in Reopenldap, the project decided to return to life.
Reopenldap project was created in 2014 to solve the problems that arose when using the OpenLDAP package in the Megafon PJSC infrastructure, where the LDAP server was involved in one of the infrastructure subsystems (NGDR is UDR (User Data Repository), according to the standard 3GPP 23.335, and is a centralized node for storing data on all types of subscribers in the IT infrastructure of the telecom operator). Such application involved industrial operation in 24 × 7 specific LDAP Catalog, the size of 10-100 million records, in a highly loaded scenario (10K updates and 50k readings per second) and in the topology of the multi-master.
Symas Corp, as the main developers, commiters and owners of the OpenLDAP code, could not solve the problems, so it was decided to try to do it on their own. As it later turned out, the code in the code was multiple more than one could assume. Therefore, more efforts were spent than planned, and Reopenldap still represents a certain value and (according to the available information) is the only LDAP server fully and reliably supporting the multi-master topology for RFC-4533, including in highly loaded scenarios.
In 2016, design goals were achieved, and support and development of the project directly in the interests of PJSC Megafon was completed. Then Reopenldap was actively developing and supported for another three years, but gradually it lost its meaning:
- Technologically “Megafon” migrated from Reopenldap on Tarantool, which is architecturally true;
- there were no clearly interested users Reopenldap;
- One of the developers did not join the project, both due to the high entry threshold and due to the low demand for Reopenldap;
- Development and support began to take too much time from the remaining (main) developer, as he professionally moved away from the industrial operation of Reopenldap.
Inactive state, the Reopenldap repository lasted until April 2022, when the GitHub administration without any warning and explanation deleted the related accounts and the repository itself. Recently, the author received several requests regarding Reopenldap, including the location of the repository and the condition of the code base. Therefore, it was decided to minimally refresh the project, form a technical release, and use this news to inform all interested.
The current state of the project, including relative to Openldap:
- Import of improvements and corrections from OpenLDAP has not been carried out since December 2018. For responsible applications, you need to analyze all the corrections to Openldap and import relevant.