david.pillant@hraccess.com David Pillant 2008-10-15 en ApacheDS 1.5.4 23 The Apache License 2.0 http://directory.apache.org/ 1.7 LDAP

Generic criteria from QSOS version 1.6 Intrinsic durability Maturity less than 3 months if between 3 months and 3 years after 3 years 2 September 2003 Unstable software with numerous releases or patches generating side effects Stabilized production release existing but old. Difficulties to stabilize development releases Stabilized software. Releases provide bug fixes corrections but mainly new functionalities 2 Software knows several problems which can be prohibitive No know major problem or crisis History of good management of crisis situations 2 only on issue reopened 72% closed Software is very likely to be forked in the future Software comes from a fork but has very few chances of being forked in the future Software has very little chance of being forked. It does not come from a fork either 2 Adoption by community and industry Very few users identified Detectable use on Internet Numerous users, numerous references 0 None Few refences, non critical usages Often implemented for critical applications 0 No community or without real activity (forum, mailing list, ...) Existing community with a notable activity Strong community: big activity on forums, numerous contributors and advocates 2 http://directory.apache.org/community%26resources/the-team.html No book about the software Less than 5 books about the software are available More than 5 books about software are available, in several languages 0 Organisation and leadership of developments 1 to 2 individuals involved, not clearly identified Between 2 and 5 independent people More than 5 people 2 http://directory.apache.org/community%26resources/the-team.html Complete dictatorship Enlightened despotism Council of architects with identified leader (e.g: KDE) 2 http://directory.apache.org/community%26resources/the-team.html Activity of the project and around the software Less than 3 developers, not clearly identified Between 4 and 7 developers, or more unidentified developers with important turnover More than 7 developers, very stable team 2 http://directory.apache.org/community%26resources/the-team.html Slow reactivity in forum or on mailing list, or nothing regarding bug fixes in releases note Detectable activity but without process clearly exposed, long reaction/resolution time Strong reactivity based on roles and tasks assignment 2 http://issues.apache.org/jira/browse/DIRSERVER No or few new functionalities Evolution of the product driven by the core team or by user's request without any clearly explained process Tool(s) to manage feature requests, strong interaction with roadmap 2 http://issues.apache.org/jira/browse/DIRSERVER?report=com.atlassian.jira.plugin.system.project:roadmap-panel Very weak activity on both production and development releases Activity on production and development releases. Frequent minor releases (bug fixes) Important activity with frequent minor releases (bugs fixes) and planned major releases relating to the roadmap forcast 2 http://issues.apache.org/jira/browse/DIRSERVER?report=com.sourcelabs.jira.plugin.portlet.releases:releases-projecttab Industrialization level of the project Developments realized at 100% by employees of a single company 60% maximum 20% maximum 2 Services offering No offer of training identified Offer exists but is restricted geographically and to one language or is provided by a single contractor Rich offers provided by several contractors, in several languages and split into modules of gradual levels 1 No offer of support except via public forums and mailing lists Offer exists but is provided by a single contractor without strong commitment quality of services Multiple service providers with strong commitment (e.g: guaranteed resolution time) 0 No offer of consulting service Offer exists but is restricted geographically and to one language or is provided by a single contractor Consulting services provided by different contractors in several languages 0 No user documentation Documentation exists but shifted in time, is restricted to one language or is poorly detailed Documentation always up to date, translated and possibly adapted to different target readers (end user, sysadmin, manager, ...) 1 Quality assurance process No QA process Identifies QA process but not much formalized and with no tool Automatic testing process included in code's life-cycle with publication of results 2 http://issues.apache.org/jira/browse/DIRSERVER?report=com.atlassian.jira.plugin.system.project:openissues-panel No bug or feature request management tool Standard tools provided (for instance by a hosting forge) but poorly used Very active use of tools for roles/tasks allocation and progress monitoring 2 http://issues.apache.org/jira/browse/DIRSERVER?report=com.atlassian.jira.plugin.system.project:openissues-panel Packaging for various operating systems Software can't be installed from source without lot of work Installation from source is limited and depends on very strict conditions (OS, arch, lib, ...) Installation from source is easy 2 http://directory.apache.org/community%26resources/sources.html The software is not packaged for Debian A Debian package exists but it has important issues or it doesn't have official support The software is packaged in the distribution 2 The software is not packaged for FreeBSD A port exists but it has important issues or it doesn't have official support A official port exists in FreeBSD 0 The software is not packaged for HP-UX A package exists but it has important issues or it doesn't have official support A stable package is provided for HP-UX 0 The software is not packaged for MacOSX A package exists but it has important issues or it doesn't have official support The software is packaged in the distribution 2 The software is not packaged for Mandriva A package exists but it has important issues or it doesn't have official support The software is packaged in the distribution 0 The software is not packaged for NetBSD A port exists but it has important issues or it doesn't have official support A official port exists in NetBSD 0 The software is not packaged for OpenBSD A port exists but it has important issues or it doesn't have official support A official port exists in OpenBSD 0 The software is not packaged for RedHat/Fedora A package exists but it has important issues or it doesn't have official support The software is packaged in the distribution 2 The software is not packaged for Solaris A package exists but it has important issues or it doesn't have official support (e.g: SunFreeware.com ) The software is supported by Sun for Solaris 2 The software is not packaged for SuSE A package exists but it has important issues or it doesn't have official support The software is packaged in the distribution 0 The project can't be installed on Windows A package exists but it is limited or has important issues or just cover some specific Windows release (e.g: Windows2000 and WindowsXP) Windows is full supported and a package is provided 2 Exploitability level Difficult to use, requires an in depth knowledge of the software functionality Austere and very technical ergonomics GUI including help functions and elaborated ergonomics 1 No administrative or monitoring functionalities Existing, functionalities but incomplete and or need improvement Complete and easy-to-use administration and monitoring functionalities. Possible integration with external tools (e.g: SNMP, syslog, ...) 1 no administration and monitoring consoles Technical adaptability Monolithic software Presence of hight level modules allowing a first level of software adaptation Modular conception, allowing easy adaptation of the software by selecting or creating modules 2 Everything by hand Recompilation possible but complex without any tools or documentation Recompilation with tools (e.g: make, ANT, ...) and documentation provided 2 Any modification requires code recompilation Architecture designed for static extension but requires recompilation Principle of plugin, architecture designed for dynamic extension without recompilation 2 Project's strategy License Very strict license, like GPL Moderate permissive license located between both extremes (GPL and BSD) dual-licensing depending on the type of user (person, company, ...) or their activities Very permissive like BSD or Apache licenses 2 Apache v2.0 Very permissive like BSD or Apache licenses Moderate permissive license located between both extremes (GPL and BSD), dual-licensing depending on the type of user (person, company, ...) or their activies Very strict license, like GPL 0 Apache v2.0 Rights held by a few individuals or entities, making it easier to change the license Rights held by numerous individuals owning the code in a homogeneous way, making relicense very difficult Rights held by a legal entity in whom the community trusts (e.g: FSF or ASF) 2 Apache Software Foundation No practical way to propose code modification Tools provided to access and modify code (like CVS or SVN) but not really used to develop the software The code modification process is well defined, exposed and respected, based on roles assignment 2 http://directory.apache.org/community%26resources/the-team.html No published roadmap Existing roadmap without planning Versionned roadmap, with planning and measure of delays 2 http://cwiki.apache.org/confluence/display/DIRxPMGT/2.0+Roadmap Software has no sponsor, the core team is not paid Software has an unique sponsor who might determine its strategy Software is sponsored by industry 2 Google, microsoft, yahoo, hp,etc... No detectable strategy or strong dependency on one unique actor(person, company,sponsor) Strategic vision shared with several other free and open source projects but without strong commitment from copyrights owners Strong independence of the code team, legal entity holding rights, strong involvement in the standardization process 2

