OpenDJ
OpenDJ is a directory server which implements a wide range of Lightweight Directory Access Protocol and related standards, including full compliance with LDAPv3 but also support for Directory Service Markup Language (DSMLv2).[2] Written in Java, OpenDJ offers multi-master replication, access control, and many extensions. OpenDJ began as a fork of OpenDS, an LDAP / DSML server which originated in 2005 as an internal project at Sun Microsystems started by Neil A. Wilson, and later grew into an open source project, maintained by Oracle Corporation;[3] following Oracle's acquisition of Sun, OpenDJ is the main trunk developed by ForgeRock.[4] and maintained by Open Identity Platform Community.[5] OpenDJ source code[6] and binary distribution[7] are available under the Common Development and Distribution License (CDDL).[8] HistoryThe work on OpenDS started as an internal Sun project around February 2005. OpenDS was initially developed primarily by Neil A. Wilson. Wilson was joined by a small team of engineers from Sun's Directory Server team. The code was open-sourced in June 2006. Sun increased the number of developers working on OpenDS technology after open-sourcing the code. Developers outside Sun also joined the new open-source project. Community members like Boni.org, Penrose, and JBoss began to use OpenDS in their projects. In early 2008 the OpenDS project had over 20 regular contributors. In April 2007, the project owners modified the project governance. The text "This Project Lead, who is appointed by Sun Microsystems, is responsible for managing the entire project" was replaced by "This Project Lead, who is appointed and removed by a majority vote of the Project Owners, is responsible for managing the entire project". In September 2007, the project owners were laid off from Sun Microsystems. Late in 2007, questions arose as to whether the project was governed as an open source project. One of the project owners complained publicly that Sun Microsystems had required project owners to accept governance changes to the project in order to keep their benefits.[9] The team resigned from their project owner role. Simon Phipps, Chief Open source Officer of Sun Microsystems, claimed that Sun was only reverting governance changes that had never been approved. John Waters also published an article on the topic.[10] OpenDJ began after the acquisition of Sun Microsystems by Oracle. At that time, Oracle announced that Sun OpenDS Standard Edition was not seen as a strategic product,[11] although the investment on the OpenDS source code would continue. Sun had supported commercial versions of Sun OpenDS Standard Edition since version 1.0 in 2008. Mid-September 2010, Ludovic Poitou, then OpenDS community leader and co-project owner, left Oracle for ForgeRock.[12] In October 2010, Oracle provided an OpenDS 2.2.1 update to the community with several fixes.[13] In December 2010, ForgeRock released OpenDJ 2.4.0 including fixes and support for new features like Collective Attributes, Microsoft Active Directory Permissive Modification Control, and multiple objectclass inheritance.[14] In late January 2011 Matthew Swift, previously "responsible for the core server" of the OpenDS project joined ForgeRock to work on OpenDJ as product architect.[15] Starting in mid-February 2011, ForgeRock began to build an "OpenDJ product suite, comprising an open source LDAP Directory Server, client tools, and LDAP SDK" as a Maven project,[16] with the tools and SDK modules appearing first. In 2011, a few months after the acquisition of Sun Microsystems, Oracle released Oracle Unified Directory, based on OpenDS. ForgeRock posted an OpenDJ roadmap through release 4, targeted for 2015.[17] Since November 2016, ForgeRock closed OpenDJ source code, renamed OpenDJ to Forgerock Directory Services and started to distribute it under commercial license.[18]
OpenDJ 2.4, released December 2010, provided improvements corresponding to many of those defined, but not yet scheduled for OpenDS 2.4[26] OpenDJ 2.6, released June 2013, provided a REST to LDAP interface allowing easy and secure access to the data, also eased integration with other services, provided native packages for Linux, and the LDAP client SDK. The latest Forgerock release of OpenDJ is 3.0.0.[27] OpenDJ 3.0 is expected to include directory proxy services, but the support for LDAP Transactions that was originally planned was dropped due to the incompatibility with the loose consistency model of LDAP. OpenDJ 3.1 and 3.2 are slated to include enhanced directory proxy services. OpenDJ 4.1.4 resumed to maintain by Open Identity Platform Community[28] and issued new release:[29] See alsoReferences
External links
|