Open Source LDAP Virtual Directory

Applications need to know who users are and what permissions they have. While most enterprises have some form of an LDAP directory and most applications support LDAP there is generally a gap between what an enterprise has and what an application can integrate with. Some common issues a virtual directory can solve are:


myvd_web_multi_forestMultiple Active Directory Forests

Since Microsoft debuted Active Directory enterprises have used it to segregate users either be geography, internal division or business unit but few applications know how to talk to multiple directories.  MyVirtualDirectory can combine these directories in real time, without any data synchronization to create one single view of the Active Directory infrastructure.





mivd_web_au_to_azStore Authentication and Authorization in Separate Directories

The people who own your enterprise’s directory aren’t generally responsible for your application. Getting groups and authorizations into the enterprise directory isn’t their priority. Using MyVirtualDirectory you can control authorizations without involving the owners of the enterprise directory keeping you in control of your application.

The same is true of applications that require additional attributes.  IF your application requires additional attributes that can’t be provided directly you don’t want to have to involve your enterprise directory team.  Changes to enterprise schemas can be difficult and time consuming both from a technical and organizational standpoint.

A virtual directory can be used for nearly any LDAP transformation.  Since it sits between an application and your enterprise directories it can:

  • Transform data
  • Incorporate data from other data sources
  • Expose web services, NoSQL databases and other systems to applications that only know how to speak LDAP

What next?  You can checkout our GitHub project where all the work is done, download MyVirtualDirectory or view the documentation.



Marc BoorshteinMy Virtual Directory