Kim Cameron, on Federated Identity and Windows Cardspace - Port 25: The Open Source Community at Microsoft
< Back to Blogs
Kim Cameron, on Federated Identity and Windows Cardspace by admin on May 12, 2006 04:19PM

Sam interviews Kim Cameron, Chief Identity Architect & local legend, on the interesting work being done around integrated identity schemes, as well as Active Directory and the forthcoming InfoCard technology.


Video: Kim Cameron, on Federated Identity and Windows Cardspace


Alternative Video Formats:
-
Download in MPG4

Check out Channel 9's deep dive into Infocard here.

Comments RSS
  1. nektar said:

    Unless you provide source code or very detailed documentation that you attempt at least to formalize with other vendors then it is clear that many people, especially in the open source community, will simply not trust you. And if they do not trust you then that means no implementation on other platforms, unless you write it yourselves or publish the source code under an open license.

    posted at 09:38AM 05/13/2006
  2. fluke said:

    Btw, Channel 9 material is still limited to WMV with patented audio codec.

    For those interested:
    http://msdn.microsoft.com/winfx/reference/infocard/default.aspx

    This seems like a re-write of the functionality in Microsoft Identity Integration Server:
    http://www.microsoft.com/windowsserversystem/miis2003/default.mspx

    An InfoWorld comparison of MIIS 2003 (against 5 other ID systems) is available at:
    http://www.novell.com/solutions/securityandidentity/12838417.pdf

    I have been doing some work with Novell IDM 3 and the issues that Cameron brought up are very familar including there being no "center" to information.  This became an important fact when deciding what attribute to act as the "key" to make sure that we where associating the right entries between different department databases.  There are collisions when working with first/last name (more than one "John Smith").  And not all databases include the username since an employee ends up existing in the HR databases before IT even assigns a login.  So, we ended up keying on employee ID #.

    Has anyone here had to deal with Sun Java System ID Manager, XellerateIM, IBM Tivoli ID Manager and Courion Enterprise Provisioning?  I would be interested in hearing how people's expierences with other solutions have been and how many of Cameron's key point remain true regardless of the system used.

    posted at 06:33PM 05/18/2006
  3. Sam Ramji said:

    Nektar - you make an excellent point, and it's a topic we've discussed a number of times internally.  When there's more to report I'll post about it to Port 25.

    Cheers,

    Sam

    posted at 11:56PM 05/24/2006
Post a Comment
*
*