Skip to content

Fix incorrect audit log IP when using Kubernetes impersonation#36322

Merged
tigrato merged 1 commit intomasterfrom
tigrato/fix-incorrect-audit-ip
Jan 5, 2024
Merged

Fix incorrect audit log IP when using Kubernetes impersonation#36322
tigrato merged 1 commit intomasterfrom
tigrato/fix-incorrect-audit-ip

Conversation

@tigrato
Copy link
Copy Markdown
Contributor

@tigrato tigrato commented Jan 5, 2024

Audit logs for Kubernetes requests showed incorrect IP addresses when reverse tunnel was used to forward the request.

Audit logs use 'req.RemoteAddr` which was never updated with the impersonated IP address.

Changelog: Fixed incorrect report of user's IP address in Kubernetes Audit Logs

Fixes #36288

Audit logs for Kubernetes requests showed incorrect IP addresses when
reverse tunnel was used to forward the request.

Audit logs use 'req.RemoteAddr` which was never updated with the
impersonated IP address.

Changelog: Fixed incorrect report of user's IP address in Kubernetes
Audit Logs

Fixes #36288

Signed-off-by: Tiago Silva <tiago.silva@goteleport.com>
@public-teleport-github-review-bot public-teleport-github-review-bot Bot removed the request for review from nklaassen January 5, 2024 18:17
@tigrato tigrato added this pull request to the merge queue Jan 5, 2024
Merged via the queue into master with commit 54b4189 Jan 5, 2024
@tigrato tigrato deleted the tigrato/fix-incorrect-audit-ip branch January 5, 2024 18:36
@public-teleport-github-review-bot
Copy link
Copy Markdown

@tigrato See the table below for backport results.

Branch Result
branch/v13 Create PR
branch/v14 Create PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Kubernetes Audit Events Metadata captured in the Teleport Audit Log not reporting correct client IP in field addr.remote

5 participants