This seems to happen to me when grafana didn’t recognize my passed in JWT as a JWT. More specifically, if you happened to specify the incoming header as Authorization as opposed to some other custom header for passing your JWT and it doesn’t recognize the token as a JWT one.
One silent error that really messed with me for a while was that the JWT implementation appears to require the claim sub to exist on your token. But the message alerting you to it appears to never be reached/logged as a result of a guard in the code.
issue with sub property requirement silently failing JWT processing:
request stopped here:
guard existing JWT processing due to missing sub:
the message I would have liked to have received to save me time and effort troubleshooting. (but the execution path never makes it here given the above code references.
If your token has a sub claim in it, and you’re not using the Authentication header, and you still have this issue. I’ll need more info about your grafana.ini [auth.jwt] section, I’m just tossing guesses out based on my own experience trying to integrate via the JWT plugin. Be sure to sanitize any identifying/sensitive details in the section before you post anything.