[ 
https://issues.apache.org/jira/browse/AMBARI-18818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15663754#comment-15663754
 ] 

Hadoop QA commented on AMBARI-18818:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12838710/AMBARI-18818.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 1 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.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9249//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9249//console

This message is automatically generated.

> Config changes for Atlas to Support KnoxSSO Authentication
> ----------------------------------------------------------
>
>                 Key: AMBARI-18818
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18818
>             Project: Ambari
>          Issue Type: New Feature
>          Components: ambari-server
>    Affects Versions: 2.5.0
>            Reporter: Mugdha Varadkar
>            Assignee: Mugdha Varadkar
>            Priority: Blocker
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-18818.patch
>
>
> Following properties are need to be added in atlas-application.properties 
> from Ambari  Configs to enable Knox SSO in Atlas
> {noformat}
> atlas.sso.knox.enabled
> atlas.sso.knox.providerurl
> atlas.sso.knox.publicKey
> atlas.sso.knox.browser.useragent
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to