Authentication with OAuth and Connected Apps


Published on

  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Authentication with OAuth and Connected Apps

  1. 1. Authentication with OAuth andConnected AppsBest Practice API AuthenticationChuck Mortimore,, Sr. Director of Product Management@cmort
  2. 2. Safe Harbor Safe harbor statement under the Private Securities Litigation Reform Act of 1995: This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any of the assumptions proves incorrect, the results of, inc. could differ materially from the results expressed or implied by the forward-looking statements we make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of product or service availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services. The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our service, new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of intellectual property and other litigation, risks associated with possible mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of our service and successful customer deployment, our limited history reselling products, and utilization and selling to larger enterprise customers. Further information on potential factors that could affect the financial results of, inc. is included in our annual report on Form 10-Q for the most recent fiscal quarter ended July 31, 2012. This documents and others containing important disclosures are available on the SEC Filings section of the Investor Information section of our Web site. Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available., inc. assumes no obligation and does not intend to update these forward- looking statements.
  3. 3. Why OAuth? Open: A standard protocol that enables secure API access Simple: No need to write UI or handle SSO/2-Factor/etc. Mobile: Mobile Policies, No API Tokens, IP Bypass, etc. Secure: Gets rid of passwords in Apps. Strong crypto options
  4. 4. The World’s SimplestOAuth Client
  5. 5. Step 1: Register your App
  6. 6. Step 2: Craft a URL to the Authorize Service ?response_type=code &client_id={YOUR_CLIENT_ID} &redirect_uri={YOUR_URL_ENCODED_REDIRECT_URI}
  7. 7. Step 3: Exchange the Code curl -d grant_type=authorization_code&client_id={CLIENT_ID}&clie nt_secret={CLIENT_SECRET}&redirect_uri={YOUR_URL_E NCODED_REDIRECT_URI}&authorization_code={CODE}
  8. 8. Step 4: You’re Done - Use your token! GET /resource HTTP/1.1 Host: Authorization: Bearer czZCaGRSa3F0MzpnWDFmQm…. curl -L -H Authorization: Bearer {ACCESS_TOKEN} -H "X- PrettyPrint: true" {RESOURCE}
  9. 9. Let’s Build a Web App
  10. 10. Code Flow: How does it work?1) App Redirects User to Authorization Services where User is Authenticated and Authorizes App2) Code Returned to App3) App Exchanges Code at Token Service
  11. 11. Let’s Build a Web App
  12. 12. Let’s Build a Mobile App
  13. 13. Token Flow How does it work?1) App Redirects User to Authorization Services where User is Authenticated and Authorizes App2) Token Response returned directly to app on URL behind a # fragment
  14. 14. What happens on Mobile?1) Device opens a browser with authorization URL1) Tokens returned on URL behind # fragment – instrumented browser is monitoring and parses URL
  15. 15. What the User Sees: Authentication Authorization
  16. 16. Codified Best Practice: Mobile SDK & Container NATIVE HYBRID WEB OAuth2.0 Secure Storage Mobile Login Standard authentication Securely store credentials and User experience, processes and implementation providing single business sensitive data with policy control optimized for the sign-on for trusted apps enterprise-class reliability and mobile environment security
  17. 17.
  18. 18. Let’s build a Web App
  19. 19. Notice SSO works! Refresh Tokens It’s a lot like a password  Allows you to get more sessions  Make sure you treat it like one! POST /services/oauth2/token HTTP/1.1 Host: Content-Type: application/x-www-form-urlencoded grant_type=refresh_token &refresh_token=5Aep8615VRsd_GrUz3LAcJl &client_id=MyApp &redirect_uri=myapp%3A%2F%2Fcallback
  20. 20. Let’s Build an Integration App
  21. 21. What if I just want to call server to server Uid / Password Flow - Simple, but uses passwords, API tokens, etc. Web SSO Assertion Flow - Reuse SAML SSO and existing Trust SAML/JWT Assertion Flow - Cert and Trust Specific to the App
  22. 22. Let’s Build a Web App
  23. 23. Enterprise Class Authorizationwith Connected Apps
  24. 24. Admin Authorization for OAuth Apps1) Admin “installs” app2) App Uses any OAuth Flow3) User Authorization is evaluated via Admin settings
  25. 25. Final Thoughts No one likes plumbing….use a toolkit Make your login URLs configurable,, other Protect against attacks Set a cookie, and check for it on response
  26. 26. Chuck Mortimore @cmort