Done
Details
Details
Assignee
Yury Barsukou
Yury BarsukouReporter
Yauhen Viazau
Yauhen ViazauPriority
Story Points
2
Sprint
None
Development Team
Eureka
Fix versions
Release
Ramsons (R2 2024) Bug Fix
RCA Group
Implementation coding issue
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created November 27, 2024 at 11:16 AM
Updated January 28, 2025 at 1:51 PM
Resolved January 10, 2025 at 1:21 PM
Preconditions:
A user without Keycloak record exists in the system
If a user was created in UI (or via API using
POST /users
call), and no capabilities/creds/roles were assigned to it, a user would not have a Keycloak recordSteps to Reproduce:
Login to https://folio-etesting-snapshot-diku.ci.folio.org/ tenant as an admin user
Go to "Users" app
Open detailed view of a user from Preconditions
Click on "Actions" button on the third pane → Select "Check for open transactions/delete user" option
Click on “Yes“ button in appeared modal
Expected Results: A user is deleted without errors. Modal is closed, deleted user’s detailed view is closed, deleted user disappeared from users list.
Actual Results: Modal remains opened. Error pop-up appears. In DevTools
DELETE /users-keycloak/users/<<UUID>>
call fails with 404 status and the following response body:Additional Information:
A user is actually deleted from Folio app. If a page is reloaded, it disappears from the list, and cannot be found via search.
NOT reproducible for users having a Keycloak record (authUsers)
Active on:
https://folio-etesting-snapshot-diku.ci.folio.org/
https://folio-etesting-snapshot-consortium.ci.folio.org/
https://eureka-bugfest-ramsons.int.aws.folio.org/
See example: