"Create user records in Keycloak" confirmation dialog appears prematurely
Description
CSP Request Details
None
CSP Rejection Details
None
Potential Workaround
None
Attachments
3
relates to
Checklist
hideActivity
Show:
Yauhen Viazau October 23, 2024 at 9:24 AM
Tested on https://folio-etesting-snapshot-diku.ci.folio.org/ - works as expected
Confirmation dialog does not disappear unless a user closed it (by clicking a button in it or pressing “Escape“ key).
It is also true for a case when some of the users to be assigned have a KC record, and some don’t.
Users with a KC record are being assigned in the background while a dialog is shown.
Users without a KC record will be promoted and assigned only if a user confirms in the dialog.
See examples:
Done
Details
Details
Assignee

Reporter
Labels
Priority
Story Points
0.5
Sprint
None
Development Team
Eureka
Fix versions
Release
Ramsons (R2 2024)
RCA Group
Implementation coding issue
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created October 2, 2024 at 12:30 PM
Updated November 1, 2024 at 9:46 AM
Resolved October 23, 2024 at 9:24 AM
TestRail: Cases
TestRail: Runs
Preconditions:
There are users with Keycloak record and without KC record in the system
Users without KC record can be created using
POST /users
API callSteps to reproduce:
Go to "Settings" → "Authorization roles"
Click on the name of any authorization role in the second pane
Click in "Assign/Unassign" button on the right side of the "Assigned users" accordion header
For several users with and without KC record, do the following:
Fill search input field with the name of a user
Click "Search" button
Select checkbox next to a user row
Click on "Save" button in "Select User" modal
Expected result:
"Create user records in Keycloak" dialog is shown and keeps being shown until “Cancel“ or “Confirm“ button in it is clicked.
Actual result:
"Create user records in Keycloak" confirmation dialog appears. Then it disappears for a short time, and reappears again.
(Approximately during this time, user(s) already having KC records are being assigned to a role)
Additional info:
See examples: