Fix As NON-ADMIN user not possible to manage own resource#11421
Conversation
b54786d to
f7a8c1a
Compare
f7a8c1a to
5fb24f1
Compare
|
Dear @stefanocudini it seems I can't reproduce the problem either by following steps in issue description here nor the ones in this comment. I can only suppose some strange race condition in managing permissions. |
b78809d to
32eb2d4
Compare
last commit apply the review suggestions by @allyoucanmap, testing in local this fix the original bug #11371 the CI Fails is caused only by this #11441 just fixed |
allyoucanmap
left a comment
There was a problem hiding this comment.
@tdipisa reported an additional problem on the save workflow where the permissions were not restored. There is already a commit to fix this here 77f6e8e
- steps to reproduce the problem:
- login as an user
- create a map
- open the resource details panel and select the permissions panel
- click on edit properties button
- edit permissions adding everyone group
- click again on edit properties button to exit editing
- click on save
- Current: No permission available message
- Expected: The permissions are still visible in the panel
Dear @allyoucanmap I was investigating issue #11436 as noted below to be a related to this issue #11421 @tdipisa this commit could solve also #11436 in this same PR |
|
No worries guys @allyoucanmap @stefanocudini I see we are aligned. @stefanocudini you can simply connect the issue #11436 to this PR then. Thank you. |
|
@ElenaGallo please test this fix on dev and let us know when we can backport, thanks |
|
Test passed, @stefanocudini please backport to 2025.01.xx. Thanks |
…ot possible to manage own resource (geosolutions-it#11421) --------- Co-authored-by: allyoucanmap <stefano.bovio@geosolutionsgroup.com>
@ElenaGallo backport merged now |
Description
fix #11371
fix lose of user owner on save resource in GeoStore module. The fix tries to keep the user attribute fixed and not lost in case the group permissions are changed, so the resource owner can still modify it.
here is defined the bug replication conditions and other considerations about server side:
#11371 (comment)
And the result or PR:
https://github.com/user-attachments/assets/bb3e922f-e324-4f09-9c33-b6bfb27661ae
The bug of resource permissions is solved, but some tests fail that I couldn't fix:
utils/__tests__/GeostoreUtils-js?:349:76ResourcesCatalog/selectors/__tests__/save-test.js?:34:9The test payload is probably wrong in new conditions.
What kind of change does this PR introduce? (check one with "x", remove the others)