CN114115881A - Authority control method, system, equipment and storage medium for front-end and back-end separation items - Google Patents
Authority control method, system, equipment and storage medium for front-end and back-end separation items Download PDFInfo
- Publication number
- CN114115881A CN114115881A CN202111470873.5A CN202111470873A CN114115881A CN 114115881 A CN114115881 A CN 114115881A CN 202111470873 A CN202111470873 A CN 202111470873A CN 114115881 A CN114115881 A CN 114115881A
- Authority
- CN
- China
- Prior art keywords
- resource
- interface
- user
- authority
- association model
- 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.)
- Withdrawn
Links
- 238000000034 method Methods 0.000 title claims abstract description 36
- 238000000926 separation method Methods 0.000 title claims abstract description 7
- 238000012795 verification Methods 0.000 claims description 26
- 230000006870 function Effects 0.000 claims description 14
- 238000013461 design Methods 0.000 claims description 8
- 238000004891 communication Methods 0.000 claims description 5
- 238000004590 computer program Methods 0.000 claims description 5
- 238000012545 processing Methods 0.000 abstract description 3
- 238000010586 diagram Methods 0.000 description 10
- 238000007726 management method Methods 0.000 description 5
- 238000013499 data model Methods 0.000 description 3
- 238000011161 development Methods 0.000 description 3
- 230000018109 developmental process Effects 0.000 description 3
- 230000003993 interaction Effects 0.000 description 3
- 238000013507 mapping Methods 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 238000013475 authorization Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000012938 design process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000033772 system development Effects 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/38—Creation or generation of source code for implementing user interfaces
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Human Computer Interaction (AREA)
- Storage Device Security (AREA)
Abstract
The invention relates to the technical field of data processing, in particular to a method, a system, equipment and a storage medium for controlling the authority of a front-end and back-end separation project. A permission control method for separating items at the front end and the rear end comprises the following steps: determining resources needing to be subjected to authority control; defining a resource ID of a unique identifier for the resource; acquiring an interface to be called of each resource ID, and establishing a first association model between the resource ID and the interface; constructing a second association model of the user ID and the resource ID of the user owning the authority; obtaining a user authorized resource ID set based on the second association model, and judging whether the resource ID is in the user authorized resource ID set; and obtaining an interface set which is called by the user with the authority based on the ID set of the user with the authority and the first association model, and verifying whether the interface requested currently is in the interface set. The method provided by the invention can simultaneously carry out authority control at the front end and the back end, thereby not only optimizing the experience of the front end user, but also ensuring the safety of the data interface.
Description
Technical Field
The invention relates to the technical field of data processing, in particular to a method, a system, equipment and a storage medium for controlling the authority of a front-end and back-end separation project.
Background
In recent years, software system development has started a front-end and back-end separated architecture mode and development mode, the front end is dedicated to page and data display, the back end is dedicated to business logic, and the front end and the back end perform data interaction through interfaces. The first one is that whether a user has the authority to use a certain menu is determined by configuring a 'user-role-menu', the menu is displayed if the user has the authority under the control of a front end, otherwise, the menu is not displayed. The second is to determine whether a user has the right to access an interface by configuring a 'user-role-interface', when a front end initiates a request, a back end detects that the user has the right to access the interface, and then response data is sent; otherwise, no permission is prompted, the scheme is not friendly to user interaction, a user can see all menus and function entries on a page, no permission is prompted when the user operates (such as clicks), when a large number of displayed function icons exist, the user is easily interfered to find the correct function icon, the frequency of mistaken clicks is increased, and time is wasted.
Disclosure of Invention
In order to overcome the above problems or partially solve the above problems, an object of the present invention is to provide a method and a system for controlling the authority of a front-end and back-end separated project, so as to solve the unsafe problem of independently relying on the front-end for authority control and the problem of independently relying on the back-end interface for authority control, which is not user-friendly.
The invention is realized by the following technical scheme:
in a first aspect, an embodiment of the present invention provides a method for controlling authority of a front-end and back-end separated item, including the following steps:
s101, determining resources needing to be subjected to authority control and display forms of the resources on a front-end page when the resources have authority or do not have the authority; s102, defining a resource ID of a unique identifier for the resource; s103, acquiring an interface to be called of each resource ID, and establishing a first association model between the resource ID and the interface; s104, constructing a second association model of the user ID and the resource ID of the user owning authority; s105, acquiring a user ID, acquiring a user authorized resource ID set based on the second association model, judging whether the resource ID is in the user authorized resource ID set, and determining the display form of the corresponding resource on a front-end page according to the judgment result; s106, after receiving the interface request, the back end obtains an interface set which is called by the user and has the authority based on the user authorized resource ID set and the first association model, verifies whether the interface requested currently is in the interface set, and executes corresponding interface logic after the verification is passed.
Based on the first aspect, in some embodiments of the present invention, the resources include menus, function modules, and operation items.
Based on the first aspect, in some embodiments of the present invention, the determining whether the resource ID is in the user-authorized resource ID set includes: if the judgment result is yes, the corresponding resource is displayed on the front-end page in the first form, and if the judgment result is no, the corresponding resource is displayed on the front-end page in the second form.
In some embodiments of the present invention based on the first aspect, the first mode is display, and the second mode is hidden.
Based on the first aspect, in some embodiments of the present invention, the verifying whether the currently requested interface is in the interface set is performed, and if the verification fails, a prompt indicating that there is no interface call right is returned.
In a second aspect, an embodiment of the present invention provides an authority control system for separating items at front and back ends, including: a page function design module: the method comprises the steps of determining resources needing to be subjected to authority control and display forms of the resources on a front-end page when the resources have authority and do not have authority; the resource ID definition module: a resource ID for defining a unique identifier for the resource; the first association model building module: the interface calling method comprises the steps of obtaining an interface to be called of each resource ID, and establishing a first association model between the resource ID and the interface; the second association model establishing module: constructing a second association model of the user ID and the resource ID of the user owning the authority; a front-end display module: the system comprises a first correlation model, a second correlation model and a front-end page, wherein the first correlation model is used for acquiring a user ID, acquiring a user authorized resource ID set based on the second correlation model, judging whether the resource ID is in the user authorized resource ID set or not, and determining the display form of a corresponding resource on the front-end page according to the judgment result; a back-end verification module: after receiving an interface request, the back end obtains an interface set which is called by the user and has the authority based on the user authorized resource ID set and the first association model, verifies whether the interface requested currently is in the interface set, and executes corresponding interface logic after the verification is passed.
Based on the second aspect, in some embodiments of the invention, the front end display module includes: the first acquisition unit is used for acquiring a user ID and acquiring a user authorized resource ID set based on the second association model; a judging unit, configured to judge whether the resource ID is in the user authorized resource ID set; the first display unit is used for displaying the corresponding resources on the front-end page in a first form; and the second display unit is used for displaying the corresponding resources on the front-end page in a second form.
Based on the second aspect, in some embodiments of the invention, the backend verification module includes: a second obtaining unit, configured to obtain, by a back end, an interface set that a user has an authority to call based on the user authorized resource ID set and the first association model after receiving an interface request; a verification unit, configured to verify whether a currently requested interface is in the interface set; the execution unit is used for executing corresponding interface logic after the verification is passed; and the prompting unit is used for returning a prompt of the interface-free calling authority when the verification fails.
In a third aspect, an embodiment of the present invention provides an electronic device, including: at least one processor, at least one memory, and a data bus; wherein, the processor and the memory complete mutual communication through the data bus; the memory stores program instructions executable by the processor, which invokes the program instructions to perform the one or more programs or methods.
In a fourth aspect, embodiments of the present invention provide a non-transitory computer readable storage medium storing a computer program, the computer program causing a computer to execute one or more of the programs or methods described above.
Compared with the prior art, the invention at least has the following advantages and beneficial effects:
1) the front end and the back end simultaneously perform authority control, so that the experience of a front end user can be optimized, and the safety of a data interface is ensured;
2) when authorization management is carried out, only visible page function permission is concerned, and interfaces for calling each function do not need to be concerned, so that the operation threshold of operation management personnel can be reduced, and the working efficiency of the operation personnel can be improved.
Drawings
In order to more clearly illustrate the technical solutions of the exemplary embodiments of the present invention, the drawings that are required to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present invention and therefore should not be considered as limiting the scope, and that for those skilled in the art, other related drawings can be obtained from these drawings without inventive effort. In the drawings:
FIG. 1 is a flowchart illustrating an embodiment of a method for controlling authority of front and back separation items;
FIG. 2 is a diagram of E-R mapping between resource IDs and data interfaces in an embodiment of a method for controlling authority of front and back-end separation items;
FIG. 3 is a data layout diagram between a resource ID and a data interface in an embodiment of a method for controlling authority of a front-end and back-end separated project;
FIG. 4 is a diagram of a "user-role-authority" data model E-R in an embodiment of a method for controlling authority of front and back-end separated items;
FIG. 5 is a design diagram of a "user-role-authority" data model database in an embodiment of an authority control method for front and back-end separated items;
FIG. 6 is a block diagram of an embodiment of a system for controlling authority for front-end and back-end disjoint items;
fig. 7 is a block diagram of an electronic device.
Icon: 1-a processor; 2-a memory; 3-a data bus; 100-a page functional design module; 200-resource ID definition module; 300-a first association model building module; 400-a second association model building module; 500-front end display module; 501-a first obtaining unit; 502-a judgment unit; 503-a first presentation unit; 504-a second presentation unit; 600-a back-end verification module; 601-a second acquisition unit; 602-a verification unit; 603-an execution unit; 604-prompt element.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is further described in detail below with reference to examples and accompanying drawings, and the exemplary embodiments and descriptions thereof are only used for explaining the present invention and are not meant to limit the present invention.
It should be noted that the terms "first", "second", etc. appearing in the description of the present invention are used merely for distinguishing between the descriptions and are not intended to indicate or imply relative importance.
Example 1
Referring to fig. 1, an embodiment of the present invention provides a method for controlling authority of a front-end and a back-end separated item, including the following steps:
s101, determining resources needing to be subjected to authority control and display forms of the resources on a front-end page when the resources have authority or do not have the authority;
in the stage of page function design, page elements such as menus, pages, function modules, operation items and the like to be subjected to authority control need to be determined, which are called resources in this embodiment, and the display forms of the page elements with and without authority are determined at the same time. In this embodiment, the display mode in the authorized state is defined as a first mode, and the display mode in the unauthorized state is defined as a second mode, for example: user management menu: if the menu item is displayed in the case of having the right, and if the menu item is hidden in the case of not having the right, the first mode is 'display', and the second mode is 'hidden'. Adding a button: the button is highlighted when the authority exists, and the button is displayed in gray when the authority does not exist, so that the first form is highlighted, and the second form is gray.
S102, defining a resource ID of a unique identifier for the resource;
in the front-end development process, a unique identifier ID, called resource ID, is defined for the resource that explicitly needs to be subjected to authority control in S101, so that the association with the interface is established in the subsequent steps. For example, a user management menu may be defined as: menu _ user _ manager; the newly added button may be defined as button _ add _ new.
S103, acquiring an interface to be called of each resource ID, and establishing a first association model between the resource ID and the interface;
in the back-end data interface design process, an interface to be called for each resource ID is specified, a one-to-many first association model of the resource ID to the data interface (i.e. a mapping table of the resource ID and the back-end data interface) is established, an E-R diagram is shown in fig. 2, and a data design diagram is shown in fig. 3.
S104, constructing a second association model of the user ID and the resource ID of the user owning authority;
illustratively, a general user-role-authority data model can be established to determine whether a user has authority to access an interface or whether resources are displayed to a desired user in a first form, and when a front end initiates a request and a back end detects that the user has authority, data is responded; otherwise, no authority is prompted. The E-R diagram is shown in FIG. 4, and the database design is shown in FIG. 5.
S105, acquiring a user ID, acquiring a user authorized resource ID set based on the second association model, judging whether the resource ID is in the user authorized resource ID set, and determining the display form of the corresponding resource on a front-end page according to the judgment result;
after the user logs in, based on the second association model established in step S104, a role ID associated with the user is queried through the current user ID, a set of associated authorized resource IDs is queried through the role ID, and the set of authorized resource IDs is responded to the front end; when the front end needs to render page elements, the front end judges whether the resource ID is in the permission set or not, and gives different display states corresponding to the resources, such as display (with permission), hiding (without permission), highlight (with permission), graying (without permission) and the like.
S106, after receiving the interface request, the back end obtains an interface set which is called by the user and has the authority based on the user authorized resource ID set and the first association model, verifies whether the interface requested currently is in the interface set, and executes corresponding interface logic after the verification is passed.
After receiving the interface request, the back end queries a role ID associated with the user through the user ID of the current request according to the second association model established in the step S104, and then queries an associated resource ID through the role ID; then, according to the first association model established in step 103, an interface set which has permission to call is inquired through resource ID association, whether the currently requested interface is in the interface set is verified, if the currently requested interface is in the set, interface logic is executed, and data is returned; otherwise, directly returning a prompt without interface calling authority.
The joint application of the first association model and the second association model can realize the visual page configuration function, and system operation management personnel maintain the association relation; when the operator manages the user role right, the association (first association model) between the resource and the interface is not needed to be concerned, and the association relationship can be determined in the development process. Operators only need to associate resource permissions for roles and authorize roles for users.
Example 2
Referring to fig. 6, an embodiment of the present invention provides a system for controlling authority of a front-end and a back-end separated item, including: page function design module 100: the method comprises the steps of determining resources needing to be subjected to authority control and display forms of the resources on a front-end page when the resources have authority and do not have authority; resource ID definition module 200: a resource ID for defining a unique identifier for the resource; the first association model building module 300: the interface calling method comprises the steps of obtaining an interface to be called of each resource ID, and establishing a first association model between the resource ID and the interface; the second association model building module 400: constructing a second association model of the user ID and the resource ID of the user owning the authority; front-end display module 500: the system comprises a first correlation model, a second correlation model and a front-end page, wherein the first correlation model is used for acquiring a user ID, acquiring a user authorized resource ID set based on the second correlation model, judging whether the resource ID is in the user authorized resource ID set or not, and determining the display form of a corresponding resource on the front-end page according to the judgment result; the back-end verification module 600: after receiving an interface request, the back end obtains an interface set which is called by the user and has the authority based on the user authorized resource ID set and the first association model, verifies whether the interface requested currently is in the interface set, and executes corresponding interface logic after the verification is passed.
Wherein, the front end display module includes: a first obtaining unit 501, configured to obtain a user ID, and obtain a user authorized resource ID set based on the second association model; a determining unit 502, configured to determine whether the resource ID is in the user authorized resource ID set; a first display unit 503, configured to display the corresponding resource in a first form on a front-end page; the second display unit 504 is configured to enable the corresponding resource to be displayed on the front-end page in a second form.
The back-end verification module includes: a second obtaining unit 601, configured to obtain, by a back end, an interface set that a user has an authority to call based on the user authorized resource ID set and the first association model after receiving an interface request; a verifying unit 602, configured to verify whether a currently requested interface is in the interface set; an execution unit 603, configured to execute a corresponding interface logic after the verification is passed; and a prompt unit 604, configured to return a prompt for the non-interface call permission when the verification fails.
The system provided by the embodiment of the present invention can be used for executing the method described in the above embodiment 1, and the specific method steps are shown in embodiment 1. And will not be described in detail herein.
Example 3
An embodiment of the present invention provides an electronic device, including: at least one processor 1, at least one memory 2 and a data bus 3;
wherein, the processor 1 and the memory 2 complete the communication with each other through the data bus 3; the memory 2 stores program instructions executable by the processor 1, and the processor 1 calls the program instructions to execute the method in the embodiment, for example, to execute: s101, determining resources needing to be subjected to authority control and display forms of the resources on a front-end page when the resources have authority or do not have the authority; s102, defining a resource ID of a unique identifier for the resource; s103, acquiring an interface to be called of each resource ID, and establishing a first association model between the resource ID and the interface; s104, constructing a second association model of the user ID and the resource ID of the user owning authority; s105, acquiring a user ID, acquiring a user authorized resource ID set based on the second association model, judging whether the resource ID is in the user authorized resource ID set, and determining the display form of the corresponding resource on a front-end page according to the judgment result; s106, after receiving the interface request, the back end obtains an interface set which is called by the user and has the authority based on the user authorized resource ID set and the first association model, verifies whether the interface requested currently is in the interface set, and executes corresponding interface logic after the verification is passed.
Fig. 7 is a schematic structural block diagram of an electronic device according to an embodiment of the present application. The electronic device comprises a memory 2, a processor 1 and a data bus 3, the memory 2, the processor 1 and the data bus 3 being electrically connected to each other, directly or indirectly, to enable transmission or interaction of data. For example, the components may be electrically connected to each other via one or more communication buses or signal lines. The memory 2 can be used for storing software programs and modules, such as program instructions/modules corresponding to the electronic device provided in the embodiments of the present application, and the processor 1 executes the software programs and modules stored in the memory 2, thereby executing various functional applications and data processing. The data bus 3 can be used for signaling or data communication with other node devices.
Example 4
Embodiments of the present invention provide a non-transitory computer readable storage medium storing a computer program, the computer program causing a computer to execute one or more of the above-mentioned programs or methods, such as performing: s101, determining resources needing to be subjected to authority control and display forms of the resources on a front-end page when the resources have authority or do not have the authority; s102, defining a resource ID of a unique identifier for the resource; s103, acquiring an interface to be called of each resource ID, and establishing a first association model between the resource ID and the interface; s104, constructing a second association model of the user ID and the resource ID of the user owning authority; s105, acquiring a user ID, acquiring a user authorized resource ID set based on the second association model, judging whether the resource ID is in the user authorized resource ID set, and determining the display form of the corresponding resource on a front-end page according to the judgment result; s106, after receiving the interface request, the back end obtains an interface set which is called by the user and has the authority based on the user authorized resource ID set and the first association model, verifies whether the interface requested currently is in the interface set, and executes corresponding interface logic after the verification is passed.
The above-described functions, if implemented in the form of software functional modules and sold or used as a separate product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the above-described method according to the embodiments of the present application. And the storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The above-mentioned embodiments are intended to illustrate the objects, technical solutions and advantages of the present invention in further detail, and it should be understood that the above-mentioned embodiments are merely exemplary embodiments of the present invention, and are not intended to limit the scope of the present invention, and any modifications, equivalent substitutions, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.
Claims (10)
1. A method for controlling authority of a front-end and back-end separated project is characterized by comprising the following steps:
determining resources needing to be subjected to authority control and display forms of the resources on a front-end page when the resources have authority and are not authorized;
defining a resource ID of a unique identifier for the resource;
acquiring an interface to be called of each resource ID, and establishing a first association model between the resource ID and the interface;
constructing a second association model of the user ID and the resource ID of the user owning the authority;
acquiring a user ID, acquiring a user authorized resource ID set based on the second association model, judging whether the resource ID is in the user authorized resource ID set, and determining the display form of the corresponding resource on a front-end page according to the judgment result;
after receiving an interface request, the back end obtains an interface set which is called by a user and has authority based on the user authorized resource ID set and the first association model, verifies whether the interface requested currently is in the interface set, and executes corresponding interface logic after the verification is passed.
2. The method for controlling authority of a front-end and back-end separated project according to claim 1, wherein the resources comprise menus, function modules and operation items.
3. The method for controlling the authority of a front-end and back-end separated project according to claim 1, wherein the step of judging whether the resource ID is in the user authorized resource ID set or not and the step of determining the display form of the corresponding resource on the front-end page according to the judgment result comprises: if the judgment result is yes, the corresponding resource is displayed on the front-end page in the first form, and if the judgment result is no, the corresponding resource is displayed on the front-end page in the second form.
4. The method of claim 3, wherein the first mode is display and the second mode is hidden.
5. The method for controlling the authority of a front-end and back-end separation project according to claim 1, wherein the current requested interface is verified whether to be in the interface set, and if the verification is not passed, a prompt without interface calling authority is returned.
6. An entitlement control system for separating items at a front end and a back end, comprising:
a page function design module: the method comprises the steps of determining resources needing to be subjected to authority control and display forms of the resources on a front-end page when the resources are authorized or not authorized;
the resource ID definition module: a resource ID for defining a unique identification for the resource;
the first association model building module: the interface calling method comprises the steps of obtaining an interface to be called of each resource ID, and establishing a first association model between the resource ID and the interface;
the second association model establishing module: constructing a second association model of the user ID and the resource ID of the user owning the authority;
a front-end display module: the system comprises a first correlation model, a second correlation model and a front-end page, wherein the first correlation model is used for acquiring a user ID, acquiring a user authorized resource ID set based on the second correlation model, judging whether the resource ID is in the user authorized resource ID set or not, and determining the display form of a corresponding resource on the front-end page according to the judgment result;
a back-end verification module: after receiving an interface request, the back end obtains an interface set which is called by a user and has authority based on the user authorized resource ID set and the first association model, verifies whether the interface requested currently is in the interface set, and executes corresponding interface logic after the verification is passed.
7. The system for controlling authority of front-end and back-end separated items according to claim 6, wherein the front-end display module comprises:
a first obtaining unit, configured to obtain a user ID, and obtain a user authorized resource ID set judgment unit based on the second association model, configured to judge whether a resource ID is in the user authorized resource ID set;
the first display unit is used for displaying the corresponding resources on the front-end page in a first form;
and the second display unit is used for displaying the corresponding resources on the front-end page in a second form.
8. The system for controlling authority of a front-end and back-end separated project according to claim 6, wherein the back-end verification module comprises:
the second obtaining unit is used for obtaining an interface set which is called by the user with the authority based on the ID set of the user with the authority and the first association model after the back end receives the interface request;
a verification unit for verifying whether the currently requested interface is within the interface set;
the execution unit is used for executing corresponding interface logic after the verification is passed;
and the prompting unit is used for returning a prompt of the interface-free calling authority when the verification fails.
9. An electronic device, comprising: at least one processor, at least one memory, and a data bus;
the processor and the memory complete mutual communication through the data bus; the memory stores program instructions executable by the processor, the processor calling the program instructions to perform the method of any of claims 1 to 5.
10. A non-transitory computer-readable storage medium storing a computer program that causes a computer to perform the method according to any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111470873.5A CN114115881A (en) | 2021-12-03 | 2021-12-03 | Authority control method, system, equipment and storage medium for front-end and back-end separation items |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111470873.5A CN114115881A (en) | 2021-12-03 | 2021-12-03 | Authority control method, system, equipment and storage medium for front-end and back-end separation items |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114115881A true CN114115881A (en) | 2022-03-01 |
Family
ID=80366781
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111470873.5A Withdrawn CN114115881A (en) | 2021-12-03 | 2021-12-03 | Authority control method, system, equipment and storage medium for front-end and back-end separation items |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114115881A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114978671A (en) * | 2022-05-18 | 2022-08-30 | 中国平安财产保险股份有限公司 | Method and device for accessing front-end resources, computer equipment and storage medium |
| CN115495718A (en) * | 2022-09-19 | 2022-12-20 | 广东云徙智能科技有限公司 | Method, device and equipment for authorizing back-end capability based on front-end declaration |
| CN118468324A (en) * | 2024-07-12 | 2024-08-09 | 宁波安得智联科技有限公司 | Interface authority configuration method and device, electronic equipment and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180101668A1 (en) * | 2015-05-19 | 2018-04-12 | Ricoh Company, Ltd. | Information processing apparatus, information processing method, and computer program |
| CN111552987A (en) * | 2020-04-16 | 2020-08-18 | 重庆富民银行股份有限公司 | Page access authority control method |
| CN111814179A (en) * | 2020-06-29 | 2020-10-23 | 中国平安人寿保险股份有限公司 | User authority management and data control method and related equipment thereof |
| CN112487392A (en) * | 2020-12-08 | 2021-03-12 | 浪潮云信息技术股份公司 | Method for realizing authority control of management system by front end |
-
2021
- 2021-12-03 CN CN202111470873.5A patent/CN114115881A/en not_active Withdrawn
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180101668A1 (en) * | 2015-05-19 | 2018-04-12 | Ricoh Company, Ltd. | Information processing apparatus, information processing method, and computer program |
| CN111552987A (en) * | 2020-04-16 | 2020-08-18 | 重庆富民银行股份有限公司 | Page access authority control method |
| CN111814179A (en) * | 2020-06-29 | 2020-10-23 | 中国平安人寿保险股份有限公司 | User authority management and data control method and related equipment thereof |
| CN112487392A (en) * | 2020-12-08 | 2021-03-12 | 浪潮云信息技术股份公司 | Method for realizing authority control of management system by front end |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114978671A (en) * | 2022-05-18 | 2022-08-30 | 中国平安财产保险股份有限公司 | Method and device for accessing front-end resources, computer equipment and storage medium |
| CN114978671B (en) * | 2022-05-18 | 2024-02-13 | 中国平安财产保险股份有限公司 | Method, device, computer equipment and storage medium for front-end resource access |
| CN115495718A (en) * | 2022-09-19 | 2022-12-20 | 广东云徙智能科技有限公司 | Method, device and equipment for authorizing back-end capability based on front-end declaration |
| CN115495718B (en) * | 2022-09-19 | 2023-10-13 | 广东云徙智能科技有限公司 | Front-end statement-based back-end capability authorization method, device and equipment |
| CN118468324A (en) * | 2024-07-12 | 2024-08-09 | 宁波安得智联科技有限公司 | Interface authority configuration method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN114115881A (en) | Authority control method, system, equipment and storage medium for front-end and back-end separation items | |
| EP3896916B1 (en) | Network distribution method for household appliance, household appliance, mobile terminal and storage medium | |
| CN107995215B (en) | Control method and device of intelligent household equipment and cloud platform server | |
| TWI788354B (en) | Method and apparatus for managing vehicle control permissions | |
| US10999721B2 (en) | Communication identifier binding processing method and terminal | |
| CN102801656B (en) | Realize condition control method, the equipment and system of instant messaging application | |
| CN101730099B (en) | Terminal management method based on authority control and device | |
| CN110598280A (en) | Equipment simulation system and method and computer readable storage medium | |
| CN112948804B (en) | Program control method, device and computer readable storage medium | |
| CN112579997B (en) | User permission configuration method and device, computer equipment and storage medium | |
| US20140099923A1 (en) | Subscriber device unlock | |
| CN113055252B (en) | Method, device, equipment and storage medium for detecting newly added service host | |
| CN106656985B (en) | Backup account login method, device and system | |
| CN114218619A (en) | Data security protection method, device, medium and electronic equipment | |
| CN114238939B (en) | Authority verification method, device and system | |
| CN104394526A (en) | Method for recovering data service and electronic apparatus | |
| CN106685914A (en) | Information authentication method, server and client | |
| CN108416207A (en) | Bluetooth access right discrimination method, device and mobile terminal | |
| CN104717258B (en) | A kind of data transmission method for uplink and system | |
| CN113779551B (en) | A rights management method and device | |
| CN113312661B (en) | User authorization system, method and device and electronic equipment | |
| CN104063659A (en) | Network connection safety improvement method and electronic equipment | |
| CN115242476B (en) | Login verification method, login verification device, login verification medium and electronic equipment | |
| CN109862081A (en) | The method, apparatus and vehicle washing system of communication connection are established with maintenance personnel | |
| CN113660288B (en) | User number binding method and system based on block chain system |
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 | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20220301 |
|
| WW01 | Invention patent application withdrawn after publication |