ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (AMBARI-16719) Enable authentication using Ambari for LogSearch
Date Wed, 01 Jun 2016 01:23:12 GMT


Hadoop QA commented on AMBARI-16719:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  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 11 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:red}-1 core tests{color}.  The patch failed these unit tests in ambari-logsearch/ambari-logsearch-portal
ambari-server ambari-web:


Test results:
Console output:

This message is automatically generated.

> Enable authentication using Ambari for LogSearch
> ------------------------------------------------
>                 Key: AMBARI-16719
>                 URL:
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-logsearch
>    Affects Versions: 2.4.0
>            Reporter: Don Bosco Durai
>            Assignee: Miklos Gergely
>             Fix For: 2.4.0
>         Attachments: AMBARI-16719.patch
> We need to add the following properties to for enabling authentication
using Ambari.
> logsearch.auth.external_auth.enable=true
> logsearch.auth.external_auth.host_url=http://AMBARI_HOST:8080
> logsearch.auth.external_auth.login_url=/api/v1/users/$USERNAME/privileges?fields=*
> logsearch.roles.allowed=AMBARI.ADMINISTRATOR
> Do not replace $USERNAME. This will be replaced by LogSearch code based on the username
> The corresponding changes to LogSearch are already committed. This can be manually tested
by adding the above properties in logsearch custom properties

This message was sent by Atlassian JIRA

View raw message