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 :-)
https://confluence.atlassian.com/display/JIRAKB/User+is+Logged+Out+of+JIRA+after+Confluence+Login
Hi Matthew,
Thank you, that was a helpful answer. It led me to further investigate Michael Seager's suggestion which only partially worked (please see my second comment on his answer)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
David,
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 :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Michael,
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!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi David
This is expected behavior. To avoid this you may implement Single Sign On between Confluence and Jira.
Hope it helps! :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bruna,
Many thanks - that was quick. I will investigate purchasing Crowd as it is the only Atlassian-endorsed solution. It is possible Crowd may even allow SSO for Lotus Notes which we still use extensively.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That isn't expected behavior at all! It didn't use to be that way for sure. Logging in/out of JIRA should not cause Confluence login. Has something changed on recent releases?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.