Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-1248

Creating user on first login through Customer Portal shouldn't count against the JIRA license

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Answered
    • None
    • None
    • None
    • We collect Jira Service Desk 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 Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.

      There have been two previous tickets that reported this problem as a BUG and have been closed since it is expected behaviour. Many customers feel that even though Atlassian considers this expected behaviour, it is still INCORRECT behaviour. Please change this ticket to an SUGGESTION instead of a BUG and leave it open until the improvement has been made. We cannot use JSD until this is addressed.

      This is an expected behaviour when Default Group Membership has been configured. See this KB

      Steps to reproduce

      1. Add a Delegated LDAP directory to JIRA
      2. Choose the option "Copy User on Login"
      3. Logout from JIRA
      4. Access the URL of the Customer Portal of one of your Service Desks to login
      5. Login with a new user from LDAP (who is not in JIRA) to create the user on first login

      Current behaviour

      The user is added to the "jira-users" group and has the permission to access JIRA and all the information from Service Desk.

      Expected behaviour

      With the new agent-based license the user, should only be created as a "Customer" in Service Desk (specially if the option to restrict the access to the customer portal is enabled in SD).

      This is not the expected behaviour because this also occurs when Service Desk is configured to restrict the access to the Customer Portal, and if the user tries to do his first login through the Custom Portal, his user has permission on all the system.

          Form Name

            [JSDSERVER-1248] Creating user on first login through Customer Portal shouldn't count against the JIRA license

            Andrew Culver added a comment -

            Correct

            Andrew Culver added a comment - Correct

            Matthew McMahon (Inactive) added a comment -

            Hi Andrew,

            Thanks for the response.

            I believe that I understand your use-case.

            You would like it that logging in through the Service Desk Customer Portal does not add any default groups, and they are treated as a customer only. However if the same LDAP user was to then log in through JIRA directly, they would be automatically added to the default groups, with the possible side-effect being that they then consume a JIRA license.

            Matt

            Matthew McMahon (Inactive) added a comment - Hi Andrew, Thanks for the response. I believe that I understand your use-case. You would like it that logging in through the Service Desk Customer Portal does not add any default groups, and they are treated as a customer only. However if the same LDAP user was to then log in through JIRA directly, they would be automatically added to the default groups, with the possible side-effect being that they then consume a JIRA license. Matt

            Andrew Culver added a comment - - edited

            Hi Matthew,

            Not quite. The first part is correct. If the first login is through the Customer Portal, the user should not be added to any default groups. This would prevent a "customer" from consuming a Jira license.

            However, the user should then be able to login to the fully Jira interface, in order to access other projects which don't use Jira Service Desk. The first time they login to Jira (even if they've previously logged into JSD and become a "customer" user with no groups), they should be added to the default groups. If they aren't added to the default groups at this point (in our case, jira-users), then they can't access any projects.

            Thanks,
            Andrew

            Andrew Culver added a comment - - edited Hi Matthew, Not quite. The first part is correct. If the first login is through the Customer Portal, the user should not be added to any default groups. This would prevent a "customer" from consuming a Jira license. However, the user should then be able to login to the fully Jira interface, in order to access other projects which don't use Jira Service Desk. The first time they login to Jira (even if they've previously logged into JSD and become a "customer" user with no groups), they should be added to the default groups. If they aren't added to the default groups at this point (in our case, jira-users), then they can't access any projects. Thanks, Andrew

            Matthew McMahon (Inactive) added a comment -

            Hi,

            Would the expected behaviour in your opinion be that if the first login is through the Customer Portal, the user is not added to any default groups.

            Should you then want to add them to the default groups, this should be a manual process?

            Regards
            Matthew

            Matthew McMahon (Inactive) added a comment - Hi, Would the expected behaviour in your opinion be that if the first login is through the Customer Portal, the user is not added to any default groups. Should you then want to add them to the default groups, this should be a manual process? Regards Matthew

            Andrew Culver added a comment -

            Please change issue type to SUGGESTION.

            Andrew Culver added a comment - Please change issue type to SUGGESTION.

              Unassigned Unassigned
              c7411bbb0ba5 Andrew Culver
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: