Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Add SSL certificate from ACM to Perforce Helix Core to allow SSL connections without p4 trust #358

Closed
henrykie opened this issue Oct 10, 2024 · 2 comments
Assignees
Labels

Comments

@henrykie
Copy link
Contributor

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.

@henrykie henrykie added feature-request feature request triage to be triaged by project maintainers perforce labels Oct 10, 2024
@henrykie
Copy link
Contributor Author

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.

@GrzesiekO GrzesiekO self-assigned this Oct 11, 2024
@gabebatista gabebatista removed the triage to be triaged by project maintainers label Nov 25, 2024
@henrykie
Copy link
Contributor Author

henrykie commented Dec 3, 2024

Closing for duplicate issue #402

@henrykie henrykie closed this as completed Dec 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants