Add additional security - ability to define your own SSL certificate

[chocolatey]

Add additional security - ability to define your own SSL certificate

[adilio]

On further discussion with @steviecoaster, we've agreed to leave some of this work out of the first release. We are striving to keep this simple, and weaving in the -InternetEnabled bits will add complexity at this point. We may revisit this later, possibly when revising the "distributed" approach with a new version of Organizational Deployment Guide.

@steviecoaster, I'll leave this open just for this one piece, if that's OK:

• Generate Register-Endpoint.ps1 script to pair with a ClientSetup.ps1 script, and output this script to choco-setup\files.

[adilio]

For the first release, to meet our internally-defined security requirements and maintain parity with QDE, we have decided to include the ability to define your own SSL Certificate.. This should cover the use cases of users bringing their own Domain cert, or purchasing a third-party cert. This is our minimum requirement if the user intends to expose this server to external endpoints on the Internet.

This will involve the following:

• Update Set-SSLSecurity.ps1 with logic to:
  • Accept external cert
  • Copy to appropriate cert store
  • Reassign services and bindings
  • Import cert into Java Key Store for Nexus
  • Update firewall rule for Nexus to 8443
• Update Jenkins job templates in the jenkins folder to reflect change of port for repo URI
• Move order of Jenkins script to the end again, as we need the CN to update repo URI