You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently automate the process of creating a self-signed certificate on the Helix Core machine during initialization. Instead, it would be best to make this flag optional for use cases where Helix Core is running behind an NLB that is performing TLS termination with a trusted CA.
Would translate to an invocation of the p4_configure.sh script that does not use the SDP to generate a self-signed certificate. We would also need to require that the Helix Core server is expecting plaintext communication from the NLB.
Alternative solutions
No response
The text was updated successfully, but these errors were encountered:
Use case
We currently automate the process of creating a self-signed certificate on the Helix Core machine during initialization. Instead, it would be best to make this flag optional for use cases where Helix Core is running behind an NLB that is performing TLS termination with a trusted CA.
Solution/User Experience
Would translate to an invocation of the
p4_configure.sh
script that does not use the SDP to generate a self-signed certificate. We would also need to require that the Helix Core server is expecting plaintext communication from the NLB.Alternative solutions
No response
The text was updated successfully, but these errors were encountered: