CN114139193A - Button authority control method and related device - Google Patents
Button authority control method and related device Download PDFInfo
- Publication number
- CN114139193A CN114139193A CN202111274625.3A CN202111274625A CN114139193A CN 114139193 A CN114139193 A CN 114139193A CN 202111274625 A CN202111274625 A CN 202111274625A CN 114139193 A CN114139193 A CN 114139193A
- Authority
- CN
- China
- Prior art keywords
- button
- authority
- user
- page
- available
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/629—Protecting access to data via a platform, e.g. using keys or access control rules to features or functions of an application
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/604—Tools and structures for managing or administering access control systems
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Health & Medical Sciences (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Health & Medical Sciences (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Bioethics (AREA)
- Automation & Control Theory (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
本申请公开了一种按钮权限控制方法，包括：配置各类用户角色的业务权限；配置按钮的使用权限；根据登录用户的所述用户角色所对应的所述业务权限与页面中所述按钮的所述使用权限，判断所述页面中的所述按钮是否可用；若所述页面中的所述按钮可用，则将所述页面中的所述按钮设置为可用状态。该方法能够实现对按钮权限进行控制，与菜单级权限控制不冲突，达到更细化的权限控制，且易移植，通用性强。本申请还公开了一种按钮权限控制装置、设备以及计算机可读存储介质，均具有上述技术效果。
The present application discloses a button authority control method, including: configuring business authority of various user roles; configuring button use authority; according to the business authority corresponding to the user role of the logged-in user and the button on the page For the usage authority, determine whether the button in the page is available; if the button in the page is available, set the button in the page to an available state. The method can realize the control of the button authority, does not conflict with the menu-level authority control, achieves more detailed authority control, is easy to transplant, and has strong versatility. The present application also discloses a button authority control device, device and computer-readable storage medium, all of which have the above technical effects.
Description
Technical Field
The application relates to the technical field of graphical user interfaces, in particular to a button authority control method; it also relates to a button right control device, an apparatus and a computer readable storage medium.
Background
Angularjs is a Web application development framework introduced by Google. It provides a series of well-compatible and extensible services including data binding, DOM operation, MVC design pattern, and module loading, among others. Angularjs is not just a class library, but provides a complete framework. The method avoids the complex work of interacting with a plurality of class libraries and needing to be familiar with a plurality of sets of interfaces. Angularljs is a front-end web independent framework, and the control of the authority is generally realized by the web, and is not bound and interacted with the back end.
For the authority control which is mainly aimed at the menu level at the present time, the implementation mode approximately comprises the following steps: 1. the ng-if implicit control function of Angularlarjs is directly used. And ng-if is hidden. This approach can only be used in systems with low traffic. Because the small information is hidden, the business must be written to death, which is equivalent to putting tiny authority control on each page, and the later maintenance is quite difficult. 2. And realizing system authority control based on ui-router. And writing the authority mapping in the route jump table in advance. And when the path jumps, performing data mapping matching and checking whether the URL is opened or not. 3. In the menu configuration data, authority control data is written. When the system is loaded, the system is loaded to the menu module, and items without authority are not displayed in the menu any more. No matter which implementation mode is adopted, the method mainly aims at the authority control of the menu level, and the implementation mode of the button level authority control is lacked. How to control the button-level authority has become a technical problem to be solved urgently by those skilled in the art.
Disclosure of Invention
The application aims to provide a button authority control method, which can realize control on button authority and is not in conflict with menu level authority control. Another object of the present application is to provide a button authority control device, an apparatus and a computer readable storage medium, all having the above technical effects.
In order to solve the technical problem, the present application provides a button authority control method, including:
configuring service authority of various user roles;
configuring the use authority of the button;
judging whether the button in the page is available according to the service authority corresponding to the user role of the login user and the use authority of the button in the page;
and if the button in the page is available, setting the button in the page to be in an available state.
Optionally, the usage right of the configuration button includes:
configuring the button to be available when a user has a preset service right; or configuring the button to be available when the user has a preset service authority and the row in the page is selected; or the button is configured to be available when the user has a preset service authority and meets a preset condition; or the button is configured to be available when the user has a preset service authority, and the row in the page is selected and meets a preset condition.
Optionally, the determining, according to the service right corresponding to the user role of the login user and the usage right of the button in the page, whether the button in the page is available includes:
if the use authority of the button is configured to that the user has a preset service authority, and the button is available, judging whether the login user has the preset service authority;
if the use permission of the button is configured that a user has a preset service permission and the row in the page is selected, the button is available, and whether the login user has the preset service permission and the row in the page is selected is judged;
if the use permission of the button is configured that the user has a preset service permission and meets a preset condition, the button is available, and whether the login user has the preset service permission and meets the preset condition is judged;
if the use permission of the button is configured to be that a user has a preset service permission, the row in the page is selected and meets a preset condition, the button is available, and whether the login user has the preset service permission and the row in the page is selected and meets the preset condition is judged.
Optionally, the determining whether the login user has the preset service right includes:
matching the user role of the login user with the user role with the preset service authority;
and if the matching is successful, the login user has the preset service authority.
Optionally, the setting the button in the page to an available state includes:
illuminating the button in the page.
In order to solve the above technical problem, the present application further provides a button authority control device, including:
the first configuration module is used for configuring the service authority of various user roles;
the second configuration module is used for configuring the use permission of the button;
the judging module is used for judging whether the button in the page is available according to the service authority corresponding to the user role of the login user and the use authority of the button in the page;
and the setting module is used for setting the button in the page to be in an available state if the button in the page is available.
Optionally, the second configuration module is specifically configured to:
configuring the button to be available when a user has a preset service right; or configuring the button to be available when the user has a preset service authority and the row in the page is selected; or the button is configured to be available when the user has a preset service authority and meets a preset condition; or the button is configured to be available when the user has a preset service authority, and the row in the page is selected and meets a preset condition.
Optionally, the determining module includes:
the first judging unit is used for judging whether the login user has the preset service authority or not if the use authority of the button is configured that the user has the preset service authority and the button is available;
the second judgment unit is used for judging whether the login user has the preset service authority and the row in the page is selected if the use authority of the button is configured that the user has the preset service authority and the row in the page is selected and the button is available;
a third judging unit, configured to judge whether the login user has the preset service authority and meets the preset condition if the use authority of the button is configured that the user has the preset service authority and meets the preset condition, and the button is available;
and the fourth judgment unit is used for judging whether the login user has the preset service authority and the row in the page is selected and meets the preset condition if the use authority of the button is configured to that the user has the preset service authority and the row in the page is selected and meets the preset condition if the button is available.
In order to solve the above technical problem, the present application further provides a button authority control device, including:
a memory for storing a computer program;
a processor for implementing the steps of the button authorization control method according to any one of the above when executing the computer program.
In order to solve the above technical problem, the present application further provides a computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the steps of the button authority control method according to any one of the above items.
The button authority control method provided by the application comprises the following steps: configuring service authority of various user roles; configuring the use authority of the button; judging whether the button in the page is available according to the service authority corresponding to the user role of the login user and the use authority of the button in the page; and if the button in the page is available, setting the button in the page to be in an available state.
Therefore, the button authority control method provided by the application configures service authorities for various user roles and configures use authorities for buttons, on the basis, judges whether the buttons in the page are available according to the service authorities corresponding to the user roles of the login users and the use authorities of the buttons in the page, and sets the buttons to be in an available state when the buttons are available, so that the control of the button-level authorities is realized, and the control of the button-level authorities is not in conflict with the control of the menu-level authorities. Meanwhile, the authority control of the button authority control method provided by the application can not be influenced by module coding, and the button authority control method has low coupling. The artificial neural network is easy to transplant and use in various angularjs systems, and has better universality.
The button authority control device, the equipment and the computer readable storage medium provided by the application have the technical effects.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed in the prior art and the embodiments are briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.
Fig. 1 is a schematic flowchart of a button authority control method according to an embodiment of the present disclosure;
fig. 2 is a schematic view of a page provided in the embodiment of the present application;
FIG. 3 is a schematic view of another page provided in the embodiments of the present application;
fig. 4 is a schematic diagram of a button authority control device according to an embodiment of the present application;
fig. 5 is a schematic diagram of a button authority control device according to an embodiment of the present application.
Detailed Description
The key point of the application is to provide a button authority control method, which can realize the control of the button authority and has no conflict with the menu level authority control. Another core of the present application is to provide a button authority control device, an apparatus and a computer readable storage medium, all having the above technical effects.
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Referring to fig. 1, fig. 1 is a schematic flow chart of a button permission control method provided in an embodiment of the present application, and referring to fig. 1, the method is implemented based on angularjs and mainly includes:
s101: configuring service authority of various user roles;
specifically, each login user has a unique user role, for example, super-user (super administrator), admin _ user (common administrator), resource _ user (resource administrator), readonly _ user (read-only administrator), device _ user (device administrator), and the like. And configuring corresponding service authority for each user role to form an authority control table. Wherein, the same user role can have multiple service authorities. User roles with certain service authority, which allow access and operate corresponding pages. For example, the user role super corresponds to the admin _ user and the cluster, and the cluster represents the cluster setting, that is, the user role super and the admin _ user have the access and operation authority of the cluster setting page. The user roles super, admin _ user, resource _ user and readonly _ user correspond to a directory, and the directory represents directory management, that is, the user roles super, admin _ user, resource _ user and readonly _ user have the access and operation authority of a directory management page.
S102: configuring the use authority of the button;
specifically, this step is intended to configure the usage right corresponding to each button in the page.
In a specific embodiment, configuring the usage right of the button includes:
configuring the button to be available when the user has the preset service right; or, configuring the button to be available when the user has the preset service authority and the row in the page is selected; or, configuring the button to be available when the user has the preset service authority and meets the preset condition; or the button is configured to be available when the user has the preset service authority and the row in the page is selected and meets the preset condition.
Specifically, the use authority of the button can be configured in the form of value | action | state. When the user has the preset service right, the button is available; when a user has a preset service authority and a row in a page is selected, a button is available; when the user has a preset service authority and meets a preset condition, the button is available; and when the user has a preset service authority and the row in the page is selected and meets the preset condition, the buttons can be used for four.
Taking the preset service authority as an example of cluster setting, four configurations in the form of value | action | state can be expressed as follows:
cluster | create, cluster | edge, cluster | create | state and cluster | edge | state.
cluster | create represents available with cluster rights; cluster | edit stands for having cluster authority and selecting a row for use; the cluster | create | state represents that it has cluster authority and it is available to satisfy the condition state. cluster | edge | state represents having cluster authority, selecting the row, and satisfying the condition state is available.
Different buttons, suitably arranged in one of the four configurations described above. In addition, the conditions set by the different buttons may be different. For example, the use authority of the start button is configured as cluster | create | state1, and the state1 indicates that the node is not usable in the on state. The traffic limit of state1 is expressed as:
Scope.$broadcast(”state1”,{
value, Cluster setting/whether or not a Cluster setting function is owned
"Disabled" …// row selected or not, and is in an enabled state
})；
At this time, the use authority of the start button is that the user has a cluster authority, and the start button is available when state1 transmits disabled _ false.
For example, the use authority of the close button in the cluster setting page is configured as cluster | create | state2, and state2 indicates that the node is usable in the open state. The traffic limit of State2 is expressed as:
Scope.$broadcast(”state2”,{
value, Cluster setting/whether or not a Cluster setting function is owned
"Disabled" …// row selected or not, and is in an enabled state
})；
At this time, the use authority of the close button is that the user has a cluster authority, and the close button is available when state2 transmits disabled _ future.
S103: judging whether the button in the page is available according to the service authority corresponding to the user role of the login user and the use authority of the button in the page;
on the basis that the use permission of the button comprises the four configuration forms, correspondingly, judging whether the button in the page is available according to the service permission corresponding to the user role of the login user and the use permission of the button in the page comprises the following steps:
if the use authority of the button is configured to that the user has the preset service authority, the button is available, and whether the login user has the preset service authority is judged;
if the login user has the preset service authority, a button in the page is available. If the login user does not have the preset service authority, the button in the page is unavailable.
If the use permission of the button is configured that the user has the preset service permission and the row in the page is selected, the button is available, and whether the login user has the preset service permission and the row in the page is selected is judged;
if the login user has the preset service authority and a certain line in the page is selected, the button in the page is available; if the login user does not have the preset service authority or no line in the page is selected, namely, any one of the preset service authority of the login user and the selected line in the page is not satisfied, the button in the page is unavailable.
If the use permission of the button is configured that the user has the preset service permission and meets the preset condition, the button is available, and whether the login user has the preset service permission and meets the preset condition is judged;
if the login user has the preset service authority and meets the preset conditions, the button in the page is available; if the login user does not have the preset service authority or does not meet the preset condition, namely, any one of the two factors of the login user having the preset service authority and meeting the preset condition is not met, the button in the page is unavailable.
If the use permission of the button is configured that the user has the preset service permission, the row in the page is selected and meets the preset condition, the button is available, and whether the login user has the preset service permission or not is judged, and the row in the page is selected and meets the preset condition.
If the login user has a preset service authority and a certain line in the page is selected and meets a preset condition, the button in the page is available; if the login user does not have the preset service authority, or no row in the page is selected, or the preset condition is not met, namely the login user has the preset service authority, the row in the page is selected, and any one of the three factors meeting the preset condition is not met, the button in the page is unavailable.
Further, in a specific implementation manner, the determining whether the login user has the preset service right includes:
matching the user role of the login user with the user role with the preset service authority; and if the matching is successful, the login user has a preset service authority.
Specifically, an include method can be used to determine whether the login user needs to have a preset service authority. If yes, the representation is successfully matched, and the current login user has the preset service authority. Wherein, a is a user role with factors and service authority, and role is a user role of the current login user. On the contrary, if _. include (a, role) is false, the token matching is not successful, and the current login user does not have the preset service authority.
S104: if the button in the page is available, setting the button in the page to be in an available state;
s105: and if the button in the page is unavailable, setting the button in the page to be in an unavailable state.
Specifically, when it is determined that a button in the page is available, the available button is set to the available state. In contrast, when it is judged that the button in the page is not available, it is set to the unavailable state.
In a specific embodiment, the setting of the button in the page to the available state includes:
the button in the page is illuminated.
Specifically, when a button in the page is not available, the button may be grayed out, and when html is judged to be available, the button is brightened.
It will be appreciated that in addition to the above embodiments, other ways of characterizing the availability or unavailability of a button may be used, and the present application is not limited thereto.
Referring to fig. 2, an embodiment provided by the present application is described below by taking a button above a node list page as an example:
and entering a node list, wherein buttons above pages of the node list are all gray. And finishing default loading of the configuration data of the use authority of each button above the node list page.
After a certain line in the node list page is selected, the watch method of the system detects that the line in the node list page is selected, and assigns values to preset conditions in the use permission of a button above the node list page. state1 represents node on status unavailable; state2 represents a node that is available in the on state. And further broadcasts state1 and state 2.
Once broadcast, the logic associated with the control button state is captured (via the on function) and the execution of the toggle disabled dBased OnState is initiated to draw the page (with the button grayed out or lit).
And the tokleDisabledBasedOnState internally calls the hasPermission method to match the user roles. And the set use authority cluster | edge | state1 of the start button is fetched for use.
Through role matching, the result of matching to HasParmission is true, which represents that the current login user has the use right of the start button above the node list page.
Then, the user returns to toggle disabledBasedOnState, after HasParission is judged to pass, the value of state1 is removed, and if state1 is false (button authority is judged to pass), the button is represented to be available. At the moment, the button can be lightened to become available through double-layer judgment.
As can be seen from fig. 3, after selecting one of the rows, the node is on according to the state shown in the third column, so the start button is grey (state1 is active) and the shutdown and restart buttons are bright (state2 is active).
In summary, the button permission control method provided by the present application configures service permissions for various user roles and configures use permissions for buttons, and on this basis, based on the service permissions corresponding to the user roles of the login user and the use permissions of the buttons in the page, determines whether the buttons in the page are available, and sets the buttons to be in an available state when the buttons are available, thereby implementing control of button-level permissions without conflict with menu-level permission control. Meanwhile, the authority control of the button authority control method provided by the application can not be influenced by module coding, and the button authority control method has low coupling. The method is easy to transplant and use in various angularjs systems, and has better universality.
The application also provides a button authority control device, and the device described below can be mutually and correspondingly referred to with the method described above. Referring to fig. 4, fig. 4 is a schematic diagram of a button authority control device according to an embodiment of the present application, and referring to fig. 4, the device includes:
the first configuration module 10 is used for configuring service permissions of various user roles;
a second configuration module 20 for configuring the usage right of the button;
the judging module 30 is configured to judge whether the button in the page is available according to the service permission corresponding to the user role of the login user and the usage permission of the button in the page;
a setting module 40, configured to set the button in the page to an available state if the button in the page is available.
On the basis of the foregoing embodiment, as a specific implementation manner, the second configuration module 20 is specifically configured to:
configuring the button to be available when a user has a preset service right; or configuring the button to be available when the user has a preset service authority and the row in the page is selected; or the button is configured to be available when the user has a preset service authority and meets a preset condition; or the button is configured to be available when the user has a preset service authority, and the row in the page is selected and meets a preset condition.
On the basis of the foregoing embodiment, as a specific implementation manner, the determining module 30 includes:
the first judging unit is used for judging whether the login user has the preset service authority or not if the use authority of the button is configured that the user has the preset service authority and the button is available;
the second judgment unit is used for judging whether the login user has the preset service authority and the row in the page is selected if the use authority of the button is configured that the user has the preset service authority and the row in the page is selected and the button is available;
a third judging unit, configured to judge whether the login user has the preset service authority and meets the preset condition if the use authority of the button is configured that the user has the preset service authority and meets the preset condition, and the button is available;
and the fourth judgment unit is used for judging whether the login user has the preset service authority and the row in the page is selected and meets the preset condition if the use authority of the button is configured to that the user has the preset service authority and the row in the page is selected and meets the preset condition if the button is available.
On the basis of the above embodiment, as a specific implementation manner, each judgment unit includes:
the matching subunit is used for matching the user role of the login user with the user role with the preset service authority; and if the matching is successful, the login user has the preset service authority.
On the basis of the foregoing embodiment, as a specific implementation manner, the setting module 40 is specifically configured to:
illuminating the button in the page.
The button authority control device provided by the application configures service authorities for various user roles and configures use authorities for buttons, on the basis, judges whether the buttons in the pages are available according to the service authorities corresponding to the user roles of login users and the use authorities of the buttons in the pages, and sets the buttons to be in an available state when the buttons are available, so that control of button-level authorities is realized, and the control of the button-level authorities is not in conflict with control of menu-level authorities. Meanwhile, the authority control of the button authority control method provided by the application can not be influenced by module coding, and the button authority control method has low coupling. The method is easy to transplant and use in various angularjs systems, and has better universality.
The present application also provides a button authority control device, as shown with reference to fig. 5, which includes a memory 1 and a processor 2.
A memory 1 for storing a computer program;
a processor 2 for executing a computer program to implement the steps of:
configuring service authority of various user roles; configuring the use authority of the button; judging whether the button in the page is available according to the service authority corresponding to the user role of the login user and the use authority of the button in the page; and if the button in the page is available, setting the button in the page to be in an available state.
For the introduction of the device provided in the present application, please refer to the above method embodiment, which is not described herein again.
The present application further provides a computer readable storage medium having a computer program stored thereon, which when executed by a processor, performs the steps of:
configuring service authority of various user roles; configuring the use authority of the button; judging whether the button in the page is available according to the service authority corresponding to the user role of the login user and the use authority of the button in the page; and if the button in the page is available, setting the button in the page to be in an available state.
The computer-readable storage medium may include: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
For the introduction of the computer-readable storage medium provided in the present application, please refer to the above method embodiments, which are not described herein again.
The embodiments are described in a progressive manner in the specification, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. The device, the apparatus and the computer-readable storage medium disclosed by the embodiments correspond to the method disclosed by the embodiments, so that the description is simple, and the relevant points can be referred to the description of the method.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
The technical solutions provided by the present application are described in detail above. The principles and embodiments of the present application are explained herein using specific examples, which are provided only to help understand the method and the core idea of the present application. It should be noted that, for those skilled in the art, it is possible to make several improvements and modifications to the present application without departing from the principle of the present application, and such improvements and modifications also fall within the scope of the claims of the present application.
Claims (10)
1. A button authority control method, comprising:
configuring service authority of various user roles;
configuring the use authority of the button;
judging whether the button in the page is available according to the service authority corresponding to the user role of the login user and the use authority of the button in the page;
and if the button in the page is available, setting the button in the page to be in an available state.
2. The button authority control method according to claim 1, wherein the configuring of the use authority of the button includes:
configuring the button to be available when a user has a preset service right; or configuring the button to be available when the user has a preset service authority and the row in the page is selected; or the button is configured to be available when the user has a preset service authority and meets a preset condition; or the button is configured to be available when the user has a preset service authority, and the row in the page is selected and meets a preset condition.
3. The method of claim 2, wherein the determining whether the button in the page is available according to the service permission corresponding to the user role of the login user and the usage permission of the button in the page comprises:
if the use authority of the button is configured to that the user has a preset service authority, and the button is available, judging whether the login user has the preset service authority;
if the use permission of the button is configured that a user has a preset service permission and the row in the page is selected, the button is available, and whether the login user has the preset service permission and the row in the page is selected is judged;
if the use permission of the button is configured that the user has a preset service permission and meets a preset condition, the button is available, and whether the login user has the preset service permission and meets the preset condition is judged;
if the use permission of the button is configured to be that a user has a preset service permission, the row in the page is selected and meets a preset condition, the button is available, and whether the login user has the preset service permission and the row in the page is selected and meets the preset condition is judged.
4. The button authority control method according to claim 3, wherein determining whether the login user has the preset service authority comprises:
matching the user role of the login user with the user role with the preset service authority;
and if the matching is successful, the login user has the preset service authority.
5. The button authority control method according to claim 1, wherein the setting the button in the page to an available state includes:
illuminating the button in the page.
6. A button authority control apparatus, comprising:
the first configuration module is used for configuring the service authority of various user roles;
the second configuration module is used for configuring the use permission of the button;
the judging module is used for judging whether the button in the page is available according to the service authority corresponding to the user role of the login user and the use authority of the button in the page;
and the setting module is used for setting the button in the page to be in an available state if the button in the page is available.
7. The button permission control device according to claim 6, wherein the second configuration module is specifically configured to:
configuring the button to be available when a user has a preset service right; or configuring the button to be available when the user has a preset service authority and the row in the page is selected; or the button is configured to be available when the user has a preset service authority and meets a preset condition; or the button is configured to be available when the user has a preset service authority, and the row in the page is selected and meets a preset condition.
8. The button authority control device according to claim 7, wherein the judging module includes:
the first judging unit is used for judging whether the login user has the preset service authority or not if the use authority of the button is configured that the user has the preset service authority and the button is available;
the second judgment unit is used for judging whether the login user has the preset service authority and the row in the page is selected if the use authority of the button is configured that the user has the preset service authority and the row in the page is selected and the button is available;
a third judging unit, configured to judge whether the login user has the preset service authority and meets the preset condition if the use authority of the button is configured that the user has the preset service authority and meets the preset condition, and the button is available;
and the fourth judgment unit is used for judging whether the login user has the preset service authority and the row in the page is selected and meets the preset condition if the use authority of the button is configured to that the user has the preset service authority and the row in the page is selected and meets the preset condition if the button is available.
9. A button authority control apparatus, comprising:
a memory for storing a computer program;
processor for implementing the steps of the button entitlement control method according to any of claims 1 to 5 when executing said computer program.
10. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, carries out the steps of the button authorization control method according to any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111274625.3A CN114139193A (en) | 2021-10-29 | 2021-10-29 | Button authority control method and related device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111274625.3A CN114139193A (en) | 2021-10-29 | 2021-10-29 | Button authority control method and related device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114139193A true CN114139193A (en) | 2022-03-04 |
Family
ID=80395044
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111274625.3A Pending CN114139193A (en) | 2021-10-29 | 2021-10-29 | Button authority control method and related device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114139193A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116628654A (en) * | 2023-07-26 | 2023-08-22 | 之江实验室 | Front-end page authority control method, device, equipment and storage medium |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080201766A1 (en) * | 2007-02-16 | 2008-08-21 | Microsoft Corporation | Efficient data structures for multi-dimensional security |
| CN101441688A (en) * | 2007-11-20 | 2009-05-27 | 阿里巴巴集团控股有限公司 | User authority allocation method and user authority control method |
| CN102930226A (en) * | 2012-10-25 | 2013-02-13 | 无锡中科泛在信息技术研发中心有限公司 | Method for controlling use permission of fine-grained client |
| CN109214207A (en) * | 2018-08-22 | 2019-01-15 | 郑州云海信息技术有限公司 | The management method and device of permission in the network of multi-user access |
| CN110162960A (en) * | 2019-05-22 | 2019-08-23 | 陕西中达公路技术服务有限公司 | A kind of method for verifying authority based on user management |
| CN110968825A (en) * | 2019-11-30 | 2020-04-07 | 信联科技(南京)有限公司 | WEB page fine-grained authority control method |
| CN111814179A (en) * | 2020-06-29 | 2020-10-23 | 中国平安人寿保险股份有限公司 | User authority management and data control method and related equipment thereof |
| CN113297550A (en) * | 2021-06-17 | 2021-08-24 | 中国农业银行股份有限公司 | Authority control method, device, equipment, storage medium and program product |
-
2021
- 2021-10-29 CN CN202111274625.3A patent/CN114139193A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080201766A1 (en) * | 2007-02-16 | 2008-08-21 | Microsoft Corporation | Efficient data structures for multi-dimensional security |
| CN101441688A (en) * | 2007-11-20 | 2009-05-27 | 阿里巴巴集团控股有限公司 | User authority allocation method and user authority control method |
| CN102930226A (en) * | 2012-10-25 | 2013-02-13 | 无锡中科泛在信息技术研发中心有限公司 | Method for controlling use permission of fine-grained client |
| CN109214207A (en) * | 2018-08-22 | 2019-01-15 | 郑州云海信息技术有限公司 | The management method and device of permission in the network of multi-user access |
| CN110162960A (en) * | 2019-05-22 | 2019-08-23 | 陕西中达公路技术服务有限公司 | A kind of method for verifying authority based on user management |
| CN110968825A (en) * | 2019-11-30 | 2020-04-07 | 信联科技(南京)有限公司 | WEB page fine-grained authority control method |
| CN111814179A (en) * | 2020-06-29 | 2020-10-23 | 中国平安人寿保险股份有限公司 | User authority management and data control method and related equipment thereof |
| CN113297550A (en) * | 2021-06-17 | 2021-08-24 | 中国农业银行股份有限公司 | Authority control method, device, equipment, storage medium and program product |
Non-Patent Citations (1)
| Title |
|---|
| 颜平超;牛熠;吴燕玲;: "基于RBAC的权限管理的设计与实现", 硅谷, no. 07, 8 April 2010 (2010-04-08) * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116628654A (en) * | 2023-07-26 | 2023-08-22 | 之江实验室 | Front-end page authority control method, device, equipment and storage medium |
| CN116628654B (en) * | 2023-07-26 | 2023-11-07 | 之江实验室 | Front-end page authority control method, device, equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10387132B2 (en) | Cloud-based application resource files | |
| KR101652191B1 (en) | Locally backed cloud-based storage | |
| CN102770854B (en) | Automatic synchronization Conflict solving | |
| CN100375016C (en) | Method for managing file replication in applications | |
| US20130311598A1 (en) | Cloud-based data item sharing and collaboration among groups of users | |
| US8719949B1 (en) | Parameter based operation | |
| US20060259964A1 (en) | Applying local machine restrictions on a per-user basis | |
| CN110944067B (en) | A load balancing method and server | |
| CN111880901B (en) | Network configuration method, device, equipment and readable storage medium | |
| EP1759289A2 (en) | Semantic task computing | |
| US20170168807A1 (en) | Method and electronic device for updating application program | |
| JP2010044642A (en) | Content distribution server and content distribution method | |
| CN104391716A (en) | Plug-in-based application program implementing method and device | |
| CN105117295A (en) | Memory resource release method and device and electronic equipment | |
| WO2008121533A1 (en) | Configuration management of an electronic device | |
| CN109618315A (en) | A kind of control method of lighting apparatus, device, storage medium and intelligent terminal | |
| US8707294B2 (en) | Model for system-wide application extension | |
| CN114139193A (en) | Button authority control method and related device | |
| US20120272242A1 (en) | Provisioning virtual server | |
| CN101506772A (en) | Environmental state changes to alter functionality | |
| CN109324731A (en) | Information display method and device | |
| JP4930078B2 (en) | Information processing method, information processing apparatus, information processing program, and recording medium recording the program | |
| CA2979691C (en) | Content deployment, scaling, and telemetry | |
| US8117053B2 (en) | Claims based factory pattern for creating objects | |
| US20160277508A1 (en) | Content Deployment, Scaling, and Telemetry |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |