Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VALID does not precede J/CWT processing rules #81

Merged
merged 2 commits into from
Nov 16, 2023
Merged

VALID does not precede J/CWT processing rules #81

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
56d03d4
VALID does not precede J/CWT processing rules
panva Nov 8, 2023
d79ea7c
Update draft-ietf-oauth-status-list.md
panva Nov 16, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions draft-ietf-oauth-status-list.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -187,6 +187,8 @@ Status types described by this specification comprise:

The issuer of the Status List Token MUST choose an adequate "bits" (bit size) to be able to describe the required Status Types for the application.

The processing rules for JWT or CWT precede any evaluation of a referenced tokens 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.

# Example JWT Status Lists

## Example Status List with 1-Bit Status Values
Expand Down Expand Up @@ -446,6 +448,7 @@ To indicate that the content is an CWT-based Status List:

We would like to thank
Brian Campbell,
Filip Skokan,
Francesco Marino,
Guiseppe De Marco,
Kristina Yasuda,
Expand Down