SAMPLE JWT — RS256, Expired
A correctly signed RS256 token whose exp passed on 2020-01-01. The signature still verifies, so it isolates expiry handling from every other check — including the libraries that validate the signature and then forget to look at exp.
eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCIsImtpZCI6Im5vdnVzLXA3LXJzYS0yMDI2In0.eyJpc3MiOiJodHRwczovL2lzc3Vlci5wa2kuc2FtcGxlLmV4YW1wbGUvIiwic3ViIjoidXNlci1zYW1wbGUtMDAwMSIsImF1ZCI6Im5vdnVzLXA3LXNhbXBsZS1hcGkiLCJpYXQiOjE1Nzc4MzMyMDAsIm5iZiI6MTU3NzgzMzIwMCwiZXhwIjoxNTc3ODM2ODAwLCJqdGkiOiJub3Z1cy1wNy1zYW1wbGUtMDAwMSIsIm5hbWUiOiJTYW0gUml2ZXJhIChTQU1QTEUpIiwic2NvcGUiOiJyZWFkOnNhbXBsZSJ9.r_OpqNQUiQ8bbvYEju9KNiOaD5CPzwaygzqxW9hpQAE-DmeHhkCyypqE0ymPdNLhuoHapaQxi_RUscR8vcv41zIj0xwzjRx6XHzjg8WuhaMQE0_XnaZAEBx5SC4usMrh9ATl4dEGP94oUae4zHrO11zunIGmKGMrGKH7FUg1s7YJbsywVuT55ThvgPt1r_L6uTZjnmx8PQp-OonFtmG08y67Jtqd923uakKAvg91J7m2SaDqRTYD9Uxsh3HYN4tAKq-3dA6izqKwJhAao4cUkp8mZvfmuHd3PVNZ1Fg76AULQqF2yMmLSJzYuoygVAVyM7PAF7V5NPOuDK4O7HPm8A
Specifications
- Alg
- RS256
- Kid
- novus-p7-rsa-2026
- Exp
- 1577836800
- Expired On
- 2020-01-01
- Valid
- false
- Sub
- user-sample-0001
- Sample Only
- true
- Seed
- 70117
Testing contract
Expected to fail- Scenario
- Verify the token with expiry checking enabled and read back the failure reason.
- Expected result
- The signature verifies but validation fails specifically on the exp claim, not on the signature.
What is a .jwt file?
A JWT (JSON Web Token) is a compact, URL-safe token made of three base64url-encoded parts — a header, a payload of claims, and a signature — separated by dots. It is widely used to carry authentication and authorisation claims between services.
How to use this file
Use a sample JWT to test token decoding, claim extraction, and signature verification. Never use an example token's secret in production.
How to use this file for testing
“SAMPLE JWT — RS256, Expired” is a deterministic Novus Examples fixture for JWT / JWKS testing, Error handling. Unsigned and SAMPLE-signed JWT variants plus JWKS documents — published sample material only, for auth parser tests.
Documented properties for this file: seed 70117 · intentionally invalid. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.
This is published, SAMPLE-only security material — never a real secret. Point certificate, key, or token parsers at it, test PEM/DER decoding and PKCS handling, and confirm your tooling reads the documented fields; any sample password is printed on this page.
These JSON fixtures are synthetic SAMPLE auth or tool-call shapes for harnesses — never production secrets or live tokens. Validate schema fields and alg variants against the documented role.
Code examples
cut -d. -f1 jwt-rs256-expired.jwt | base64 -d; echo
cut -d. -f2 jwt-rs256-expired.jwt | base64 -d; echo # payload claimsRelated files
- jwtJWT — Intentionally Invalid SegmentsIntentionally invalid JWT (truncated) for parser error-path tests.
- jwtJWT (HS256 Expired) — SAMPLESAMPLE HS256 JWT with a past exp claim — for expiry-validation harnesses.
- jsonJWKS (Empty Keys) — SAMPLEEmpty JWKS keys array for edge-case JWKS loaders.
- jsonOAuth Error — Insufficient ScopeOAuth 2.0 SAMPLE error JSON (insufficient_scope) for client error-path tests.
- jsonOAuth Error — Invalid ClientOAuth 2.0 SAMPLE error JSON (invalid_client) for client error-path tests.
- jsonOAuth Error — Invalid GrantOAuth 2.0 SAMPLE error JSON (invalid_grant) for client error-path tests.
Generated by generation/security_p7.py. Free for any use, no attribution required — license.