You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This does add convenience, but we want to be careful here. Exposing decoded header or payload JSON directly may encourage consumers to rely on unverified JWT data, since decoding does not imply signature verification. While the data is already accessible today, adding a dedicated API makes this usage more prominent.
Could you share the concrete use case you’re trying to solve with this change? That context will help us decide whether this belongs in the core API and, if so, how we should document or name it to avoid accidental misuse.
Activity
marktech0813 commentedon Nov 10, 2025
Hi, Can I handle this issue?
Fix -- Read the payload written by withPayload auth0#725
marktech0813 commentedon Nov 21, 2025
Please check PR.
thanks.
tanya732 commentedon Feb 10, 2026
Hi @bmaehr
Thank you for raising the issue!!
This does add convenience, but we want to be careful here. Exposing decoded header or payload JSON directly may encourage consumers to rely on unverified JWT data, since decoding does not imply signature verification. While the data is already accessible today, adding a dedicated API makes this usage more prominent.
Could you share the concrete use case you’re trying to solve with this change? That context will help us decide whether this belongs in the core API and, if so, how we should document or name it to avoid accidental misuse.
Thank you
bmaehr commentedon Feb 10, 2026
When creating the JWT I can do something like this:
On the other hand I would like to do while decoding