curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cameron McKenzie (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (CURATOR-356) Allow SASL configuration for TestingServer
Date Wed, 26 Oct 2016 22:36:58 GMT

     [ https://issues.apache.org/jira/browse/CURATOR-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Cameron McKenzie closed CURATOR-356.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.11.1
                   3.2.1

> 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
>             Fix For: 3.2.1, 2.11.1
>
>
> 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)

Mime
View raw message