When a client first connects to Helix Core server they will need to p4 trust the server after validating the fingerprint returned by initial connection. This inhibits automated provisioning and connections from CI/CD server that have not "trusted" the server previously.
Solution/User Experience
Provide a mechanism for adding the certificate to the certificate.txt file on the Helix Core server. See this documentation for details.
Alternative solutions
Manually run p4 trust in the service containers on initial connection. Manually configure the certificates on the Helix Core server.
Currently, there is not an easy way to use a certificate generated by ACM inside an application running on EC2. We could potentially consider running Helix Core inside a nitro enclave.
Use case
When a client first connects to Helix Core server they will need to
p4 trust
the server after validating the fingerprint returned by initial connection. This inhibits automated provisioning and connections from CI/CD server that have not "trusted" the server previously.Solution/User Experience
Provide a mechanism for adding the certificate to the
certificate.txt
file on the Helix Core server. See this documentation for details.Alternative solutions
Manually run p4 trust in the service containers on initial connection. Manually configure the certificates on the Helix Core server.