On 2/15/2017 1:06 AM, Sarp Kaya wrote:
Hello,
I’m aware of keycloak import/export functionality but when I export keycloak
configuration it exports with bunch of ids. I’m guessing this is useful for back-ups or
duplicating the entire environment.
My problem is, say if you have different environments with slight configuration
differences (because environments probably have different keys, URLs etc.) but would like
to keep majority of the configuration the same; then this export/import becomes unusable:
1) Everything has an id, so therefore just exporting and then importing singular
item will not work due to id mismatch.
If I recall, if you remove an id, a new one
will be created. However,
sometimes an id is used to refer to other things in the data structure
so you have to be careful (Again, going from memory here. Test early
and often).
2) During the import, it’s not possible to select what can be overwritten and what
can be skipped. Importing condition applies for all.
My question is, what is the best practice to configure keycloak in multiple environments?
This can get incredibly complex due to dependencies between entities.
But if you keep it simple enough the current import facilities can suffice.
The best answer I can give is that it just depends on what you are
trying to do.
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user