- How to make new stuff from your piles of obsolete tech
- Why your computer sucks
- 10 recession-proof IT skills
- Juniper execs share network vision
- 9-year-old plots his fifth Microsoft certification
One challenge network administrators face in implementing portals or other enterprise applications is that user identity is fractured, residing in multiple directories tied to individual applications throughout an organization. As a result, it is difficult to provide enterprise applications with the comprehensive view of users they require to deliver their full value.
Virtual directory technology offers a way to provide that consolidated view of user identity without having to reconstruct an entire directory infrastructure. Implemented in the form of middleware, a virtual directory is a lightweight service that operates between applications and identity data.
A virtual directory receives queries and directs them to the appropriate data sources. When the user data comes back, the directory presents the data to the enterprise application as if it all had been stored in one place all along. This ability to reach into native repositories makes virtual directory technology ideal for consolidating data stored with two or more corporate divisions, between trading partners or within one entity that is using different directory services for different applications.
An important distinction between virtual directories and meta directories is that virtual directories loosely couple identity data and applications.
A meta directory provides a consolidated view of user identity by adding a layer of infrastructure that sits above native repositories, drawing user data from them and storing it in a new consolidated directory that faces an enterprise application. While this tight coupling is a good choice for situations in which data is not updated frequently, it is often insufficient to use with more agile applications such as portals and CRM systems, because synchronization delays could cause users to work with data that was minutes or even hours out of date.
Instead of creating new identity repositories, virtual directories handle identity queries on a case-by-case basis, drawing the required, authorized data (and only the required data) in real time from its native repositories around a network and presenting it to an enterprise application as needed. When the query is complete the virtual directory disappears; once again, the data exists only in its native repositories, under the control of the original owner.
Comment