Monday, July 07, 2008
The future state of building identity aware enterprise applications...
is a story told by Matt Flynn. Here is the following quote:
- If the idea is simply to talk about what the future should look like, I think James hit on something. There has been a ground swell of apps that directly support Active Directory as the user store. So, maybe the next versions of the HR and LOB apps in the above scenario would attach directly to AD eliminating the need for any solution here. As prevalent as AD has become, that seems more likely than mass-consumption of virtual directory technologies. And it's probably what Jackson was alluding to (Quest enables *nix systems to leverage AD).
Imagine if Peoplesoft could avoid having its own database and instead update Active Directory natively. Eliminating the latency of updates could potentially increase the security of other applications. I would think that instead of having a management strategy where identity is still spread all over the enterprise, it would make better sense to consolidate to one directory where Microsoft is currently the best choice. I do hope that Nishant Kaushik, Jackson Shaw,Ian Yip, Mark Wilcox and Kim Cameron will continue the discussion on how future enterprise applications should be built. While they are at it, I would love insight into whether an application should be claims aware and integrate with an STS (Microsoft approach) or should they instead look at CARML/AAPML (Oracle)...
Links to this post: