You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Don Bosco Durai (JIRA)" <ji...@apache.org> on 2016/05/23 23:14:12 UTC

[jira] [Commented] (AMBARI-16719) Enable authentication using Ambari for LogSearch

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

Don Bosco Durai commented on AMBARI-16719:
------------------------------------------

[~oleewere], let me know if you need any additional information from my side. Thanks

> 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
>            Reporter: Don Bosco Durai
>            Assignee: Olivér Szabó
>
> 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)