Multi-Subject JSON Web Token (JWT)

Introduction JSON Web Token (JWT) is a mechanism that is used to transfer claims between two parties across security domains. Nested JWT is a JWT in which the payload is another JWT. The current specification does not define a means by which the enclosing JWT could have its own Claims Set, only the enclosed JWT would have claims. There are a number of use cases where there is a need to represent multiple related subjects in one JWT; a primary subject and a related secondary subject. This specification defines a mechanism for including multiple subjects in a JWT. A primary subject in an enclosing JWT with its own claims, and a related secondary subject in a nested JWT with its own claims.

Terminology 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 .

Use Cases The following are few use cases that might benefit from such a concept, that fall into two different categories:

One Issuer Category In the following cases, both JWTs are issued by the same issuer.

Primary Subject with Secondary Authority Subject A primary subject with a related secondary subject that has authority over the primary subject, e.g. Child/Parent, Pet/Owner. The secondary user (e.g., parent) logs in to an application (e.g., pharmacy application), gets redirected to the authorization server, authenticates, and asks for permission to access resources (e.g., medication) for the primary subject (e.g., child). The authorization server then issues a JWT with the primary subject in the enclosing JWT and the secondary subject in the nested JWT.

Multiple Primary Subjects Two or more primary related subjects e.g. a married couple. The authorization server is setup to provide one of the subjects with permissions to access the other related subject resources. One user (e.g., wife) logs in to a application (e.g., pharmacy application), gets redirected to the authorization server, authenticates, and asks for permission to access resources (e.g., medication) for the other primary subject (e.g., husband). The authorization server then issues a JWT with the primary subject in the enclosing JWT and the other primary subject in the nested JWT.

Delegation of Authority A primary subject delegates authority over a resource to a secondary subject who acts on behalf of the primary subject, as defined in .

Multiple Issuers Category In the following cases, the JWTs are issued by different issuers.

STIR defines a PASSporT, which is a JWT, that is used to verify the identity of a caller in an incoming call. The PASSporT Extension for Diverted Calls draft uses a nested PASSporT to deliver the details of an incoming call that get redirected. An authentication service acting for a retargeting entity generates new PASSporT and embeds the original PASSporT inside the new one. When the new target receives the nested PASSporT it will be able to validate the enclosing PASSporT and use the details of the enclosed PASSporT to identify the original target. In this case, the original JWT is issued by the calling service, and the new enclosing JWT is issued by the retargeting service.

Network Service Mesh (NSM) Network Service Mesh [NSM] is a mechanism that maps the concept of a service mesh in Kubernetes to L2/L3 payloads. NSM GRPS messages may pass through multiple intermediaries, each of which may transform the message. Each intermediary is expected to create its own JWT token, and include a claim that contains the JWT it received with the message it has transformed. In this case, the original JWT is issued by the entity sending the initial message, and the new enclosing JWT is issued by the intermediate entity.

Authorization Request To allow the AS to differentiate between an authorization request for a single subject and an authorization request for multiple subjects, this document defines the following parameter:

issuer-hint:

A hint to the AS that the request is for a multi-subject token, which can take one of two values:

Internal: Indicates that the AS handling the current request will be issuing both enclosing and enclosed JWTs.

External: Indicates that an external entity has issued the JWT to be enclosed, which will be carried in access_token parameter.

If the access_token query parameter is included in the request, then the AS SHOULD embed the provided token in the issued token, if the issuer-hint has the "External" value.

JWT Content The payload of the enclosing JWT is JSON object that contains the Claims Set of the primary subject, and one new claim that is used to hold the enclosed JWT and its relation to the primary subject. This document defines a new claim, "rsub" (Related Subject) Claim, that is used to contain the enclosed JWT and its relation to the primary subject. The "rsub" contains two claims:

rel:: Defines the relationship between the enclosed JWT and the enclosing JWT. It can take one of the values defined in section

jwt:: Contains the enclosed JWT.

Token Relationship The following relathionship types are defined by this specification:

urn:ietf:params:oauth:subject-type:authority: Indicates that the subject in the enclosed JWT has authority over the subject in the enclosing JWT.
: This URN could be used in the child/parent use case described in .

urn:ietf:params:oauth:subject-type:primary: Indicates that the subject in the enclosed JWT is related primary subject
: This URN could be used in the married couple use case described in .

urn:ietf:params:oauth:subject-type:actor: Indicates that the subject in the enclosed JWT is acting on behalf of the primary subject
: This URN could be used in the delegation use case described in .

urn:ietf:params:oauth:subject-type:original: Indicates that the subject in the enclosed JWT is the original JWT that resulted in the primary subject JWT
: This URN could be used in all the use cases described in .

Example The following example is for a multi-subject token that represents a child/parent relashionship. The enclosing JWT represents the primary user, the child in this case, and the enclosed token in the "rsub" claim represents the secondary user, the parent in this case. In this use case, both JWTs are issued by the same entity handling the authorization request.

Security Considerations The existing security considerations apply to the use cases where the JWTs are issued by the same entity. Allowing more than one subject to access the same account might open the door for potential abuse. Care must be taken to ensure that when a secondary subject is added to an account that an adequate approval process is in place. In the multiple issuers use cases, the entity handling the incoming authorization request that contains a JWT MUST validate the token and ensure that it is coming from a trusted entity, before attempting to embed that JWT into a new multi-subject JWT issued by the AS.

IANA Considerations TODO

Acknowledgments TODO