OpenID for the Government, led by Chris Messina. (@chrismessina, http://factoryjoe.com)
OpenID provides:
1. Authentication:OpenID as your identity's credit card on the web. Terms: Identity Providers = IDPs; Relying Parties = RPs;
2. Authorization: Current status quo: Individual email address, different secrets between individual website providers. (If hacked,
someone can come in who knows 1 secret that attaches to a public identity, and try that secret all sorts of other
places. Sometimes, it works.)
OpenID's structure. Me → Relying party → IDP (yes/no) → RP Direct connection between IDP and yourself. IDP can rely on anything, secure tokens, biometrics, something you know.
(Paypal is a good model for how OpenID works, but as an e-commerce setting.)
==== Privacy: ==== Allows for
- Pseudonymity
- Anonymity
- Directed Identity - obscured personal identity, but can be correlated between sites for reputation management.
Biggest issue with OpenID:
Cashing checks to moving towards a credit card economy, the credit card readers have to be installed everywhere.
What happens when an identity provider goes out of business? An argument for delegation. === Places that provide OpenID management: === Nombray.com - Agree2.com - Claimid.org - danddyid.org - chi.mp -
