Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Won't Fix
-
2.5.0
-
None
Description
Steps to reproduce:
1.Login ambari with ambari administrator role and create a user named Test on host A.
2.Assign service administrator role(or any other one of five roles) to this user Test.
3.On host B, login ambari with user Test .Now it plays as a service administrato role.
4.On host A, unassign the role of user Test , or change the role to another one, or even delete this user.
5.On host B, we will find the user Test can continue to operate ambari with previous permissions as a service administrator which actually have already changed by step 4.
Except for on two different hosts, we also can reproduce this problem between two different browsers on local host.
One solution:
Periodly schedule a task to update current user's authorization. If receive an unauthorized acess exception or even user is deleted, we should log off current user.
Attachments
Attachments
Issue Links
- links to
