Posted By: Charles | May 12th, 2006 @ 11:00 AM | 50,071 Views | 21 Comments

Nigel Watling, InfoCard Technical Evangelist, leads an in depth discussion of how InfoCard works, how it's designed (and why) and how it will evolve in the future(great Going Deep stuff!) with InfoCard chief Architect Arun Nanda and Software Developer Ruchi Bhargava.

Media Downloads:
Rating:
0
0
Zeo
Zeo
Channel 9 :)

This is a great deep dive on the technology. I like how they use real world future scenearios.

LaBomba
LaBomba
Summer
I like how they write with blue markers on the white board. 8-)
eddie505
eddie505
jazzbo

Interesting video....

I would like to know how this compares to SXIP?

Also how does this fit in with Microsoft Passport? (It seems like Passport attempted to solve this problem already, does this mean Passport fell short of its orginal goals. why?)

Cheers Ed.

Kryptos
Kryptos
Backup People!

Yes it is a replacement for MS Passport, Passport fellshort because no one trusted MS enough, well thats how I understand it.

It does sound very similar to SXIP.... is this just MS implenmentation?

EDIT: Added question and amended typo above...

Where/how do digital certs fit in with InfoCard Architecture?

mkanwar
mkanwar
UberGeek
Another great video from the Channel 9 team!
Kryptos wrote:


Yes it is a replacement for MS Passport, Passport fellshort because no one trusted MS enough, well thats how I understand it.



No, it is not. InfoCard does not replace passport. Passport (or Windows Live ID, its new name) will be one of many identity providers supported by InfoCard, but it won't get any special treatment over any other identiy provider. InfoCard is an identity selector, which essentially is a secure way for users to choose amongst various providers that might be able to make statements about the user. For example: A web page might require the age of its users before it shows its content. The web page would trigger the InfoCard UI, the Infocardsystem would look at the set of identity providers the user is registered with, would pick the ones that can certify the age of the user (and maybe Windows Live ID is one of them), present a UI to the user that lets him/her pick which provider to use and then securly transmits that claim to the web page. It is actually a bit more complicated that that, but there are many good whitepapers on it on MSDN.

But the key point is: Infocard does NOT replace Passport. It solves a different set of problems.

Truly a great video... One of the best I have seen with respect to a clear overview of the framework from an architecture perspective. 

I was also stunned that they didn't employ more managed code for the UI.  As I was thinking it (and as my wife would attest, vocally complaining about it) Charles asked it.  I would have to say I still don't clearly understand why they didn't.  As Charles said, one would think that would be a more secure way to implement the UI, with less effort.  Can Arun, Ruchi or Nigel give a little more detail as to why?

The whole "They might not have the .NET Framework" just doesn't hold water....

Another thought is if the interfaces are written as they stated, one major step Microsoft could do to convince us they want this to use open standards and foster other platforms use it, would be to offer some of it via share source/open source for use in... well... Mono maybe? Then each platform need only implement the "windows service" piece in their own way and use the other pieces to offer a common interface...  Am I crazy to want Microsoft to take this approach more often than not for this type of stuff?

Anyhow, great video, keep these coming.
>> The whole "They might not have the .NET Framework" just doesn't hold water....

Yes it does, if they want to support (and they stated they did) all operating systems.  That would include operating environments that don't have a Framework implementation.
assuming they will be sharing code you have a potential point if you ignore Project Mono http://www.mono-project.com or don't believe in it.... I didn't hear anything about them sharing code... Just using open standards, which means other are free to use anything... C++, Java, or whatever.  But on Windows why not use .NET and offer some or most up via shared-source/open source?
Microsoft Communities