Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-77664

No sub claim in JWT when sending webhook for user_updated/created/deleted events

      Issue Summary

      When using webhooks, defined in the app descriptor to catch some events happening in Jira. there is an issue with the user events. The host-based on the JWT coming from the request (using the Authorization parameter) for the issue events, but this doesn't work for the user events. 

      Steps to Reproduce

      1. Create a connect app using JWT
      2. trigger user-related events

      Expected Results

      JWT that comes with a webhook registered by connect app for `user_created/user_updated/user_deleted` events should contain `sub` claim, which should have accountId of a user.

      Actual Results

      JWT that comes with a webhook registered by connect app for `user_created/user_updated/user_deleted` events does not contain `sub` claim, which should have accountId of a user.

      Workaround

      Currently, there is no known workaround for this behaviour. A workaround will be added here when available

          Form Name

            [JRACLOUD-77664] No sub claim in JWT when sending webhook for user_updated/created/deleted events

            Atlassian Update - October 26, 2022

            Hi everyone,

            Thank you for previously raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.

            As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.

            Thank you again for providing valuable feedback to our team!
            Jira Cloud team

            Matthew Hunter added a comment - Atlassian Update - October 26, 2022 Hi everyone, Thank you for previously raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users. As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know. Thank you again for providing valuable feedback to our team! Jira Cloud team

              Unassigned Unassigned
              hnyeche Prince N
              Affected customers:
              5 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: