best design for an responsibility system

Mohammad K

I am trying to build a main system ( web application ) that contain different systems

that provide service for sales , packing and HR dept etc , so i have many users (about one thousand users ) with different page access permissions ( dynamic responsibility that may change at any time )

what is the best design for the responsibility system that can give them the permission to access for some page that developed for them

thx in advance

i have tried to give each system ,page and user an id ,

the store in DB for each user the system and page ids that can be accessed by this user

3 Replies

Know the answer? Post it — somebody with the same question will find it here.

Roshan Patil6y ago
Let these 3 systems be 3 areas of you MVC application.
Each of these Areas will be having multiple Views (Pages) and Controllers.
As told in earlier reply, Create a mapping table which will have Area (System), Controller and Action/View (Page), and the Roles asscciated with it.
Provide IT supervisore and Admin role who can do mapping of Roles with Area, Controller and Action/View. You can even provide a front end to perform this mapping.
Create a custom authorization filter. In this filter get the Role of the user, the Area, Controller and Action/View name he is requesting. Check if configuration fot this data exists in you mapping table. If not respond with Unauthorized response. If exist no need to do any thing.
User this cutom authorization globall or on the required controllers.
Mohammad K6y ago
to explain my case i will provide an example :
i have 3 systems with one login and dashboard page
each one of this systems have a multi pages
so i want to give user A access to system s1 and s2
and from s1 he can view page p1 and p2 just
and so on,
the IT supervisore is who responsable to give this users this roles dynamicly
and yes it is MVC5 web application
Roshan Patil6y ago
For each System, Page and Role maintain a master in you database.
Create a mapping table which will have System and Page, and the Roles asscciated with it.
When user is accessing the page, check if his Role, Page and System he is accessing have an entry in your Mapping table.

In ASP.net you can create as many menu as much accessible to a particular role. If the page is critical, on every page load (or in your master page) check if the user have previlege to access the page (by checking against the mapping table)

In ASP.net MVC you can use Areas and Authorization filters. Can create different Areas for Sales, Packing, HR etc. For every controller/action you can user Authorization filter to provide accesss to the user with particular Role.
In case of MVC you need to create mapping table for Role, Area, Controller and Action.
In filter code (custom filter) check User Role, Action, Controller and action which he is trying to access and authorize the user accordingly.