ScopeMappings for realm roles does not work about keycloak-operator

[KreMat]

I am experiencing the very same issue. The problem is, when the operator wants to update the configuration via keycloak server api it runs into a NullPointerException. The operator dues a call against ../scope-mappings/realm/ which maps to the following method in Keycloak: org.keycloak.services.resources.admin.ScopeMappedResource#addRealmScopeMappings

addRealmScopeMappings takes the id (not the name) from the payload and fails as it is not present. If you add the id in your yaml definition (can be retrieved via API or in Admin Console from browser url) everything is fine. However, this is not very practical as the generated uuid will differ between each installation.

From my point of view using the name as identifier is much more convenient and less error prone. I am working an a PR to keep the CRD with name as identifier but applying a logic to fetch the id if not present.

[andreaTP]

Closing this one as a duplicate of keycloak/keycloak#10022

Thanks for submitting the issue and the possible fix @KreMat !