RSA Conference Update

1. April 20th, 2009 RSA Conference Update

2. Agenda • OpenID Update • Business case for OpenID • Managing user profile data • Security Update

3. OpenID Foundation • Mission • A membership organization for individuals and organizations that facilitates the development of OpenID technologies, ensures the technology is open, and promotes the technology. • Current emphasis on usability, data management, and security • BOD Members • Facebook, Google, IBM, Microsoft, PayPal, Verisign, Yahoo • 8 additional “community” members • 20+ corporate members • Working relationships with related organizations • OAuth, Open Web, Portable Contacts, Concordia, Liberty, InfoCard, XRI, OASIS, OSIS, etc.

4. Market Developments • Key market developments driving adoption: • > 1 Billion Enabled Accounts • Technology Advances • Deployability Improvements • Usability Improvements • Social networks

5. Enabled Accounts (millions) AOL Orange Yahoo Blogger Facebook Mixi Telecom Italia Google MySpace Windows Live ID Live Journal myOpenID Verisign

6. 40,000+ Websites Accepting 3rd Party Login iPhoto

7. Technology Advances 2005 2006 2007 2008 2009 OpenID 1.0 (May 2005) OpenID 2.0 (Dec 2007) Protocol Contract Exchange (Feb 2009) Attribute Exchange 1.0 (Dec 2007) PAPE 1.0 (Dec 2008) SREG 1.0 (Mar 2006) XRD Discovery (Mar 2009) Extension UX Extension (Mar 2009) MSFT Cardspace integrate s with OpenID ( Feb 2007) SXIP joined OpenID ( Jun 2006) Phone-based , 2 –factor auth Integrations Portable Contacts Oauth Draft (Jul 2007) Oauth 1.0 (Dec 2007) Activity Streams (FB, MS, Yahoo) Related

8. Deployability 2005 2006 2007 2008 2009 Open source libraries and plug-ins SaaSAbstractions Wordpress Ruby Ruby On Rails Google Friend Connect MySpace Connect Beta Python Drupal MediaWiki Facebook Connect RPX Wordpress plug-in Pearl phpNuke Joomla C# JanRain RPX Cold Fusion Django Java Squeak MSFT .NET 2.0 Smalltalk C, C++ Haskell

9. Usability 2008 2009 2007 • OpenID User must understand and remember URL • Each OpenID Provider has different URL syntax • This worked “OK” on tech-focused blogs, wikis, discussion groups, etc. but not well with broader audiences and applications • Yahoo buttons, Google Friend Connect, Facebook Connect, ID Selector • Content Provider Advisory Committee meeting in NYC • First UX Summit at Yahoo • Major OPs improving workflow • Second UX Summit at Facebook • OP and RP best practices • MySpace Connect • Graphical interface of major Identity Providers, including proprietary solutions from Facebook, MySpace, & Microsoft • User only needs to click on icon for preferred identity account

10. Increasing Value of Social Networks Social networks driving the value of registered users and activity stream benefits to website operators • Community users (CU) remain customers 50% longer than non-community users, AT&T • CU spend 54% more than non-community users, EBay • CU visit 9X more often and have 4X as many page views than non-community users, McKinsey • 56% of online community members log in once a day or more, Annenberg • In customer support, live interaction costs 87% more per transaction than forums and other web self-service options, Association of Support Professionals • 43% of support community visits are in lieu of opening up a support case, Cisco • Customers report good experiences in online communities more than twice as often as they do via calls or mail, Jupiter

11. Accepting Customers with Existing Accounts Street Racers Track This Interscope Records UserVoice Sulit

12. Agenda • OpenID Market Update • Business case for OpenID • Managing user profile data • Security Update

13. Relying Party Benefits • Higher registration rates • PropertyMaps.com registrations increased 200% and now 25% of registrations are via OpenID • Single click login • No user name/password to forget. Increase customer satisfaction & reduce forgotten password costs • Keeping customer data current • When users change data in their OpenID profile, data can be pushed to websites where the OpenID has been used • Importing friends and contact info • From the identity provider to the recipient website • Bi-directional activity stream data • Data flows between the identity provider and recipient website. This allows the website to project its brand and customer activities to Facebook, MySpace, Yahoo, etc • Federated login across internal and partner sites • Japan Airlines (JAL) uses OpenID to allow customers to also book hotel rooms and car rentals using OpenID to transfer customer profile, flight, and other information

14. Sample Data • Google/Plaxo:92% login success rate • Sulit: 15% of logins are via OpenID, up from 10% a couple of months ago • 37 Signals:15% of logins are via OpenID • Mixx: UI improvement resulted in ten-fold increase in registrations via OpenID and third-party services. 20% increase in registrations from direct and referrer traffic. • AFI (Rock band, event promotion): “We were blown away with the fan response. In two weeks we received 850 submissions, had 12,500+ fans register on the website, 10,000+ comments, and over 100,000 votes to select our winners.” • GetSatisfaction: On deployments for their customers -Twitter and Songbird are experiencing OpenID utilization of 20% or more • Sourceforge.net:OpenID login has grown to about 10% of our total logins • Stackoverflow: Third party registrations have grown from 10K to 50K users in a couple of months

15. Some Examples • Plaxo/Google • Hybrid OpenID/Oauth login • Sulit • Philippine eBay-like commerce site • JAL • Federated ID with partners

16. Plaxo/Google – 92% login success

