Repository navigation
Realm Import - Potential id conflicts #13530
MarkCupitt
started this conversation in
Archive
Replies: 2 comments 3 replies
|
@MarkCupitt Hello, you can use custom IDs to avoid conflicts as long as you make sure the changed IDs are also reflected in other resources that use that ID as a reference. |
0 replies
|
@vmuzikar Do you think it's good idea to have a script like this inside the keycloak repo and be able to call it on exported realms to rename them and re-import them. This is very useful for multi tenancy use cases. This script can also be called by a later version of the operator to duplicate realms, or even from keycloak itself to be able to that from the GUI. I often find myself needing to do this. It can also be easily tested in keycloaks test battery, to make sure everything keeps working after a clone/duplicate. |
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
We are using the new Operator V19.0.1 with the
KeycloakRealmImportyaml definition. We have exported one of our realms from an older version of Keycloak (v16), converted it to yaml and loaded it. It works. (As described here here)This question is related to the ids, specifically potential conflicts with duplicate ids and the way the YAML is structured.
The realm has lots of ids for the exported data:
This is the realm itself, I assume we can leave the id field out and it will be automatically created, and unique
However, when we come to clients, and some other items, we see that the id is actually used as a
key, for exampleWe want to use this yaml as a template to import multiple realms
Can we assign our own unique ids and is there any impact on the use of the id elsewhere in the yaml?
If, not, how do we achieve this and what are the risks of duplicate id's being used in multiple realms?
All reactions