Issue Summary

When a custom idle timeout policy is configured, managed Atlassian account users logged in to JSM help centre are being logged out at the end of the custom timeout period regardless of ongoing activity. 

Steps to Reproduce

1. Claim a managed account
2. Configure a relatively short custom idle session duration (e.g. 20mins)
3. Grant the managed account any JSM role
4. Log into JSM help centre as the managed account 
5. Perform any activity (raise requests, comment, search e.c.t.) intermittently for the idle session duration + 10 minutes 
6. After the idle session duration + 10 minutes has passed, attempt to perform some activity e.g. raise a request 

Expected Results

The user has not been idle for the idle session duration, so remains logged in and is able to raise a request

Actual Results

The user sees an error when trying to raise a request, and is logged out of their session

Workaround

Increase the idle session timeout