17. Sulit.com.ph • Grown from 10% of new registrations in January to 15% for Q1 • Forgotten password inquiries down 50%

18. Tatsuki Sakushima - NRI JAL – Hotel SSO Federated ID And Commerce Exchange (CX)

19. Overview • JAL partners with several hotel reservation sites and refers customers. • Provides aggregated hotel search front-end. After selection, user transferred to hotel reservation system via OpenID, also sending verified personal information including credit card number with user’s consent. • Since transactions range from $100 to >$1,000, both sides needed non-repudiation, integrity, and confidentiality. • JAL used the Trusted Data Exchange (TX ) extension proposed in December 2007 at IIW. • System went LIVE on May 28, 2008

20. Search Results Click “Reservation Details”

21. Hotel Selection Confirmation Click Confirm

22. User Login • Press Login “You can login with your JMB Membership Number” Although there is no mention of OpenID here, this actually is an OP Identifier based OpenID Login.

23. Attribute Transfer Contract Explanation • Select attributes to send Data Usage Policy Data to be provided Name Address Tel email Credit Card Number • Press “Agree & Proceed” Expiration date for this contract For non-repudiation, mutually e-signed contract is created for the transaction* This Transaction Only Until June 16, 2009 • Select expiration date for contract *Based on http://wiki.openid.net/Trusted_Data_Exchange

24. Payment Method Confirmation Credit Card Wire Transfer CVS Payment

25. Credit Card Confirmation Masked for security When user selects “Credit Card”, the CC infois prefilled with data transferred from JAL to the Hotel site using TX extension.

26. Managing the Contracts View Detail Stop Data Provision (contract termination) date ActualData A Contract

27. Trusted data eXchange (TX) sequence

28. Business Benefits for JAL • Lower cost • Faster deployment • More flexibility • Easier federation with partners • Registration rates on partner sites increased 100%

29. State of TX/CX proposal • Preliminary feedback from the community • Current implementation uses XML signature making it difficult to program in many scripting languages, consider tagged value pairs • XML processing seems to be unpopular among the community • OP and the Data Provider do not have to coincide • Data channel can be pluggable • TX non-repudiation/confidentiality/integrity properties and ability to send data in the back channel asynchronously has earned some interest among mobile operators and financial institutions. • Incorporating feedback, have created the CX proposal for the OpenID Foundation, forming Working Group • OIDF would welcome your participation with the CX Working Group

30. Economic Impact

31. Agenda • OpenID Market Update • Business case for OpenID • Managing user profile data • Security Update

32. Rich User Data Build rich user profiles more quickly & easily with data provided by the identity providers with customer approval • AOL: country, postal-code, birthday, email, gender, preferred-username, url • Google: verified email, testing name, language, country • Facebook: about me, activities, affiliations, birthday, books, current location, education history, first name, friend id, hometown location, hs info, interest, last name, locale, meeting for, meeting sex, movies, music, name, notes count, political, profile url, proxied email, quotes, relationship status, religion, sex, significant other id, status, time zone, tv, wall count, work history • Microsoft LiveID: email, first and last name, birthday, display name, anniversary, phone numbers, profile photo, urls, addresses • MySpace: about me, age, body type, books, children, current location, date of birth, drinker, emails, ethnicity, friends, gender, has app, heroes, interests, jobs, looking for, movies, name, family name, network presence, nickname, profile song, profile url, religion, sexual orientation, status, tv shows, urls, photos • Yahoo: email, nickname, full name, gender, language, postal-code

33. Data Considerations

34. Agenda • OpenID Market Update • Business case for OpenID • Leveraging user profile data • Security Update

35. Security Update • PAPE • Contract Exchange • CardSpace • Multi-Factor Authentication • OP Security Settings

36. PAPE Extension • Provider Authentication Policy Extension • PAPE Extensions strengthen OpenID logins • Authentication with additional warrants • Phishing-Resistant Authentication • Multi-Factor Authentication • Client SSL cert + password • MSFT InfoCard + password • Image grid + password • Phone verification + password • Physical Multi-Factor Authentication • USB hardware key • Biometric hardware device

37. PAPE Extension for OpenID * With FIPS 140-2 Level 2 crypto and Level 3 physical device

38. Contract Exchange (CX) Extension • Legally binding contract format. • Query/response communication protocols for establishing and canceling of the contract. • Message Encryption method to be used for the relevant communications. • Notification interface for asynchronous communications. • Provisions for long term storage of the contracts. • Field encryption method • A Public Key Cryptography based digital signature method.

39. CardSpace for OpenID • An “Infocard” Replaces password credentials • Strong authentication strengthens OpenID authentication • Protects against phishing automatically • Cards can be self-issued, or obtained from a third party • Flexible, fine-grained control over attribute sharing • Supports multiple token formats • SAML • Kerberos • X.509

40. CardSpace for OpenID An InfoCard is a strong, phishing resistant upgrade for your password.

41. Multi-factor Authentication • Phone based • Identity Provider calls your cell phone to authenticate you • Second factor to password (or other) credential • No extra hardware, tokens, certificates • Available through JanRain’s CallVerifIDTM service as part of myOpenID.com

42. CallVerifIDTM

43. OP Security Options

44. Wrap-up • Key Feedback • Business case for OpenID • Managing user profile data • Security Update • Next Steps • Internet Identity Workshop • OpenID Foundation Committees, Working Groups, Listservs, etc. Thank You!