We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Keycloak-config-cli deletes all existing required actions, only leaving or creating the one mentioned in the realm JSON.
Keycloak-config-cli should leave the existing required actions untouched.
The realm JSON contains one required action:
... "requiredActions": [ { "alias": "verify-email-code-action", "name": "Verify email by code", "providerId": "verify-email-code-action", "enabled": true, "defaultAction": false, "priority": 1001, "config": {} } ] ...
When running Keycloak-config-cli, the --import.managed.required-action=no-delete option is given.
--import.managed.required-action=no-delete
To me it looks like RequiredActionsImportService looks for the property for client scopes, while it should probably check the required actions property.
RequiredActionsImportService
The text was updated successfully, but these errors were encountered:
Indeed it looks like giving the --import.managed.client-scope=no-delete option prevents deletion of pre-existing required actions.
--import.managed.client-scope=no-delete
Sorry, something went wrong.
Calebasah
Successfully merging a pull request may close this issue.
Current Behavior
Keycloak-config-cli deletes all existing required actions, only leaving or creating the one mentioned in the realm JSON.
Expected Behavior
Keycloak-config-cli should leave the existing required actions untouched.
Steps To Reproduce
The realm JSON contains one required action:
When running Keycloak-config-cli, the
--import.managed.required-action=no-delete
option is given.Environment
Anything else?
To me it looks like
RequiredActionsImportService
looks for the property for client scopes, while it should probably check the required actions property.The text was updated successfully, but these errors were encountered: