[
https://issues.apache.org/jira/browse/AMBARI-17621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15367531#comment-15367531
]
Hadoop QA commented on AMBARI-17621:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12816799/AMBARI-17621.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7736//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7736//console
This message is automatically generated.
> Kerberized Solr support for Atlas
> ---------------------------------
>
> Key: AMBARI-17621
> URL: https://issues.apache.org/jira/browse/AMBARI-17621
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-17621.patch
>
>
> Currently Atlas does not support kerberized Solr communication.
> To make kerberized Solr client work:
> 1\. Set `java.security.auth.login.config` property, which points to a jaas-
> file (with Client block)
> 2\. Use Kerberos http client configurer.
> This option should be bind to a new property (e.g.:
> "atlas.solr.kerberos.enable")
> call this before creating CloudSolrClient instance: (most likely
> Solr5Index.java)
>
>
>
> boolean securityEnabled =
> PropertiesUtil.getBooleanProperty("atlas.solr.kerberos.enable", false);
> if (securityEnabled) {
> System.setProperty("java.security.auth.login.config",
> "/etc/atlas/conf/atlas-jaas.conf");
> HttpClientUtil.setConfigurer(new Krb5HttpClientConfigurer());
> }
>
> some useful documentation from Ranger:
> <https://cwiki.apache.org/confluence/display/RANGER/How+to+configure+Solr+Clou
> d+with+Kerberos+for+Ranger+0.5>
> On ambari side: we should handle this property if kerberos is enabled. The new
> property should be added only if Solr is used for Atlas
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
