You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@slider.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2015/11/12 16:51:11 UTC

[jira] [Commented] (SLIDER-983) Use RegistrySecurity for SliderClient

    [ https://issues.apache.org/jira/browse/SLIDER-983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15002278#comment-15002278 ] 

Steve Loughran commented on SLIDER-983:
---------------------------------------

+ (as discussed in a hangout): use the registry security notion of a conf option to list all ZK ACLs to give full write access. There's a method in RegistrySecurity to parse the string & append the current realm to any sasl:user@ strings. 

> Use RegistrySecurity for SliderClient
> -------------------------------------
>
>                 Key: SLIDER-983
>                 URL: https://issues.apache.org/jira/browse/SLIDER-983
>             Project: Slider
>          Issue Type: Bug
>          Components: client, security
>    Affects Versions: Slider 0.81
>            Reporter: Billie Rinaldi
>            Assignee: Billie Rinaldi
>
> Currently SliderClient is not using SASL when connecting to ZooKeeper, so when security is enabled SliderClient silently fails to create the default ZK node.  I think we should change the behavior so that it throws an exception if the node isn't created when requested, and we should also enable secure connection to ZooKeeper in the client.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)