OAuth Token Introspection — SAMPLE
SAMPLE RFC 7662-style token introspection response for auth middleware tests.
{
"active": true,
"scope": "openid profile",
"client_id": "novus-sample-client",
"username": "sam.rivera.sample",
"token_type": "Bearer",
"exp": 1767312000,
"iat": 1767225600,
"sub": "user-sample-001",
"aud": "novus-api-sample",
"iss": "https://auth.sample.example/"
}
Specifications
- Active
- true
- Sample Only
- true
Testing contract
Expected to pass- Scenario
- Exercise OAuth Token Introspection — SAMPLE in its oauth workflow. SAMPLE RFC 7662-style token introspection response for auth middleware tests.
- Expected result
- top-level keys are active, scope, client_id, username, token_type, exp, iat, sub, aud, iss; selected values: {"active": true, "exp": 1767312000, "iat": 1767225600}. Declared feature checks: active=True.
What is a .json file?
JSON (JavaScript Object Notation) is a lightweight, text-based data-interchange format representing objects, arrays, strings, numbers, booleans, and null. It is language-independent, human-readable, and the dominant format for web APIs and configuration. It requires a single well-formed root value.
How to use this file
Use an example JSON file to test parsers and serializers, schema validation, Unicode and number-precision handling, and API request or response processing.
How to use this file for testing
“OAuth Token Introspection — SAMPLE” is a deterministic Novus Examples fixture for JWT / JWKS testing, API testing. Unsigned and SAMPLE-signed JWT variants plus JWKS documents, published sample material only, for auth parser tests.
Documented properties for this file: JSON · 301 bytes. 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
import json
with open("token-introspection.json") as f:
data = json.load(f)
print(type(data), len(data))Related files
- jsonOAuth Device Code Response — SAMPLESAMPLE OAuth device-authorization response for device-flow client tests.
- jsonOAuth Token Error — SAMPLESAMPLE OAuth error JSON for token-endpoint failure handling.
- jsonOAuth Token Response — SAMPLESAMPLE OAuth 2.0 token endpoint JSON with access, refresh, and id_token fields.
- jsonOpenID Provider Configuration — SAMPLESAMPLE OpenID Connect discovery document for OIDC client and metadata parsers.
- jsonSAMPLE JWS — Flattened JSON SerializationThe single-signature flattened JSON form of the exact same RS256 token shipped in compact serialization. Both encodings must verify to the identical payload, which is the round-trip this pair is for.
- jsonSAMPLE JWS — General JSON SerializationOne payload carrying two independent signatures — RS256 and EdDSA — in the General JSON serialization that the compact form cannot express. Multi-signature handling is the part of RFC 7515 most libraries never implemented.
Generated by generation/security_wave_g.py. Free for any use, no attribution required, license.