Slashdot Mirror


User: RichTurner

RichTurner's activity in the archive.

Stories
0
Comments
3
First seen
Last seen
Profile
(view on slashdot.org)

Comments · 3

  1. Re:The good thing about InfoCards on Slashback: Quinn, InfoCards, McKinnon · · Score: 1

    Yep, it's a virtual card ... but can be unlocked with a hardware-based or dynamically retrieved/generated key if required. It's not part of IE7 - IE7 just understands the MIME type and how to request a token from the "InfoCard" subsystem. It's not just goign to be part of Vista - it's going to be available for XP (SP2+), 2003 Server (SP1+) and Vista upwards. At some point you'll see similar and compatible subsystems on other platforms too ... and before you ask ... no, not from Microsoft - from those platform vendors!

  2. Re:Too biased and anti-Microsoft... partial nonsen on Slashback: Quinn, InfoCards, McKinnon · · Score: 1

    Just as a point of clarification: Yes, "InfoCard" is a Microsoft proprietary implementation of the core user-agent of the Identity Metasystem. However, the Identity Metasystem is not Microsoft proprietary and is (definitely) not Passport v.next: In the Identity Metasystem, all communications are carried out using standard HTTP & WS-* protocols, "InfoCard" will communicate with Identity Providers running on any other platform that supports the same protocols. Further, we openly welcome other platform vendors to implement "InfoCard" like capabilities in their platforms and products. You get to store your own identity information (in the case of self-issued cards) or store cards containing metadata referencing information stored by trusted third parties (your bank, your airline frequent-flyer club, your insurance company, your whatever).

  3. Re:InfoCard is open source on Slashback: Quinn, InfoCards, McKinnon · · Score: 1

    Ermmm ... slight clarification: "InfoCard" is the codename for a new technology from Microsoft that implements the core user-agent portion of the Identity Metasystem. While "InfoCard" itself is not open source, it does use standard WS-* protocols (including WS-MetadataExchange, WS-SecurityPolicy, WS-Security, WS-SecureConversation, WS-Trust) in order to securely obtain and exchange identity information between "Identity Providers" (eg: your employer, your frequent flyer club, your bank, your credit card, etc) and "Relying Parties" (eg: websites).