I noticed following issue, I run the Atlassian Connect Express framwork on my computer and it self-registers via ngrok with my jira instance. Also for production the same add-on runs on a public server (with the same add-on key.)
- Installing add-on in development mode in jira cloud instance (either via ACE or by passing the link)
- Remove said add-on
- Install the same add-on with different url (in this case production server) by passing the URL to jira instance.
- Installation fails due to an authentification problem.
Authentication verification error (400): Unable to decode JWT token: Error: Signature verification failed for input: with method sha256
If we clear the table
AddonSettings table on the production system we can install the add-on.
The same problem vice versa, when I remove the production installation from my jira instance and go back to my dev version, the self-registration fails with the same error. I have to reset my dev database, then it works fine.
I guess this is by design, but how can we use the same add-on key and switch between dev and production on the same jira instance?