Support for ClientCertificateCommonNames in azurerm_service_fabric_cluster

[JSchenken]

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

Currently there is support for client_certificate_thumbprint, but no support for the ability to specify client certificates by common name. Azure supports this and the ARM templates have a parameter for ClientCertificateCommonNames (see this link for more details).

"ClientCertificateCommonNames": [ { "CertificateCommonName": "[CertificateCommonName]", "CertificateIssuerThumbprint": "[Thumbprint1,Thumbprint2,Thumbprint3,...]", "IsAdmin": true } ],

This request is to also support a client_certificate_commonnames setting in azurerm_service_fabric_cluster resource.

New or Affected Resource(s)

azurerm_service_fabric_cluster

Potential Terraform Configuration

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key.

References

https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-windows-cluster-x509-security

• #0000

[JSchenken]

dupe of 4528

[ghost]

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!