Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

400 Unable to decode JWT token

Ezra_Knobloch
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 30, 2020

I know this has been asked before, and i know how to quick-fix it (deleting entrys in store.db or just delete the whole file), but anyways.

As far as i know this problem occurs when the sharedKey part of the JWT process is not matching the one stored on the server, or atleast some part of the signature of the request does not match whats stored on the server (in the store.db).

I can trigger this by installing my addon from two different sources in a row. This happens very often as we have a productive and a staging app, and installing the one after uninstalling the other triggers this error.

The error only is triggered if a store.db was already present (as the first request is not signed).

Is there any decent way to solve this beside editing/removing store.db each time? Maybe by handling JWT tokens manually?

Thanks!

0 answers

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events