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

Backport of docs - update x_forwarded_for_authorized_addrs into release/1.10.x #19733

Conversation

hc-github-team-secure-vault-core
Copy link
Collaborator

Backport

This PR is auto-generated from #19546 to be assessed for backporting due to the inclusion of the label backport/1.10.x.

The below text is copied from the body of the original PR.


On https://developer.hashicorp.com/vault/docs/configuration/listener/tcp#x_forwarded_for_authorized_addrs we could be clearer in the information we provide in order to help users of Vault log the client IP when fronting Vault with a load balancer, this PR aims to help.

preview: https://vault-2q49ku9fo-hashicorp.vercel.app/vault/docs/configuration/listener/tcp#x_forwarded_for_authorized_addrs


Overview of commits

@hc-github-team-secure-vault-core hc-github-team-secure-vault-core force-pushed the backport/tcp-listener-x-forwarded-for-update/remarkably-present-anchovy branch 2 times, most recently from db85982 to 85388f9 Compare March 23, 2023 23:00
@yhyakuna yhyakuna enabled auto-merge (squash) March 23, 2023 23:01
@VioletHynes VioletHynes added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Jul 6, 2023
@ncabatoff ncabatoff merged commit b193dca into release/1.10.x Aug 17, 2023
37 of 39 checks passed
@ncabatoff ncabatoff deleted the backport/tcp-listener-x-forwarded-for-update/remarkably-present-anchovy branch August 17, 2023 18:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed pr/no-changelog pr/no-milestone
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants