Add correct IP propagation on node registration and login IP to bot certs#34454
Add correct IP propagation on node registration and login IP to bot certs#34454
Conversation
9b3a6b3 to
fc3c117
Compare
|
The PR changelog entry failed validation: Changelog entry not found in the PR body. Please add a "no-changelog" label to the PR, or changelog lines starting with |
|
The PR changelog entry failed validation: Changelog entry not found in the PR body. Please add a "no-changelog" label to the PR, or changelog lines starting with |
|
@nklaassen @xacrimon friendly ping |
|
The PR changelog entry failed validation: Changelog entry not found in the PR body. Please add a "no-changelog" label to the PR, or changelog lines starting with |
2 similar comments
|
The PR changelog entry failed validation: Changelog entry not found in the PR body. Please add a "no-changelog" label to the PR, or changelog lines starting with |
|
The PR changelog entry failed validation: Changelog entry not found in the PR body. Please add a "no-changelog" label to the PR, or changelog lines starting with |
|
@nklaassen addressed your comments. |
Co-authored-by: Nic Klaassen <nic@goteleport.com>
e05f1e3 to
550cda3
Compare
This PR adds correct IP propagation when node/bot joins cluster through
RegisterUsing*calls and uses this IP to addLoginIPto the certificates generated for bots.Before we always took IP from the context (e.g. from the incoming connection) directly, but when cluster joining was performed through Proxy and not directly through Auth server, then we ended up with the Proxy IP address. In this PR we make sure that Proxy sets correct IP to the request and Auth server trusts it, if it's coming from the Proxy, otherwise it takes IP from the connection.
Changelog: Fix IP propagation for nodes/bots joining the cluster and add LoginIP to bot certificates.
Fixes #13483