6. Why an Identity MetaSystem? Prevent Phishing Attacks Prevent Identity Theft Reduce User Names and Passwords Put the User in Control
7.
8. Identity Metasystem Seven Laws User Control and Consent Minimal Disclosure Justifiable Parties Pluralism of Operators Human Integration Consistent Experience Directional Identity
9. Identity System Model User Identity Provider Relying Party Trust Identity Selector Claims Token translation
10.
11. What is CardSpace? No Personal Data Processing Engine Replace User Names and Passwords Digital Identity in CardSpace Built on .NET Framework 3.0
12. CardSpace as a Metaphor My Business My Government My Bank My School
16. Protocol Drill Down Identity Provider (IP) Relying Party (RP) Client Client would like to access a resource RP provides identity requirements: format, claims & issuer of security token 1 2 User 3 Client shows which of known IPs can satisfy requirements User selects an IP 4 5 Request to IP Security Token Service for security token providing user credentials 6 IP generates security token based on RP’s requirements with display token and proof of possession for user 7 User views token and approves the release of token 8 Token is released to RP with proof of possession RP reads claims and allows access