Details
-
Bug
-
Resolution: Fixed
-
Low
-
None
-
None
-
6
-
Minor
Description
Issue Summary
Customer migrated one of their Jira cloud instances to another Jira cloud instance. The issue happens in the instance that they have restore the backup from the old instance. So, the app doesn't work in the new instance.
Steps to Reproduce
1- Create a new Jira Cloud instance (we'll call this the old instance)
2- Install Time in Status by OBSS to this instance (https://marketplace.atlassian.com/1211756)
3- Use the Time in Status link in the main Jira menu to open and confirm that Time in Status is working properly.
4- Create a backup of old instance using Backup Manager page (with "Include attachments, avatars, and logos in the backup" selected)
5- Create another Jira Cloud instance (we'll call this the new instance)
6- Restore the backup from the old instance onto the new instance using Restore System page (with "Merge with existing cloud users" selected)
7- Select "grant application access" when restore is completed
8- Install Time in Status to the new instance.
9- Check and confirm that the app is not working on the new instance.
Expected Results
app should work normally
Actual Results
{"status":500,"message":"An unexpected error has occurred. If this error persists, please contact Time in Status support through http://pluginsupport.obss.com.tr/","messages":["403 : [{\"error\": \"Add-on 'com.obss.plugin.time-in-status' disallowed to impersonate the user because 'no valid active user exists'\"}]"],"pluginVersion":"1.18.0.373","time":"2020-06-08 21:24:48"}
Workaround
After reproducing the same steps that the vendo OBSS did (check the last bounce), we've also received the same error call when trying to access the app in the new instance:
{"status":500,"message":"An unexpected error has occurred. If this error persists, please contact Time in Status support through http://pluginsupport.obss.com.tr/","messages":["403 : [{\"error\": \"Add-on 'com.obss.plugin.time-in-status' disallowed to impersonate the user because 'no valid active user exists'\"}]"],"pluginVersion":"1.18.0.373","time":"2020-06-08 21:24:48"}
So, we checked the add-on user in the new instance
select * from cwd_user where email_address like '%time-in-status%'
and saw that the user was appearing as removed:
id,directory_id,user_name,lower_user_name,active,created_date,updated_date,first_name,lower_first_name,last_name,lower_last_name,display_name,lower_display_name,email_address,lower_email_address,credential,deleted_externally,external_id,localservicedeskuser 10009,1,removed10,removed10,1,2020-06-08T20:36:42.632Z,2020-06-08T21:03:36.636Z,,,,,Time in Status,time in status,com.obss.plugin.time-in-status@connect.atlassian.com,com.obss.plugin.time-in-status@connect.atlassian.com,,0,5c988819b709c020b2eee1bc,0
We came into the conclusion that the user was imported as a regular user, not as add-on user, when it was imported in the new instance.
To confirm, we followed those steps in my instances tests:
- I uninstalled the app in the new instance
- I deleted the user:
delete from cwd_user where id = 14215
- I reinstalled the app (it forced the user creation again) and then the app worked
So, I did the same procedure at customer instance and it also worked.
I checked the user again and now the directory_id=1
select * from cwd_user where email_address like '%time-in-status%'
id,directory_id,user_name,lower_user_name,active,created_date,updated_date,first_name,lower_first_name,last_name,lower_last_name,display_name,lower_display_name,email_address,lower_email_address,credential,deleted_externally,external_id,localservicedeskuser 14300,1,addon_time-in-status-report,addon_time-in-status-report,1,2020-05-23T02:45:16.716Z,2020-05-23T02:45:16.716Z,,,,,Time in Status for Jira Cloud,time in status for jira cloud,time-in-status-report@connect.atlassian.com,time-in-status-report@connect.atlassian.com,,0,5bcf8230c9cd504f86cfaaff,0
Attachments
Issue Links
- is related to
-
HOT-91642 Loading...