[GitHub] [rocketmq-externals] zhangjidi2016 commented on issue #707: The problem of rocketmq-console permission

[GitBox <gi...@apache.org>]

zhangjidi2016 commented on issue #707:
URL: https://github.com/apache/rocketmq-externals/issues/707#issuecomment-893574845


   Currently, there are two types of users on the console, admin and common users. The admin user has the permission to access all interfaces, and the common user has the permission to view resources but cannot operate related resources. To do this, I'm going to implement a simple permission verification feature.
   
   1. When the login user calls all interfaces, the permission of each interface is verified by AOP, by checking whether the role to which the user belongs has the access permission of the interface. All interface urls that a common user role has access permissions are saved in a file. The file is hot updated to facilitate adding or deleting permissions.
   
   2. In the interface, in order to distinguish admin from ordinary users more easily, the buttons for creating, updating and deleting operations are not displayed for ordinary users.
   
   Please help to evaluate whether this scheme is feasible? @francisoliverlee @vongosling 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org