# \#jwks

**URL:** https://community.auth0.com/tag/jwks/150.md

[Latest](https://community.auth0.com/latest.md) · [Categories](https://community.auth0.com/categories.md) · [Tags](https://community.auth0.com/tags.md)

---

## [\[Issue\] Unable to select JWK under JWT SIGNATURE VALIDATION](https://community.auth0.com/t/issue-unable-to-select-jwk-under-jwt-signature-validation/189978)

<div class="topic-metadata">

**Author:** [@Dahventura](https://community.auth0.com/u/Dahventura)\
**Replies:** 1\
**Last updated:** [July 31, 2025, 7:43pm UTC](https://community.auth0.com/t/issue-unable-to-select-jwk-under-jwt-signature-validation/189978 "2025-07-31T19:43:06Z")

</div>

When attempting to validate a JWT, I receive the following error when selecting the JWK public key format from the dropdown menu. Uncaught TypeError: can't access property "some", e.options is undefined

---

## [JWK is not verified in debugger](https://community.auth0.com/t/jwk-is-not-verified-in-debugger/93113)

<div class="topic-metadata">

**Author:** [@jlaudenbach](https://community.auth0.com/u/jlaudenbach)\
**Replies:** 9\
**Last updated:** [November 16, 2022, 4:27pm UTC](https://community.auth0.com/t/jwk-is-not-verified-in-debugger/93113 "2022-11-16T16:27:01Z")

</div>

Hi, I am quite new in this topic, so I just might miss a main thing that is easy to solve. I generated a JWT, private\_key.pem, public\_key.pem and a JWKS. I used the debugger on jwt.io to verify my components. When I u…

---

## [Occasional 5xx errors from Auth0 JWKS endpoint](https://community.auth0.com/t/occasional-5xx-errors-from-auth0-jwks-endpoint/90160)

<div class="topic-metadata">

**Author:** [@anish1](https://community.auth0.com/u/anish1)\
**Replies:** 1\
**Last updated:** [October 8, 2022, 12:10am UTC](https://community.auth0.com/t/occasional-5xx-errors-from-auth0-jwks-endpoint/90160 "2022-10-08T00:10:07Z")

</div>

We have a backend with code similar to the Python quickstart for Auth0 that fetches the JWKS from "https://"+AUTH0\_DOMAIN+"/.well-known/jwks.json". Last week, we were seeing ephemeral errors when hitting this endpoint, i…

---

## [Is the endpoint to get the JWK for token validation rate limited?](https://community.auth0.com/t/is-the-endpoint-to-get-the-jwk-for-token-validation-rate-limited/91483)

<div class="topic-metadata">

**Author:** [@a.saad](https://community.auth0.com/u/a.saad)\
**Replies:** 1\
**Last updated:** [September 28, 2022, 6:08pm UTC](https://community.auth0.com/t/is-the-endpoint-to-get-the-jwk-for-token-validation-rate-limited/91483 "2022-09-28T18:08:16Z")

</div>

Hello, I have a backend service that needs to validate tokens. I read this guide and it mentions that I should hit the endpoint: https://your-tenant.auth0.com/.well-known/jwks.json in order to retrieve the public key.…

---

## [Node-jwks-rsa: expressJwtSecret: why is it called "secret"?](https://community.auth0.com/t/node-jwks-rsa-expressjwtsecret-why-is-it-called-secret/85380)

<div class="topic-metadata">

**Author:** [@cretaceousflower](https://community.auth0.com/u/cretaceousflower)\
**Replies:** 1\
**Last updated:** [June 27, 2022, 5:05pm UTC](https://community.auth0.com/t/node-jwks-rsa-expressjwtsecret-why-is-it-called-secret/85380 "2022-06-27T17:05:30Z")

</div>

Hi. I am unclear re the expressJwtSecret() secret provider generator. If it’s role is to retrieve a public key - why is it called “secret”? Is there some handling of secrets that I am missing? Thanks!

---

## [Is it safe to hard code https://AUTH0\_DOMAIN/.well-known/jwks.json contents on my backend](https://community.auth0.com/t/is-it-safe-to-hard-code-https-auth0-domain-well-known-jwks-json-contents-on-my-backend/81468)

<div class="topic-metadata">

**Author:** [@dudumonteiro](https://community.auth0.com/u/dudumonteiro)\
**Replies:** 1\
**Last updated:** [April 8, 2022, 9:26pm UTC](https://community.auth0.com/t/is-it-safe-to-hard-code-https-auth0-domain-well-known-jwks-json-contents-on-my-backend/81468 "2022-04-08T21:26:55Z")

</div>

My frontend app makes a lot of backend calls, so if I could avoid a jump to https://AUTH0\_DOMAIN/.well-known/ on every call it would be great. Is it safe to simply hard code it’s contents on my backend?

---

## [Native app RS256 key not appearing in JWKS /.well-known/jwks.json](https://community.auth0.com/t/native-app-rs256-key-not-appearing-in-jwks-well-known-jwks-json/57960)

<div class="topic-metadata">

**Author:** [@henning.wagner](https://community.auth0.com/u/henning.wagner)\
**Replies:** 3\
**Last updated:** [February 17, 2021, 1:24pm UTC](https://community.auth0.com/t/native-app-rs256-key-not-appearing-in-jwks-well-known-jwks-json/57960 "2021-02-17T13:24:01Z")

</div>

We have multiple environments + web and native clients., resulting in a couple of Auth0 Applications configured. The Applications that are of type Machine to Machine are listed in our /.well-known/jwks.json but the Appli…

---

## [\[Solved\]JwksError: Not found.(i don't know why)](https://community.auth0.com/t/solved-jwkserror-not-found-i-dont-know-why/55902)

<div class="topic-metadata">

**Author:** [@nikunj321](https://community.auth0.com/u/nikunj321)\
**Replies:** 1\
**Last updated:** [January 8, 2021, 7:36pm UTC](https://community.auth0.com/t/solved-jwkserror-not-found-i-dont-know-why/55902 "2021-01-08T19:36:05Z")

</div>

const express = require('express'); const jwt = require('express-jwt'); // validate JWT and set req.user const jwksRsa = require('jwks-rsa'); // Retrieve RSA key set form a JSON Web Key set(JWSK) endpoint const checkS…

---

## [Retrieving the jwks when using multiple JWT issuers](https://community.auth0.com/t/retrieving-the-jwks-when-using-multiple-jwt-issuers/11157)

<div class="topic-metadata">

**Author:** [@eric3](https://community.auth0.com/u/eric3)\
**Replies:** 1\
**Last updated:** [December 18, 2018, 5:53pm UTC](https://community.auth0.com/t/retrieving-the-jwks-when-using-multiple-jwt-issuers/11157 "2018-12-18T17:53:57Z")

</div>

I want to verify that my thinking is correct: I currently have an API that will get requests that include JWTs from more than one issuer. These all use RS256. What I’m doing is using the ‘iss’ claim to construct the URL …

---

## [Verifying RS256 token using downloaded certificate](https://community.auth0.com/t/verifying-rs256-token-using-downloaded-certificate/8135)

<div class="topic-metadata">

**Author:** [@patrickrainier](https://community.auth0.com/u/patrickrainier)\
**Replies:** 7\
**Last updated:** [February 12, 2018, 4:51pm UTC](https://community.auth0.com/t/verifying-rs256-token-using-downloaded-certificate/8135 "2018-02-12T16:51:58Z")

</div>

I am able to successfully verify a RS256 token using the public key I extracted from the certificate which I downloaded on the clients page then I just passed that in my app as the secret. I am aware that the standard fo…

---

## [Golang: Invalid certificate from jwks](https://community.auth0.com/t/golang-invalid-certificate-from-jwks/9099)

<div class="topic-metadata">

**Author:** [@smousa](https://community.auth0.com/u/smousa)\
**Replies:** 0\
**Last updated:** [December 31, 2017, 3:50am UTC](https://community.auth0.com/t/golang-invalid-certificate-from-jwks/9099 "2017-12-31T03:50:44Z")

</div>

I am unable to decode the certificate from the jwks in golang: https://initiative-sked.auth0.com/.well-known/jwks.json I get the error following error: asn1: structure error: integer not minimally-encoded See snippet: …

---

## [Invalid certificate from jwks for signing JWT](https://community.auth0.com/t/invalid-certificate-from-jwks-for-signing-jwt/8908)

<div class="topic-metadata">

**Author:** [@justen](https://community.auth0.com/u/justen)\
**Replies:** 1\
**Last updated:** [December 28, 2017, 8:59pm UTC](https://community.auth0.com/t/invalid-certificate-from-jwks-for-signing-jwt/8908 "2017-12-28T20:59:34Z")

</div>

So this is for the situation where there is a change to the contents of the access\_token (eg. user updating name) which means i need to generate a new JWT access\_token. I have all the data for the new JWT I need to sig…
