In the last ten years or so, directory services flourished to address identity management issues. Web Applications, operating systems, authentication servers or appliances are common examples of LDAP enabled clients of those services. And historical or organizational reasons (like acquisitions) are often at the source of LDAP repositories multiplication. Without failure, it sometimes leaded to complex architectures or synchronization processes. Or even no synchronization at all. Also, costs of ownership increased as IT departments saw directories grow like mushrooms. That's why one of the next trend was to design and build a unique directory, where it made sense. To further leverage its usage, some organizations developed at the same time a specific business layer to offer business applications a unique LDAP access layer. But this layer doesn't necessarily covers the whole needs. Mobile devices or external (cloud) applications like portals usually don't fit in this model. That's why deploying a more modern access interface to the LDAP service makes senses for some businesses at least. And guess what ? Json2LDAP proposes such a solution. As a web application, it can rely on an underlying application server for fault tolerance and load balancing, as well as common operations (monitoring, deployment, ..)