Does the LDAP server implement the RFC 4510? (Lightweight Directory Access Protocol (LDAP) Technical Specification Roadmap) Not implemented Partially implemented Fully implemented 2 http://cwiki.apache.org/confluence/download/attachments/31742/ApacheCon2006-ADS.pdf?version=1 Does the LDAP server implement the RFC 4511? (The Protocol) Not implemented Partially implemented Fully implemented 2 http://cwiki.apache.org/confluence/display/DIRxSRVx11/Supported+RFCs Does the LDAP server implement the RFC 4512? ( Directory Information Models) Not implemented Partially implemented Fully implemented 2 http://cwiki.apache.org/confluence/display/DIRxSRVx11/Supported+RFCs Does the LDAP server implement the RFC 4513? (Authentication Methods and Security Mechanisms) Not implemented Partially implemented Fully implemented 2 http://cwiki.apache.org/confluence/display/DIRxSRVx11/Supported+RFCs Does the LDAP server implement the RFC 4514? (String Representation of Distinguished Names) Not implemented Partially implemented Fully implemented 2 http://cwiki.apache.org/confluence/display/DIRxSRVx11/Supported+RFCs Does the LDAP server implement the RFC 4515? (String Representation of Search Filters) Not implemented Partially implemented Fully implemented 2 http://cwiki.apache.org/confluence/display/DIRxSRVx11/Supported+RFCs Does the LDAP server implement the RFC 4516? (Uniform Resource Locator) Not implemented Partially implemented Fully implemented 2 http://cwiki.apache.org/confluence/display/DIRxSRVx11/Supported+RFCs Does the LDAP server implement the RFC 4517? (Syntaxes and Matching Rules) Not implemented Partially implemented Fully implemented 2 http://cwiki.apache.org/confluence/display/DIRxSRVx11/Supported+RFCs Does the LDAP server implement the RFC 4518? ( Internationalized String Preparation) Not implemented Partially implemented Fully implemented 2 http://cwiki.apache.org/confluence/display/DIRxSRVx11/Supported+RFCs Does the LDAP server implement the RFC 4519? (Schema for User Applications) Not implemented Partially implemented Fully implemented 2 http://cwiki.apache.org/confluence/display/DIRxSRVx11/Supported+RFCs Does the LDAP server implement the RFC 4520? (Internet Assigned Numbers Authority (IANA) Considerations for the Lightweight Directory Access Protocol (LDAP)) Not implemented Partially implemented Fully implemented 0 Does the LDAP server implement the RFC 4521? (Considerations for Lightweight Directory Access Protocol (LDAP) Extensions) Not implemented Partially implemented Fully implemented 0 Does the LDAP server implement the RFC 2247? (Use of DNS domains in distinguished names) Not implemented Partially implemented Fully implemented 1 Supported Does the LDAP server implement the RFC 2307? (Using LDAP as a Network Information Service) Not implemented Partially implemented Fully implemented 1 Supported Does the LDAP server implement the RFC 2589? (Dynamic Directory Services Extensions) Not implemented Partially implemented Fully implemented 2 Does the LDAP server implement the RFC 2798? (inetOrgPerson LDAP Object Class) Not implemented Partially implemented Fully implemented 2 Does the LDAP server implement the RFC 2849? (The LDAP Data Interchange Format (LDIF)) Not implemented Partially implemented Fully implemented 2 Does the LDAP server implement the RFC 3062? ( LDAP Password Modify Extended Operation) Not implemented Partially implemented Fully implemented 1 Supported Does the LDAP server implement the RFC 3296? (Named Subordinate References in LDAP Directories) Not implemented Partially implemented Fully implemented 2 Does the LDAP server implement the RFC 3671? (Collective Attributes in LDAP) Not implemented Partially implemented Fully implemented 2 Does the LDAP server implement the RFC 3672? (Subentries in LDAP) Not implemented Partially implemented Fully implemented 2 Does the LDAP server implement the RFC 3687? (LDAP Component Matching Rules) Not implemented Partially implemented Fully implemented 1 Supported Does the LDAP server implement the RFC 3698? (LDAP: Additional Matching Rules) Not implemented Partially implemented Fully implemented 1 Supported Does the LDAP server implement the RFC 3829? (LDAP Authorization Identity Controls) Not implemented Partially implemented Fully implemented 1 Supported Does the LDAP server implement the RFC 3909? (LDAP Cancel Operation) Not implemented Partially implemented Fully implemented 1 Supported Does the LDAP server implement the RFC 3928? (LDAP Client Update Protocol) Not implemented Partially implemented Fully implemented 1 Supported Does the LDAP server implement the RFC 4370? (LDAP Proxied Authorization Control) Not implemented Partially implemented Fully implemented 0 Does the LDAP server implement the RFC 4522? (LDAP: Binary Encoding Option) Not implemented Partially implemented Fully implemented 1 Supported Does the LDAP server implement the RFC 4523? (LDAP: X.509 Certificate Schema) Not implemented Partially implemented Fully implemented 1 Supported Does the LDAP server implement the RFC 4524? (LDAP: COSINE Schema) Not implemented Partially implemented Fully implemented 1 Supported Does the LDAP server implement the RFC 4525? (LDAP: Modify-Increment Extension) Not implemented Partially implemented Fully implemented 1 Supported Does the LDAP server implement the RFC 4526? (LDAP: Absolute True and False Filters) Not implemented Partially implemented Fully implemented 1 Supported Does the LDAP server implement the RFC 2247? Not implemented Partially implemented Fully implemented 2 Does the LDAP server implement the RFC 4527? (LDAP: Read Entry Controls) Not implemented Partially implemented Fully implemented 1 Supported Does the LDAP server implement the RFC 4533? (LDAP Content Sync Operation) Not implemented Partially implemented Fully implemented 1 Supported Does the LDAP server implement the RFC 4422? (Simple Authentication and Security Layer (SASL)) Not implemented Partially implemented Fully implemented 2 Does the LDAP server implement the RFC 4752? (The Kerberos V5 ("GSSAPI") Simple Authentication and Security Layer (SASL) Mechanism) Not implemented Partially implemented Fully implemented 2 Does the LDAP server implement the Draft behera? (Password policy for LDAP directories) Not implemented Partially implemented Fully implemented 0 Future version (1.5.6) No thread pooling support Thread pooling is partial or doesn't work correctly Thread pooling is performing 2 No proxy cache support Proxy cache is partial or doesn't work correctly Proxy cache is performing 2 WebSphere is not supported WebSphere support documented but not tested Fully WebSphere support 2 http://chintanrajyaguru.com/blog/tech/apache-ds-and-was-6.1-installing-and-configuring-apache-ds.html Tomcat is not supported Tomcat support documented but not tested Fully Tomcat support 2 http://www.screaming-penguin.com/node/5677 JBoss is not supported JBoss support documented but not tested Fully JBoss support 2 Weblogic is not supported Weblogic support documented but not tested Fully Weblogic support 2 Geronimo is not supported Geronimo support documented but not tested Fully Geronimo support 2 http://cwiki.apache.org/GMOxDOC11/ldap-realm.html JOnas is not supported JOnas support documented but not tested Fully JOnas support 2 No Load balancing/Failover support Load balancing/Failover is partial or doesn't work correctly Load balancing/Failover is performing 0 future version 1.6 No SSL support Partial SSL support Fully SSL support and integration 2 http://directory.apache.org/apacheds/1.5/start-tls-with-apacheds.html No transactional support Partial transactional support Full transactional support 0 No SASL support Partial SASL support Full SASL support 2 http://directory.apache.org/apacheds/1.5/howto-do-sasl-gssapi-authentication-to-apacheds.html No database support Default database support Database can be changed 2 The software is not packaged for RedHat A package exists but it has important issues or it doesn't have official support The software is packaged in the distribution 2

