Bamboo Documentation

   Bamboo 5.0.x
   Bamboo 4.4.x
   Bamboo 4.3.x
   Bamboo 4.2.x  
   More...   

 

Bamboo Knowledge Base Resources

Skip to end of metadata
Go to start of metadata

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

  1. Check your JIRA and Bamboo server for correctness, using the tasklist below;

    0%

    Task List

    1. handler

      Bamboo server's Base URL,

      Priority MEDIUM
      N/A
    2. handler

      JIRA server's Base URL,

      Priority MEDIUM
      N/A
    3. handler

      JIRA remote api access is enabled,

      Priority MEDIUM
      N/A
    4. handler

      Bamboo remote api access is enabled,

      Priority MEDIUM
      N/A
    5. handler

      Bamboo has plans and build results,

      Priority MEDIUM
      N/A
    6. handler

      Time offset between jira and bamboo server

      Priority MEDIUM
      N/A
    7. handler

      Apache HTTPD configuration for JIRA and Bamboo

      Priority MEDIUM
      bdziedzic
      Sep 13, 2010
    8. handler

      Does Bamboo has different security mode than JIRA

      Priority MEDIUM
      smaiyaki
      Dec 13, 2012
  2. Add jira as an oauth consumer in bamboo.
  3. Re-index Bamboo to ensure the data source for the gadgets is in a defined state.