[
https://issues.apache.org/jira/browse/AMBARI-15370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15191378#comment-15191378
]
Hudson commented on AMBARI-15370:
---------------------------------
ABORTED: Integrated in Ambari-trunk-Commit #4483 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4483/])
AMBARI-15370. Login as regular user (no cluster access at all) but (hiveww:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=68034ae84354f82eac8c875c319e0c8d5cd699ac])
* ambari-web/app/controllers/global/update_controller.js
> Login as regular user (no cluster access at all) but background ops are
> running about cluster
> ---------------------------------------------------------------------------------------------
>
> Key: AMBARI-15370
> URL: https://issues.apache.org/jira/browse/AMBARI-15370
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.2.0
> Reporter: Antonenko Alexander
> Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-15370.patch, user-running-ui (4).tiff
>
>
> I created a local user and did not give them access to any cluster.
> Logged in and notice that Ambari Web is making calls to backend about cluster
> items (hosts, alerts, etc).
> The calls come back 403 since this user doesn't have access to cluster
> resources but these calls are not necessary overhead, and in case of real
> problems, errors like this will confuse real errors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
