...
The Secure Login session is intertwined with the session of the underlying application. So, the Secure Login session lasts as long as this session. According to this, there could be two different reasons for the problem:
Overall, the configured session timeout of the underlying
application is application is too short and the users have to login multiple times a day.
As most users are using the "remember me" functionality, a user has to revalidate the 2FA pin without an explicit login, as the login is done automatically. In that case, a suitable increase of the session duration of the underlying application by a system administrator should solve this problem. For more information please see: https://confluence.atlassian.com/jira063/changing-the-default-session-timeout-683542392.html
There is a known problem with the bot protection plugin of Atlassian.
This bug reduces the session timeout to one hour independent from the configured session timeout. As system administrator, please disable the bot killer plugin. Here you can find more information about that issue: https://community.atlassian.com/t5/Jira-questions/JIRA-session-timeout-set-to-1-hour-due-to-JIRA-bug-Okta-and-2FA/qaq-p/630382
Related articles
| Filter by label (Content by label) |
|---|
| showLabels | false |
|---|
| max | 10 |
|---|
| spaces | com.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@a59 |
|---|
| sort | modified |
|---|
| showSpace | false |
|---|
|
...
| | reverse | true |
|---|
| type | page |
|---|
| cql | label = "secure_login" and type = "page" and space = "SL" |
|---|
| labels | secure_login |
|---|
|