Psst: <session-timeout> is in minutes. Your JIRA sess timeout is still 300 minutes (5 hours). [BTW, default is 30 minutes] since the application web.xml takes precedence over the server-wide settings.
Are you sure this is the problem ? It doesn't look like it ... Check the logs, please ....
1 minutes doesn't sound right - i think the default (standalone installation) is 60 minutes. This may be a symptom of another issue, but first you ashoudl check web.xml. Here's a link to the offcial documentation on session timeout: http://confluence.atlassian.com/display/JIRA/Changing+the+default+session+timeout
Since I logged in ticking the "Remember me" box, I remained logged in but had to reauthenticate every 10 seconds when doing any admin functions, and some form submissions had to be repeated.
In my case, the above linked article had me try the JSESSIONID -> JIRASESSIONID fix - this was the only change I made - and it solved both problems.
If this is just the admin session that needs to re-authenticate, I'm wondering if this is the websudo kicking in?:
You can disable or change the timeout if that's the case.
A quick tip for users in 2019
If any of the installations are data center editions and on AWS, I suggest to update the following:
Update timeout in the following three places and make sure timeout number matches in all 3
3. Sticky session on ALB Target group(if you are using AWS infra)
Remember that time you realized it was possible to refresh your Jira data in Google sheets with just one click? What if we told you that you can now get the latest data with no clicks at all?! Zero! ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events