Server and client setup

By default, a P4PORT setting that does not specify a protocol is assumed to be in plaintext. It is good practice to configure Helix Core client applications to explicitly specify the protocol to use when establishing a client-server connection.

plaintext	ssl
`tcp:host:port`	`ssl:host:port`
`tcp:123.45.67.8:1666`	`ssl:123.45.67.8:1666`
	The first time that users connect to an SSL-enabled Helix Core Server, their client application informs them of the certificate fingerprint of the server’s identity key. If users can independently verify that the fingerprint is accurate, they should add the server to their `P4TRUST` file by doing one of the following: using the `p4 trust` command following the prompts in the client application manually adding the fingerprint to the file Tip Consider the alternative of SSL connections that do not require P4TRUST, which is described in the `p4 trust` topic of Helix Core Command-Line (P4) Reference.

plaintext

ssl

tcp:host:port ssl:host:port

tcp:123.45.67.8:1666 ssl:123.45.67.8:1666

The first time that users connect to an SSL-enabled Helix Core Server, their client application informs them of the certificate fingerprint of the server’s identity key.

If users can independently verify that the fingerprint is accurate, they should add the server to their P4TRUST file by doing one of the following:

using the p4 trust command
following the prompts in the client application
manually adding the fingerprint to the file

Tip

Consider the alternative of SSL connections that do not require P4TRUST, which is described in the p4 trust topic of Helix Core Command-Line (P4) Reference.