Summary

In Jira Align, when using SSO integration to externally manage user authentication, the session of a logged in user times out much earlier than the Session Timeout value set in the Settings / Administration > Platform > Security (tab)

Environment

Jira Align

Diagnosis

User sessions have been disconnected earlier than expected, for examaple: "In Jira Align, although the Session Timeout was defined as 4 hours (240 mins), the users were forced to re-login again after 20-30 minutes".

Cause

This is caused by a mismatch of the timeout values set in the SSO product when compared to the Session Timeout value defined in Jira Align.

Solution

In both Jira Align and the SSO product, configure the timeout values to be the same (or match as closely as possible).

For example, if the Session Timeout is defined as 240 mins (4h) in Jira Align, but this value is given as 120 mins (2h) in Okta, this can cause unexpected timeouts due to frequency mismatch.
Solution: Choosing 240 mins in for both products in the example above will work.

Related Content:

• Security settings in Jira Align Help page

• Enforce a limited session lifetime for all policies in Okta Documentation

• AD FS 2016 Single Sign On Settings in Microsoft Documentation