JWKS Metadata Inspector

Summarizes each local JWKS key's kid, kty, use, key_ops, alg, certificate count, and presence of private fields. It does not export PEM or validate key material.

Jwks Inspector · Client runtimeSandboxed
Formatted results will render here in real time.

About this jwks metadata inspector

Summarizes each local JWKS key's kid, kty, use, key_ops, alg, certificate count, and presence of private fields. It does not export PEM or validate key material Validates and converts interface schemas client-side without transmitting private endpoint specifications.

API contract & interface schema logic

Lists each key’s kid, kty, use, alg, and whether private fields are present. It does not reconstruct or export public keys as DER or PEM.

Worked schema conversion scenario

Scenario: A security engineer inspects a local JWKS and lists key metadata without exporting PEM keys.

Sample input:

{"keys": [{"kty": "RSA", "kid": "key_2026", "use": "sig", "n": "u1...qQ", "e": "AQAB"}]}

Processing: Lists kid, kty, use, key_ops, alg, certificate count, and presence of private fields; it does not validate key material.

Illustrative output:

[ { "kid": "key_2026", "kty": "RSA", "use": "sig", "key_ops": [], "alg": "unspecified", "x5cCount": 0, "hasPrivateMaterial": false } ]

Schema version & syntax constraints

The top-level keys field must be an array; a missing or non-array field is an input error, while an empty array returns an empty list. No key material is reconstructed, exported as PEM/DER or cryptographically validated.

API specifications and schema models in JWKS Metadata Inspector reflect OpenAPI and JSON Schema standards. Verify generated schemas against your runtime validator.

Client-side schema processing boundary

Schema analysis and protocol mapping in JWKS Metadata Inspector execute locally in the browser tab without uploading endpoint definitions.

OpenAPI Specification & JSON Schema standards

OpenAPI Specification standards and JSON Schema draft definitions:

JWKS Metadata Inspector verification · Audit standards

How to use it

  1. Paste JWKS JSON with a keys array.
  2. List each key’s kid, kty, use, alg and whether selected private fields are present.
  3. Read the metadata array.

Frequently asked questions

What does JWKS Inspector summarize?+

It reads a JSON keys array and maps each item to kid, kty, use, alg and hasPrivateMaterial. Missing kid or kty become the literal marker (missing), and missing use or alg becomes unspecified.

Can you show an input and its result?+

A public RSA signing key and an EC entry containing d produced two rows. The RSA row was not private, while the EC row was flagged hasPrivateMaterial true.

Which JWK validation is not performed?+

It does not validate base64url values, key parameters, curves, modulus size, certificates, thumbprints, key-operation consistency, duplicates, issuer provenance, JWKS HTTP cache headers or cryptographic usability.

Does a private-material flag make a key safe?+

No. The flag checks whether d, p, q or k is truthy in each submitted key object. It does not protect the input, remove sensitive material, verify a key or establish secure publication.