Fix #12368 - userDelete new parameter#12523
Merged
Merged
Conversation
3 tasks
Member
|
This is now ready for review. Assigned to you @dsuren1. Thanks. |
dsuren1
approved these changes
Jun 23, 2026
Member
Author
|
Successfully created backport PR for |
Contributor
|
@ElenaGallo Kindly test this change in DEV when available. Thanks! |
offtherailz
added a commit
that referenced
this pull request
Jun 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Pass
cascadeResourceDelete=USERSESSIONquery parameter to the GeoStoreDELETE /users/user/{id}endpoint when deleting a user from the User Manager. This triggers backend cleanup of USERSESSION resources solely owned by the deleted user, preventing orphaned session resources in the database.Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x", remove the others)
Issue
What is the current behavior?
When a user is deleted via the User Manager, their USERSESSION resources remain orphaned in the database with no owner.
Refs #12368
What is the new behavior?
The DELETE request now includes
?cascadeResourceDelete=USERSESSION. GeoStore (≥ geosolutions-it/geostore#544) deletes all USERSESSION resources solely owned by the user before removing the user. Shared resources and resources of other categories are untouched. If the backend does not support the parameter or no resources are found, user deletion proceeds normally.Breaking change
Does this PR introduce a breaking change? (check one with "x", remove the other)
Other useful information
Requires GeoStore ≥ 2.6, so on MapStore:
On geostore