fix: add the proxy-protocol option#33276
Conversation
Unreported flaky test detectedIf the flaky tests below are affected by the changes, please review and update the changes accordingly. Otherwise, a maintainer should report the flaky tests prior to merging the PR. org.keycloak.testsuite.webauthn.registration.passwordless.PwdLessResidentKeyRegTest#residentKeyRequiredCorrectKeycloak CI - WebAuthn IT (chrome) |
|
@vmuzikar updated to proxy-protocol-enabled |
Unreported flaky test detectedIf the flaky tests below are affected by the changes, please review and update the changes accordingly. Otherwise, a maintainer should report the flaky tests prior to merging the PR. org.keycloak.testsuite.webauthn.passwordless.WebAuthnPwdLessPropertyTest#changeAuthenticatorPropertiesKeycloak CI - WebAuthn IT (chrome) org.keycloak.testsuite.webauthn.registration.PubKeySignRegisterTest#publicKeySignaturesEmptyKeycloak CI - WebAuthn IT (chrome) org.keycloak.testsuite.webauthn.registration.passwordless.PwdLessPubKeySignRegTest#publicKeySignaturesNonExistingKeycloak CI - WebAuthn IT (chrome) |
closes: keycloak#10492 Signed-off-by: Steve Hawkins <[email protected]>
Co-authored-by: Martin Bartoš <[email protected]> Signed-off-by: Steven Hawkins <[email protected]>
Unreported flaky test detectedIf the flaky tests below are affected by the changes, please review and update the changes accordingly. Otherwise, a maintainer should report the flaky tests prior to merging the PR. org.keycloak.testsuite.webauthn.registration.passwordless.PwdLessPubKeySignRegTest#publicKeySignaturesNonExistingKeycloak CI - WebAuthn IT (chrome) |
closes: #10492
cc @keycloak/cloud-native-maintainers
Does an integration test for this make sense? The quarkus pr did not include a high level test either.
The quarkus name is use-proxy-protocol, but we generally want our proxy options to all start with proxy, so for us it's just proxy-protocol - but that does read oddly as a boolean. However proxy-use-proxy-protocol seems too long.
We potentially could be opinionated and set this to true when https is enabled and proxy-headers has no value - but we'd to understand if there are any risks / performance overhead before doing that.
@vmuzikar do you want to consider this for v26?