Microsoft

mbj@microsoft.com http://self-issued.info/

Microsoft

tonynad@microsoft.com

Security OAuth Working Group RFC Request for Comments I-D Internet-Draft JSON Web Token JWT Delegation on-behalf-of act-as This specification defines how to request and obtain Security Tokens from OAuth Authorization Servers, including enabling one party to act on behalf of another or enabling one party to delegate authority to another.

This specification defines how to request and obtain Security Tokens from OAuth Authorization Servers , including enabling one party to act on behalf of another or enabling one party to delegate authority to another. The functionality defined and the terminology used in this specification are intentionally parallel to the functionality and terminology defined by , including On-Behalf-Of and Act-As. A Security Token is a set of information that facilitates the sharing of identity and security information across security domains. Examples of Security Tokens include JSON Web Tokens (JWTs) and SAML Assertions . Security Tokens are typically signed to achieve integrity and sometimes also encrypted to achieve confidentiality. Security Tokens are also described as Assertions in . This specification defines a new Security Token Request Grant Type used at the Token Endpoint to convey the parameters for a Security Token request and Security Token response parameter used in responses to these requests. The Security Token Request is a JSON Web Token (JWT) that is issued by the requesting party that contains parameters of the request as Claims. The Security Tokens obtained could be used in a number of contexts, the specifics of which are beyond the scope of this specification. Examples include using them with the

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

This specification uses the terms "Authorization Server" "Token Endpoint", "Token Request", and "Token Response" defined by OAuth 2.0, and the terms "Claim" and "JWT Claims Set" defined by JSON Web Token (JWT).

When principal A acts on behalf of principal B, A is given all the rights that B has within some defined rights context. Whereas, with on-behalf-of semantics, principal A still has its own identity separate from B and it is explicitly understood that while B may have delegated its rights to A, any actions taken are being taken by A and not B. In a sense, A is an agent for B. On-behalf-of semantics are therefore different than impersonation semantics, with which it is sometimes confused. When principal A impersonates principal B, then in so far as any entity receiving Claims is concerned, they are actually dealing with B. It is true that some members of the identity system might have awareness that impersonation is going on but it is not a requirement. For all intents and purposes, when A is acting for B, A is B.

A Security Token Request is sent to the Token Endpoint as a Token Request message using this Grant Type value: Grant Type value indicating that this Token Request is a Security Token Request. A Token Request parameter with a related name is used to convey the information contained in Security Token Request as a JWT: Token Request parameter whose value is a JWT containing the Security Token Request information.

An example Security Token Request (with extra line breaks for display purposes only) follows:

The security_token_request parameter value is a JWT with the following members: REQUIRED. Issuer of the principal requesting the Security Token. REQUIRED. Identifier of the principal requesting the Security Token at the issuer. OPTIONAL. Identifier for the type of the requested Security Token. If not present, the default is that a JWT is being requested. A JWT can also be requested with the identifier urn:ietf:params:oauth:token-type:jwt. OPTIONAL. Array of strings, each of which represents a service context that the requested Security Token is being requested to be used for. The array MUST contain at least one scope value. The definition of these contexts is outside the scope of this specification. (Note: This request element serves the same purpose as the WS-Trust AppliesTo RST element.) The request JWT MUST be signed by the issuer so the identity of the requesting party can be validated unless the identity of the requesting party is known to the Authorization Server by other means; in that case, the JWT can use the alg value none.

The following is an example of a JWT Claims Set for a Security Token Request:

This specification defines the ability to request a Security Token for the requesting party to use to act as the specified party. This is accomplished using this Token Request parameter: This OPTIONAL request parameter indicates that the requested Security Token is expected to contain information about the identity represented by the Security Token that is the value of this parameter, enabling the requesting party to use the returned Security Token to act as this identity. Unless the act_as_type parameter is also included and specifies a different token type, the act_as parameter MUST contain a Security Token that is a JWT. This OPTIONAL request parameter declares the type of the Security Token in the act_as parameter. If the Security Token is a JWT, this identifier is urn:ietf:params:oauth:token-type:jwt.

