Skip to content

[v17] Fix AWS Console (w/ integration) access when using IP Pinning#61655

Merged
marcoandredinis merged 2 commits intobranch/v17from
bot/backport-61489-branch/v17
Nov 21, 2025
Merged

[v17] Fix AWS Console (w/ integration) access when using IP Pinning#61655
marcoandredinis merged 2 commits intobranch/v17from
bot/backport-61489-branch/v17

Conversation

@marcoandredinis
Copy link
Copy Markdown
Contributor

Backport #61489 to branch/v17

changelog: Fixed AWS Console access when using AWS IAM Roles Anywhere or AWS OIDC integrations, when IP Pinning is enabled.

When IP Pinning is enabled, the certificate's pinned IP and the IP
presented by the client in the connection must be the same.

For AWS Console access which uses an integration, we don't use an
Application Service to proxy connections, the Proxy Service is used
instead.

In this situation, it uses a `net.Pipe` which sets both Local/Remote
addrs to `pipe`.

When validating whether that's the same IP as the one present in the
certificate's pinned IP, it fails because that's the address of an
intermediate connection.

This PR fixes this by wrapping the connection with an overrided
`RemoteAddr` method which returns the true client's IP extracted from
the context.
@marcoandredinis marcoandredinis added this pull request to the merge queue Nov 21, 2025
Merged via the queue into branch/v17 with commit 3f1c46c Nov 21, 2025
38 checks passed
@marcoandredinis marcoandredinis deleted the bot/backport-61489-branch/v17 branch November 21, 2025 12:05
@doggydogworld doggydogworld mentioned this pull request Dec 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants