# Unable to automatically download public key from JWT

**URL:** <https://community.auth0.com/t/unable-to-automatically-download-public-key-from-jwt/195234>\
**Category:** JWT.io\
**Created:** [December 5, 2025, 5:52pm UTC](https://community.auth0.com/t/unable-to-automatically-download-public-key-from-jwt/195234 "2025-12-05T17:52:50Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![hippogamesunity](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/hippogamesunity/32/59574_2.png) [@hippogamesunity](https://community.auth0.com/u/hippogamesunity)\
**Post date:** [December 5, 2025, 5:52pm UTC](https://community.auth0.com/t/unable-to-automatically-download-public-key-from-jwt/195234/1 "2025-12-05T17:52:50Z")

</div>

Hello! Why cannot [jwt.io](http://jwt.io) download a public key?

> **[JSON Web Tokens - jwt.io](https://www.jwt.io/#token=eyJhbGciOiJSUzI1NiIsImtpZCI6IjUxY2NmMGQ0ZjA5M2MwMjI5ZTVmMzA4MjIwMjk3NDY3IiwidHlwIjoiSldUIn0.eyJpc3MiOiJodHRwczovL3BsYXlpZC5vcmciLCJhdWQiOiIwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMCIsInN1YiI6MSwibmFtZSI6IkhpcHBvIEdhbWVzIiwiZW1haWwiOiJVbmF2YWlsYWJsZSBmb3IgRXhhbXBsZSBhcHAuIiwicGxhdCI6MTYzLCJpYXQiOjE3NjQ5NTM4NjIsImV4cCI6MTc2NDk2MTA2Miwic3RhdGUiOiJjZjQxNzU0NzhlOTc0OTkxOWI5MTAzNDdjYzRkYTQyYyIsIm5vbmNlIjpudWxsfQ.Do_6OAR4ec2xwlpNdiEZPBtoQ72ZgyD_0T7OAD8cW0_t5DpCflVQe-KOwPNbgh635GxLKJHz7VawnT6erLCytH7SHgd0p9FmY0JJCmiY3PKMm8T22NbMJ-IbHUuO5xffZP6J-9L4337RSawNS4E_mI4obHgQsb-XH_4sESlKl6sIJ0bTtN_Qcft4XJgUOJJsFnYBWOhRJDXqtvfQHkPrdz0dv9W7t257y5oFTcsh4Ow0ak4XbCqFiSzVxUstbApru_4rYpWUsvlHcRO60G8lkYHy695V13hneQv66xBmKjFqBF5Yg-je3mPbrvSlqa7DtDYz4KKsTWybmkKOC07A6Q)**
>
> JSON Web Token (JWT) is a compact URL-safe means of representing claims to be transferred between two parties. The claims in a JWT are encoded as a JSON object that is digitally signed using JSON Web Signature (JWS).

When debugging, it loads [https://playid.org/.well-known/openid-configuration](https://playid.org/.well-known/openid-configuration), then [https://playid.org/.well-known/jwks](https://playid.org/.well-known/jwks) where the mentioned key is present. But it says “Unable to automatically download public key from JWT”.

---

<div class="post-metadata">

**Author:** ![dawid.matuszczyk](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/dawid.matuszczyk/32/74550_2.png) [@dawid.matuszczyk](https://community.auth0.com/u/dawid.matuszczyk)\
**Post date:** [December 31, 2025, 3:34pm UTC](https://community.auth0.com/t/unable-to-automatically-download-public-key-from-jwt/195234/2 "2025-12-31T15:34:04Z")

</div>

Hi @hippogamesunity

Welcome to the Auth0 Community!

Thank you for bringing that to us. I’ll report that issue to our engineering team behind [JWT.io](http://JWT.io) and will update you as soon as I have more information.

Thanks!  
Dawid

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [January 14, 2026, 3:34pm UTC](https://community.auth0.com/t/unable-to-automatically-download-public-key-from-jwt/195234/3 "2026-01-14T15:34:24Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.

---

<div class="post-metadata">

**Author:** ![gerald.czifra](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/gerald.czifra/32/75301_2.png) [@gerald.czifra](https://community.auth0.com/u/gerald.czifra)\
**Post date:** [October 15, 2026, 9:05pm UTC](https://community.auth0.com/t/unable-to-automatically-download-public-key-from-jwt/195234/4 "2026-10-15T21:05:49Z")

</div>

Hi everyone,

We are optimizing the content on our Community forum to keep information relevant, in case others encounter the same issue or behaviour.

I understand you are facing the “Unable to automatically download public key from JWT”  
message when attempting to download the public key during debugging.

**The Root Cause: Missing CORS Headers**

The reason **[jwt.io](http://jwt.io)** cannot automatically download the public key from `https://playid.org/.well-known/jwks` is a **Cross-Origin Resource Sharing (CORS)** restriction .

When you paste a JWT into the browser-based debugger at **[jwt.io](http://jwt.io)**, the JavaScript running in your browser attempts to perform a client-side `fetch` (an XHR request) to retrieve your OpenID configuration and JWKS .

Because the request originates from `https://jwt.io` and is targeting a different domain (`https://playid.org`), the browser enforces CORS rules :

1. The browser sends a request to `playid.org`’s endpoints .

2. For the browser to allow [jwt.io](http://jwt.io)’s JavaScript to read the response, `playid.org` **must return the following HTTP response header** :

If your server hosting `https://playid.org/.well-known/jwks` (and the OpenID configuration) does not return this header, your browser blocks the request internally for security . The network request itself may succeed with a `200 OK` status when inspected directly, but [jwt.io](http://jwt.io)’s code is legally blind to it, resulting in the generic message: **“Unable to automatically download public key from JWT”**.

* * *

**Recommended fix**

To resolve this issue, you must configure CORS on the server or gateway hosting **[playid.org](http://playid.org)**.

**1. Enable CORS Headers on your Server**

Ensure that both of your discovery endpoints return the appropriate wildcard CORS headers :

- **Endpoints requiring CORS:**

- **Headers to add:**

**2. Handle HTTP OPTIONS (Preflight) Requests**

Browsers will sometimes send an HTTP `OPTIONS` request (a preflight request) to check permission before fetching. Make sure your server is configured to respond to `OPTIONS` requests on those endpoints with a `200 OK` status and the CORS headers above— **without requiring authentication**.

**Common Pitfall:** Many framework-level CORS configurations are only applied to custom API routes and silently exclude the automatic static pathing under `.well-known/` . Be sure your reverse proxy (such as Nginx, Cloudflare, or an API gateway) is explicitly configured to inject these headers for the `.well-known` path .

* * *

**Temporary Workaround for Quick Debugging**

If you cannot modify the server configuration immediately, you can still verify your signatures in [jwt.io](http://jwt.io):

1. Fetch your JWKS payload directly (e.g., using `curl https://playid.org/.well-known/jwks` or by opening it in a new browser tab).

2. Copy the single JSON Web Key (JWK) object from the `keys` array.

3. Paste that JWK object directly into the **Public Key** input box in the bottom-right corner of the [jwt.io](http://jwt.io) debugger.

We hope this helped provide some insight!

Have a great one,  
Gerald
