Settings

The token

The keys

Result

How it works

Signature and claims are two different checks

A token can have a perfect signature and still be rejected because it has expired, is not yet valid, or is for another audience. JWKS shows the signature verdict and the claim checks separately, so you know which one to fix. It never fetches the token's jku and nothing is uploaded, so it is safe for a live credential. To decode a token without keys, JOT.

The guide: JWT kid not found in the JWKS

Questions people ask about JWKS

What is a JWKS, and what is the kid for?

A JSON Web Key Set is a JSON object with a keys array, each entry one public key written as a JWK: its type in kty, its numbers (n and e for RSA; crv, x and y for an elliptic curve) and usually a kid, alg and use. An issuer publishes the set at the jwks_uri named in its OpenID configuration, often /.well-known/jwks.json.

The kid in a token’s header names the key in that set which signed it, so an issuer can rotate keys with the old and new published side by side. Here the key with the matching kid is used; if none matches, the set’s only key, or the only key whose alg is unset or agrees with the token’s.

Why does it say the token’s kid is not in the key set?

Because no key in the set you pasted carries that kid, and there is more than one key it could otherwise be. The usual causes are a rotation (the set is older than the token, or the old key has already been taken out), a token from another environment or tenant, or a set copied from the wrong issuer. Open the issuer’s jwks_uri again and paste what it serves now.

Which signing algorithms can it check?

RS256, RS384 and RS512; PS256, PS384 and PS512; ES256, ES384 and ES512 on the P-256, P-384 and P-521 curves; and HS256, HS384 and HS512 when you give the shared secret. Any other alg, EdDSA included, is reported as unsupported rather than guessed at.

A token whose header says "alg": "none" is refused outright: it has no signature, and accepting one is a classic way verifiers have been fooled. If the chosen key carries an alg that differs from the token’s, that is reported too, before any signature is checked.

The signature verifies, so why is the token still rejected?

Because a good signature only proves who made the token, not that it is still good for you. A verifier also checks the claims: exp (expiry), nbf (not before), the audience in aud and the issuer in iss. They are shown here separately from the signature verdict, with 60 seconds allowed for clocks that disagree.

Fill in the expected audience and issuer to have those compared; aud may be a single string or a list, and matches if your value is in it. A time claim written as a string, "1700000000" rather than 1700000000, is flagged, because a strict library rejects it. A token with no exp is noted as never expiring.

How do I verify an HS256 token?

Paste the shared secret in the secret field. HS256 is an HMAC: the same secret both signs and verifies, so there is no public key and no JWKS to fetch. It also means anyone holding the secret can make tokens of their own, so treat it as a password.

The secret is used exactly as typed, as UTF-8 text. If your service stores the secret base64-encoded and decodes it before signing, the bytes that signed the token are the decoded ones, and pasting the base64 text will not verify.

Can it fetch the keys from the issuer for me?

No. It does not fetch a JWKS and never follows a jku or x5u URL named in the token’s header. Open the issuer’s jwks_uri in another tab and paste the JSON. That refusal is also good practice in a real verifier: trusting a key address written inside the token lets whoever wrote the token choose the key that checks it.

Can I paste a PEM public key instead of a JWK?

No. The keys box takes JSON only: a whole set ({"keys":[...]}), a bare array of JWKs, or a single JWK with its kty. A PEM file beginning -----BEGIN PUBLIC KEY----- has to be converted to a JWK first. To read a token’s header and payload without any key at all, use JOT.

Doing this often? OBSCURA Umbra edits the service that issues or checks the tokens, and runs JavaScript, TypeScript and Python in a sandbox. Everything is US$5 a month or US$48 a year.