Before we get down to the question, let me give you a bit of background of our environment. Our JIRA is available for both internal and external access. The external access is sitting behind a TMG server. So the user need to login to TMG first then JIRA. It has been working fine for a year or so until last month when the connection is keep dropping for no apparent reason.
When a user is logged in, it will take them between 1-5 mins before they got booted out. The timing is a bit random. We know for sure that it is TMG that dropped the connection since once they were logged out by TMG and put in the TMG password again, they are back to the last JIRA session that they had. So in other words, JIRA kept the session.
We decided to trace the issue in TMG, and it appears that the browser is sending a request to JIRA using Anonymous login, and since this is not permitted in our TMG rules, it is blocked and the session ends there. The URL that they are trying to reach is http://jira.company.com.au/osd.jsp.
Now the question is: what made the browser suddenly decide to use anonymous login (in the log the previous 5 entries have correct login)? Could it be affected by the cookie that is sent by JIRA? Or could it be something else?
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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