Fix proxy SPNego authentication to respect krb5.conf canonicalization settings. #541
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR changes
SPNegoSchemeFactoryconstructor inProxyUtils.javato useuseCanonicalHostname=false, deferring hostname canonicalization to the Kerberos library based onkrb5.confconfiguration instead of forcing it at the SDK level.The previous implementation forced hostname canonicalization for proxy Kerberos authentication, overriding user-configured
krb5.conf settings (rdns, dns_canonicalize_hostname). This caused authentication failures in environments with specific Kerberos configurations.Client libraries should respect system Kerberos configuration rather than override it. This fix makes the SDK compliant with standard Kerberos behavior.
Migration note: Users whose non-compliant Kerberos setups were accidentally working due to forced canonicalization may need to verify their
krb5.confsettings are correctly configured.