we use UGS with a P4 server that has SSL enabled, and we are running into an issue when deploying UGS to PCs where no one has connected to P4 before. To connect to an SSL-enabled P4 server, the P4 trust fingerprint must be confirmed, which UGS currently does not support, and it shows a generic error message instead.
The only solution we can think of is adding automatic acceptance of the fingerprint during login using p4 trust -y. Do you have a better approach for this?
Good find and thanks for the report! You’re right, that path is not exercised much internally at Epic. I don’t have a quick fix or suggestion, sans patching code. I’ve created an issue to track this internally (UE-355341). In the mean time, it seems you’ve found a workaround so hopefully it’s not blocking you and your team.
I have already extended PerforceConnection.cs with the P4 trust command and I am calling it before the login step. Should I create a pull request for this change? Would you be interested in it?