RELATED IDEAS
Installing K2 with trusted certificates instead of self-signed
K2 typically installs self-signed certificates for internal use by its services, which is generally acceptable for most customers. However, self-signed certificates violate "CAT II finding in IIS Site STIG" policy. During the installation process, it would be great if you could specify a trusted certificate that K2 can use for its internal services. These are separate certificates to the IIS binding certificate that is currently configurable.
Some official documentation detailing the internal certificates generated during the K2 installation process, including their purpose and the current limitation of not being able to specify or replace them with custom certificates would also be helpful.
Certificates includes:
* Environment Owner
* K2 OAuth High Trust
* K2 On Premise Root
* “hostname.domain.topleveldomain” – issued by “K2 On Premise Root”
* K2 STS Certificate
* sourcecode-appit-apptemplates