Skip to content
AdminKit

JWKS (JSON Web Key Set)

What is JWKS (JSON Web Key Set)?

A JWKS (JSON Web Key Set) is a JSON object publishing an authorization server's current public keys, each one a JSON Web Key, so a resource server can verify a JWT's signature without a hardcoded key. The AdminKit MCP & Agent Gateway, which Netbase deploys and runs for customers, validates OAuth tokens against a server's JWKS the same way.

By AdminKit team, Netbase JSC · Updated

A JSON Web Key Set (JWKS) is a JSON object, defined by the JWK Set structure in RFC 7517, containing a single “keys” member whose value is an array of JSON Web Keys — each one a public key (or, less commonly, a shared secret) represented as JSON, carrying fields like its key type, intended use, and a key ID (“kid”) — the registered values for these fields live in IANA’s JSON Object Signing and Encryption (JOSE) registry. An authorization server typically publishes its JWKS at a URL referenced by its own configuration — the jwks_uri field in its OAuth 2.0 Authorization Server Metadata, defined in RFC 8414 — so any resource server that receives a JWT it issued can fetch the current set of valid public keys, match the JWT header’s kid to the right entry, and verify the token’s signature without that key ever having been shared out of band or hardcoded into the resource server. OpenID providers advertise the same document through the jwks_uri field that OpenID Connect Discovery 1.0 makes required in provider metadata, pointing to the JWK Set holding the signing keys relying parties use to validate signatures. Publishing a set rather than a single key is what makes key rotation possible without downtime: the authorization server can add a new signing key to the published set, start using it for newly issued tokens, and only remove the old key once every token it signed has expired, so a resource server that re-fetches the JWKS periodically never has to be updated by hand to keep verifying correctly — Auth0’s own JWKS documentation walks through this same rotation-without-downtime pattern.

AdminKit groups jWKS (JSON Web Key Set) under its AI agents & MCP cluster — browse the AdminKit glossary index for other related terms.

Frequently asked questions

What does a JWKS actually contain?

A JSON object with a single "keys" member whose value is an array of JSON Web Keys, each one a public key (or, less commonly, a shared secret) carrying its key type, intended use and a key ID.

How does a resource server find an authorization server's JWKS?

Typically through the jwks_uri field published in the authorization server's OAuth 2.0 Authorization Server Metadata document, defined in RFC 8414.

Why publish a set of keys rather than a single key?

It makes key rotation possible without downtime -- a new signing key can be added and used for new tokens while old tokens still verify until the old key is finally removed.