We have Jira and Confluence installed on our server (Ubuntu 11.10). Programs are behind the Apache proxy in separate paths (/confluence and /jira) and configured to use HTTPS. Jira and Confluence are linked together and Confluence uses Jira's user directory. Everything works well apart the problem, that sometimes blocks the user from logging in to Jira on Confluence entirely. Instead of the login screen, user gets Unauthorized (401) error from the Jira and in Confluence HTTP Status 401 - Basic Authentication Failure - Reason: AUTHENTICATED_FAILED error from Tomcat.
We suspect that the reason for the problem is died session, that causes error instead of the login screen. Sometimes deleting cookies from the browser helps, but particularly not with Confluence.
Proxy configuration that we use is not supported by Atlassian, so the troubleshooting was quite hard. We ended up setting session timeout in conf/web.xml to -1 (no timeout). Hope, it doesn't raise new issues :) I also considered persistent sessions, but wasn't sure if it's possible with Jira & Confluence.
Hi, thanks for the suggestion. It seems that problem is not the overwritten session cookie, because both applications session cookies seems to be happily path specific (/jira and /confluence). Problem occurs when user has open browser windows with died sessions because of the session timeout (5h).
The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs