Skip to content

ZOOKEEPER-5108: Client SASL settings set to true with trailing whitespace are read as false - #2484

Open
dajiaohuang wants to merge 1 commit into
apache:masterfrom
dajiaohuang:ZOOKEEPER-5108
Open

dajiaohuang wants to merge 1 commit into
apache:masterfrom
dajiaohuang:ZOOKEEPER-5108

Conversation

@dajiaohuang

Copy link
Copy Markdown

Fixes ZOOKEEPER-5108

ZKClientConfig.isSaslClientEnabled() and SASL hostname canonicalization now use the existing ZKConfig.getBoolean accessor, which trims property values before parsing. This keeps explicitly configured true values consistent with the existing configuration behavior.

Regression coverage verifies trailing whitespace for both SASL settings.

Validation:

  • ClientCanonicalizeTest: 7 tests passed.
  • SaslClientTest: 1 test passed.
  • Module-scoped -Pfull-build Maven verification on native Windows/JDK 25 with tests skipped: Apache RAT passed (0 unapproved/unknown files), SpotBugs passed (0 bugs/errors), Checkstyle passed (0 violations), and the Jute/server sources and tests compiled. Javadoc emitted warnings in unchanged source files; the build succeeded.
  • git diff --check passed.

Generated-by: Pi 1.4.0 (openai-codex/gpt-6-luna)

…pace are read as false

Use the existing trimmed boolean configuration accessor for SASL client enablement and hostname canonicalization, and cover both trailing-space cases.

Generated-by: Pi 1.4.0 (openai-codex/gpt-6-luna)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants