- Page 2 and 3:
Who here has usedOpenID?
- Page 4 and 5:
What is OpenID?
- Page 6 and 7:
What problemsdoes it solve?
- Page 8 and 9: “Someone else alreadygrabbed my u
- Page 10 and 11: What is an OpenID?
- Page 12 and 13: http://swillison.livejournal.com/
- Page 14 and 15: http://simonwillison.net/
- Page 16 and 17: What can you dowith an OpenID?
- Page 18 and 19: You can provethat claim
- Page 20 and 21: You can use it forauthentication
- Page 22 and 23: “I’m simonwillison.net”
- Page 24 and 25: (magic happens)
- Page 26 and 27: So it’s a bit likeMicrosoft Passp
- Page 28 and 29: And Microsoftdon’t get to own you
- Page 30 and 31: You, the user, decide.
- Page 32 and 33: (just like e-mail)
- Page 34 and 35: Yes, but it can besomeone you trust
- Page 36: OK, how do I use it?
- Page 43 and 44: Not necessarily
- Page 45 and 46: You don’t knowtheir name
- Page 47 and 48: You don’t knowif they’re a pers
- Page 49 and 50: Where do I get thatinformation from
- Page 51: OpenID can even helpthem answer
- Page 57: Same as usual: challengethem with a
- Page 63 and 64: Site fetches HTML,discovers identit
- Page 65 and 66: Redirects you to theidentity provid
- Page 67 and 68: How does my identityprovider know w
- Page 69 and 70: username/passwordis common
- Page 71 and 72: Client SSL certificates
- Page 73 and 74: IP based loginrestrictions
- Page 75 and 76: SecurID keyfobs
- Page 77 and 78: Just say “yes”?
- Page 79 and 80: http://www.jkg.in/openid/
- Page 81 and 82: What if I decide Ihate my provider?
- Page 83: Delegate to aprovider you trust
- Page 88 and 89: This minimises lock in
- Page 90 and 91: Probably not
- Page 92 and 93: People like maintainingmultiple onl
- Page 94 and 95: OpenID makes it easierto manage mul
- Page 96 and 97: If an OpenID is just a URL, isthere
- Page 98 and 99: My AOL OpenID provesmy AIM screen n
- Page 100 and 101: A last.fm OpenIDcould incorporatemy
- Page 102 and 103: ... and a FOAF filelisting my frien
- Page 104 and 105: Why is OpenID worthimplementing ove
- Page 106 and 107: Unix philosophy:It solves one,tiny
- Page 108 and 109:
Many of the competingstandards are
- Page 110 and 111:
Bad news: chances areyou already do
- Page 112 and 113:
OpenID just makes thisa bit more ob
- Page 114 and 115:
Phishing is a problem
- Page 116 and 117:
Your identity providerFake editionU
- Page 118 and 119:
An untrusted siteredirects you to y
- Page 120 and 121:
PayPalYahoo! BBAuthGoogle AuthGoogl
- Page 122:
One solution: don’t letthe user l
- Page 125 and 126:
CardSpace
- Page 127 and 128:
Competition betweenproviders
- Page 129 and 130:
Best practices forOpenID consumers?
- Page 131 and 132:
Allow multiple OpenIDsto be associa
- Page 133 and 134:
People can un-associatean OpenID wi
- Page 135 and 136:
Any other neat tricks?
- Page 137 and 138:
Facebook (and others)currently ask
- Page 139 and 140:
Lightweight accounts
- Page 141 and 142:
Social whitelists
- Page 143 and 144:
Decentralised socialnetworks?
- Page 145 and 146:
Doesn’t this outsource thesecurit
- Page 147 and 148:
... so do “forgottenpassword” e
- Page 149 and 150:
Password e-mails areessentially SSO
- Page 151 and 152:
Cross correlation ofaccounts
- Page 153 and 154:
Allow users to opt-outof sharing th
- Page 155 and 156:
This could be built todayby sites c
- Page 157 and 158:
“Directed identity” inOpenID 2.
- Page 159 and 160:
Sun and VeriSign haveboth announced
- Page 161 and 162:
They will smack downanyone else who
- Page 163 and 164:
(Slide borrowed from David Recordon
- Page 165 and 166:
Microsoft: Bill Gatesexpressed thei
- Page 167 and 168:
Sun: Patent Covenant,33,000 employe
- Page 169 and 170:
VeriSign
- Page 171:
Yahoo! - indirectly
- Page 174 and 175:
http://openid.net/http://www.openid