Skip to content

Commit 57a13e8

Browse files
authored
clarify that Status List validation SHOULD not be performed if Refere… (#348)
* clarify that Status List validation SHOULD not be performed if Referenced Token validation is deemed invalid already * Update draft-ietf-oauth-status-list.md * update history entry
1 parent 515fa86 commit 57a13e8

1 file changed

Lines changed: 5 additions & 1 deletion

File tree

draft-ietf-oauth-status-list.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -667,7 +667,7 @@ Content-Type: application/statuslist+jwt
667667

668668
## Validation Rules
669669

670-
Upon receiving a Referenced Token, a Relying Party MUST first perform the validation of the Referenced Token - e.g., checking for expected attributes, valid signature and expiration time. The processing rules for Referenced Tokens (such as JWT or CWT) MUST precede any evaluation of a Referenced Token's status. For example, if a token is evaluated as being expired through the "exp" (Expiration Time) but also has a status of 0x00 ("VALID"), the token is considered expired. As this is out of scope for this document, this validation is not described here, but is expected to be done according to the format of the Referenced Token.
670+
Upon receiving a Referenced Token, a Relying Party MUST first perform the validation of the Referenced Token - e.g., checking for expected attributes, valid signature and expiration time. The processing rules for Referenced Tokens (such as JWT or CWT) MUST precede any evaluation of a Referenced Token's status. For example, if a token is evaluated as being expired through the "exp" (Expiration Time) but also has a status of 0x00 ("VALID"), the token is considered expired. If the validation procedures for the Referenced Token determine it is invalid, no further procedures regarding Status List MUST be performed, e.g. fetching a Status List Token, unless the Referenced Token procedures or the use case require further evaluation.
671671

672672
If this validation is not successful, the Referenced Token MUST be rejected. If the validation was successful, the Relying Party MUST perform the following validation steps to evaluate the status of the Referenced Token:
673673

@@ -1821,6 +1821,10 @@ CBOR encoding:
18211821

18221822
\[\[ To be removed from the final specification \]\]
18231823

1824+
-17
1825+
1826+
* clarify that Status List validation MUST not be performed if Referenced Token validation is deemed invalid already
1827+
18241828
-16
18251829

18261830
* change http status codes & query parameter wording for the historical resolution

0 commit comments

Comments
 (0)