234 leigh doddsconcurrent4d

25
Knock, Knock – Who’s There? Towards Federated Authentication Leigh Dodds Chief Technology Officer, Ingenta Society for Scholarly Publishing San Francisco, June 2007

Upload: society-for-scholarly-publishing

Post on 07-Jul-2015

77 views

Category:

Documents


2 download

TRANSCRIPT

Page 1: 234 leigh doddsconcurrent4d

Knock, Knock – Who’s There?Towards Federated Authentication

Leigh DoddsChief Technology Officer, Ingenta

Society for Scholarly PublishingSan Francisco, June 2007

Page 2: 234 leigh doddsconcurrent4d

The Identity Problem

Page 3: 234 leigh doddsconcurrent4d

Too many passwords

…Flickr & YouTube & FaceBook & MySpace & LiveJournal & LinkedIn…

Page 4: 234 leigh doddsconcurrent4d

Identity Silos

Page 5: 234 leigh doddsconcurrent4d

Vendor Lock-In

E.g. Microsoft Passport

Page 6: 234 leigh doddsconcurrent4d

Single Sign-On can solve these problems

Single Sign-On = Federated Authentication

Page 7: 234 leigh doddsconcurrent4d

Knock, Knock

Page 8: 234 leigh doddsconcurrent4d

Who’s There?

Page 9: 234 leigh doddsconcurrent4d

Dude..It’s Me…

Page 10: 234 leigh doddsconcurrent4d

Who Says?

Page 11: 234 leigh doddsconcurrent4d

Er…Ask That Guy…

Page 12: 234 leigh doddsconcurrent4d
Page 13: 234 leigh doddsconcurrent4d

Hey, do you know this guy?

Page 14: 234 leigh doddsconcurrent4d

Dude, that’s Leigh

Page 15: 234 leigh doddsconcurrent4d

Respect Mah Authoritah!

Page 16: 234 leigh doddsconcurrent4d

Oh, OK. Thanks

Page 17: 234 leigh doddsconcurrent4d

Hi, Leigh…

Page 18: 234 leigh doddsconcurrent4d

There’s More Than One Way to Implement This

Page 19: 234 leigh doddsconcurrent4d

User

Service Provider

Identity Provider

Page 20: 234 leigh doddsconcurrent4d

Where Things Differ…

• How do we know who the user’s Identity Provider is?

• How do the Service Providers and Identity Providers talk to one another?

• What information does the Identity Provider expose about the User?

• Can we trust the Identity Provider?

• How does the Identity Provider authenticate the user?

Page 21: 234 leigh doddsconcurrent4d
Page 22: 234 leigh doddsconcurrent4d
Page 23: 234 leigh doddsconcurrent4d

OpenId

• User-centric

• Simple to implement

• Growing number of open source toolkits

• Rapid adoption in web community

• Does not address trust issue

Page 24: 234 leigh doddsconcurrent4d

Shibboleth

• Library-centric

• Complex to implement

• Open source software plus commercial options

• Growing adoption in library and publishing communities

• Introduces element of trust

Page 25: 234 leigh doddsconcurrent4d

Conclusions & Further Reading

http://del.icio.us/ldodds/tag/ssp-2007-06