Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use secureClientPort instead of clientPort #480

Open
maltesander opened this issue May 6, 2022 · 1 comment
Open

Use secureClientPort instead of clientPort #480

maltesander opened this issue May 6, 2022 · 1 comment
Labels

Comments

@maltesander
Copy link
Member

Currently for TLS and authentication we use the clientPort instead of secureClientPort due to a bug in ZooKeeper (https://issues.apache.org/jira/browse/ZOOKEEPER-4276).

Once this is fixed and we should switch from clientPort to secureClientPort and remove the portUnification property (allows plaintext and secured communication via the same port).

The necessary steps are documented in the code (see rust/crd/src/lib.rs)

Since this does not work in versions 3.8.0 or lower, it will be a little more work to differentiate between zookeeper versions with and without that bug.

Relates to PR #479.

@sbernauer
Copy link
Member

Good news, ZOOKEEPER-4276 was fixed and will be released in 3.10.0 🥳

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants