Spec Update - OpenID Retail Summit at PayPal
Download as PPTX, PDF1 like660 views
The document provides an update on ongoing work to extend the OpenID specifications to support new use cases like mobile phones and social login functionality. It discusses the OpenID Artifact Binding working group's progress in developing specifications based on OAuth 2.0, JSON Web Tokens, and other standards. The working group aims to complete draft specifications by May 2011 to allow for testing and further refinement.
Spec Update - OpenID Retail Summit at PayPal
- 1. OpenID Specification Work UpdateOpenID Retail Summit – March 8, 2011Mike Jones – Microsoft
- 2. Spec Work OngoingExisting OpenID 2.0 specifications in use nowAlready work fine for many use casesActive working occurring to extend specifications for new use casesMobile phones and other limited platforms“Facebook Connect” style functionality for easy registrationEasier deployment than OpenID 2.0
- 3. Working GroupSpec work occurring in “Artifact Binding” working groupIncorporates submissions to former “Connect” working groupMerger sometimes called “OpenID ABC”Almost certainly not final branding!OpenID specs developed via an open processAll free to participate
- 4. WG ParticipantsKey working group participants:Nat Sakimura – Nippon Research Institute – JapanJohn Bradley – Independent – ChileBreno de Medeiros – Google – USPaul Tarjan – Facebook – USAxel Nennker – Deutsche Telekom – GermanyKick Willemse – Independent – NetherlandsTony Nadalin – Microsoft – USMike Jones – Microsoft – USBy no means an exhaustive list!
- 5. New Spec Building BlocksBuild on OAuth 2.0Use JavaScript Object Notation (JSON)JSON Web Token (JWT) claims representationGoal: Easy implementation on all modern web platforms
- 6. Spec StructureOpenID AB spec contains in two partsCore – abstract specificationBinding – OAuth 2 based bindingJSON Web Token (JWT) spec with signingNext version will add encryptionOther specs like UMA are looking to adopt itDiscovery a separate specWill refer to OAuth 2.0 specs once finished
- 7. Spec ProgressCurrent statusCore – 70% doneBindings – 75% done (pending OAuth 2.0 completion)Discovery – 80% (working from SWD)JWT – 90% done for tokens and signatureEncryption remains to be specifiedOAuth 2.0 – 95%Target: Complete drafts by Internet Identity Workshop (IIW) in May
- 8. Implementation StatusOpenID ABCDemo version of core and artifact binding available in PHP (BitBucket)Code needs updates for current JWT and yesterday’s spec resultsJSON Web Token (JWT)Implementations for Java, PHP, Python, Ruby, .NET
- 9. ABC CapabilitiesArtifact BindingUserInfo EndpointSimple RPsHigher LoASession ManagementUnregistered ClientsOAuth 2 IntegrationUse of JWTsSingle Logout
- 10. Open Spec IssuesKinds of identifiers are supportedHarmonization with OAuth 2Permissioning distributed attribute providersClaims specification and integrationTrust metadata formats and transports
- 11. IdentifiersNeed to define the supported formats and normalization rulesE-mail Addresshttp/https URLPhone Number?
- 12. Use of SummitsMay IIW : Review drafts, make remaining decisionsMunich: Brief participants on progress, specs - gather inputTokyo: Test implementations; learn from implementation and deployment experiencesColorado: Interop work – potentially in cooperation with OSISLondon: Brief participants on progress, specs - gather inputNov IIW: Spec refinement and/or finalization
- 13. Discussion & ResourcesArtifact Binding Working Group Wiki Pagehttp://wiki.openid.net/w/page/12995134/Artifact-BindingArtifact Binding Mailing Listhttp://lists.openid.net/mailman/listinfo/openid-specs-abMy blog:http://self-issued.info/