The new setting looks like this and is OFF by default:
Before this PR (and still the case if the parameter stays OFF), if you try to click "Delete" on a Keycloak User fetched by the plugin, you get the error "Error! User couldn't be deleted":
The PR adds the possibility, when the new setting is ON, to let Keycloak delete its version of the user (not the user record in the linked RDBMS), allowing the user to be re-fetched from scratch from the RDBMS on the next sync.
This is useful for testing, but also to solve sync issues for given users.
The new setting looks like this and is OFF by default:
Before this PR (and still the case if the parameter stays OFF), if you try to click "Delete" on a Keycloak User fetched by the plugin, you get the error "Error! User couldn't be deleted":
The PR adds the possibility, when the new setting is ON, to let Keycloak delete its version of the user (not the user record in the linked RDBMS), allowing the user to be re-fetched from scratch from the RDBMS on the next sync. This is useful for testing, but also to solve sync issues for given users.
Note that the
addUser
method is implemented to satisfy theUserRegistrationProvider
interface, but does nothing more than before: it just lets the call pass through, as per the recommendation in the Keycloak documentation here: https://www.keycloak.org/docs/latest/server_development/#:~:text=The%20addUser()%20method%20will%20be%20called