Json2Ldap

<h2 id="background">Background</h2>
<p>Json2Ldap was initially conceived as a lightweight <a href="/facts/JSON/bs1rUAhd">JSON</a> alternative to existing <a href="/facts/Directory_Service_Markup_Language/x4uzqPsT">XML-based</a> gateways for providing <a href="/facts/Directory_service/6fsVdntu">directory service</a> access to <a href="/facts/Web_browser/2pfyymLs">web browsers</a>. Its first official release was in May 2010.<a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a> In May 2011 development of the software was passed to Nimbus Directory Services.<a class="footnote-ref" id="fnref:5" href="#fn:5"><sup>5</sup></a>
</p>
<h2 id="interface-specification">Interface specification</h2>
<p>Json2Ldap provides a <a href="/facts/JSON/bs1rUAhd">JSON</a> web interface for establishing <a href="/facts/LDAP/KgpfD8nR">LDAP</a> client connections to one or more <a href="/facts/Directory_server/6fsVdntu">directory servers</a>.
</p><p>Client web interface:
</p>
<ul><li>Version 2.0 of the <a href="/facts/JSON-RPC/v2yyqEob">JSON-RPC</a> protocol.</li>
<li>Requests are accepted over <a href="/facts/HTTP/TWtvf7JD">HTTP</a> POST.</li>
<li>Optional support for <a href="/facts/Cross-Origin_Resource_Sharing/oXGvyzQc">Cross-Origin Resource Sharing</a> (CORS) requests.</li></ul>
<p>Supported standard <a href="/facts/LDAP/KgpfD8nR">LDAP</a> directory operations (as per RFC 4510):
</p>
<ul><li>Bind (authenticate): simple, <a href="/facts/Simple_Authentication_and_Security_Layer/4z9w1bx6">plain SASL</a>, <a href="/facts/Simple_Authentication_and_Security_Layer/4z9w1bx6">digest MD5 SASL</a>, anonymous</li>
<li>Search</li>
<li>Compare</li>
<li>Add a new entry</li>
<li>Delete an entry</li>
<li>Modify an entry</li>
<li>Modify distinguished name (DN)</li>
<li>Unbind</li></ul>
<p>Supported extended <a href="/facts/LDAP/KgpfD8nR">LDAP</a> operations:
</p>
<ul><li>Password Modify (RFC 3062)</li>
<li>StartTLS (RFC 4511)</li>
<li>Who am I (RFC 4532)</li></ul>
<p>Supported extended LDAP controls:
</p>
<ul><li>Authorisation identity bind control (RFC 3829).</li>
<li>Server-side sorting of search results (RFC 2891).</li>
<li>Simple paged results (RFC 2696).</li>
<li>Virtual-list-view search control (draft-ietf-ldapext-ldapv3-vlv-09)</li>
<li>Sub-tree delete (draft-armijo-ldap-treedelete-02).</li></ul>
<p>Non-standard extensions:
</p>
<ul><li><a href="/facts/Secure_Remote_Password_protocol/xznfeN8v">Secure Remote Password protocol</a> (SRP-6a) authentication.</li></ul>
<h2 id="example-messages">Example messages</h2>
<h3>Example request message</h3>
<p>Example directory search request:
</p>
{ 
  "method"  : "ldap.search",
  "params"  : { "CID" : "096032ca-ca91-47eb-a366-143832ff4a26",
                "baseDN" : "ou=people,dc=my,dc=org",
	        "scope"  : "SUB",
		"filter" : "(givenName=Alice)" },
  "id"      : "0001",
  "jsonrpc" : "2.0" 
}

<h3>Example response message</h3>
<p>Example directory search response:
</p>
{ 
  "result"  : { "objectClass" : [ "top", "person", "inetOrgPerson" ],
                "uid"         : [ "alice" ],
		"mail"        : [ "alice@wonderland.net" ],
		"sn"          : [ "Kingsleigh" ],
		"cn"          : [ "Alice Kingsleigh" ],
		"initials"    : [ "AK" ],
		"mobile"      : [ "+44 755 123 456" ] },
  "id"      : "0001",
  "jsonrpc" : "2.0"
}

<h2 id="system-requirements">System requirements</h2>
<p>Json2Ldap is distributed as a <a href="/facts/Java_(software_platform)/fpn6x8WL">Java</a> <a href="/facts/Web_application_archive/KohLDBAw">web application archive</a> (WAR) for deployment in a Java <a href="/facts/Servlet_container/Pv06YKvB">servlet container</a>.<a class="footnote-ref" id="fnref:6" href="#fn:6"><sup>6</sup></a>
</p>
<h2 id="see-also">See also</h2>
<ul><li><a href="/facts/JSON-RPC/v2yyqEob">JSON-RPC</a></li>
<li><a href="/facts/List_of_LDAP_software/6paE8q0B">List of LDAP software</a></li></ul>

<h2 id="references">References</h2>

<ol>
<li id="fn:1"><p>"Announcement of Nimbus Directory Services taking over Json2Ldap development". Archived from the original on 2012-03-28. Retrieved 2011-08-04. <a href="https://web.archive.org/web/20120328125719/http://blog.dzhuvinov.com/?p=791" target="_blank">https://web.archive.org/web/20120328125719/http://blog.dzhuvinov.com/?p=791</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li>
<li id="fn:2"><p>"Network World, Security Identity Management Alert, 2010-07-20". 20 July 2010. <a href="http://www.networkworld.com/newsletters/2010/071910id2.html" target="_blank">http://www.networkworld.com/newsletters/2010/071910id2.html</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li>
<li id="fn:3"><p>"Json2Ldap web API". <a href="http://connect2id.com/products/json2ldap/web-api" target="_blank">http://connect2id.com/products/json2ldap/web-api</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li>
<li id="fn:4"><p>"Give your LDAP server a JSON front-end". Archived from the original on 2012-03-28. Retrieved 2011-08-04. <a href="https://web.archive.org/web/20120328125751/http://blog.dzhuvinov.com/?p=96" target="_blank">https://web.archive.org/web/20120328125751/http://blog.dzhuvinov.com/?p=96</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li>
<li id="fn:5"><p>"Announcement of Nimbus Directory Services taking over Json2Ldap development". Archived from the original on 2012-03-28. Retrieved 2011-08-04. <a href="https://web.archive.org/web/20120328125719/http://blog.dzhuvinov.com/?p=791" target="_blank">https://web.archive.org/web/20120328125719/http://blog.dzhuvinov.com/?p=791</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li>
<li id="fn:6"><p>"Json2Ldap system requirements". <a href="http://connect2id.com/products/json2ldap/datasheet" target="_blank">http://connect2id.com/products/json2ldap/datasheet</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></p></li>
</ol>

Json2Ldap open-in-new

Json2Ldap