[8.x](backport #5494) Add support for CLI flag for mTLS client certificate key passphrase #5574
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
It adds support for encrypted client certificate key during install/enroll, which done by the cli flag
--elastic-agent-cert-key-passphrase
.Why is it important?
It enables Elastic Agent to be configured with passphrase-protected private keys for client mTLS certificates.
Checklist
[ ] I have made corresponding change to the default configuration files./changelog/fragments
using the changelog tool[ ] I have added an integration test or an E2E testAuthor's checklist
Tests
--elastic-agent-cert-key-passphrase
adheres to the same requirements as--fleet-server-cert-key-passphrase
.--elastic-agent-cert-key
and--elastic-agent-cert
are provided when--elastic-agent-cert-key-passphrase
is present.*enrollCmdOption.remoteConfig()
accurately incorporates the passphrase intotlscommon.CertificateConfig
.fleetclient.NewWithConfig
generates a valid client capable of establishing an mTLS connection to a mock server.policy with SSL config
to ensure the client certificate key passphrase from the cli is not left in the config when the policy's client client certificate key is not passphrase-protected.Disruptive User Impact
How to test this PR locally
Related issues
Questions to ask yourself
This is an automatic backport of pull request #5494 done by [Mergify](https://mergify.com).