reverse-skills-max: initial public release (restored, redacted, hardened)
This commit is contained in:
@@ -0,0 +1,27 @@
|
||||
# JWT Claim Confusion Checklist
|
||||
|
||||
## First Pass
|
||||
|
||||
- Token form: JWS, JWE, nested token, detached signature, or bearer wrapper
|
||||
- Header fields: `alg`, `kid`, `typ`, `cty`, `jku`, x5u-like references, embedded keys
|
||||
- Claim fields: `iss`, `aud`, `sub`, `exp`, `nbf`, `iat`, tenant, role, scope, custom privilege claims
|
||||
|
||||
## Validation Chain To Reconstruct
|
||||
|
||||
1. Token parser invoked
|
||||
2. Key source selected
|
||||
3. Signature or decryption step performed
|
||||
4. Claim validation and normalization applied
|
||||
5. App session or privilege accepted
|
||||
|
||||
## Evidence To Keep Together
|
||||
|
||||
- Header side: fields, key source, lookup behavior, cache or remote key material
|
||||
- Claim side: issuer, audience, subject, roles, scopes, time claims, normalization rules
|
||||
- Acceptance side: session cookie, route unlock, backend action, or privilege-bearing claim usage
|
||||
|
||||
## Common Pitfalls
|
||||
|
||||
- Stopping at successful decode without proving authorization acceptance
|
||||
- Focusing on one claim without showing the whole validation chain
|
||||
- Ignoring key lookup or normalization behavior that matters more than the raw claim value
|
||||
Reference in New Issue
Block a user