Skip to content

Fix #12368 - userDelete new parameter#12523

Merged
dsuren1 merged 2 commits into
geosolutions-it:masterfrom
offtherailz:fix_528
Jun 23, 2026
Merged

Fix #12368 - userDelete new parameter#12523
dsuren1 merged 2 commits into
geosolutions-it:masterfrom
offtherailz:fix_528

Conversation

@offtherailz

@offtherailz offtherailz commented Jun 19, 2026

Copy link
Copy Markdown
Member

Description

Pass cascadeResourceDelete=USERSESSION query parameter to the GeoStore DELETE /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)

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Other... Please describe:

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)

  • Yes, and I documented them in migration notes
  • No

Other useful information

Requires GeoStore ≥ 2.6, so on MapStore:

On geostore

@offtherailz offtherailz added this to the 2026.02.00 milestone Jun 19, 2026
@offtherailz offtherailz requested a review from MV88 June 19, 2026 14:59
@cla-bot cla-bot Bot added the CLA Ready label Jun 19, 2026
@offtherailz offtherailz linked an issue Jun 19, 2026 that may be closed by this pull request
3 tasks
@offtherailz offtherailz changed the title Fix #528 - userDelete new parameter Fix #12368 - userDelete new parameter Jun 19, 2026
@tdipisa tdipisa requested review from dsuren1 and removed request for MV88 June 23, 2026 09:40
@tdipisa tdipisa assigned dsuren1 and unassigned MV88 Jun 23, 2026
@tdipisa tdipisa marked this pull request as ready for review June 23, 2026 09:40
@tdipisa

tdipisa commented Jun 23, 2026

Copy link
Copy Markdown
Member

This is now ready for review. Assigned to you @dsuren1. Thanks.

@dsuren1 dsuren1 merged commit 0f51e19 into geosolutions-it:master Jun 23, 2026
12 checks passed
@offtherailz

Copy link
Copy Markdown
Member Author

Successfully created backport PR for 2026.02.xx:

@dsuren1

dsuren1 commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

@ElenaGallo Kindly test this change in DEV when available. Thanks!

offtherailz added a commit that referenced this pull request Jun 23, 2026
(cherry picked from commit 0f51e19)

Co-authored-by: Tobia Di Pisa <tobia.dipisa@geosolutionsgroup.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update User Manager to trigger USERSESSION cleanup on deletion

4 participants