[
https://issues.apache.org/jira/browse/ZOOKEEPER-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom Klonikowski updated ZOOKEEPER-1112:
---------------------------------------
Attachment: ZOOKEEPER-1112_3.patch
ZOOKEEPER-1112_2.patch
ZOOKEEPER-1112_1.patch
Further improvements and splitted patch into (consecutive) work items
Patch 1:
- implements sasl operations
- extended tests/zkServer.sh to start a digest-md5 enabled server
- simple test that checks the initial digest-md5 response
No external requirements yet, but you can already let your own sasl
implementation/library communicate with a (sasl-enabled) zookeeper via
zoo_(a)sasl function.
Or you can additionally use
Patch 2:
- provides a simple api for sasl authentication (zoo_sasl_init,
zoo_sasl_connect, zoo_sasl_authenticate)
- requires libsasl2 (and plugins)
- autoconf/make configuration
- test for digest-md5 authentication
- extended configuration for digest-md5 sasl server required by sasl2
Patch 3:
- includes a sasl-enabled cli as additional make artifacts
When using the test configuration as in src/c/tests/jaas.digest.server.conf you
can login via:
cli_sasl_st -u super -h zk-sasl-md5 -m DIGEST-MD5 hostlist
and password 'test'.
If you set up Kerberos 5 on the server side and have a valid ticket its just:
cli_sasl_st -m GSSAPI hostlist
This patches deprecate the earlier single patch.
> Add support for C client for SASL authentication
> ------------------------------------------------
>
> Key: ZOOKEEPER-1112
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1112
> Project: ZooKeeper
> Issue Type: New Feature
> Reporter: Eugene Koontz
> Attachments: ZOOKEEPER-1112.patch, ZOOKEEPER-1112_1.patch,
> ZOOKEEPER-1112_2.patch, ZOOKEEPER-1112_3.patch, zookeeper-c-client-sasl.patch
>
>
> Hopefully this would leverage the SASL server-side support provided by
> ZOOKEEPER-938. It would be similar to the Java SASL client support also
> provided in ZOOKEEPER-938.
> Java has built-in SASL support, but I'm not sure what C libraries are
> available for SASL and if so, are they compatible with the Apache license.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
