Fix TSL host mismatch

[coleheinbaugh]

This PR fixes the TSL host mismatch by manually setting the TSL server name in TestSelfSignedCA to match what is given by the new dynamic leaf cert generator.

In commit c814860 we start using dynamic leaf certs, that have the server name of local host as opposed to the old cert this test would get which allowed for server name local host and cassandra.

TODO only if you're a HashiCorp employee

• Backport Labels: If this fix needs to be backported, use the appropriate backport/ label that matches the desired release branch.
  • LTS: If this fixes a critical security vulnerability or severity 1 bug, it will also need to be backported to the current LTS versions of Vault. To ensure this, use all available enterprise labels.
• Jira: If this change has an associated Jira, it's referenced either in the PR description, commit message, or branch name.
• RFC: If this change has an associated RFC, please link it in the description.

PCI review checklist

• I have documented a clear reason for, and description of, the change I am making.
• If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
• If applicable, I've documented the impact of any changes to security controls.

Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.

[vercel]

Deployment failed with the following error:

The `vercel.json` schema validation failed with the following message: should NOT have additional property `public`

Learn More: https://vercel.com/docs/concepts/projects/project-configuration

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
vault-ui	Error		Jun 24, 2026 7:02pm

[github-actions]

CI Results:
All Go tests succeeded! ✅

[coleheinbaugh]

This PR should have been opened in Vault-Enterprise, so it has been moved there: https://github.com/hashicorp/vault-enterprise/pull/15813