No console of administration is available Limited and incomplete administration console Complete administration console 0 No available script to administrate the server Some scripts are available (start, stop, update, import/export...) Available language to write powerful scripts 1 Some attributes required but not in RFC Pre-requisites of management password in HR No encrypted password option Encrypted password option is documented but not tested Encrypted password option is available 2 No Management of 11 previous passwords option Management of 11 previous passwords option is documented but not tested Management of 25 previous passwords is available 0 Future version (1.5.6) No Wrong password counter option Wrong password counter option is documented but not tested Wrong password counter option is available 0 Future version (1.5.6) No configuration of the password template Some rules are implemented All rules are implemented 0 No Locked attribute option Locked attribute option is documented but not tested Locked attribute option is available 0 Future version (1.5.6) No First connection option First connection option is documented but not tested First connection option is available 0 Future version (1.5.6) Don't generate any monitoring file Monitoring file generation doesn't work correctly Many options are available to define monitoring 2 Use external tools No IDE supported Limited IDE integration An IDE is delivered with LDAP server 2 Apache Directory Studio No Identity management solution available with this LDAP server Possible integration with external Identity management solution LDAP Server is delivered with an identity management solution 2 TripleSec Slice model integration No port management Some ports are configurable All ports are configurable 1 http://directory.apache.org/apacheds/1.5/service-configuration.html Standard installation available Configurable installation available Powerful installation and architecture available 1