Skip to content
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

azurerm_service_fabric_cluster support for client certificates common name #4528

Closed
arestarh opened this issue Oct 5, 2019 · 2 comments
Closed

Comments

@arestarh
Copy link
Contributor

arestarh commented Oct 5, 2019

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

You should be able to add both an admin and reader client certificates for Service Fabric clusters using either certificate thumbprint or common name.
Currently there is a support only for adding client certificates using certificate thumbprint via client_certificate_thumbprint block.

Adding client certificates using either certificate thumbprint or common name should be mutually exclusive, so this 2 options will not conflict.

I've raised this as a feature, but it could be argued that this is a bug.

New or Affected Resource(s)

  • azurerm_service_fabric_cluster

Potential Terraform Configuration

client_certificate_common_names {
   certificate_common_name = "fabricam.com"
   certificate_issuer_thumbprint = "8c2462bd8af801206f3284780e8f63271774902b"
   is_admin = false
}
katbyte pushed a commit that referenced this issue Mar 25, 2020
Addressing #4528

Added support in azurerm_service_fabric_cluster for client_certificate_common_name block. Example block:

client_certificate_common_name {
  certificate_common_name = "CertificateCommonName"
  is_admin   = true
  certificate_issuer_thumbprint = "3341DB6CF2AF72C611DF3BE3721A653AF1D43ECD50F584F828793DBE9103C3EE"
}
Change also required updating unit tests for Cluster Code Version (previous was no longer supported) as well as updating thumbprints from "33:41:DB:6C:F2:AF:72:C6:11:DF:3B:E3:72:1A:65:3A:F1:D4:3E:CD:50:F5:84:F8:28:79:3D:BE:91:03:C3:EE"
to
"3341DB6CF2AF72C611DF3BE3721A653AF1D43ECD50F584F828793DBE9103C3EE"
to fix error of

Error: Error creating Service Fabric Cluster "acctest-200312100109887030" (Resource Group "acctestRG-200312100109887030"): servicefabric.ClustersClient#Create: Failure sending request: StatusCode=400 -- Original Error: Code="InvalidCertificateThumbprint" Message="Certificate thumbprint '33:41:DB:6C:F2:AF:72:C6:11:DF:3B:E3:72:1A:65:3A:F1:D4:3E:CD:50:F5:84:F8:28:79:3D:BE:91:03:C3:EE' is invalid." Details=[]
@arestarh
Copy link
Contributor Author

@katbyte As long as PR #6097 addressed my request should I close this issue or you'll do this?

@ghost
Copy link

ghost commented May 17, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!

@ghost ghost locked and limited conversation to collaborators May 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants