C4B Azure Enviornment - Only allow use of CA Certs #379
Description
Description of Changes Requested
Have run into the case where a customer has used a self-signed certificate to setup the C4B Azure Enviornment. This is all good until they go to deploy Chocolatey to their endpoints and realize they need a method of deploying their cert as well. Otherwise the endpoint will never be able to SSL handshake to the azure enviornment.
Feel it would be better practice if we updated documentation to only allow for use of CA trusted certs so an issue doesn't come back to support of how do we deploy our certificate to our endpoints? In QSG we handle this by hosting the self-signed cert for download over an IIS entry at hostname: port 80. However doing so in an Azure online infrastructure is not a good security practice.
References:
- ZenDesk Ticket
- Link to current Self-Signed SSL Certificates section of C4B Azure Enviornment documentation.
Tagging @pauby @Windos and @JPRuskin for additional comments to this suggestion.