• Etelos
  • IBM
  • Microsoft
  • Adobe Systems, Inc.
  • Cynergy
  • Nokia
  • Openmaru Studio
  • WebEx
  • AOL
  • Citrix Systems
  • Coghead
  • Confident Technologies
  • Disney
  • Disney
  • EffectiveUI
  • F5 Networks
  • HCL Technologies
  • Intuit Quickbase
  • Oracle
  • S60
  • Salesforce.com
  • Spinscape
  • Sun Microsystems
  • Symphoniq Corporation
  • TeleAtlas
  • Yahoo! Inc.
  • Amazon Web Services
  • Atlassian Software Systems
  • awareness
  • BroadSoft
  • Curl
  • Denodo
  • Dixero
  • Force10 Networks
  • Humanix Inc.
  • Intel
  • JackBe
  • Jaduka
  • Jive Software
  • Juniper Networks
  • Kapow Technologies
  • Keynote Systems
  • Leverage Software
  • LiquidApps
  • LithiumTechnologies
  • LongJump
  • Morfik
  • Mzinga
  • NeuStar
  • Octopz
  • ONEsite
  • OpSource
  • Panther Express
  • Profy
  • Real Time Content
  • Rearden
  • Rearden Commerce
  • Remy
  • Reply
  • spigit
  • StreamVerse, Inc.
  • StrikeIron
  • XBOSoft
  • Znak
  • O'Reilly Alpha Tech Ventures
  • Panorama Capital
  • ACM Queue
  • Berlin Partner
  • BlogHer
  • Business Marketing Association
  • Dr. Dobbs
  • Fast Company
  • GigaOM
  • Juniper Research
  • Mashable
  • MSDN Magazine
  • NewTeeVee
  • Revenue Magazine
  • TechNet
  • Technorati
  • Topix
  • Webware
  • Wired
  • WOW

Sponsor & Exhibitor Opportunities

Vicki Sanders

Media Sponsor Opportunities

Liliana Arancibia

Press/Media Inquiries



Natalia Wodecki

Contact Us

View a complete list of Web 2.0 Expo contacts.

The "How" of OAuth

Location: 2003 Level: Intermediate
Presentation: The "How" of OAuth Presentation 1 [PPT]

This talk will be comprised of 3 sections:

  • An introduction to OAuth.
  • Implementing OAuth as a Consumer.
  • Implementing OAuth os a Service Provider.

In the introduction Fleckenstein will explain what OAuth is and why to use it, introducing general terminology used when discussing OAuth. He’ll also present two different scenarios (“two-legged” and “three-legged”) in which OAuth can be used.

With concern to implementing a consumer application of an OAuth-enabled API, he’ll outline what you as a developer will need to implement: go through the full Authorization flow from start to finish, ending with your application being able to access a protected resource from an OAuth-enabled site. We’ll use the GetSatisfaction.com API as a service provider to which we can call against.

Next, Fleckenstein will talk about what it takes to provide an OAuth-enabled API. OAuth leaves some decision to the discretion of the application developer, so you’ll learn what you have to do to implement OAuth in your API. Included are the three actions your app needs to provide to support OAuth, and the supporting infrastructure you should provide around OAuth to create a good experience.

Code examples will be given in Ruby, using the OAuth gem. Links to where other OAuth libraries can be found will be provided.

Scott Fleckenstein


Scott Fleckenstein has been developing web application professionally for seven years, most recently constructing getsatisfaction.com from the ground up.