[
https://issues.apache.org/jira/browse/CURATOR-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15608288#comment-15608288
]
ASF GitHub Bot commented on CURATOR-356:
----------------------------------------
GitHub user eolivelli opened a pull request:
https://github.com/apache/curator/pull/170
CURATOR-356 Allow SASL configuration for TestingServer
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/eolivelli/curator CURATOR-356
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/curator/pull/170.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #170
----
commit dd20f1dbed3879372483d7e8f7eb05d920707168
Author: eolivelli <[email protected]>
Date: 2016-10-26T11:43:21Z
CURATOR-356 Allow SASL configuration for TestingServer
----
> Allow SASL configuration for TestingServer
> ------------------------------------------
>
> Key: CURATOR-356
> URL: https://issues.apache.org/jira/browse/CURATOR-356
> Project: Apache Curator
> Issue Type: Improvement
> Components: Tests
> Affects Versions: 3.2.0
> Reporter: Enrico Olivelli
>
> I would like to set the folloing properties on my TestingServer
> {code}
> properties.setProperty("authProvider.1",
> "org.apache.zookeeper.server.auth.SASLAuthenticationProvider");
> properties.setProperty("kerberos.removeHostFromPrincipal", "true");
> properties.setProperty("kerberos.removeRealmFromPrincipal", "true");
> {code}
> Would it be better to let QuorumConfigBuilder (and InstanceSpec) accept a
> custom Properties object to be merged to the actual configuration ?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
