{"id":105051,"date":"2022-09-08T21:36:41","date_gmt":"2022-09-08T19:36:41","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/reliz-ldap-servera-reopenldap-1-2-0"},"modified":"2022-09-08T21:36:41","modified_gmt":"2022-09-08T19:36:41","slug":"reliz-ldap-servera-reopenldap-1-2-0","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/reliz-ldap-servera-reopenldap-1-2-0","title":{"rendered":"Release of the LDAP server ReOpenLDAP 1.2.0.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
The formal release of the ReOpenLDAP LDAP server version 1.2.0 has been published, aimed at reviving the project after its repository on GitHub was blocked. In April, GitHub deleted the accounts and repositories of many Russian developers linked to companies that fell under U.S. sanctions, including the ReOpenLDAP repository. Due to the renewed interest of users in ReOpenLDAP, the project has been decided to be revived. <\/p>\n
The ReOpenLDAP project was created in 2014 to address issues encountered when using the OpenLDAP package in the infrastructure of PJSC \"MegaFon\", where the LDAP server was utilized in one of the infrastructure subsystems (NGDR represents a UDR (User Data Repository), according to the 3GPP 23.335 standard, and serves as a centralized node for storing data on all types of subscriber services in the IT infrastructure of the telecommunications operator). Such an application suggested industrial operation in a 24\u00d77 mode of a specific LDAP catalog with a size of 10-100 million records, under a high-load scenario (10K updates and 50K reads per second) and in a multi-master topology. <\/p>\n
Symas Corp, as the primary developers, committers, and owners of the OpenLDAP code, were unable to resolve the existing issues, so it was decided to attempt to tackle it independently. As it turned out, there were significantly more errors in the code than could have been presumed. Therefore, more effort was required than initially planned, and ReOpenLDAP still holds certain value and (according to available information) is the only LDAP server that fully and reliably supports multi-master topology for RFC-4533, including in high-load scenarios. <\/p>\n
By 2016, the project goals were achieved, and support and development of the project directly in the interests of PJSC \"MegaFon\" was concluded. Subsequently, ReOpenLDAP continued to evolve and be maintained for another three years, but gradually this became less meaningful: <\/p>\n
\n
Technologically, \"MegaFon\" migrated from ReOpenLDAP to Tarantool, which is architecturally correct;\n
There were no clearly interested users of ReOpenLDAP;\n
No developers joined the project, both due to a high entry barrier and low demand for ReOpenLDAP itself;\n
The development and maintenance have taken too much time from the remaining (main) developer, as he has professionally distanced himself from the industrial operation of ReOpenLDAP. <\/ul>\n
In an inactive state, the ReOpenLDAP repository lasted until April 2022, when GitHub administration deleted associated accounts and the repository itself without any warnings or explanations. Recently, the author received several inquiries about ReOpenLDAP, including the location of the repository and the state of the codebase. Therefore, it was decided to minimally refresh the project, create a technical release, and use this news to inform all interested parties. <\/p>\n
Current project status, including regarding OpenLDAP: <\/p>\n
\n
Imports of improvements and fixes from OpenLDAP have not been conducted since December 2018. For responsible applications, all corrections in OpenLDAP need to be analyzed and relevant ones imported.\n
Current versions of OpenLDAP are now being formed based on the 2.5 branch. Therefore, the improvements described below were made only in the \"devel\" branch (corresponding to OpenLDAP 2.5), and then merged into the \"master\" (which corresponded to OpenLDAP 2.4 prior to merging).\n