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

Hudson commented on AMBARI-19363:
---------------------------------

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #644 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/644/])
AMBARI-19363. Log Search: external authentication roles are hard coded 
(oleewere: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=dd9904d7ed0cc04ee94bdd685aeea16a387a15ab])
* (edit) ambari-server/src/test/python/stacks/2.4/LOGSEARCH/test_logsearch.py
* (edit) ambari-server/src/test/python/stacks/2.4/configs/default.json
* (edit) 
ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logsearch-properties.xml
* (edit) 
ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/package/scripts/params.py
* (edit) ambari-web/app/data/HDP2/site_properties.js


> 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)

Reply via email to