Added support for components using the internal realm name.
This resolves issue #802
The issue arises as the provider assumes that realmId==parentId which is not the case for imported realms, as their parentId is the internalId generated by keycloak, which uses an UUID.
When the internal id is not set, the behavior defaults to the old one, as to not break any currently supported realms using this provider to manage their keys.
Added support for components using the internal realm name.
This resolves issue #802
The issue arises as the provider assumes that
realmId==parentIdwhich is not the case for imported realms, as theirparentIdis theinternalIdgenerated by keycloak, which uses an UUID.When the internal id is not set, the behavior defaults to the old one, as to not break any currently supported realms using this provider to manage their keys.