117 chars · 1 line
157 chars · 13 lines
117 chars · 1 line
157 chars · 13 lines
JWT audience troubleshooting
JWT audience data can represent one intended recipient or multiple recipients. The decoder preserves the JSON shape it receives; deciding whether your service is an allowed audience belongs to trusted verifier policy. This tool is free to use. No account or payment is required.
Last updated
A local decoder can show whether aud is one string or an array of strings. It cannot know which audience identifier your service trusts.
The example payload targets two audience identifiers.
"aud":["api://orders","api://admin"]Two declared audiences; verifier policy decides whether either is acceptable.Common questions
No. Audience validation must account for the claim shape used by the issuer.
No. The decoder only exposes token-controlled data.
No. Preserve the issuer's claim shape and apply explicit audience validation.
Debugging a specific JWT issue? Browse JWT troubleshooting.