Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-11970

As an admin I would like to be able to set the amount of concurrent logins per user

XMLWordPrintable

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      As a security measure we do not want to allow more than 2 concurrent logins for any Jira user.
      Unfortunately, this feature is not available in JIRA 3.7.1 Enterprise.
      I will strongly recommend including this in your future release.

      Please refer to support issue # JSP-9605

          Form Name

            [JRASERVER-11970] As an admin I would like to be able to set the amount of concurrent logins per user

            Sandra Fraune added a comment -

            It is 2023 now and security issues became more and more important.
            Multiple login from different devices can cause a security problem in there days. I would vote for reopening this issue.

            Sandra Fraune added a comment - It is 2023 now and security issues became more and more important. Multiple login from different devices can cause a security problem in there days. I would vote for reopening this issue.

            Flavio Beck added a comment -

            Hi,

             

            yes, I consider this feature really is relevant, even probably there are few instances with this kind of need.

            maybe some  workaround in tomcat should be enough.

            like this:

            https://stackoverflow.com/questions/39374640/limit-concurrent-sessions-to-apache-tomcat-web-application

             

            but i am not sure if works for Jira.

             

             

             

            Flavio Beck added a comment - Hi,   yes, I consider this feature really is relevant, even probably there are few instances with this kind of need. maybe some  workaround in tomcat should be enough. like this: https://stackoverflow.com/questions/39374640/limit-concurrent-sessions-to-apache-tomcat-web-application   but i am not sure if works for Jira.      

            Josh Devenny added a comment -

            Hi,

            This is a bulk update to specific issues in the JIRA (JRA) project

            As part of an effort to ensure we are transparent about the JIRA issues on jira.atlassian.com, we have decided to resolve those that have been open for multiple years with minimal activity and with a low number of votes. In light of the fact that JIRA is rapidly changing and that this issue may not be a valid request any longer, we will be resolving it today.

            Votes are not the only metric that we use to determine the requests that are implemented, however they do factor in to our decision making process. We have decided that the combination of this issue being open for a long period of time, and it's low number of votes means that we are unlikely to implement it. If you would like thoughts on how we use jira.atlassian.com, please see: https://answers.atlassian.com/questions/110373/how-does-the-jira-team-use-jira-atlassian-com

            If you have believe this issue is still relevant, please comment on the issue and we will respond. We are watching all these issues that we bulk close.

            Best regards
            Josh Devenny and Roy Krishna
            JIRA Product Management

            Josh Devenny added a comment - Hi, This is a bulk update to specific issues in the JIRA (JRA) project As part of an effort to ensure we are transparent about the JIRA issues on jira.atlassian.com, we have decided to resolve those that have been open for multiple years with minimal activity and with a low number of votes. In light of the fact that JIRA is rapidly changing and that this issue may not be a valid request any longer, we will be resolving it today. Votes are not the only metric that we use to determine the requests that are implemented, however they do factor in to our decision making process. We have decided that the combination of this issue being open for a long period of time, and it's low number of votes means that we are unlikely to implement it. If you would like thoughts on how we use jira.atlassian.com, please see: https://answers.atlassian.com/questions/110373/how-does-the-jira-team-use-jira-atlassian-com If you have believe this issue is still relevant, please comment on the issue and we will respond. We are watching all these issues that we bulk close. Best regards Josh Devenny and Roy Krishna JIRA Product Management

            Roy Krishna (Inactive) added a comment -

            Updated summary.

            Roy Krishna (Inactive) added a comment - Updated summary.

            Thomas Dahlin added a comment -

            I would also like this, may it be configurable.

            Signing in a second time (other browser window/computer) should invalidate the first login, if it's still active.

            Thomas Dahlin added a comment - I would also like this, may it be configurable. Signing in a second time (other browser window/computer) should invalidate the first login, if it's still active.

            Neal Applebaum added a comment -

            What I meant is that I am also a user of JIRA, and if Atlassian did implement your enhancement request, it would have to be configurable so it wouldn't affect me. My clients each have one user account that all their users share and could have any number logged in at the same time.

            Neal Applebaum added a comment - What I meant is that I am also a user of JIRA, and if Atlassian did implement your enhancement request, it would have to be configurable so it wouldn't affect me. My clients each have one user account that all their users share and could have any number logged in at the same time.

            Vinita Bakhshi added a comment -

            Neal,

            I did not quite get you when you said - "This would have to be
            configurable"
            Do you mean to say that this configuration is possible and available
            within Jira 3.7.1 Enterprise? or
            Do you mean to say that this will indeed be considered as an Enhancement
            request for future releases of Jira?

            Could you please be more explicit?

            Thanks,
            Vinita

            Vinita Bakhshi added a comment - Neal, I did not quite get you when you said - "This would have to be configurable" Do you mean to say that this configuration is possible and available within Jira 3.7.1 Enterprise? or Do you mean to say that this will indeed be considered as an Enhancement request for future releases of Jira? Could you please be more explicit? Thanks, Vinita

            Neal Applebaum added a comment -

            This would have to be configurable, as our use case has many users sharing one account login.

            Neal Applebaum added a comment - This would have to be configurable, as our use case has many users sharing one account login.

              Unassigned Unassigned
              510fe1793ba6 Vinita Bakhshi
              Votes:
              2 Vote for this issue
              Watchers:
              17 Start watching this issue

                Created:
                Updated:
                Resolved: