Troubleshooting Gadgets
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
This KB article is relevant if you are having problems integrating Bamboo gadget into other applications.
Common symptoms include;
Bamboo Gadgets in Jira Dashboard does not authenticate.
Can't successfully 'Login & Approve' bamboo gadgets.
Bamboo Gadgets doesn't show content.
Possible Error messages in the logs
oauth_problem=timestamp_refused
Remote API not activated for this JIRA installation
oauth_problem="signature_invalid"
Cause
There a many factors and parameters that need to be 'right'. Please check the tasklist in the following Resolution
section.
A possible Error Scenario - Bamboo's Base URL
Bamboo and JIRA run behind a reverse proxy. Bamboo and JIRA are reachable from the outside world as https://bamboo.domain.com and https://jira.domain.com. Thus the bamboo server in jira is configured as https://bamboo.acme.com
Because this is the way bamboo is reached from JIRA, the proxy may terminate the https protocol and talk to bamboo via http as the base url of bamboo is set to http://bamboo.acme.com.
When registering jira (https://jira.domain.com) as an oauth consumer in bamboo http://bamboo.domain.com is set as the provider. When jira comes to use bamboo gadgets it will send an oauth request to bamboo based on the stored bamboo server info in jira (https://bamboo.domain.com). Bamboo will receive this request but will not be able to identify itself as https://bamboo.domain.com (because bamboo's base url is http://bamboo.domain.com). Thus bamboo's oauth module will respond with 'signature_invalid'.
Authentication between jira and bamboo will fail.
Resolution
Confirm that the following System apps are enabled on Bamboo.
Atlassian Bamboo gadgets plugin
Atlassian Gadgets API
Atlassian Gadgets SPI
Check your JIRA and Bamboo server for correctness, using the list below:
Add JIRA as an OAuth consumer in Bamboo.
Re-index Bamboo to ensure the data source for the gadgets is in a defined state.
Was this helpful?