When using a third-party authenticator, user sessions may terminate earlier than expected when idle

Cross Product Knowledge

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible


By default, sessions will last for several hours when using the default authenticator. After using a third-party authenticator, such as Okta, you may find that sessions initiated when Okta is enabled will be terminated if they are idle for an hour, even if the session configuration for your application is much higher. In most Atlassian Applications, the session length is 4 hours.

The problem is mostly fixed in the recent LTS versions: 8.5.6, 8.13.x (see bug below)


The Atlassian Bot Killer Plugin has been shown to terminate sessions when a third-party authenticator such as Okta is enabled. If a session submits only a single request in an hour time frame, then that session will be terminated - idle activity can sometimes run afoul of this plugin.

Related bugs:


As a first step, try to disable the Atlassian Bot Killer Plugin. If that doesn't resolve the problem, please contact Atlassian Support.

To disable the bot: 

  1. Navigate to ⚙️ → Manage apps.
  2. Filter for System apps and search for Atlassian Bot Session Killer.
  3. Click Disable.
  • If your instance is not publicly accessible, there should not be any significant ramifications - although you should monitor your instance to ensure performance and resource consumption stay normal.

Last modified on Oct 21, 2021

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.