We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TF code
resource "keycloak_openid_client" "openid_client" { realm_id = data.keycloak_realm.realm.id client_id = "xxxx" name = "xxxx" enabled = true access_type = "CONFIDENTIAL" client_authenticator_type = "client-secret" standard_flow_enabled = false implicit_flow_enabled = false direct_access_grants_enabled = false service_accounts_enabled = true valid_redirect_uris = [] web_origins = [] authorization { policy_enforcement_mode = "ENFORCING" decision_strategy = "AFFIRMATIVE" allow_remote_resource_management = "true" } }
After it's applied, the Keycloak console still shows Decision strategy as UNANIMOUS.
Decision strategy
UNANIMOUS
The RPT authorization result matches the Decision strategy in the Keycloak console.
The text was updated successfully, but these errors were encountered:
fixed keycloak#965 by loading the authorization settings
fe7f38d
fixes keycloak#965 by loading the authorization settings
2ad9361
seems the issue also relate to this keycloak/keycloak#16998
Sorry, something went wrong.
the same issue keycloak:24.0.4 provider: 4.4.0
changing values via
resource "keycloak_openid_client" "some_client" { ... authorization { policy_enforcement_mode = "ENFORCING" decision_strategy = "UNANIMOUS" #policy_enforcement_mode = "PERMISSIVE" #decision_strategy = "AFFIRMATIVE" }
not work with both "policy_enforcement_mode" and "decision_strategy"
Successfully merging a pull request may close this issue.
TF code
After it's applied, the Keycloak console still shows
Decision strategy
asUNANIMOUS
.The RPT authorization result matches the
Decision strategy
in the Keycloak console.The text was updated successfully, but these errors were encountered: