atlassian-connect-play-java: can not migrate to the JSON

I need to migrate my plugin: the new JSON module descriptors and JWT and I stuck here.

I used old xml descriptor + oauth version of the atlassian-connect-play-java. Now when I swithced to the freshest verison of the atlassian-connect-play-java and created the appropriate JSON descriptor, I am not able to install the plugin to the local JIRA.

To simplify I started wtih the tutorial: still get the error:

On the manage Add-ons page I get "Not authorized to install add-on http://localhost:9000/.". When I debug the UpmClient.class I see the following error:

{"type":"PLUGIN_INSTALL","status":{"errorMessage":"The add-on at {0} cannot be installed on this OnDemand instance.","source":"http://localhost:9000","done":true},"links":{"self":"/jira/rest/plugins/1.0/pending/d87d0d31-2907-48e1-9d51-d8494b3f58bf"},"timestamp":1402127729240,"userKey":"admin"}

The JSON descriptor looks like:

     "name": "Hello World",
     "description": "Atlassian Connect add-on",
     "key": "com.example.myaddon",
     "baseUrl": "${localBaseUrl}",
     "vendor": {
         "name": "Example, Inc.",
         "url": ""
     "authentication": {
         "type": "none"
     "version": "1.0",
     "modules": {
         "generalPages": [
                 "url": "/helloworld",
                 "key": "hello-world",
                 "name": {
                     "value": "Greeting"

Please help me. I would be very thankfull if you point me where to look and debug.

1 answer

1 accepted

Hi Volodymyr,

It looks that your JSON is configured right based on Atlassian Documentation.

However it’s very hard to help you based only on these information, to test if it’s not some issue on your local JIRA to import this plugin. I would ask you to try the simplest plugin example on the documentation instead of your plugin, then we’ll be able to know if your local JIRA can import the most simple example of the atlassian documentation.

Any other steps that you have tried before that you want to share will be welcome to better understand what you have already tried and what I can do further.

Kind Regards,

Henrique Lechner

Hi Henrique,

The problem was with new development jira configuration. The config I copied from not work:

atlas-run-standalone --product jira --version 6.3-OD-03-012 --bundled-plugins com.atlassian.plugins:atlassian-connect-plugin:1.0.2,com.atlassian.jwt:jwt-plugin:1.0.0,com.atlassian.bundles:json-schema-validator-atlassian-bundle:1.0-m0 --jvmargs -Datlassian.upm.on.demand=true

I reverted to my old config and plugin started working:

atlas-run-standalone --product jira --version 6.2-OD-08-034 --bundled-plugins com.atlassian.plugins:atlassian-connect-plugin:1.0.0-rc2,com.atlassian.jwt:jwt-plugin:1.0-m8,com.atlassian.bundles:json-schema-validator-atlassian-bundle:1.0-m0,com.atlassian.upm:atlassian-universal-plugin-manager-plugin:2.15 --jvmargs -Datlassian.upm.on.demand=true

I am not sure if it's my "private issue" or there are some troubles with the freshest JIRA config.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,748 views 18 21
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you