Uploaded image for project: 'Jira Align'
  1. Jira Align
  2. JIRAALIGN-2215

REST API 2.0 Token Bug

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • 10.83
    • 10.80
    • REST API
    • None
    • 1
    • Severity 3 - Minor
    • Breakers - Usher 8
    • None

      Issue Summary

      There is an issue when using a PATCH request (REST API 2.0) on a user. The problem is that when a user is updated via patch the user loses their API token.

      Reproduces against https://alignsupport.jiraalign.com

      Steps to Reproduce

      1. I used my own account for this purpose. userid is 661675
      2. My API token prior to it being removed was
        Mpxg6+4Y(U<`ynh[z_:Dips`Y&l5BeGOJId)RwXs
      3. I ran the following API call to change the start date for my user account: 
        curl --request PATCH --url https://alignsupport.jiraalign.com/rest/align/api/2/Users/661675 --header 'authorization: Bearer Mpxg6+4Y(U&lt;`ynh[z_:Dips`Y&l5BeGOJId)RwXs' --header 'content-type: application/json' --data '[ { "op":"replace", "path": "/userStartDate", "value": "2020-04-01T00:00:00Z" } ]'

      Expected Results

      User info is updated, but, API token should remain.

      Actual Results

      I checked my user account's profile after making the API change, and noticed that the API token had disappeared:

      Workaround

      The affected user will need to re-generate a new API token to continue using API 2.0 against Jira Align

        1. image-2020-10-23-16-05-07-802.png
          22 kB
          Kent Baxley

            [JIRAALIGN-2215] REST API 2.0 Token Bug

            Kyle Foreman added a comment -

            Thank you for your patience! This issue was fixed in the Jira Align 10.83 release that was deployed to cloud test environments on November 7, 2020.

            -Kyle

            Kyle Foreman added a comment - Thank you for your patience! This issue was fixed in the Jira Align 10.83 release that was deployed to cloud test environments on November 7, 2020. -Kyle

              kforeman@atlassian.com Kyle Foreman
              kbaxley Kent Baxley (Inactive)
              Affected customers:
              0 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: