RFC6749 et alia 20130504

Checkpoint
The problem
The history

1.1 Roles
resource owner
resource server
authorization server
client
@Override
protected AuthorizationCodeFlow initializeFlow()
throws IOException …

1.2 Flow
Authorization Request
@Override
protectedAuthorizationCodeFlowinitializeFlow()
throwsIOException…
Authorization Grant
Authorization Grant
Access Token
Access Token
Protected Resource

1.3 Authorization Grant
•  Four grant types
– authorization code
– implicit
– resource owner password credentials
– client credentials
– (extension grants…)

1.4 Access Token
•  a string representing an authorization
– usually opaque to the client
•  may denote an identifier used to retrieve
the authorization information
•  may self-contain the authorization
information in a verifiable manner
•  details in companion specifications

1.5 Refresh Token
•  credentials used to obtain access tokens
– when access token has expired
– long lived (forever and ever)
– only sent to authorization server
– denotes an identifier used to retrieve the
authorization information
– OPTIONAL

2.0 Client Registration
•  Needs to be done (client type, redirect
URI, keys)
•  Details out-of-scope for RFC6749
– Manual
– OAuth 2.0 Dynamic Client Registration
Protocol
•  draft-ietf-oauth-dyn-reg-09
– OpenID Connect Dynamic Client Registration
1.0 - draft 08

•  Real world examples
– Google
– Facebook
– Twitter
2.0 Client Registration

2.1 Client types
•  Confidential
– web application
•  Public
– user-agent-based application
– native application

2.2/3 Identifier & Auth
•  Client Identifier
– client_id (string, not secret)
•  Client Authentication (confidential client
type)
– Basic Authentication (client_id:client_secret)
•  And
– Other Authentication Methods
– Unregistered

3.0 Protocol Endpoints
•  authorization server endpoints (URL:s)
– Authorization endpoint
– Token endpoint
•  client endpoint
– Redirection endpoint
•  resource server
– As required…

4.0 Obtaining Authorization
•  Our main target is getting an Access
Token
– There are a couple of ways to do it
•  depending on the client type

4.1 Authorization Code Grant
Authorization Grant
Authorization Grant
Access Token
Access Token
Protected Resource
@override
Authentication

4.2 Implicit Grant
Access Token
Redirection URI
Script
Access Token
Protected Resource
@override
Authentication
@override
resource

4.3 Resource Owner
Password Credentials Grant
Authorization Grant
Access Token
Access Token
Protected Resource
@override

4.4 Client Credentials Grant
Authorization Grant
Access Token
Access Token
Protected Resource
@override

4.5 Extension Grants
POST /token HTTP/1.1
Host: server.example.com
Content-Type: application/x-www-form-urlencoded
grant_type=urn%3Aietf%3Aparams%3Aoauth
%3Agrant-type%3Asaml2-
bearer&assertion=PEFzc2VydGlvbiBJc3N1ZUluc3
RhbnQ9IjIwMTEtMDU [...omitted for
brevity...]aG5TdGF0ZW1lbnQ-PC9Bc3NlcnRpb24-
------ Example is OAuth-SAML2

4.5 Extension Grants
grant_type=urn:ietf:params:oauth:grant-
type:saml2-bearer
&assertion=PEFzc2VydGlvbiBJc3N1ZUluc3RhbnQ
9IjIwMTEtMDU [...omitted for
brevity...]aG5TdGF0ZW1lbnQ-PC9Bc3NlcnRpb24-
------ Example is OAuth-SAML2

5. Issuing an Access Token
HTTP/1.1 200 OK
Content-Type: application/json;charset=UTF-8
Cache-Control: no-store Pragma: no-cache
{
"access_token":"2YotnFZFEjr1zCsicMWpAA",
"token_type":"example",
"expires_in":3600,
"refresh_token":"tGzv3JOkF0XG5Qx2TlKWIA",
"example_parameter":"example_value"
}

5.1 Successful response
•  access_token
–  REQUIRED
•  token_type
–  REQUIRED
•  expires_in
–  RECOMMENDED
•  refresh_token
–  OPTIONAL
•  scope
–  OPTIONAL/REQUIRED

6.0 Refreshing an Access
Token
Authorization: Basic czZCaGRSa3F0MzpnWDFmQmF0M2JW
grant_type=refresh_token
&refresh_token=tGzv3JOkF0XG5Qx2TlKWIA

7. Accessing Protected
Resources
•  Present access token
– How depends on token_type
•  Server validates (out of scope)
– Generally interaction with Authorization Server

7.1 Access Token Types
•  What type of token?
– Compare with concept of grant_type
•  Not defined by OAuth2
– A registry is defined
•  Contents
– Bearer (RFC6750)
– Mac (Oauth-HTTP-MAC)

Extensibility
•  Defining Access Token Types
•  Defining New Endpoint Parameters
•  Defining New Authorization Grant Types
•  Defining New Authorization Endpoint
Response Type
•  Defining Additional Error Codes

Critiscism
•  Not that specified
•  A consultants dream

Bearer Token Usage
•  RFC6750
– Details on OAuth2 access_token
– Defines token_type bearer (first)
•  “A security token with the property that any party in
possession of the token (a "bearer") can use the token in
any way that any other party in possession of it can.
Using a bearer token does not require a bearer to prove
possession of cryptographic key material (proof-of-
possession).”

Bearer Token Usage
•  does not specify the encoding or the
contents of the token??
•  Methods
– Authorization Request Header Field
– Form-Encoded Body Parameter
– URI Query Parameter

Mac Token
•  draft-ietf-oauth-v2-http-mac-03
– access_token
•  token_type = mac (second, not yet approved)
– integrity

OAuth Assertions Framework
•  draft-ietf-oauth-assertions-11
– Framework, needs instances
•  ietf-oauth-saml2-bearer
•  ietf-oauth-jwt-bearer

SAML2 Bearer Assertions
Authorization Grant
Access Token
Access Token
Protected Resource
@override

SAML2 Bearer Assertion
•  Note: ‘Bearer’ now used to describe
assertion on Authorization Grant – not
Access Token
•  SAML2 Assertion – another possible
grant_type

JWT Bearer Tokens
Authorization Grant
Access Token
Access Token
Protected Resource
@override

JWT Bearer Tokens
•  Similar to SAML2
•  grant_type: urn:ietf:params:oauth:grant-
type:jwt-bearer

JWT Tokens
•  JSON Web Token (JWT) is a compact
means of representing claims to be
transferred between two parties.
– JSW (JSON Web Signature)
– JWE (JSON Web Encryption)
•  Enables MAC/signed/encrypted

OpenID Connect
•  a simple identity layer on top of the OAuth
2.0 protocol.
•  allows Clients to verify the identity of the
End-User based on the authentication
performed by an Authorization Server

OpenID Connect: flow
•  Authorization Code Flow
– response_type = code id_token
•  Implicit Flow (RECOMMENDED)
– response_type = token id_token

OpenID Connect: scope
•  openid - REQUIRED
•  profile - OPTIONAL
•  email - OPTIONAL
•  address - OPTIONAL
•  phone - OPTIONAL

additions
•  response_type: id_token
•  endpoint: /check_id, /userinfo
•  id_token is returned
•  send as access_token to /check_id
•  control info returned
•  send access_token to /userinfo
•  user_info is returned

Recap
@Override
protectedAuthorizationCodeFlowinitializeFlow()
throwsIOException…
Authorization Grant
Authorization Grant
Access Token
Access Token
Protected Resource

?Thank You!
@mjidhage
www.sakerhetspodcasten.se

Why – the plot?
53
: Hmm, don’t know - could it be, lisa@hotmail.com?
: h4pp1n3ss!
: Perfect! We’ll steal your paypal, twitter and facebook account through the hotmail account and print your photos right away. If we
find any other interesting private photos while we are in there we’ll print them too for our personal viewing pleasure.fake
: Ok, great! What’s your password?fake
: Hi Lisa, what’s your username?
fake

54
How?
Authorization in 5 easy steps
• Intent
• Request Token
• Authorize Request Token
• Exchange Token
• Access Data

55
: Hi, ! I would like to order printouts of some of my
on , they are marked as private.
Could you please print them?
: Sure, we just need to ask permission from
Step 1: Intent

56
Hi ! This is speaking! Can I have a Request Token?
HMAC-SHA1 (Yours Truly, Moo.)
: “Sure! Your Request Token is: 9iKot2y5UQTDlS2V
and your secret is: 1Hv0pzNXMXdEfBd”
: Thanks!
Step 2: Request Token

57
Step 3: Authorize Request Token
: Sure, just redirect my browser and I will be
done in a second!
: Hi , could you please go to to authorize
the Request Token:9iKot2y5UQTDlS2V?
When you have made the authorization, I can
fetch your .

58
Step 3, Continued
: , I would like to authorize 9iKot2y5UQTDlS2V
: Sure - to be on the safe side; you are allowing to read your
private pictures? We trust them, so there are no issues from our
side.
: Yes, that is correct!
: Ok, good. Now get back too and tell them it is ok to proceed.

59
Step 3, Optional Notify
: Hi , I just told that you are allowed to access my
private pictures and they told me the pictures are ready for
you to access them.
: Perfect, thank you!

60
Step 4: Exchange Token
: Hi, . Could I exchange this token: 9iKot2y5UQTDlS2V
for an Access Token? HMAC-SHA1 (Yours Truly, Moo.)
: Sure! Your Access Token is: 94S3sJVmuuxSPiZz
and your Secret is: 4Fc8bwdKNGSM0iNe”
: Perfect, thank you!

61
Step 5: Access Data
: Hi , I would like to fetch the private pictures owned by
94S3sJVmuuxSPiZz. HMAC-SHA1 (Yours Truly, Moo.)
: Here they are , anything else?

62
Take Away
•  No information on the identity of Lisa is passed to
Moo and Moo have no idea of what Lisas
credentials on Flickr is.
•  => Not an authentication protocol/standard/
technology
•  API independent
–  there are lots of different implementations on both client and
server side
The Standard

64
—  2006-11 Blaine Cook, Twitter started working on Twitter’s OpenID implementation.
—  2007-04 A Google group started to write a draft protocol specification
—  2007-06 A first draft was ready and the group was opened for everyone interested in
contributing to the specification
When?
t

65
• 2007-12 Initial version OAuth 1.0 ready
• mainly based on the Flickr Auth API and Google AuthSub
• 2009-06 Revised version 1.0a due to a security flaw
• http://oauth.net/core/1.0a
• 2010-04 RFC 5849 - IETF Informational RFC “The OAuth 1.0 Protocol”
• OAuth 2.0 http://tools.ietf.org/html/draft-ietf-oauth-v2-31
• New protocol, not backward compatible with OAuth1
• Simplify and create a better user experience
• Less secure due to no digital signature?
When?
t

RFC6749 et alia 20130504

Recomendados

Recomendados

Más contenido relacionado

La actualidad más candente

La actualidad más candente (20)

Destacado

Destacado (7)

Similar a RFC6749 et alia 20130504

Similar a RFC6749 et alia 20130504 (20)

Último

Último (20)

RFC6749 et alia 20130504