After upgrading (JIRA to 5.0.6, Confluence to 4.3), why does logging on to one log me off the other? We would prefer to have 'seamless' transitions between the two applications once logged on to either one or the other.
Are there security configuration settings that I need to adjust?
And a quick link to the knowledge base for the solution ;-) We had the same problem when we first started out and had both apps on the same box. They soon got popular & justified the move to two servers :-)
Something else to check is if you have both applications running on the same server without a context path.
For example, your browser will treat http://myserver:8080 and http://myserver:8090 as different, but cookies won't. You can add a context path to make it http://myserver:8080/jira and http://myserver:8090/confluence via the server.xml files to avoid that problem.
Might help :)
Sounds like a possibility - as we are running both JIRA and Confluence on the same server.
A new question then - which files contain the context path setting? I seem to recall seeing context path at some stage during the recent upgrading process, but I simply cannot remember where - too much else was happening!
Hi again Michael,
Following up here...
I located the server.xml files for each application (bit of a newbie I'm afraid). I edited the <Context path="" attribute as suggested.
This appears to work for Confluence, but not for JIRA which throws exceptions to the catalina log (I hav attached it (catalina.2012-09-28.log) ). It appears that a ':' character in path="http://myserver:8080/jira" is not allowed.
So this begs yet another question, why is a ':' character in <Context path=""... acceptable to Confluence, but not to JIRA?
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG