P4TRUST

When P4 Code Review is configured to connect to a P4 Server (P4D) using an SSL connection, P4 Code Review automatically executes the p4 trust command, which accepts the SSL fingerprint and creates a p4trust file containing a list of trusted servers and their fingerprints.

The location the p4trust file is saved to depends on whether P4 Code Review is connected to a single P4 Server or to multiple P4 Servers.

• Single P4 Server: saved as SWARM_ROOT/data/p4trust
• Multiple P4 Servers: saved as a separate file for each server. For example, for serverA, serverB, and serverC they are saved as:
• SWARM_ROOT/data/serverA/p4trust
• SWARM_ROOT/data/serverB/p4trust
• SWARM_ROOT/data/serverC/p4trust

If a certificate changes

If a certificate for a P4 Server is changed for any reason then P4 Code Review connections to that server will fail after that server is restarted.

The solution is to delete the p4trust file for that P4 Server from the location described above. P4 Code Review will automatically run p4 trust on the next request if the p4trust file is not found.