# How is JWT.io able to validate signatures

**URL:** <https://community.auth0.com/t/how-is-jwt-io-able-to-validate-signatures/122194>\
**Category:** JWT.io\
**Created:** [December 2, 2023, 9:15am UTC](https://community.auth0.com/t/how-is-jwt-io-able-to-validate-signatures/122194 "2023-12-02T09:15:50Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![elias.nithin](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/elias.nithin/32/50151_2.png) [@elias.nithin](https://community.auth0.com/u/elias.nithin)\
**Post date:** [December 2, 2023, 9:15am UTC](https://community.auth0.com/t/how-is-jwt-io-able-to-validate-signatures/122194/1 "2023-12-02T09:15:50Z")

</div>

How is [JWT.io](http://JWT.io) able to validate signatures automatically for id & access tokens signed using RS256 . I am not providing the public keys but i wonder how they are able to verify the signature ?

---

<div class="post-metadata">

**Author:** ![thameera](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/thameera/32/13430_2.png) [@thameera](https://community.auth0.com/u/thameera)\
**Post date:** [December 3, 2023, 11:58pm UTC](https://community.auth0.com/t/how-is-jwt-io-able-to-validate-signatures/122194/2 "2023-12-03T23:58:40Z")

</div>

Hey @elias.nithin , [JWT.io](http://JWT.io) figures out the JWKS endpoint of the Identity Provider that issued the token, which will include the X.509 certificate that can be used to validate the signature.

The rough algorithm for this would be:

1. Find the `iss` property of the JWT payload, which usually indicates the issuer’s URL.
2. Read the openid-configuration JSON of issuer by appending `/.well-known/openid-configuration`. For example, if the issuer is `https://example.auth0.com/`, the URL to look would be `https://example.auth0.com/.well-known/openid-configuration`.
3. Find the `jwks_uri` from the above configuration and read the JWKS info info by visiting that URL. Example: `https://example.auth0.com/.well-known/jwks.json`.
4. This JWKS endpoint can have multiple certificates. The right cert can be inferred by looking at the `kid` (“key ID”) attribute in JWT’s header and matching that with the `kid` in the jwks.json file.
5. Use the `x5c` attribute, which is the signing certificate, to validate the JWT’s signature.

This depends on the issuer to be set to the domain of the IdP, and for the `/.well-known/openid-configuration` URL to be available (almost all standard OIDC IdPs host it in that location).

---

<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 9, 2024, 4:17am UTC](https://community.auth0.com/t/how-is-jwt-io-able-to-validate-signatures/122194/4 "2024-01-09T04:17:46Z")

</div>

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