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
- I used my own account for this purpose. userid is 661675
- My API token prior to it being removed was
Mpxg6+4Y(U<`ynh[z_:Dips`Y&l5BeGOJId)RwXs - 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<`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
- resolves
-
PS-67962 You do not have permission to view this issue
[JIRAALIGN-2215] REST API 2.0 Token Bug
Remote Link | Original: This issue links to "ALIGNSP-6614 (Atlassian Support System)" [ 510773 ] | New: This issue links to "PS-67962 (Atlassian Support System)" [ 510773 ] |
Sprint | New: Breakers - Usher 8 [ 6206 ] |
Sprint |
Sprint | New: Breakers - Usher 7 [ 6205 ] |
Sprint |
Sprint | New: Breakers - Usher 6 [ 6139 ] |
Sprint |
Sprint | New: Breakers - Usher 5 [ 6138 ] |
Sprint |
Rank | New: Ranked higher |