Wednesday, May 07, 2008
Thoughts on Active Directory Application Mode
Mark Wilcox questions the usage of ADAM in some scenarios. I figured, I would provide another perspective...
I guess I would ask Mark, to instead of questioning the usage of ADAM, help others outside of Oracle write better enterprise applications that bind natively to LDAP and don't require anything fugly like syncronization...
| | View blog reactions- Whenever I hear about ADAM being deployed - I always question why is it being deployed - so see if there is a better way. For example if the reason ADAM is being deployed is because you have data that exists in another database but you need it to be LDAP accessible, then that is clearly a benefit of deploying OVD.
- Or it could be that you need to make your existing AD user data look like InetOrgPerson (instead of AD's proprietary user schema). OVD can on the fly make AD look like InetOrgPerson without needing to bring up ADAM.
- Another slight twist to this use case is where you are deploying an application such as a portal,web access management or Unix authentication that needs to store data in user's entry but you can't extend the AD schema.
- exposes a standards-based changelog so your provisioning tools can easily integrate with it.
I guess I would ask Mark, to instead of questioning the usage of ADAM, help others outside of Oracle write better enterprise applications that bind natively to LDAP and don't require anything fugly like syncronization...