[
https://issues.apache.org/jira/browse/SLIDER-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14165634#comment-14165634
]
ASF subversion and git services commented on SLIDER-392:
--------------------------------------------------------
Commit ee7844ea28734b7056c44f6e012de4dff3cf0720 in incubator-slider's branch
refs/heads/develop from [~jmaron]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;h=ee7844e ]
SLIDER-392 auto set the global security_enabled app config property
> Security enabled or not should depend on correct configuration
> --------------------------------------------------------------
>
> Key: SLIDER-392
> URL: https://issues.apache.org/jira/browse/SLIDER-392
> Project: Slider
> Issue Type: Bug
> Components: agent-provider, app-package
> Affects Versions: Slider 0.50
> Reporter: Sumit Mohanty
> Assignee: Jonathan Maron
> Fix For: Slider 0.60
>
>
> Several packages rely on core-site config properties to determine if the
> cluster is secure. However, core-site is not being passed on to the agent
> from agent provider.
> This by itself could be the bug and it may make sense to pass core-site,
> yarn-site, etc. if explicitly asked via appConfig property "system_configs":
> "core-site".
> Alternatively, we can introduce a new appConfig.json variable for security.
> But lets investigate if passing core-site, yarn-site, etc when application
> asks for it is a good idea or not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
