Composite Token Claims

Claims Composition claims contain one or more claim sets. In CWTs without composition claims, there is exactly one set of claims, so the acceptability of the claim set decides the acceptability of the CWT. However, this document defines multiple sets of claim sets, so it instead refers to accepting or rejecting claim sets. If the primary claim set is unacceptable, the CWT is unacceptable and MUST be rejected. Some applications use tokens to convey information. For example, a token might simply have a subject claim that identifies the bearer and the relying party simply uses that as information, not necessarily as a means by which to provide or deny access or make some other kind of decision. In this context, the token simply describes all situations in which the token would accurately describe that situation. Composition claims can be nested to an arbitrary level of depth. Implementations MAY limit the depth of composition nesting by rejecting CWTs with too many levels but MUST support at least four levels of nesting.

Logical Claims These claims identify one or more sets of claims in a logical relation. The type of these claims is array and the elements of the array are maps that are themselves sets of claims. For the following CDDL, Claims-Set is a map of claims as defined in . It is described informatively in [draft-ietf-rats-eat] Appendix D.

or (Or) Claim The "or" (Or) claim identifies one or more sets of claims of which at least one is acceptable. If every set of claims in an "or" claim would, when considered with all the other relevant claims, result in the claim set being rejected, the claim set containing the "or" claim MUST be rejected. Use of this claim is OPTIONAL. The Claim Key [add key number] is used to identify this claim. The "or" (OR) claim is described by the following CDDL: or-claim-value ) or-claim-label = TBD or-claim-value = [ + Claims-Set ] ]]>

nor (Not Or) Claim The "nor" (Nor) claim identifies one or more sets of claims of which none are acceptable. If any set of claims in a "nor" claim would, when considered with all other relevant claims, result in the claim set being accepted, the claim set containing the "nor" MUST be rejected. This is the logical negation of the "or" claim. Use of this claim is OPTIONAL. The Claim Key [add key number] is used to identify this claim. The "nor" (NOR) claim is described by the following CDDL: nor-claim-value ) nor-claim-label = TBD nor-claim-value = [ + Claims-Set ] ]]>

and (And) Claim The "and" (And) claim identifies one or more sets of claims of which all are acceptable. If any claim in an "and" claim would, when considered with all other relevant claims, result in the claim set being rejected, the claim set containing the "and" claim MUST be rejected. The "and" claim is often unnecessary because a given claim set is only accepted when all its claims are acceptable. However, CBOR maps cannot have duplicate keys, so claims cannot be repeated more than once. The "and" claim is useful for claims that may be claimed multiple times, including the "or" and "nor" claims. Use of this claim is OPTIONAL. The Claim Key [add key number] is used to identify this claim. The "and" (AND) claim is described by the following CDDL: and-claim-value ) and-claim-label = TBD and-claim-value = [ + Claims-Set ] ]]>

Examples These logical claims can be used to describe more complex relationships between claims. For example, the following claim set describes a token with multiple subject claims. This token describes a situation where either of the two subjects must be true, but the issuer is not disclosing which one must be true or even whether the two subjects are genuinely different. A relying party that receives this token knows that bearer claims to be both George and Harriet and if either subject is acceptable, the token is acceptable. The "nor" claim is useful both as a logical negation, even when only one claim is present. For example, consider the following claim set: This token is intended for any audience except "example.com". Complex relationshops can also be described using the claims in combination. The "geohash" claim describes a geographical region. For example: This token describes an audience of "https://example.com" and a region described by the geohash of "9q8yy" that does not include the region described by "9q8yy9" or "9q8yyd". And if a very complex relationship is required, the "and" claim can be used to combine multiple claims. For example, consider the following claim set: This admittedly contrived example describes a token that is valid for both George and Harriet and is intended for both https://example.com and https://example.net. It is a bit contrived because the "aud" claim already describes a list of acceptable audiences. The use of the "and" claim is required in order to effectively repeat the "or" claim, because a single claim set cannot contain the same claim twice.

crit (Critical) Claim The "crit" (Critical) claim lists the claims required to process this claim set. The type of this claim is array and the elements of the array are strings, negative integers, or unsigned integers. The elements of the array correspond to claims that MUST be present in the token. If a claim listed in the "crit" claim is present in a claim set and the processor cannot process the claim for any reason, the claim set MUST be rejected. If a claim listed in the "crit" claim is not present in a claim set, the claim set MUST be rejected. If a "crit" claim is present in a claim set, a processor SHOULD consider claims it does not understand to be acceptable if they are not present in the "crit" claim, unless application-specific processing defines otherwise. That is, when a "crit" claim is present, any claims not listed may by default be assumed to be non-critical. Use of this claim is OPTIONAL. The Claim Key [add key number] is used to identify this claim.

Example A "crit" claim can be used in conjunction with logical claims to condition a portion of the token on the ability to process a claim: This example assumes the existance of some kind of claim in the private space that a relying party may or may not be able to process. This token claims that the subject is in the described region and also that a private claim is present and that the relying party must be able to verify at least one of those claims, but it does not need to be able to process both.