[
https://issues.apache.org/jira/browse/AMBARI-16719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15312520#comment-15312520
]
Hudson commented on AMBARI-16719:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #4990 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4990/])
AMBARI-16719. Remove reverted (see: AMBARI-16272) upgrade changes from
(oleewere:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6f3b17313f47c966096fe29489d4a45efd7c816b])
*
ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logsearch-properties.xml
> Enable authentication using Ambari for LogSearch
> ------------------------------------------------
>
> Key: AMBARI-16719
> URL: https://issues.apache.org/jira/browse/AMBARI-16719
> 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, AMBARI-16719_appendum.patch
>
>
> We need to add the following properties to logsearch.properties 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
(v6.3.4#6332)