The following is an example of a JWT Claims Set for a Security Token Request using an act_as Claim:

This specification defines the ability to request a Security Token on behalf of another party. This is accomplished using this Token Request parameter: This OPTIONAL request parameter indicates that the Security Token is being requested on behalf of another party. The identity of the party upon whose behalf the request is being made is represented by the Security Token that is the value of this parameter. Proof of eligibility to act on behalf of that identity MAY be conveyed by including an actor Claim identifying the requesting party in the Security Token, per , provided the Security Token is a JWT. Unless the on_behalf_of_type parameter is also included and specifies a different token type, the on_behalf_of parameter MUST contain a Security Token that is a JWT. This OPTIONAL request parameter declares the type of the Security Token in the on_behalf_of parameter. If the Security Token is a JWT, this identifier is urn:ietf:params:oauth:token-type:jwt.

The following is an example of a JWT Claims Set for a Security Token Request using an on_behalf_of Claim:

A Security Token Response is returned from the Token Endpoint as a Token Response message containing these members: Returned Security Token. Identifier for the type of the returned Security Token. If the Security Token is a JWT, this identifier is urn:ietf:params:oauth:token-type:jwt.

An example successful response is as follows:

It is useful to be able to make a statement that one party is authorized to act on behalf of another party. This can be done by having the party being acted for issue a Security Token containing a Claim identifying the party that will act for it as an authorized actor. This statement can also optionally identify scopes in which the actor is eligible to act through another Claim. The following Claims are defined for use in JWTs for these purposes: Security Token that identifies a party that is asserted as being eligible to act for the party identified by the JWT containing this Claim. OPTIONAL. Array of strings, each of which represents a service context for which the actor is asserted as being eligible to act for the party identified by the JWT containing this Claim. The array MUST contain at least one scope value. The definition of these contexts is outside the scope of this specification. The JWT issued by the party being acted for MUST be signed so the identity of the party being acted for can be validated unless the identity of the party being acted for is known to the Authorization Server by other means; in that case, the JWT can use the alg value none.

Implementations of the specification MUST implement support for using JWTs as the Security Tokens. Other Security Token types MAY be supported.

The urn:ietf:params:oauth:grant-type:security-token-request Grant Type is to be registered in the "OAuth URI" registry established by "An IETF URN Sub-Namespace for OAuth". The scopes, act_as, act_as_type, on_behalf_of, and on_behalf_of_type Claims are to be registered in the IANA "JSON Web Token Claims" registry established by .

All of the normal security issues, especially in relationship to comparing URIs and dealing with unrecognized values, that are discussed in JWT also apply here. In addition, on-behalf-of introduces its own unique security issues. Any time one principal is delegated the rights of another principal, the potential for abuse is always a concern. That is why use of the scopes member is suggested. The scope values restrict the contexts in which the delegated rights can be exercised.

Microsoft

mbj@microsoft.com http://self-issued.info/

Ping Identity

ve7jtb@ve7jtb.com

Nomura Research Institute

n-sakimura@nri.co.jp

Ping Identity Salesforce.com Microsoft Microsoft

The following decisions need to be made and updates on this spec performed: Should we say anything about proof of possession of the target party's key in the On-Behalf-Of case beyond specifying the use of the actor Claim? Revise the text in the On-Behalf-Of vs. Impersonation Semantics section to better align the terminology used with the semantics specified. Address the sources of potential terminological confusion discussed in John Bradley's review comments. Add examples illustrating concrete uses of act-as and on-behalf-of.

The authors wish to thank Brian Campbell and John Bradley for their reviews of the specification.

[[ to be removed by the RFC Editor before publication as an RFC ]] -02 Enabled use of Security Token types other than JWTs for act_as and on_behalf_of request values. Referenced the JWT and OAuth Assertions RFCs. -01 Updated references. -00 Created initial working group draft from draft-jones-oauth-token-exchange-01.