Uploaded image for project: 'Atlassian Guard'
  1. Atlassian Guard
  2. ACCESS-1451

Improvements to Idle Session Authentication Policy Options

XMLWordPrintable

    • 18

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      We are hoping to have more granular control in our Authentication Policies in the Idle Session Duration.

      • Ability to implement Idle Sessions on mobile users
      • Ability to see 'active' users and terminate sessions at an Admin level (including mobile)
      • Ability to set Idle Timeouts on pages with refreshes as well (Like Dashboards)
      • Ability to set timeouts based on a group (Admin, Project Lead, Customer...etc)
      • Ability to set a longer idle session duration
      • Ability to set session to not be persistent if the authenticating client is closed and reopened

       

            [ACCESS-1451] Improvements to Idle Session Authentication Policy Options

            Chris Tetzlaff added a comment -

            I concur with this feature request,  we ask for a idle session duration of 365 days and / or an option to allow unlimited idle session. (The need comes from JSM Portal not integrated with SAML SSO.) 

            Chris Tetzlaff added a comment - I concur with this feature request,  we ask for a idle session duration of 365 days and / or an option to allow unlimited idle session. (The need comes from JSM Portal not integrated with SAML SSO.) 

              Unassigned Unassigned
              47564f916a4b Ben W
              Votes:
              12 Vote for this issue
              Watchers:
              21 Start watching this issue

                Created:
                Updated: