# \#debugger

**URL:** https://community.auth0.com/tag/debugger/836.md

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

---

## [Can JWT easily be hacked by Debugger?](https://community.auth0.com/t/can-jwt-easily-be-hacked-by-debugger/102259)

<div class="topic-metadata">

**Author:** [@Tone](https://community.auth0.com/u/Tone)\
**Replies:** 3\
**Last updated:** [March 28, 2023, 12:03am UTC](https://community.auth0.com/t/can-jwt-easily-be-hacked-by-debugger/102259 "2023-03-28T00:03:40Z")

</div>

This is probably a super noob question, so please bear with. I’m using the jsonwebtoken library in Node to generate a JWT. I can copy and past this token into the debugger at jwt.io and see my header and all my payload …

---

## ["credentials\_required" error for debugger](https://community.auth0.com/t/credentials-required-error-for-debugger/44314)

<div class="topic-metadata">

**Author:** [@aprildagonese](https://community.auth0.com/u/aprildagonese)\
**Replies:** 6\
**Last updated:** [June 16, 2020, 4:45pm UTC](https://community.auth0.com/t/credentials-required-error-for-debugger/44314 "2020-06-16T16:45:03Z")

</div>

I’m getting the following error when trying to use Debug Rule in the console: {“error”:“credentials\_required”,“message”:“No authorization token was found”} Everything else works for me just fine, and other people in my…

---

## [Jwt.io debugger and ESxxx validation](https://community.auth0.com/t/jwt-io-debugger-and-esxxx-validation/41716)

<div class="topic-metadata">

**Author:** [@fxmathieu](https://community.auth0.com/u/fxmathieu)\
**Replies:** 0\
**Last updated:** [April 24, 2020, 4:02pm UTC](https://community.auth0.com/t/jwt-io-debugger-and-esxxx-validation/41716 "2020-04-24T16:02:40Z")

</div>

Hi, Just a question about validation of signature token using ESS algorithm. Is it normal to reject a signature made with a certificate of a different ECDSA while standard Java signature verification allow it ? In oth…

---

## [Rule debugging - Connection error](https://community.auth0.com/t/rule-debugging-connection-error/11195)

<div class="topic-metadata">

**Author:** [@Joe\_Tillotson](https://community.auth0.com/u/Joe_Tillotson)\
**Replies:** 5\
**Last updated:** [October 7, 2018, 4:34pm UTC](https://community.auth0.com/t/rule-debugging-connection-error/11195 "2018-10-07T16:34:19Z")

</div>

Hello community, just starting yesterday (2018-04-26) (AFAIK), we are not able to debug rules in our dev or test auth0 tenants. When I try to debug a rule, I immediately see a red bar along the bottom of the (new) brows…

---

## [Have the jwt.io debugger error if token is base64 encoded](https://community.auth0.com/t/have-the-jwt-io-debugger-error-if-token-is-base64-encoded/7694)

<div class="topic-metadata">

**Author:** [@keno](https://community.auth0.com/u/keno)\
**Replies:** 1\
**Last updated:** [July 31, 2017, 8:07pm UTC](https://community.auth0.com/t/have-the-jwt-io-debugger-error-if-token-is-base64-encoded/7694 "2017-07-31T20:07:53Z")

</div>

The debugger on jwt.io accepts both base64 and base64url encoded tokens. However, since the standard specified base64url, it would be nice if the debugger generated an error for base64 tokens.