Thank you very much. I shared it with the team for a lookup.
Does it mean that a single user can be bound to more then one User Federation/Identity Provider? Can you provide more detail on how you've done this?
What would be the suggested way to automate resources creation? I use various home made Ansible roles and I find the Keycloak API to be inconsistent. Eg: Various GET methods that doesn't return complete payload and some…
May I know how many replicas and CACHE_OWNERS do you have?
It looks like Quarkus is going to be considered for one of the next major release [1]. That said, do you believe it will still be possible to extend Keycloak using the deployment-scanner? Also, do you happen to have…
When using a K8s cluster with the helm chart [1], it's actually the stateful set that takes care to the update. When the first replica restart, Keycloak makes the updates to the database itself. Sometimes rolling back…
Cool list but I would like to see them being implemented using FP approach when possible.
Thank you very much. I shared it with the team for a lookup.
Does it mean that a single user can be bound to more then one User Federation/Identity Provider? Can you provide more detail on how you've done this?
What would be the suggested way to automate resources creation? I use various home made Ansible roles and I find the Keycloak API to be inconsistent. Eg: Various GET methods that doesn't return complete payload and some…
May I know how many replicas and CACHE_OWNERS do you have?
It looks like Quarkus is going to be considered for one of the next major release [1]. That said, do you believe it will still be possible to extend Keycloak using the deployment-scanner? Also, do you happen to have…
When using a K8s cluster with the helm chart [1], it's actually the stateful set that takes care to the update. When the first replica restart, Keycloak makes the updates to the database itself. Sometimes rolling back…
Cool list but I would like to see them being implemented using FP approach when possible.