ASP.NET system user permission design and implementation

For example, to declare the syntax of the controls imported above: This control is part of the page and will be presented when the page is processed. Also, the public property, events, and methods of the control will open to the web form page and can be used by programming. According to this principle, the operation (such as login verification, role verification) to be executed (such as login verification, role verification) can be encapsulated during each page. RBAC's basic idea of ​​RBAC (role access control) can be expressed simply by Figure 1, ie, divide the entire access control process into two steps: access rights associated with the role, the role is associated with the user, thus achieving the user The logic separation of access rights. Since the RBAC implements logical separation of users and access rights, it greatly facilitates rights management. For example, if a user's position changes, just remove the user's current role, join the role representing new positions or new tasks, the changes between roles / permissions are relatively slow than the changes between roles / user relationships. Many, and delegated users to the role without many technologies, they can be implemented by administrative personnel, and the configuration rights to the role is more complicated. It takes certain technologies to be borne by specialized technicians, but do not give them users. Permissions, this is just consistent with the situation in reality. User Permissions In .NET, Design and Implementation of Utilization. The basic idea of ​​implementing permission control in the .NET is: assign a role to the user according to the basic principle of role access control (RBAC), each role corresponds to some permissions, then Use the user control (UserControl) in ASP.NET to determine whether the role of the user has access to the access page. The specific implementation process will be set forth from three aspects of the database design, add role, and user controls. 1. Design of the database in the database First, design three tables such as function module tables, menu and role tables in the database. (1) Function Module Table In order to manage the permissions of the user, first organize the module of the system, and design a function module table for this purpose. See Table 1. (2) Functional Table Each functional module is called function, such as the product management module Goods (the category of functional modules) contains product information queries, product information update, product information deletion, product pricing information query, commodity pricing The information update is five functions, and the design of the menu is shown in Table 2. The example mentioned above can be inserted into a function module table and a function table as such a record separately.

Insert Into TModule Values ​​(0, 'Product Management Module', 'Goods', 5); Insert Into TFunction Values ​​(0,' Product Information Query ',' Selectgoods', 0); Insert Into TFunction VALUES (1, 'Product Information Update ',' updategoods ', 0); Insert Into TFunction VALUES (2,' Product Information Delete ", 'deletegoods', 0); Insert Into TFunction Values ​​(3, 'Product Pricing Information Query', 'SelectGoodsprice', 0) Insert INTO TFUNCTION VALUES (4, 'Product Pricing Information Update', 'UpdateGoodSprice', 0); (3) The design key of the role table role table is the definition of the role value, which is a similar binary number consisting of 0 and 1 String. The FUNCNO field in the function table represents the position in the Role Value field in the role table, if the value corresponding to the location is 0, indicating that the role is no such authority, if the value is 1, then Indicates that the role has this authority. Such as the role of the role is 100100 ... 00 (a total of 100), as shown above, the function number of the product information query is 0, the 0th bit of the role value of 100100 ... 00 is 1, so the ordinary member role has product information The function of the query;, in contrast, the first bit of the role value is 0, and the function of the function number is 1 is updated for the product information, so the ordinary member role does not have the permissions of the product information update. Their relationship can be represented by Figure 2. 2, the role is added with several tables, the function module of the role page, and its corresponding functions can be read from the function module table and the function table, as shown in Figure 3. When you insert a new role normal member into the database, you first set all the bits of the role value to 0, then use the Replace function in the .NET Framework class library to change the value of the function of the hook in the role value accordingly. To 1. For example, the newly added role name is the role of ordinary members, and its features are available for product information query (function number 0) and commodity pricing information query (function number 3), the role value should be 1001000 ... 00 (100 Bit), that is, the value of the 0th and third bits in the role value is 1, the rest is 0.3, and the user control is used to implement access rights in defining the user control .ascx file (head.ascx) and .ascx.cs ( Head.ascx, CS) file, next to the registration and declaration of it in the .aspx file. (1) Registration (2) Declaration After the Practice, declaration in .aspx files. SASCX files can be divided into several cases: the first case: second case: third case: field FLAG is used to control how to control Sign for permission check, FuncName refers to the function in the function table.