Jira clobbers my Bamboo session

[Simon Inglis]

Howdy,

My Jira session is getting clobbered by Bamboo. That is to say, I have logged into both Jira and Bamboo in the same browser, any Jira operation asks for a login after which any subsequent Bamboo operation will then ask for a login, after which any further Jira session asks for a login. Rinse and repeat ad infinitum.

The net result is that I can only either use Jira or Bamboo but not both at the same time in the same browser.

I have Jira and Bamboo installed on the same server and have set up an application link so that Bamboo can authenticate against Jira. Both Jira and Bamboo are using a default configuration except for both products configured to use a local MYSQL instance.

One thing that I have found is that if I log into Jira first, I can open Bamboo up in another tab without Bamboo asking for a login. However, when I navigate back to Jira, it then asks for a login.

Cheers,

Simon.

[JamieA]

You need to have a context path for each one, rather than /. It's the same problem as described here: http://confluence.atlassian.com/display/JIRAKB/User+is+Logged+Out+of+JIRA+after+Confluence+Login

I'm assuming the server name is the same but the port is different?

[Simon Inglis]

Yes, it's the same server name (actually an IP address) and using the default ports of 8080 and 8085 for Jira and Bamboo respectively.

[JamieA]

OK... the link above gives you your options.

[Simon Inglis]

What I ended up doing was to modify the 'conf/wrapper.conf' file and change the following setting from using '/' to '/bamboo':

# The webapp context path. Which must be of form / or /your-context
#
wrapper.app.parameter.4=/bamboo

Now my bamboo is running on '<host>:8085/bamboo' and my initial testing shows that this has fixed the problem.

The two options described in the Atlassian documentation link (above) are:

1) use virtual hosts or

2) to modify the web application context for an EAR-WAR deployment.

Option 1 is non-trivial and option 2 doesn't apply to a standalone install. From what I can tell by looking at the logs, the standalone install uses Jetty not Tomcat.

Thanks for putting me on the right path.

[JamieA]

Yes, 2) can be done with a standalone install. A standalone install is just a preconfigured tomcat with the web app exploded.

Unfortunately there aren't easy options, particularly if you want to keep old urls working. The important thing is to get it right when you first set it up, but of course people don't.