SAMPLE JWT — EdDSA, Valid
An EdDSA (Ed25519) token with a fixed 64-byte signature and the same claim set as the RS256 reference. EdDSA signing is deterministic, so this token is reproducible in a way an ES256 one could never be.
eyJhbGciOiJFZERTQSIsInR5cCI6IkpXVCIsImtpZCI6Im5vdnVzLXA3LWVkMjU1MTktMjAyNiJ9.eyJpc3MiOiJodHRwczovL2lzc3Vlci5wa2kuc2FtcGxlLmV4YW1wbGUvIiwic3ViIjoidXNlci1zYW1wbGUtMDAwMSIsImF1ZCI6Im5vdnVzLXA3LXNhbXBsZS1hcGkiLCJpYXQiOjE3NjcyMjU2MDAsIm5iZiI6MTc2NzIyNTYwMCwiZXhwIjoyMDgyNzU4NDAwLCJqdGkiOiJub3Z1cy1wNy1zYW1wbGUtMDAwMSIsIm5hbWUiOiJTYW0gUml2ZXJhIChTQU1QTEUpIiwic2NvcGUiOiJyZWFkOnNhbXBsZSJ9.MS4shQtLznXs9iLmUlQfrFcKxC_F5ZH14pEcjsxZ2K8uA74zC9Qb9-kIkUXXVhbeX7eRYg60hs35bYkc5FskAA
Specifications
- Alg
- EdDSA
- Curve
- Ed25519
- Kid
- novus-p7-ed25519-2026
- Signature Bytes
- 64
- Valid
- true
- Sub
- user-sample-0001
- Sample Only
- true
- Seed
- 70117
Testing contract
Expected to pass- Scenario
- Verify the token against the OKP key in the p7 JWK set.
- Expected result
- The 64-byte Ed25519 signature verifies and the claim set matches the RS256 reference token's.
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 — EdDSA, Valid” is a deterministic Novus Examples fixture for JWT / JWKS testing. Unsigned and SAMPLE-signed JWT variants plus JWKS documents — published sample material only, for auth parser tests.
Documented properties for this file: seed 70117. 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-eddsa-valid.jwt | base64 -d; echo
cut -d. -f2 jwt-eddsa-valid.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.
- jwtJWT (HS256) — SAMPLESAMPLE JWT with alg=HS256 for auth parsers and algorithm-handling tests. Published sample material only.
- jwtJWT (HS384) — SAMPLESAMPLE JWT with alg=HS384 for auth parsers and algorithm-handling tests. Published sample material only.
- jwtJWT (HS512) — SAMPLESAMPLE JWT with alg=HS512 for auth parsers and algorithm-handling tests. Published sample material only.
- jwtJWT (none) — SAMPLESAMPLE JWT with alg=none for auth parsers and algorithm-handling tests. Published sample material only.
Generated by generation/security_p7.py. Free for any use, no attribution required — license.