-
Notifications
You must be signed in to change notification settings - Fork 300
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
addTokenSigningCertificate Invalid Parameters GCC High #1447
Comments
From the provider docs: "The Azure Provider can be used to configure infrastructure in Azure Active Directory using the Microsoft Graph API." If the official API docs says that this endpoint isn't available in GCC High then the provider is working as expected. |
The Microsoft documentation must be out of date. The endpoint is available as verified by using the Graph CLI which is a wrapper for the Graph API (https://learn.microsoft.com/en-us/graph/cli/overview). |
Seems like a malformed payload as the body only contains |
Here is the new TF resource:
And this is the API request from the debug. Same error but display_name is shown:
|
Community Note
Terraform (and AzureAD Provider) Version
Terraform v1.9.3
provider registry.terraform.io/hashicorp/azuread v2.53.1
Affected Resource(s)
azuread_service_principal_token_signing_certificate
Terraform Configuration Files
Debug Output
https://gist.github.com/offlineadmin/f039c2015b3dc34748be3c75abd111e8
Panic Output
Expected Behavior
Resource should have been created
Actual Behavior
The API post for addTokenSigningCertificate fails because TF is sending invalid parameters in the request body. See below on line 13
Steps to Reproduce
terraform apply -auto-approve
Important Factoids
This is in GCC High / USGov L4.
I have tried this with TF for Windows and TF for Ubuntu.
I manually used the API with the Graph CLI and it worked as expected with the same credentials in the same tenant.
I have tried using older versions of azuread provider and terraform, but no change
References
The text was updated successfully, but these errors were encountered: