You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Aleksandr Kovalenko (JIRA)" <ji...@apache.org> on 2016/06/23 11:37:16 UTC
[jira] [Commented] (AMBARI-17401) Service actions are available via
firepath even if not visible on UI (RBAC)
[ https://issues.apache.org/jira/browse/AMBARI-17401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15346295#comment-15346295 ]
Aleksandr Kovalenko commented on AMBARI-17401:
----------------------------------------------
+1 for the patch
> Service actions are available via firepath even if not visible on UI (RBAC)
> ---------------------------------------------------------------------------
>
> Key: AMBARI-17401
> URL: https://issues.apache.org/jira/browse/AMBARI-17401
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.4.0
> Reporter: Antonenko Alexander
> Assignee: Antonenko Alexander
> Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17401.patch
>
>
> Login as a service operator. (He is not allowed to move components)
> Move to services tab, move to MapReduce service. Now with firepath search for xpath : //a[text()='Move History Server']. Even though it is not visible, it is accessible via UI elements. Anyone with this knowledge can run a script to do move components to different hosts (My selenium test successfully ran for service operator.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)