• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Securing API data models
 

Securing API data models

on

  • 1,174 views

Security and Usability, two methodologies that have fought each other since the there was a login. As we have have progressed from a simple thought that even though something is painful developers ...

Security and Usability, two methodologies that have fought each other since the there was a login. As we have have progressed from a simple thought that even though something is painful developers will use it if it's secure, to an enlightened stage of good security and usability balance and judgement, we have seen the death of many specs and standards. Two open standards are leading the charge for this new auth age: OAuth 2 and OpenID Connect. In this talk we will explore the principles and standards behind API auth security, which will include: Using OAuth 2 and OpenID Connect as the entry point for secure API data auth - How those implementations have cannibalized previous standards to create something both secure and usable - How to practically use these standards.

Statistics

Views

Total Views
1,174
Views on SlideShare
1,057
Embed Views
117

Actions

Likes
2
Downloads
17
Comments
0

4 Embeds 117

https://twitter.com 99
http://www.nakedtechnologist.com 10
http://lanyrd.com 5
http://www.feedly.com 3

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • This is where REST and OAuth 2 come in

Securing API data models Securing API data models Presentation Transcript

  • Building on the Ashes of Past StandardsSecuring API Data ModelsJonathan LeBlancHead of Developer Evangelism (North America)Github: http://github.com/jcleblancSlides: http://slideshare.net/jcleblancTwitter: @jcleblanc
  • The Ultimate DecisionSecurity Usability
  • The Insecure, Unmanageable Start
  • Very Secure, Long to Implement
  • Two Currently Widely Used Specs
  • Fetching a CodePrepare the Redirect URIAuthorization Endpointclient_id response_type (code)scope redirect_urinonce stateBrowser RedirectRedirect URI
  • Fetching the Access TokenFetch the Access TokenAccess Token Endpointclient_id code (query string)client_secret grant_typeHTTP POSTAccess Token Endpoint
  • A few implementation differencesEndpointsScopes (dynamic / static)Using the Access Token in a request
  • How it’s Normally UsedAccess user detailsPush data throughuser social streams
  • But why?Access token as acontrol structureImprove ExistingProductsOur showcase:Seamless Checkout
  • A Few Code LinksOAuth2 & OpenID Connect Sampleshttps://github.com/jcleblanc/oauthhttps://github.com/paypal/paypal-accessLog in with PayPalhttp://bit.ly/loginwithpaypal
  • http://bit.ly/securing_apisThank You! Questions?Jonathan LeBlancHead of Developer Evangelism (North America)Github: http://github.com/jcleblancSlides: http://slideshare.net/jcleblancTwitter: @jcleblanc