Problem Statement

Certificate does not get presented to Vault Auth, unless forced with GetClientCertificate.
This is also how vault client is authenticating mTLS: https://github.com/hashicorp/vault/blob/df563db795d6e95e7695e0df2ede069f6540e2cd/api/client.go#L350

When using cert with different intermediate than Vault Server we get following error:

Code: 400. Errors:

client certificate must be supplied

Proposed Changes

Use tls.Config.GetClientCertificate instead of tls.Config.Certificates.
We've tested with @jasonjoo2010 this against our infra and it fixes the issue.

Format

Please ensure that your PR follows the following format for the title:

feat(scope): add new feature
fix(scope): fix bug
docs(scope): update documentation
chore(scope): update build tool or dependencies
ref(scope): refactor code
clean(scope): provider cleanup
test(scope): add tests
perf(scope): improve performance
desig(scope): improve design

Where scope is optionally one of:

• charts
• release
• testing
• security
• templating

Checklist

• I have read the contribution guidelines
• All commits are signed with git commit --signoff
• My changes have reasonable test coverage
• All tests pass with make test
• I ensured my PR is ready for review with make reviewable