Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.2.0
-
None
Description
Currently, "USE" permission for users + groups needs to manually mapped by an Ambari Admin for each view instance.
In cases where a view can be auto-configured for a locally managed cluster and we expect that view to be available to that same users that have Cluster Operator or other role access to that cluster, we need to provide an option for Ambari Admins to inherit USE permission on view instances from the cluster permissions. This means:
- Any user or group with different role on the cluster will also get USE access on the view instance.
- This should be available in-addition-to specific view USE permission mapping
- This should be available from Ambari Administration interface and optional set during <auto-create>
- Views like Capacity Scheduler and Tez UI should be adjusted to use this feature for their auto-create instances
Attachments
Attachments
Issue Links
- blocks
-
AMBARI-16246 Allow roles to be treated like principals in Ambari DB
- Resolved
-
AMBARI-16247 Authorizations given to role-based principals must be dereferenced upon user login
- Resolved
- links to
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12801412/AMBARI-16177.trunk.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 15 new or modified test files.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
+1 core tests. The patch passed unit tests in ambari-admin ambari-server.
Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/6723//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/6723//console
This message is automatically generated.