"But when the reply to that request comes through it doesn’t recognize it as such, just as another request to re-package data and tokens within the right protocol."
does this mean that the bus translates the reply back to the original request protocol?
so the bus will accept any or some limited number of protocols and translate the requests to the protocol for the corresponding identity store and then translate back to the original protocol for the request?
Latest security headlines from Network World:
10 steps to loading dock security
Shell blames IT contractor for benefits fraud
Militants send terror messages in India by 'wardriving'
|
Does Verizon's Voyager stack up to the iPhone? |
|
|
5 IT skills that won't boost your salary 
[1,407]
Women 4 times more likely than men to cough up personal info [589]
Japan's 10 funniest tech-related commercials [Videos] [407]
Throwing away a promo CD is "unauthorized distribution"? [1,265]
Adults too quick to dismiss educational video games [682]
Attack of the iPhone clones [Slideshow] [578]
10 things IT needs to know about AJAX [1,258]
This Year's 25 Geekiest 25th Anniversaries [Slideshow] [409]
|
|
the ID bus/hub
As I see it, the bus/hub isn't aware of the nature of the data (request, response, etc.) it reads the source protocol/schema and the target protocol/schema and performs a transformation. If the request goes to a service which can 'speak' the requestor's native language, it could reply directly without the need for the transformation.
not sure I get it
I'm in a large global enterprise. One of the biggest problems we have is identifying users across systems as there's (to date) little conformity in how accounts are named. We use a hub (in this case a meta directory) to keep track of who is who. The connectors provide the correct protocol to the systems the hub touches. How would your idea help in this scenario?
Thanks,
James
Re:not sure I get it
Issue you are facing is related to global and consolidated identities and their unique identification. It's combination of data cleaning as well as virtualization.
Identity hub appears to be a proper subset of Virtual directory.
Ashwin
Identity Hub - Subset of Virtual directory
First of all I dont agree with the Virtual Directory definition given. I don't agree that virtual directory needs to know all the information about identities, that's just how one of the virtual directory available in market, in IMHO that's crudest form of virtual directory. Most of the virtual directories just know the location of identity information for each virtualization zone/node that's it! It's a full blown directory, just that identites come from different places, using different rules. How can it be different from identity hub! And that's how any data retrieval will happen, I dont see how Identity Hub can do it differently.
Virtual directory join engine will translate to identity hub when there is only one repository.
Ashwin