Secure Channel script file names

This is a reference for the Secure Channel certificate file names created by the SecureChannelCertificateInstaller.ps1 script.

SecureChannelCertificateInstaller.ps1 will create file names that it recognizes, and that are recognized by the install.sh script. This file name syntax isn't necessary if you are using the MMC or other methods to install certificates. Your company may provide files with a different naming syntax. If you want to use the script to install the certificates, rename them using the following syntax. The other file types use the same name, but with a different extension (CER, KEY, PEM, PFX).

• A CA certificate without private key CER file syntax is: RootCA_<40-character alphanumeric string>.cer, for example RootCA_52B0188BBD56D07475B29FE30C4017AF4A7D9052.cer

• A gateway certificate with private key PFX file syntax is: <gateway machine name> Studio Database Gateway_<40-character alphanumeric string>_<40-character alphanumeric string>.pfx, for example MACHINE1 Studio Database Gateway_0E4C8FADABB8C0AD1692EFB9D18C628D3759884C_52B0188BBD56D07475B29FE30C4017AF4A7D9052.pfx

• A client certificate with private key PFX file syntax is: <client name> Studio Database Client_<40-character alphanumeric string>_<40-character alphanumeric string>.pfx, for example Client1 Studio Database Client_CC1727A4663763D3FEBDD486B9F44706A7EF4307_52B0188BBD56D07475B29FE30C4017AF4A7D9052.pfx

  Tip: The 40-character alphanumeric strings generated by the script use one or more certificate thumbprints (or hashes). These strings are not validated by the script, so any combination of numbers or letters should work. In PowerShell, you can run the command -join ((65..90) + (97..122) | Get-Random -Count 40 | % {[char]$_}) to generate a similar string.