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

複数製品に共通のナレッジ

このページの内容

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

プラットフォームについて: Server と Data Center のみ - この記事は、サーバーおよびデータセンター プラットフォームのアトラシアン製品にのみ適用されます。

問題

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 Atlassian Bot Killer Plugin has been shown to terminate sessions when a third party authenticator such as Okta is enabled. If a session makes 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.

最終更新日 2020 年 6 月 26 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.