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

Service desk sometimes treats Connect addon users as external customers

XMLWordPrintable

      NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.

      If an administrator removes a Connect addon user from all the groups that have use permissions in JIRA, `RedirectExternalCustomerToPortalFilter` will redirect all the REST calls done by the Connect addon to the customer portal.

      It would be possible to detect if the user is a connect addon user, and skip the redirect. (Atlassian connect does its own scope based permission check, so this is not going to cause any problems)

      See https://ecosystem.atlassian.net/browse/AC-1416.

            [JSDSERVER-970] Service desk sometimes treats Connect addon users as external customers

            Owen made changes -
            Workflow Original: JSD Bug Workflow v5 - TEMP [ 2305191 ] New: JAC Bug Workflow v3 [ 3125706 ]
            Status Original: Done [ 10044 ] New: Closed [ 6 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 [ 2059129 ] New: JSD Bug Workflow v5 - TEMP [ 2305191 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 - TEMP [ 2056528 ] New: JSD Bug Workflow v5 [ 2059129 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 [ 1956116 ] New: JSD Bug Workflow v5 - TEMP [ 2056528 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v4 [ 1615750 ] New: JSD Bug Workflow v5 [ 1956116 ]
            jonah (Inactive) made changes -
            Description Original: If an administrator removes a Connect addon user from all the groups that have use permissions in JIRA, `RedirectExternalCustomerToPortalFilter` will redirect all the REST calls done by the Connect addon to the customer portal.

            It would be possible to detect if the user is a connect addon user, and skip the redirect. (Atlassian connect does its own scope based permission check, so this is not going to cause any problems)

            See https://ecosystem.atlassian.net/browse/AC-1416.             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This bug report is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSDCLOUD-970].
              {panel}

            If an administrator removes a Connect addon user from all the groups that have use permissions in JIRA, `RedirectExternalCustomerToPortalFilter` will redirect all the REST calls done by the Connect addon to the customer portal.

            It would be possible to detect if the user is a connect addon user, and skip the redirect. (Atlassian connect does its own scope based permission check, so this is not going to cause any problems)

            See https://ecosystem.atlassian.net/browse/AC-1416.
            jonah (Inactive) made changes -
            Link New: This issue relates to JSDCLOUD-970 [ JSDCLOUD-970 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v2 [ 1602905 ] New: JSD Bug Workflow v4 [ 1615750 ]
            Owen made changes -
            Workflow Original: JSD Bug Workflow [ 1398681 ] New: JSD Bug Workflow v2 [ 1602905 ]
            Marty (Inactive) made changes -
            Component/s New: API and Integrations [ 35993 ]
            Component/s Original: User Management [ 32692 ]

              knguyen@atlassian.com Kha Nguyen (Inactive)
              ekaukonen eero (Inactive)
              Affected customers:
              2 This affects my team
              Watchers:
              17 Start watching this issue

                Created:
                Updated:
                Resolved: