ldapjs-riak is a full LDAP backend implementation for ldapjs and Riak. Using ldapjs-riak, you can easily stand up a highly available LDAP cluster. To get bootstrapped, the following code will give you a v3-compliant LDAP server that allows a user to make changes to their own entry, and any child entries (as an example):

var ldap = require('ldapjs');
var ldapRiak = require('ldapjs-riak');

var SUFFIX = 'o=example';

function authorize(req, res, next) {
  var bindDN = req.connection.ldap.bindDN;

  if (req.type === 'BindRequest' ||
      bindDN.parentOf(req.dn) ||
      bindDN.equals(req.dn))
    return next();

  return next(new ldap.InsufficientAccessRightsError());
}


var server = ldap.createServer();
var backend = ldapRiak.createBackend({
    "bucket": {
      "name": "ldapjs_riak",
    },
    "uniqueIndexBucket": {
      "name": ldapjs_ldapjs_riak",
    },
    "indexes": {
      "email": true,
      "uuid": true,
      "cn": false,
      "sn": false
    },
    "client": {
      "url": "http://localhost:8098",
      "clientId": "ldapjs_riak_1",
      "retry": {
        "retries": 3,
        "factor": 2,
        "minTimeout": 1000,
        "maxTimeout": 10000
      }
    }
});

server.bind('cn=root', function(req, res, next) {
  if (req.version !== 3)
    return next(new ldap.ProtocolError(req.version + ' is not v3'));

  if (req.credentials !== 'secret')
    return next(new ldap.InvalidCredentialsError(req.dn.toString()));

  res.end();
  return next();
});

server.add(SUFFIX, backend, authorize, backend.add());
server.modify(SUFFIX, backend, authorize, backend.modify());
server.bind(SUFFIX, backend, authorize, backend.bind());
server.compare(SUFFIX, backend, authorize, backend.compare());
server.del(SUFFIX, backend, authorize, backend.del());
server.modifyDN(SUFFIX, backend, authorize, backend.modifyDN());
server.search(SUFFIX, backend, authorize, backend.search());

server.listen(1389, function() {
  console.log('ldap-riak listening at: %s', server.url);
});

Note that ldapjs-riak requires Riak 1.0 with the eleveldb_backend, as it makes heavy use of Riak's secondary indexing feature. Once you have a Riak instance running, and are running that code, try:

ldapadd -x -D cn=root -w secret -H ldap://localhost:1389 -f data.ldif

Where data.ldif has:

dn: o=example
o: example
objectclass: organization

dn: email=nobody@acme.com, o=example
cn: Sample
sn: User
email: nobody@acme.com
userpassword: secret2
objectclass: person

Now you can try searching as the child user:

ldapsearch -x -D email=nobody@acme.com,o=example -w secret2 -H ldap://localhost:1389 -b email=nobody@acme.com,o=example email=*

All of the standard LDAP operations:

• Add
• Bind
• Compare
• Delete
• Modify
• ModifyDN
• Search

are supported by the Riak backend. In addition, it supports an "almost" compliant changelog implementation (there are a few differences, like instead of storing changes in LDIF, they are stored in JSON).