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
Check your JIRA and Bamboo server for correctness, using the tasklist below;
1:_p1532567280JIRA remote api access is [enabled,|http://confluence.atlassian.com/display/JIRA/Configuring+JIRA+Options]$generalUtil.htmlEncode($task.priority)$generalUtil.htmlEncode($task.createdDate)$generalUtil.htmlEncode($task.completed)$generalUtil.htmlEncode($task.completedDate)$generalUtil.htmlEncode($task.locked)
1:_p1458197975Bamboo remote api access [is enabled|BAMBOO:Enabling Bamboo\'s Remote API],$generalUtil.htmlEncode($task.priority)$generalUtil.htmlEncode($task.createdDate)$generalUtil.htmlEncode($task.completed)$generalUtil.htmlEncode($task.completedDate)$generalUtil.htmlEncode($task.locked)
handler
Bamboo has plans and build results,
1:_p1398537113Bamboo has plans and build results,$generalUtil.htmlEncode($task.priority)$generalUtil.htmlEncode($task.createdDate)$generalUtil.htmlEncode($task.completed)$generalUtil.htmlEncode($task.completedDate)$generalUtil.htmlEncode($task.locked)
handler
Time offset between jira and bamboo server
1:_n533403450Time offset between jira and bamboo server$generalUtil.htmlEncode($task.priority)$generalUtil.htmlEncode($task.createdDate)$generalUtil.htmlEncode($task.completed)$generalUtil.htmlEncode($task.completedDate)$generalUtil.htmlEncode($task.locked)
1:_p2054602056Apache HTTPD configuration for [JIRA|http://confluence.atlassian.com/display/JIRA/Integrating+JIRA+with+Apache] and [Bamboo|http://confluence.atlassian.com/display/BAMKB/Running+bamboo+behind+apache+httpd+proxy]$generalUtil.htmlEncode($task.priority)$generalUtil.htmlEncode($task.createdDate)$generalUtil.htmlEncode($task.completed)$generalUtil.htmlEncode($task.completedDate)$generalUtil.htmlEncode($task.locked)bdziedzic
Add jira as an oauth consumer in bamboo.
Re-index Bamboo to ensure the data source for the gagdets is in a defined state.