Support using internal realm name on components for support with imported realms #929
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 theirparentId
is theinternalId
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.