[
https://issues.apache.org/jira/browse/AMBARI-20768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keta Patel updated AMBARI-20768:
--------------------------------
Description:
A local Ambari user with no cluster roles assigned to it can successfully log
into the Logsearch UI.
Logsearch service exercises restriction on who can access its UI using a
property "logsearch.roles.allowed". This property is a comma-separated list of
roles to be allowed access to Logsearch UI. This defect deals with the
following 2 issues:
1. If Logsearch service requires that only certain roles be allowed to access
its UI, then a local Ambari user with no roles must not be allowed to access
the UI.
2. If some user with privilege to edit the config properties, updates
"logsearch.roles.allowed" by removing the "AMBARI.ADMINISTRATOR" role from its
list, then the Ambari Admins will not be able to access the Logsearch UI. This
violates the Ambari Administrator privilege which must be able to access all
frames of Ambari UI as well as perform all UI operations.
DESIRED BEHAVIOR:
=================
1. A local user with no role assigned to it, must not be able to access
Logsearch UI.
2. Ambari Administrators must be always be allowed to access the Logsearch UI.
No user is allowed to revoke this access right of Ambari Administrator for the
Logsearch UI.
was:
Ambari admin and local Ambari user with no cluster roles assigned to it are
able to successfully log into Logsearch UI.
However, when the local user is assigned some cluster role, that user is not
able to log into Logsearch UI.
As a fix to access the Logsearch UI by the cluster roles, the property
"logsearch.roles.allowed" is added under Log Search->configs->Advanced->Custom
logsearch-properties. This value of this property is a comma-separated list of
the cluster roles allowed to log into Logsearch UI. As a result of this, the
local ambari users having the corresponding roles are now able to log into
Logsearch UI, but Ambari admins show unsuccessful login.
On removing the "logsearch.roles.allowed" property, all Ambari admins, local
users with NO roles assigned are able to successfully log into Logsearch UI,
but users with some cluster roles assigned to them are not allowed to login.
The following behavior is what is required:
- Ambari Admins must be able to successfully log into Logsearch UI regardless
of whether the "logsearch.roles.allowed" property has been added or not.
- All local users with NO roles assigned to them must NOT be able to log into
the Logsearch UI. This behavior is seen after adding the
"logsearch.roles.allowed" property, but not before that. Ideally, those users
must not be able to log into Logsearch UI regardless of whether the
"logsearch.roles.allowed" was added or not.
> Local Ambari user with no cluster role must not be able to access Logsearch UI
> ------------------------------------------------------------------------------
>
> Key: AMBARI-20768
> URL: https://issues.apache.org/jira/browse/AMBARI-20768
> Project: Ambari
> Issue Type: Bug
> Components: logsearch
> Affects Versions: trunk, 2.5.0
> Reporter: Keta Patel
> Assignee: Keta Patel
>
> A local Ambari user with no cluster roles assigned to it can successfully log
> into the Logsearch UI.
> Logsearch service exercises restriction on who can access its UI using a
> property "logsearch.roles.allowed". This property is a comma-separated list
> of roles to be allowed access to Logsearch UI. This defect deals with the
> following 2 issues:
> 1. If Logsearch service requires that only certain roles be allowed to access
> its UI, then a local Ambari user with no roles must not be allowed to access
> the UI.
> 2. If some user with privilege to edit the config properties, updates
> "logsearch.roles.allowed" by removing the "AMBARI.ADMINISTRATOR" role from
> its list, then the Ambari Admins will not be able to access the Logsearch UI.
> This violates the Ambari Administrator privilege which must be able to access
> all frames of Ambari UI as well as perform all UI operations.
> DESIRED BEHAVIOR:
> =================
> 1. A local user with no role assigned to it, must not be able to access
> Logsearch UI.
> 2. Ambari Administrators must be always be allowed to access the Logsearch
> UI. No user is allowed to revoke this access right of Ambari Administrator
> for the Logsearch UI.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
