Add configurable SASL Kerberos hostname override (Java-style kerberos.domain.name) #5233
+26
−4
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.
Introduce sasl.kerberos.domain.name, mirroring the Java client’s kerberos.domain.name so librdkafka users can target a fixed hostname portion in Kerberos service principals. Document the new property and register it in the config tables.
Update both SASL paths to honor the override:
Cyrus (Linux/macOS): pass the configured hostname to sasl_client_new() when present.
Win32 SSPI: build the SPN as service/override instead of the broker-advertised hostname.
This allows environments that rely on alternative hostnames (e.g., /etc/hosts aliases) to request the same SPN that the Java clients use.