Case Study - Using ADAM and ADSynch Light
One LDAP directory? We got more than one!
Summary
Whether it is for currently ongoing projects, whether for legacy systems, proprietary software, migration scenarios or maybe just because there are connected divisions running their own systems - the reasons for running more than one LDAP based directory are divers.
And then? Data is copied or entered manually, often using non documented processes. When not being performed regularly, data will become inconsistent. Also, the maintenance of more than one user details and account credentials often can become a nightmare security wise and for the added support weight, like when changing communication details or passwords.
One of the excelling properties of Windows Active Directory in Application Mode is its integration into the Windows Back Office framework and with its added functionality to add single sign on capabilities even for legacy applications and to become completely transparent towards these, it is the ideally suited LDAP directory that unifies the burden in keeping more than one directory data store.
Read more...