[
https://issues.apache.org/jira/browse/AMBARI-20013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó resolved AMBARI-20013.
-----------------------------------
Resolution: Fixed
committed to branch-2.5:
{code:java}
commit be18ae1bc541474829f7a693b7249a41f2fb0fa5
Author: oleewere <[email protected]>
Date: Mon Feb 13 18:34:50 2017 +0100
AMBARI-20013. Add Solr authorization settings during LogSearch/Atlas/Ranger
startup (oleewere)
{code}
committed to trunk:
{code:java}
commit 347ba2a9983d400cddf4d888e7f8c15d72b71d5a
Author: oleewere <[email protected]>
Date: Mon Feb 13 18:34:50 2017 +0100
AMBARI-20013. Add Solr authorization settings during LogSearch/Atlas/Ranger
startup (oleewere)
{code}
> Add Solr authorization settings during LogSearch/Atlas/Ranger startup
> ---------------------------------------------------------------------
>
> Key: AMBARI-20013
> URL: https://issues.apache.org/jira/browse/AMBARI-20013
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.5.0
> Reporter: Olivér Szabó
> Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-20013.patch
>
>
> During ranger/logsearch/atlas startup, we need to make sure these services
> have permission to access for specific collections.
> Also ranger plugins should be able to write into ranger collection as well.
> There will be a new solr_cloud_util function to add user-roles to solr, which
> will update security.json on the zookeeper znode.
> For newly added services with ranger plugins, solr will need to be restarted
> to generate the correct security.json on zookeeper.
> Also this task will introduce a new custom security.json which can override
> that is used by default.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
