identity in the browser at 5 lessons learned
play

Identity in the browser at 5. Lessons learned. Paul Trevithick - PowerPoint PPT Presentation

Identity in the browser at 5. Lessons learned. Paul Trevithick paul@azigo.com informationcard.net higgins-project.org Tuesday, May 24, 2011 Infocard in 60 seconds flat Tuesday, May 24, 2011 Click: Card picker window appears Tuesday, May 24,


  1. Identity in the browser at 5. Lessons learned. Paul Trevithick paul@azigo.com informationcard.net higgins-project.org Tuesday, May 24, 2011

  2. Infocard in 60 seconds flat Tuesday, May 24, 2011

  3. Click: Card picker window appears Tuesday, May 24, 2011

  4. User clicks on a card Tuesday, May 24, 2011

  5. User authenticates to card/IdP Tuesday, May 24, 2011

  6. Token is retrieved and HTTPS POST-ed to site Tuesday, May 24, 2011

  7. Good & bad • We got it right from the start • We got it wrong at first but eventually got it right • We still haven’t got it right Tuesday, May 24, 2011

  8. Capabilities • User-centric and decentralized architecture • Claims (attributes) not identifiers • Self-asserted and third-party asserted claims • Extensible schema • Claims as URIs • End-to-end crypto, audience restriction, verified claims • Separation of token format from network protocol • Browser-initiated (not SP-initiated) flow; anti-phishing protection • Passive advertisement of website policy • Privacy: minimal disclosure, pseudonym generation Tuesday, May 24, 2011

  9. User Experience • Support for multiple identities (cards) • Automatic card matching & filtering (no more NASCAR) • Roaming support • Cross-browser, cross-platform (including mobile) • Unmodified browser support • Cross-protocol: should have invested more in building bridges • Finding the right balance • Transparency, notice & consent vs. usability • Performance vs. security Tuesday, May 24, 2011

  10. User Experience • Dynamic claims (e.g. for payment use-cases) • Claims aggregation • Attribute/claim providers vs. identity providers Tuesday, May 24, 2011

  11. Driving adoption • Put majority of resources on winning SPs/RPs (not IdPs) • Avoid having a single, dominant vendor in the ecosystem Tuesday, May 24, 2011

Recommend


More recommend