# To visually verify RS256-signed tokens

**URL:** <https://community.auth0.com/t/to-visually-verify-rs256-signed-tokens/136592>\
**Category:** Get Help\
**Tags:** oauth-2-0, protocols\
**Created:** [June 18, 2024, 5:26pm UTC](https://community.auth0.com/t/to-visually-verify-rs256-signed-tokens/136592 "2024-06-18T17:26:14Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![martin617](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/martin617/32/57864_2.png) [@martin617](https://community.auth0.com/u/martin617)\
**Post date:** [June 18, 2024, 5:26pm UTC](https://community.auth0.com/t/to-visually-verify-rs256-signed-tokens/136592/1 "2024-06-18T17:26:15Z")

</div>

Hello,

On the Auth0 documentation page ‘Validate JSON Web Tokens’ (`https://auth0.com/docs/secure/tokens/json-web-tokens/validate-json-web-tokens`), it would have saved me a few hours of time if the instruction steps in the section ‘Verify RS256-signed tokens’ had been more clear.

The instructed download step of the certificate returns a `cert.pem` file (BEGIN/END CERTIFICATE). This needs to be turned into a `pubkey.pem` file (BEGIN/END PUBLIC KEY), before proceeding.

Command: `openssl x509 -pubkey -noout -in cert.pem > pubkey.pem`

---

<div class="post-metadata">

**Author:** ![rueben.tiow](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/rueben.tiow/32/11646_2.png) [@rueben.tiow](https://community.auth0.com/u/rueben.tiow)\
**Post date:** [June 26, 2024, 7:24pm UTC](https://community.auth0.com/t/to-visually-verify-rs256-signed-tokens/136592/3 "2024-06-26T19:24:38Z")

</div>

Hi @martin617,

Thanks for letting us know that the instructions in our documentation are unclear. I will pass this information back to our docs team.

Also, thank you for sharing the command that helped you convert the cert to a public key.

I would also add that you can get the public key from your tenant’s JWKS:  
`https://{yourDomain}/.well-known/jwks.json`

On that page, you can copy one of the objects in the `keys` array and include them in your public key signature. This should produce a verified signature.

I hope that helps!

Thanks,  
Rueben

---

<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:** [July 10, 2024, 7:25pm UTC](https://community.auth0.com/t/to-visually-verify-rs256-signed-tokens/136592/4 "2024-07-10T19:25:29Z")

</div>

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