-
Notifications
You must be signed in to change notification settings - Fork 246
New issue
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
grafana_sso_settings azuread / Entra ID - new required field (client_authentication) #1990
Comments
@grafana/identity-access-team could you check this? Looks like that the are a lot of fields used here that aren't in TF or documented. |
Thanks for the ping @spinillos , I think we should fix this on grafana side first while the feature is hashed out fully cc @mgyongyosi We should update https://github.com/grafana/grafana/blob/main/pkg/login/social/connectors/azuread_oauth.go#L385-L387 to perform the same check as we do when |
Merged fix into grafana, Lets keep this one open because we need to add support for other client authentication methods here |
I just tested this with the latest grafana image and I am still getting the |
Guessing there's been another downstream change as a slightly different error has started appearing for this resource, whether using the above workaround or not 🤕 It's now complaining that the auth_url isn't present, even though it is. The only fix I've found is to forcefully update any older providers to >=3.16.0 |
Terraform Version
1.10.4
Terraform Grafana Provider Version
3.16.0
Grafana Version
Cloud
Affected Resource(s)
grafana_sso_settings
Terraform Configuration Files
Expected Behavior
Actual Behavior
API failure returned:
Steps to Reproduce
terraform apply
terraform apply
Important Factoids
Looks like an API change at source (i.e., in this case Grafana Cloud), the following custom setting can be added to the terraform resource oauth2_settings (based on scraping network PUT in CloudUI):
Does this need to be handled better in the provider resource, or documentation to be updated to show as "required"?
References
No response
The text was updated successfully, but these errors were encountered: