[
https://issues.apache.org/jira/browse/AMBARI-12247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14611182#comment-14611182
]
Velmurugan Periasamy commented on AMBARI-12247:
-----------------------------------------------
Passed python unit tests (in branch-2.1)
----------------------------------------------------------------------
Ran 226 tests in 6.437s
OK
----------------------------------------------------------------------
Total run:758
Total errors:0
Total failures:0
OK
> Ranger Plugin SSL configuration for YARN needs to be fixed to not clash with
> HDFS
> ---------------------------------------------------------------------------------
>
> Key: AMBARI-12247
> URL: https://issues.apache.org/jira/browse/AMBARI-12247
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.1.0
> Reporter: Velmurugan Periasamy
> Assignee: Velmurugan Periasamy
> Priority: Critical
> Fix For: 2.1.0
>
> Attachments:
> 0001-AMBARI-12247-Use-separate-ranger-policymgr-ssl.xml-f.patch
>
>
> When enabling SSL for Ranger, Yarn plugin communication breaks due to the
> below two issues.
> 1] Ambari code generates ranger-policymgr-ssl.xml for both HDFS and Yarn.
> Need to generate different config file name for each service (because
> NameNode and ResourceManager can be running on the same host)
> 2] In yarn config (Advanced ranger-yarn-security),
> ranger.plugin.yarn.policy.rest.ssl.config.file attribute needs to be set as
> /etc/hadoop/conf/ranger-policymgr-ssl-yarn.xml => Currently, it is using the
> default value /etc/yarn/conf/ranger-policymgr-ssl.xml which is incorrect
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
