Over the next few days I will be posting a series of my notes as I finish typing them up on some of the day’s sessions at the Microsoft Architect Forum in London, Mayfair.
I will not be covering every session in detail as there just was so much, I found it hard to take it all in, being mortal and all.
Anyway down to business ...
The first session of the Architect Forum was Connected Systems Strategy by Anthony Saxby, Practice Manager and CTO at Microsoft, a man I have had the pleasure of meeting on more than one occasion.
The talk discuss briefly the different types of modelling, Aspect, Interaction and of course capability. Head-line: Anthony Saxby discloses that Microsoft Big Bet is Services! Really?! Thats was a shock.
This moved us nicely on to discussing the protocol framework and how Microsoft is working together with other partners in the Industry. Anthony wanted to give an indication of the road map for services in the time he was allowed.
Microsoft © 2005
Anthony didn’t want to go into the Framework in any detail as this was really going to the topic of Benjamin Mitchell’s talk later on in the day.
To the main point of the talk which centred around Identity management and the evolving ideas on that. Now this was an area that I hadn’t heard than much about so my ears pricked up at this point.
Identity Management isn’t a subject that has many of us riveted in the Architecture world but I felt it’s just about to become fundament and a whole lot more interesting.
Hmmm, are we talking about Passport? No, but yes, Passport was should as very much Identity management heritage but several important lesson had been learnt from that time, the most important being that organisations do like their privacy and they weren’t about to had that over to a commercial organisation such as Microsoft.
A heckler from the crowd cried “How do you prove that someone is who they say they are?” I instantly thought to myself, what are you on about mate, since the beginning of time there has been impostors and if someone can mimic someone else then that’s life, our challenge is to keep applications accessible to the users who are valid and inaccessible to those that aren’t, it’s a balancing act between security and usability. As far as I’m concern … every little bit helps!
We saw a slide that should the historic lineage of Identity Meta Data system, from the past, i.e. ID for each system, application focused, limited value to business. To present, i.e. Identity integration, Internal and external to applications, High cost to value. To the future and the ideals, i.e. Federated Identity, Built to Extend and Low cost to value.
So if we break down what that means,
- Assumes people will have multiple identities
- Assumes multiple underlying identity providers, platforms and technologies
- Provides an industry standard framework based on 7 Laws of Identity.