[
https://issues.apache.org/jira/browse/AMBARI-19363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó resolved AMBARI-19363.
-----------------------------------
Resolution: Fixed
committed to trunk:
{code:java}
commit 6b198cc71ffd5b1ee5332ee036eb1272ee767c8b
Author: oleewere <oleew...@gmail.com>
Date: Wed Jan 4 20:24:29 2017 +0100
AMBARI-19363. Log Search: external authentication roles are hard coded
(oleewere)
Change-Id: Ic3d67d22f4a82e09ed940160e1fa1099937ca049
{code}
committed to branch-2.5:
{code:java}
commit dd9904d7ed0cc04ee94bdd685aeea16a387a15ab
Author: oleewere <oleew...@gmail.com>
Date: Wed Jan 4 20:21:50 2017 +0100
AMBARI-19363. Log Search: external authentication roles are hard coded
(oleewere)
Change-Id: I52e4672de69935b9461bfe4c2fa0a01299e6abd5
{code}
> Log Search: external authentication roles are hard coded
> --------------------------------------------------------
>
> Key: AMBARI-19363
> URL: https://issues.apache.org/jira/browse/AMBARI-19363
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Olivér Szabó
> Assignee: Olivér Szabó
> Fix For: 2.5.0
>
> Attachments: AMBARI-19363.patch, AMBARI-19363_branch-2.5.patch
>
>
> By default AMBARI.ADMINISTRATOR (logsearch.roles.allowed) role is used for
> LogSearch users (with external ambari server authentication)
> these roles should be editable on ambari UI (not only with adding as custom
> property)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
