View
121
Download
3
Category
Tags:
Preview:
DESCRIPTION
Now that you have built your API, how do you let the right people have access to the right API at the right time? This talk covers the basics of API access management and then does a deep dive into modern authorization architectures.
Citation preview
The API GatekeeperDick Hardt
Monday, November 4, 13
Agenda
2
Monday, November 4, 13
Agenda
•Access Control Overview
2
Monday, November 4, 13
Agenda
•Access Control Overview•OAuth History
2
Monday, November 4, 13
Agenda
•Access Control Overview•OAuth History•OAuth Flows
2
Monday, November 4, 13
Agenda
•Access Control Overview•OAuth History•OAuth Flows•Implementation Steps
2
Monday, November 4, 13
Agenda
•Access Control Overview•OAuth History•OAuth Flows•Implementation Steps•What can go wrong?
2
Monday, November 4, 13
Agenda
•Access Control Overview•OAuth History•OAuth Flows•Implementation Steps•What can go wrong?•Q & A
2
Monday, November 4, 13
Authorization Code
3
Monday, November 4, 13
Authorization Code
•key into database
3
Monday, November 4, 13
Authorization Code
•key into database–user, scope, app id, expiry (5 min)
3
Monday, November 4, 13
Authorization Code
•key into database–user, scope, app id, expiry (5 min)
•token (self contained)
3
Monday, November 4, 13
Authorization Code
•key into database–user, scope, app id, expiry (5 min)
•token (self contained)–user, scope, app id, expiry (5 min)
3
Monday, November 4, 13
Authorization Code
•key into database–user, scope, app id, expiry (5 min)
•token (self contained)–user, scope, app id, expiry (5 min)–JWT
3
Monday, November 4, 13
Access Token Lifecycle
4
Monday, November 4, 13
Access Token Lifecycle•key into database
4
Monday, November 4, 13
Access Token Lifecycle•key into database–user, scope, app id, expiry, status
4
Monday, November 4, 13
Access Token Lifecycle•key into database–user, scope, app id, expiry, status
•token (self contained)
4
Monday, November 4, 13
Access Token Lifecycle•key into database–user, scope, app id, expiry, status
•token (self contained)–user, scope, app id, expiry (60 minutes)
4
Monday, November 4, 13
Access Token Lifecycle•key into database–user, scope, app id, expiry, status
•token (self contained)–user, scope, app id, expiry (60 minutes)–JWT
4
Monday, November 4, 13
Access Token Lifecycle•key into database–user, scope, app id, expiry, status
•token (self contained)–user, scope, app id, expiry (60 minutes)–JWT
•Refresh token
4
Monday, November 4, 13
Access Token Lifecycle•key into database–user, scope, app id, expiry, status
•token (self contained)–user, scope, app id, expiry (60 minutes)–JWT
•Refresh token–user, scope, app id, expiry / status
4
Monday, November 4, 13
Access Token Lifecycle•key into database–user, scope, app id, expiry, status
•token (self contained)–user, scope, app id, expiry (60 minutes)–JWT
•Refresh token–user, scope, app id, expiry / status–JWT
4
Monday, November 4, 13
API Authorization Middlewareimplementation dependent
Monday, November 4, 13
X-RateLimit-Limit: 500X-RateLimit-Remaining: 432
Monday, November 4, 13
Developer Documentation / Sandbox
Monday, November 4, 13
Developer Documentation / Sandbox
Monday, November 4, 13
What can go wrong?
8
Monday, November 4, 13
What can go wrong?•Compromise of client secret
8
Monday, November 4, 13
What can go wrong?•Compromise of client secret•Compromise of access tokens (server)
8
Monday, November 4, 13
What can go wrong?•Compromise of client secret•Compromise of access tokens (server)–Developer rests client secret
8
Monday, November 4, 13
What can go wrong?•Compromise of client secret•Compromise of access tokens (server)–Developer rests client secret–All access tokens are invalidated
8
Monday, November 4, 13
What can go wrong?•Compromise of client secret•Compromise of access tokens (server)–Developer rests client secret–All access tokens are invalidated–Refresh tokens still work, but require new secret
8
Monday, November 4, 13
What can go wrong?•Compromise of client secret•Compromise of access tokens (server)–Developer rests client secret–All access tokens are invalidated–Refresh tokens still work, but require new secret
•Compromise of access token (client)
8
Monday, November 4, 13
What can go wrong?•Compromise of client secret•Compromise of access tokens (server)–Developer rests client secret–All access tokens are invalidated–Refresh tokens still work, but require new secret
•Compromise of access token (client)–User revokes authorization
8
Monday, November 4, 13
What can go wrong?•Compromise of client secret•Compromise of access tokens (server)–Developer rests client secret–All access tokens are invalidated–Refresh tokens still work, but require new secret
•Compromise of access token (client)–User revokes authorization
•Resolution is self service8
Monday, November 4, 13
Recommended