Repository navigation
Inconsistent availability and visibility of client scope "roles" #50303
Unanswered
UristMcEngineer
asked this question in
Q&A
Replies: 0 comments
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 loa 8000 ding. Please reload this page.
When creating several keycloak instances in different k8s clusters but using the same terraform configuration I find some inconsistent behaviour regarding the automatically created client scope "roles" in a newly created realm. In one instance the client scope is present in the json-export and visible in the GUI. In a second instance the client scope is present in the json-export but not visible in the GUI. In a third instance the client scope is neither present in the json-export nor visible in the GUI. Terraform configuration setting the client scope "roles" as optional in a specific client fails in the third instance but not the first two. To alleviate my confusion I ask the community for help answering the following questions: What determines the availability and visibility of the client scope "roles"? Is it whether or not a client exists in the cluster that has requested the roles scope from keycloak? Is it something I did in the GUI that led to the creation of the client scope without me noticing? Is the inconsistency originating from the terraform-provider?
Any help is highly appreciated.
All reactions