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

Service Desk Customers will count towards jira-users license if "Default Group Memberships" is configured

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

      When Default Group Membership is enabled for JIRA to LDAP or Crowd, new users will be automatically added into the configured group(s), usually jira-users so they can login.

      In Service Desk 2.0 with public signup, Customers will be added into the configured groups and count towards JIRA license.

      Steps to reproduce

      1. Configure JIRA to use Crowd for user management
      2. Configure Default Group Memberships
      3. In JIRA, set Crowd Directory to the top position in Administration >> User management >> User Directories
      4. Create Service Desk with public signup
      5. Configure email in Service Desk >> Settings >> Email settings
      6. Customer to send email to Service Desk

      Expected behavior

      • Customer does not belong to any groups in JIRA but appear under Service Desk >> People >> Customers
      • Customer cannot login JIRA

      Actual behavior

      • Customer belongs to jira-users group in JIRA
      • Customer is now able to login JIRA.

          Form Name

            [JSDSERVER-878] Service Desk Customers will count towards jira-users license if "Default Group Memberships" is configured

            I agree with this ticket and we're running into the same problem with our user directory coming from LDAP with Copy-on-first-login enabled.

            Furthermore, we have multiple projects that users might access. Most of our users will hit our Helpdesk project, which has a Jira Service Desk Customer Portal. If this is their first time logging into Jira, it should not add them to jira-users. However, those same users might later need to access another project which does not use the Customer Portal. So if a user's initial login is to a Customer Portal, they should not be added to jira-users to avoid consuming a license, but this should not limit them from accessing Jira at a later point, at which time they'll need to be added to jira-users in order to access other projects which don't have Jira Service Desk.

            Andrew Culver added a comment - I agree with this ticket and we're running into the same problem with our user directory coming from LDAP with Copy-on-first-login enabled. Furthermore, we have multiple projects that users might access. Most of our users will hit our Helpdesk project, which has a Jira Service Desk Customer Portal. If this is their first time logging into Jira, it should not add them to jira-users. However, those same users might later need to access another project which does not use the Customer Portal. So if a user's initial login is to a Customer Portal, they should not be added to jira-users to avoid consuming a license, but this should not limit them from accessing Jira at a later point, at which time they'll need to be added to jira-users in order to access other projects which don't have Jira Service Desk.

            JSC Webra added a comment -

            Hi.
            First of all - it strange to see, that bug with lower id is marked as duplicate something with higher id.
            Second. I looked in JSD-903 and completely disagree with comment and resolution.

            As i think - adding a customer to ServiceDesk calls to the same method, as adding regular user to jira. But it's a bit different. With ServiceDesk v2 license policy there is a new terminology - a customer, and this is a new behavior for jira service desk, as well as for jira itself. And i think there is have to be another method, or additional parameters to add customer to database. For example force restrict it to internal database, or pass additional params to method, and override default group membership as it is not a user, it is a customer - an object (class) with completely different behavior, and one should not treat it as the same.

            JSC Webra added a comment - Hi. First of all - it strange to see, that bug with lower id is marked as duplicate something with higher id. Second. I looked in JSD-903 and completely disagree with comment and resolution. As i think - adding a customer to ServiceDesk calls to the same method, as adding regular user to jira. But it's a bit different. With ServiceDesk v2 license policy there is a new terminology - a customer, and this is a new behavior for jira service desk, as well as for jira itself. And i think there is have to be another method, or additional parameters to add customer to database. For example force restrict it to internal database, or pass additional params to method, and override default group membership as it is not a user, it is a customer - an object (class) with completely different behavior, and one should not treat it as the same.

              Unassigned Unassigned
              cchan Chung Park Chan
              Affected customers:
              4 This affects my team
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: