[
https://issues.apache.org/jira/browse/AMBARI-17688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15379271#comment-15379271
]
Hadoop QA commented on AMBARI-17688:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12818122/AMBARI-17688.1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 4 new
or modified test files.
{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:green}+1 core tests{color}. The patch passed unit tests in
ambari-server ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7862//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7862//console
This message is automatically generated.
> Ranger stack changes in Ambari to support secure Solr
> -----------------------------------------------------
>
> Key: AMBARI-17688
> URL: https://issues.apache.org/jira/browse/AMBARI-17688
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Mugdha Varadkar
> Assignee: Mugdha Varadkar
> Fix For: 2.4.0
>
> Attachments: AMBARI-17688.1.patch, AMBARI-17688.patch
>
>
> Recommend below properties for plugin, if solr secure is enabled on Ranger
> Admin:
> {noformat}
> xasecure.audit.jaas.Client.loginModuleName=com.sun.security.auth.module.Krb5LoginModule
> xasecure.audit.jaas.Client.loginModuleControlFlag=required
> xasecure.audit.jaas.Client.option.useKeyTab=true
> xasecure.audit.jaas.Client.option.storeKey=false
> xasecure.audit.jaas.Client.option.serviceName=solr
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
