1. OpenID – Identity in the CLOUD? Nat Sakimura (=nat) twitter.com/_nat www.sakimura.org/en/

2. Bom dia.

6. CHANGE

8. CLOUD

15. Audit & TRUST

18. O pen R eputation M anagement S ystem

20. Relationship Management and non-repudiation

22. CX Basic Flow (Simplified Version) This is a special case of the generalized “Base Model” that is explained later. This special case is optimized for OpenID. Relying Party (RP) OpenID Provider (OP) 1. User access the service 1 3. User Consent verified 3 2. RP creates signed “Offer” and sends it to OP “ Offer” 2 RP 4. OP creates the signed “Contract” based on the “Offer” 4 “ Contract” OP “ Offer” RP

24. CX Basic Flow (Artifact+Synchronous)

25. CX Basic Flow (Artifact+Asynchronous) OP Service End Point XRD Access Service Get XRD to obtain service end point and the public key of the OP. Create “Offer” and sign Send “Offer” to OP Return Ticket for the “Offer” Browser Redirect to show OP the Ticket (Optional) Get XRD to obtain service end point and the public key of the Obtain User Consent on the Offer pointed by the Ticket. Create “TransactionID” Browser Redirect to send “TransactionID” to RP Done! Save TrabsactionID RP Service End Point XRD Store Offer Other Processing Send Notification that a Contract for the TransactionID has benn created Create Signed Contract GET Contract based on TransationID Return the (encrypted) Contract Store the Contract

27. JAL-Hotel SSO & Data Transfer Sequence

30. sequence

31. Fig.1 JAL: Search Result Press “Reservation Details”

32. Fig.2 Myu : Hotel Selection Confirmation Press Confirm

37. Fig.7 Hotel : Room Confirm

38. Fig.8 Hotel : Payment Method Confirm Credit Card Wire Transfer CVS Payment

39. Fig.9 Hotel : Credit Card Confirm Masked for security reason When user selects “Credit Card”, the number etc. are prefilled because the data was transferred from JAL to the Hotel site using TX extension.

40. Contract Management

41. Fig.10 JAL: Managing the contracts/relationship A Contract date Actual Data View Detail Stop Data Provision (contract termination)

42. Fig.11 JAL: Contract Termination

43. Situations in Japan

44. Success in Japan

45. WHY?

47. SECURITY

49. COMMUNITY

54. Balanced Composition As of Nov.1, 2008 Note: Some mebes wishes not to announce their participation in public so they are not listed in the web page. Published Member List: http:// www.openid.or.jp/memberlist.html

57. OpenID Foundation Japan Structure Membership Corporation (OIDF-J) Fee *2 Activity Proposal Board of Trustees (3) (For fiscal fiduciary) SIG 1 SIG 2 SIG n *1 Funding & Support SIG Leadership Council Advisors (Academic) Advisors ( Government ) Liason ( LAP etc. ) *1 Anticipated Initial SIGs: 1. Marketing, 2. Payment, 3. Assurance, 4. User Interface *2 Fees are deliberately cheap because OIDF-J do not spend much… Fee = approx US$2000+$1000 Break even at 20 members for min. activities: Targeting at 100 members or more. Secretariat (Accounting and Facilitation)

58. Building Bridges Harmonize

60. The Bi-Cameral Model Board of Trustees Member A Member B Member N Leadership Council WG 1 DG 1 DG/WG N Coordination (Members & Non-Members) Staff support report Participants (Members & Non-Members)

65. Recent Development in Japan besides more and more companies announcing support such as NTT…

68. × ｙｏｕｒ ｉｄ ｅａ．