CN113839960A - Method, system and storage medium for managing resource and interface authority - Google Patents
Method, system and storage medium for managing resource and interface authority Download PDFInfo
- Publication number
- CN113839960A CN113839960A CN202111408112.7A CN202111408112A CN113839960A CN 113839960 A CN113839960 A CN 113839960A CN 202111408112 A CN202111408112 A CN 202111408112A CN 113839960 A CN113839960 A CN 113839960A
- Authority
- CN
- China
- Prior art keywords
- resource
- user
- interface
- authority
- service system
- 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.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/20—Network architectures or network communication protocols for network security for managing network security; network security policies in general
Abstract
The application discloses a method, a system and a storage medium for managing resource and interface permissions, and belongs to the technical field of computers. The management method comprises the steps of obtaining characteristic data of a user and a resource authority request of the user, which are sent by at least one third-party service system; and aiming at each third-party business system, executing a first operation: configuring an available resource list of each user according to the characteristic data of the user and the resource authority request of each user; returning the available resource lists of all the users to the third-party service system; acquiring an operation request initiated by each user in a corresponding third-party service system based on the available resource list of each user; performing authority verification on the interface address of the operation request; returning the interface address verification result of each operation request to the third-party service system; the management of the resources and the interface authority of a plurality of third-party service systems is realized, and the management efficiency of the resources and the interface authority is improved.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method, a system, and a storage medium for managing resource and interface permissions.
Background
The authority control is a very basic and common functional module for software systems, almost all software systems need to be accessed with the authority control, a front-end interface correspondingly displays according to resource authority, and a rear-end interface determines whether the operation authority can be called to a user or not according to the interface authority.
At present, different service systems are developed for different service operators, each user in the different service systems has respective authority, and each service system needs to configure the authority of different users, so that only part of resources and operation authority which accord with the authority of the target user are provided for the target user.
However, the permission control is generally developed and maintained in the service system, which results in that multiple sets of permission control systems or modules need to be developed for multiple service systems, which results in too high development cost, is not favorable for upgrade iteration of services, and is also not favorable for management and maintenance of user permission in the later period.
Disclosure of Invention
The application provides a method, a system and a storage medium for managing resources and interface authorities, which are used for solving the problems in the prior art and improving the management efficiency of the resources and the interface authorities.
In order to achieve the purpose, the following scheme is adopted in the application:
in one aspect, an embodiment of the present application provides a method for managing resources and interface permissions, where the method includes:
acquiring characteristic data of a user and a resource authority request of the user, which are sent by at least one third-party service system;
and aiming at each third-party business system, executing a first operation:
configuring an available resource list of each user according to the characteristic data of the user and the resource authority request of each user;
returning the available resource lists of all the users to the third-party service system;
acquiring an operation request initiated by each user in a corresponding third-party service system based on the available resource list of each user;
performing authority verification on the interface address of the operation request;
and returning the interface address verification result of each operation request to the third-party service system.
Optionally, the method further includes:
and generating target application corresponding to each third-party service system based on each third-party service system, and returning the application ID of each target application to the corresponding third-party service system.
Optionally, when the characteristic data of the user and the resource permission request of the user, which are sent by the at least one third-party service system, are obtained, the method further includes:
determining a target application corresponding to the third-party service system according to the application ID sent by the third-party service system;
and executing the first operation through the target application corresponding to the application ID.
Optionally, the method further includes:
adding corresponding resource items of a third-party service system and interface addresses corresponding to all the resource items in the target application, and associating each resource item with the corresponding interface address;
and carrying out authority management on the corresponding third-party service system through the target application.
In a second aspect, an embodiment of the present application provides a method for managing resources and interface permissions, where the method includes:
sending characteristic data of a user and a resource authority request of the user to the resource and interface authority management system;
receiving available resource lists of all the users sent by the resource and interface authority management system;
acquiring an operation request initiated by each user at the front end based on the available resource list of each user;
sending the operation request to the resource and interface authority management system;
receiving an interface address verification result of each operation request returned by the resource and interface authority management system;
and opening or closing the authority of the corresponding interface to the user according to the interface address verification result of each operation request.
Optionally, the method further includes:
before sending the characteristic data of the user and the resource authority request of the user to the resource and interface authority management system, connecting the resource and interface authority management system, and receiving an application ID returned by the resource and interface authority management system;
wherein the application ID corresponds to a target application in the resource and interface rights management system.
In a third aspect, an embodiment of the present application provides a third-party service system, where the system includes:
the acquisition module is used for acquiring the characteristic data of the user and the resource authority request of the user, which are sent by at least one third-party service system;
the processing module is used for executing a first operation aiming at each third-party service system:
configuring an available resource list of each user according to the characteristic data of the user and the resource authority request of each user;
the sending module is used for returning the available resource lists of all the users to the third-party service system;
the obtaining module is further configured to obtain an operation request initiated by each user in a corresponding third-party service system based on the available resource list of each user;
the processing module is further used for performing authority verification on the interface address of the operation request;
and the sending module is used for returning the interface address verification result of each operation request to the third-party service system.
In a fourth aspect, an embodiment of the present application provides a resource and interface authority management system, where the system includes:
the sending module is used for sending the characteristic data of the user and the resource authority request of the user to the resource and interface authority management system;
the receiving module is used for receiving the available resource lists of all the users sent by the resource and interface authority management system;
an obtaining module, configured to obtain an operation request initiated by each user at a front end based on an available resource list of each user;
the sending module is further configured to send the operation request to the resource and interface authority management system;
the receiving module is further configured to receive an interface address verification result of each operation request returned by the resource and interface authority management system;
and the processing module is used for opening or closing the authority of the corresponding interface to the user according to the authority verification result of the corresponding interface.
In another aspect, an embodiment of the present application provides an electronic device, including: the system comprises a processor, a memory and a program stored on the memory and capable of running on the processor, wherein the program realizes the steps of the management method of the resource and the interface authority according to any one of the embodiments provided in the application when being executed by the processor.
In another aspect, the present application provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the steps of the method for managing resource and interface rights according to any one of the embodiments provided in the present application.
The beneficial effects brought by the technical scheme provided by the embodiment of the application at least comprise:
the embodiment of the application provides a method for managing resources and interface permissions, which comprises the steps of obtaining characteristic data of a user and a resource permission request of the user, wherein the characteristic data is sent by at least one third-party service system; and aiming at each third-party business system, executing a first operation: configuring an available resource list of each user according to the characteristic data of the user and the resource authority request of each user; then returning all the available resource lists of the users to the third-party service system; acquiring an operation request initiated by each user in a corresponding third-party service system based on the available resource list of each user; performing authority verification on the interface address of the operation request; returning the interface address verification result of each operation request to the third-party service system; therefore, the management of the resources and the interface authority of a plurality of third-party service systems is realized, the management efficiency of the resources and the interface authority is improved, and the maintenance cost is reduced.
Drawings
Fig. 1 is a first flowchart of a method for managing resources and interface permissions according to an embodiment of the present application;
fig. 2 is a data structure diagram of a management method for resource and interface permissions according to an embodiment of the present application;
FIG. 3 is a second flowchart of a method for managing resource and interface permissions according to an embodiment of the present application;
fig. 4 is a schematic view of interaction of resource and interface right management information according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of a resource and interface right management system according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of a third-party service system according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the drawings of the embodiments of the present application. It should be apparent that the described embodiments are only some of the embodiments of the present application, and 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.
The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that embodiments of the application may be practiced in sequences other than those illustrated or described herein, and that the terms "first," "second," and the like are generally used herein in a generic sense and do not limit the number of terms, e.g., the first term can be one or more than one. In addition, "and/or" in the specification and claims means at least one of connected objects, a character "/" generally means that a preceding and succeeding related objects are in an "or" relationship.
In addition, the technical features mentioned in the different embodiments of the present application described below may be combined with each other as long as they do not conflict with each other.
The following describes in detail a method for managing resources and interface permissions provided by the embodiments of the present application through specific embodiments and application scenarios thereof with reference to the accompanying drawings.
Referring to fig. 1, which shows a first flowchart illustration of a management method for resource and interface permissions provided by an embodiment of the present application, a method flow shown in fig. 1 may be used in a resource and interface permissions management system, and includes:
Specifically, the "user" herein refers to a user currently logged into the third-party service system.
Exemplarily, for example, the service system 1 sends feature data of users "zhang san" and "lie si" and resource authority requests of the users "zhang san" and "lie si"; the service system 2 sends a resource authority request of a user 'emerald' and the user 'emerald'; the business system 3 sends resource authority requests of users 'wang di', 'zhao yi', 'qin wu' and the users 'wang di', 'zhao yi', 'qin wu'; the method for managing resources and interface permissions provided in the embodiment of the present application can simultaneously obtain the characteristic data of multiple users and the resource permission requests of these users, which are sent by the service system 1, the service system 2, and the service system 3.
and configuring an available resource list of each user according to the characteristic data of the user and the resource authority request of each user.
Exemplarily, such as feature data of user "zhang san" and "lie si" and resource permission requests of the user "zhang san" and "lie si", which are sent according to the service system 1; respectively configuring the available resource lists of the users in the service system 1 for the users "zhang san" and "lie si", for example, after the configuration is completed, obtaining:
"resource list X1y001q 123", "X + number" indicates a system number indicating the number of the service system 1 in the resource and interface right management system, "y + number" indicates a user ID, for example, "y 001" indicates that the user ID of zhang san is 001, and "q + number" indicates the number of a certain request;
"resource list X1y001q 111" represents a resource list corresponding to a request with a request ID q111 initiated by user number 001 "zhang san" in the service system 1;
similarly, the resource list corresponding to the request with the request ID q222 initiated in the service system 1 by the user "liquad" is obtained as "resource list X1y002q 222".
That is, by performing the first operation, the resource and interface privilege management system obtains "resource list X1y001q 111" and "resource list X1y002q 222" by receiving the user characteristic data of "zhang san" and "zhangsi"; the same is not repeated in the resource lists of "wang di", "zhao yi", "qin wu" and "cuihua".
Specifically, for example, the "resource list X1y001q 111" and the "resource list X1y002q 222" obtained in step 102 are returned to the business system 1, the "delphinium" resource list is returned to the business system 2, and the "wang di", "zhao yi", and "qin wu" resource lists are returned to the business system 3.
And 104, acquiring an operation request initiated by each user in the corresponding third-party service system based on the available resource list of each user.
Specifically, according to the available resource list of each user, in the corresponding third-party service system, for example, the front end of the service system opens their respective available resource list for each user, and the user initiates an operation request according to the available resource shown by the front end.
Illustratively, after receiving the resource list "X1 y001q 111" and the resource list "X1 y002q 222", the service system 1 opens a third available resource list for the user "zhangsan" in the service system 1 according to the resource list "X1 y001q 111", opens a fourth available resource list for the user "zhangsan" in the service system 1 according to the resource list "X1 y002q 222", and the user "zhangsan" performs some operations on its own available resource list, initiates an operation request, and can receive, through step 104, an operation request initiated by each user for its own available resource list in each third-party service system.
Specifically, the operation performed by the user may be an operation performed on an available resource list interface provided by the service system, such as a button resource operation request, for example, clicking/checking a function virtual key or a box, such as "delete", "edit", "add", "maintain", "export", "synchronize", and the like, where the specific type is determined by each third-party service system and is not listed here; the operation executed by the user can also be, for example, a module resource loading request, for example, a data acquisition request for a certain module is initiated by the user; the method can also comprise the request initiated by other operations executed by the user on the resource list, the specific type is determined by the third-party service system, and the requests are not listed one by one, and the user usually makes the operation initiation operation request at the front end of the third-party service system; and receiving the operation requests by the back end of the third-party service system and sending the operation requests to the resource and interface authority management system.
And 105, performing authority verification on the interface address of the operation request.
Illustratively, the resource and interface authority management system performs authority verification according to a request url interface address derived from an operation request initiated by a user Zhang III in the service system 1, and obtains a verification result, which has authority or no authority.
And step 106, returning the interface address verification result of each operation request to the third-party service system.
Specifically, the resource and interface authority management system performs interface address url verification on each operation request, and returns the result to the respective third-party service system; the third-party service system determines whether to respond to the operation request to the user initiating the operation request according to the verification result; if the service system 1 has the authority according to the operation request c001 of the user Zhang III, the service system 1 responds to the operation request c001 initiated by the user Zhang III, and if the authority does not exist, the authority deficiency prompt is returned to the front end of the service system 1 to remind the user Zhang III that the authority of the operation request c001 is deficient.
To sum up, the method for managing resource and interface permissions provided by the embodiment of the present application can achieve resource and interface permission management of multiple third-party service systems, improve management efficiency of resource and interface permissions, reduce maintenance cost, provide a privatization deployment function for third-party service system parties, and achieve direct access to permission systems or deployment of their own general permission systems inside a company for maintenance,
Optionally, the method further includes:
and generating target application corresponding to each third-party service system based on each third-party service system, and returning the application ID of each target application to the corresponding third-party service system.
Specifically, when the resource and interface authority management system uses the method provided by the present application, in order to facilitate management, first, third-party service systems are docked, so that the third-party service systems are docked with the resource and interface authority management systems, a corresponding target application is generated for each docked third-party service system, and an application ID of the target application is sent to the corresponding third-party service system.
For example, referring to fig. 2, a corresponding relationship between targets applied to third-party service systems is shown, after a first service system accesses a resource and interface authority management system, the resource and interface authority management system generates a first application, and the resource and interface authority management system sends an application ID of the first application, such as "X1", to the first service system, and so on, a second service system corresponds to a second application, and a second service system corresponds to a third application, and also sends their application IDs to corresponding service systems respectively.
Specifically, the third-party service system is used for docking a resource and interface authority management system for third-party service, an application is created for the third-party service system in the resource and interface authority management system and used for configuring the resource and interface authority of the third-party service system later, an application ID is provided for a service party, and the service party obtains the self-configured authority by sending the application ID to the resource and interface authority management system, such as an available resource list, an interface address authority verification result and the like.
Optionally, when the characteristic data of the user and the resource permission request of the user, which are sent by the at least one third-party service system, are obtained, the method further includes:
determining a target application corresponding to the third-party service system according to the application ID sent by the third-party service system;
and executing the first operation through the target application corresponding to the application ID.
Specifically, after the third-party service system and the access resident resource and interface authority management system are connected, according to the received application ID, when a resource authority request is initiated, the application ID is sent together, and the resource and interface authority management system determines a target application through the application ID, and performs authority management on the third-party service system through the application, for example, referring to a data structure diagram of a management method of resource and interface authority shown in fig. 2, the "service system" receives an application ID of "application one": x1, the resource and interface authority management system determines to perform resource and interface authority management on the business system through the received 'X1' determination and 'application one', such as executing a first operation, determining interface address authority and the like.
Optionally, the method further includes:
adding corresponding resource items of a third-party service system and interface addresses corresponding to all the resource items in the target application, and associating each resource item with the corresponding interface address;
and carrying out authority management on the corresponding third-party service system through the target application.
Specifically, each resource item is associated with a corresponding interface address, so that high-speed and quick authority management operation can be realized, and management of resources and interface authorities of a corresponding third-party service system by a target application is facilitated, so that the target application can provide different authority strategies according to the requirements of a service side system and allocate the authority strategies to different users.
Referring to fig. 3, which shows a second flowchart illustration of a method for managing resource and interface permissions provided by an embodiment of the present application, a method flow shown in fig. 3 may be used in a third-party service system, and may be generally executed by a backend of the third-party service system, and includes:
For example, after the rear end of the third-party service system receives the available resource lists of all the users sent by the resource and interface right management system, the available resource list is shown for a specific user at the front end of the third-party service system according to the available resource list, and the user can execute corresponding operations at the front end to initiate an operation request.
Specifically, the foregoing examples of the operation request have been listed and are not described again here.
Specifically, after receiving an operation request initiated by a user at a front end, a back end of the third-party service system sends each operation request to a resource and interface authority management system, and interface address authority authentication of each operation request is performed.
Specifically, if the address url of the operation request a passes the verification result, the front end of the third-party service system corresponding to the operation request a responds to the user who initiated the operation request a, and if the address url of the operation request a does not pass the verification result, an unauthorized prompt is initiated to the user who initiated the operation request a.
Optionally, the method further includes:
before sending the characteristic data of the user and the resource authority request of the user to the resource and interface authority management system, connecting the resource and interface authority management system, and receiving an application ID returned by the resource and interface authority management system;
wherein the application ID corresponds to a target application in the resource and interface rights management system.
Specifically, the third-party service system is docked with the resource and interface authority management system, after the resource and interface authority management system is docked, the rear end of the third-party service system receives an application ID sent by the resource and interface authority management system, then information interaction is carried out between the application ID and a target application generated in the resource and interface authority management system, and an authority management strategy of the target application to the third-party service system is received.
Referring to fig. 4, a schematic diagram of information interaction when performing resource and interface right management between a front end of a third-party service system, a back end of the third-party service system, and a resource and interface right management system;
1. the front end of the service system sends a resource authority request initiated by a user to the back end of the service system;
2. the back end of the service system sends an application ID, user characteristic information and a user resource authority request to a resource and interface authority management system;
3. the resource and interface authority management system returns an available resource list of each user to the back end of the service system;
4. the front end of the service system displays an available resource list for each user;
5. the front end of the service system sends an operation request initiated by each user to the back end of the service system;
6. the back end of the service system initiates interface address authority verification of each operation request to a resource and interface authority management system;
7. the resource and interface authority management system returns an interface address authority verification result of each operation request to the back end of the service system;
8. and the front end of the service system opens or closes the authority of the corresponding interface to the user according to the interface address authority verification result of each operation request.
Referring to fig. 5, an embodiment of the present application provides a resource and interface rights management system 50, including:
an obtaining module 51, configured to obtain characteristic data of a user and a resource permission request of the user, where the characteristic data is sent by at least one third-party service system;
a processing module 52, configured to execute, for each third-party service system, a first operation of:
configuring an available resource list of each user according to the characteristic data of the user and the resource authority request of each user;
a sending module 53, configured to return all available resource lists of the users to the third-party service system;
the obtaining module 51 is further configured to obtain an operation request initiated by each user in a corresponding third-party service system based on the available resource list of each user;
the processing module 52 is further configured to perform authority verification on the interface address of the operation request;
the sending module 53 is configured to return an interface address verification result of each operation request to the third-party service system.
Optionally, the processing module 52 is further configured to generate a target application corresponding to each third-party service system based on each third-party service system, and return an application ID of each target application to the corresponding third-party service system.
Optionally, when acquiring the characteristic data of the user and the resource authority request of the user, which are sent by at least one third-party service system, the processing module 52 is further configured to:
determining a target application corresponding to the third-party service system according to the application ID sent by the third-party service system;
and executing the first operation through the target application corresponding to the application ID.
Optionally, the processing module 52 is further configured to add, in the target application, a corresponding resource item of the third-party service system and interface addresses corresponding to all resource items, and associate each resource item with a corresponding interface address;
and carrying out authority management on the corresponding third-party service system through the target application.
Referring to fig. 6, an embodiment of the present application provides a third-party service system 60, including:
a sending module 61, configured to send the characteristic data of the user and the resource authority request of the user to the resource and interface authority management system;
a receiving module 62, configured to receive the available resource list of all the users sent by the resource and interface authority management system;
an obtaining module 63, configured to obtain an operation request initiated by each user at a front end based on an available resource list of each user;
the sending module 61 is further configured to send the operation request to the resource and interface authority management system;
the receiving module 62 is further configured to receive an interface address verification result of each operation request returned by the resource and interface authority management system;
and the processing module 64 is configured to open or close the authority of the corresponding interface to the user according to the interface address verification result of each operation request.
Optionally, the processing module 64 is further configured to connect to the resource and interface authority management system before sending the characteristic data of the user and the resource authority request of the user to the resource and interface authority management system, and receive, through the receiving module 62, the application ID returned by the resource and interface authority management system;
wherein the application ID corresponds to a target application in the resource and interface rights management system.
Referring to fig. 7, an embodiment of the present invention further provides an electronic device 70, which includes a processor 71, a memory 72, and a computer program stored in the memory 72 and capable of running on the processor 71, where the computer program, when executed by the processor 71, implements the processes of the embodiment of the method for managing resource and interface permissions, and can achieve the same technical effect, and is not described herein again to avoid repetition.
The embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements each process of the embodiment of the method for managing resource and interface permissions, and can achieve the same technical effect, and is not described herein again to avoid repetition. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
It should be understood that the above examples are only for clarity of illustration and are not intended to limit the embodiments. Other variations and modifications will be apparent to persons skilled in the art in light of the above description. And are neither required nor exhaustive of all embodiments. And obvious variations or modifications of this invention are intended to be covered by the scope of the invention as expressed herein.
Claims (10)
1. A method for managing resource and interface permissions, comprising:
acquiring characteristic data of a user and a resource authority request of the user, which are sent by at least one third-party service system;
and aiming at each third-party business system, executing a first operation:
configuring an available resource list of each user according to the characteristic data of the user and the resource authority request of each user;
returning the available resource lists of all the users to the third-party service system;
acquiring an operation request initiated by each user in a corresponding third-party service system based on the available resource list of each user;
performing authority verification on the interface address of the operation request;
and returning the interface address verification result of each operation request to the third-party service system.
2. The method of managing resource and interface permissions according to claim 1, further comprising:
and generating target application corresponding to each third-party service system based on each third-party service system, and returning the application ID of each target application to the corresponding third-party service system.
3. The method for managing resource and interface permissions according to claim 2, where, when acquiring the user's feature data and the user's resource permission request sent by at least one third-party service system, further comprising:
determining a target application corresponding to the third-party service system according to the application ID sent by the third-party service system;
and executing the first operation through the target application corresponding to the application ID.
4. The method of managing resource and interface permissions according to claim 3, further comprising:
adding corresponding resource items of a third-party service system and interface addresses corresponding to all the resource items in the target application, and associating each resource item with the corresponding interface address;
and carrying out authority management on the corresponding third-party service system through the target application.
5. A method for managing resource and interface permissions, the method comprising:
sending characteristic data of a user and a resource authority request of the user to a resource and interface authority management system;
receiving available resource lists of all the users sent by the resource and interface authority management system;
acquiring an operation request initiated by each user at the front end based on the available resource list of each user;
sending the operation request to the resource and interface authority management system;
receiving an interface address verification result of each operation request returned by the resource and interface authority management system;
and opening or closing the authority of the corresponding interface to the user according to the interface address verification result of each operation request.
6. The method of managing resource and interface permissions according to claim 5, further comprising:
before sending the characteristic data of the user and the resource authority request of the user to the resource and interface authority management system, connecting the resource and interface authority management system, and receiving an application ID returned by the resource and interface authority management system;
wherein the application ID corresponds to a target application in the resource and interface rights management system.
7. A resource and interface rights management system, the system comprising:
the acquisition module is used for acquiring the characteristic data of the user and the resource authority request of the user, which are sent by at least one third-party service system;
the processing module is used for executing a first operation aiming at each third-party service system:
configuring an available resource list of each user according to the characteristic data of the user and the resource authority request of each user;
the sending module is used for returning the available resource lists of all the users to the third-party service system;
the obtaining module is further configured to obtain an operation request initiated by each user in a corresponding third-party service system based on the available resource list of each user;
the processing module is further used for performing authority verification on the interface address of the operation request;
and the sending module is used for returning the interface address verification result of each operation request to the third-party service system.
8. A third party business system, the system comprising:
the system comprises a sending module, a receiving module and a sending module, wherein the sending module is used for sending characteristic data of a user and a resource authority request of the user to a resource and interface authority management system;
the receiving module is used for receiving the available resource lists of all the users sent by the resource and interface authority management system;
an obtaining module, configured to obtain an operation request initiated by each user at a front end based on an available resource list of each user;
the sending module is further configured to send the operation request to the resource and interface authority management system;
the receiving module is further configured to receive an interface address verification result of each operation request returned by the resource and interface authority management system;
and the processing module is used for opening or closing the authority of the corresponding interface to the user according to the interface address verification result of each operation request.
9. An electronic device, comprising: processor, memory and a program stored on the memory and executable on the processor, the program implementing the steps of the method for managing resources and interface rights according to any one of claims 1 to 4, or claims 5 to 6, when executed by the processor.
10. A computer-readable storage medium, characterized in that a computer program is stored thereon, which computer program, when being executed by a processor, carries out the steps of the method for managing resources and interface rights of one of claims 1 to 4, or of claims 5 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111408112.7A CN113839960B (en) | 2021-11-25 | 2021-11-25 | Method, system and storage medium for managing resource and interface authority |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111408112.7A CN113839960B (en) | 2021-11-25 | 2021-11-25 | Method, system and storage medium for managing resource and interface authority |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113839960A true CN113839960A (en) | 2021-12-24 |
| CN113839960B CN113839960B (en) | 2022-03-11 |
Family
ID=78971629
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111408112.7A Active CN113839960B (en) | 2021-11-25 | 2021-11-25 | Method, system and storage medium for managing resource and interface authority |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113839960B (en) |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103036855A (en) * | 2011-09-29 | 2013-04-10 | 北京新媒传信科技有限公司 | Achievement device and method of authority management |
| CN104992118A (en) * | 2015-06-30 | 2015-10-21 | 北京奇虎科技有限公司 | Unified permission management method and system for multiple service systems |
| CN105429999A (en) * | 2015-12-17 | 2016-03-23 | 北京荣之联科技股份有限公司 | Unified identity authentication system based on cloud platform |
| CN110084033A (en) * | 2019-04-19 | 2019-08-02 | 广东中安金狮科创有限公司 | User identity management method, system and computer readable storage medium |
| CN110149328A (en) * | 2019-05-22 | 2019-08-20 | 平安科技（深圳）有限公司 | Interface method for authenticating, device, equipment and computer readable storage medium |
| CN110363012A (en) * | 2019-05-28 | 2019-10-22 | 石化盈科信息技术有限责任公司 | Method, permission system and the storage medium of authority configuration are carried out to permission resource |
| CN111191221A (en) * | 2019-12-30 | 2020-05-22 | 腾讯科技（深圳）有限公司 | Method and device for configuring authority resources and computer readable storage medium |
| CN111935260A (en) * | 2020-07-30 | 2020-11-13 | 珠海大横琴科技发展有限公司 | Account synchronization method and device, electronic equipment and storage medium |
| CN112579997A (en) * | 2020-12-17 | 2021-03-30 | 数字广东网络建设有限公司 | User permission configuration method and device, computer equipment and storage medium |
| CN112818328A (en) * | 2021-02-26 | 2021-05-18 | 重庆度小满优扬科技有限公司 | Multi-system authority management method, device, equipment and storage medium |
| CN113098695A (en) * | 2021-04-21 | 2021-07-09 | 金陵科技学院 | Micro-service unified authority control method and system based on user attributes |
-
2021
- 2021-11-25 CN CN202111408112.7A patent/CN113839960B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103036855A (en) * | 2011-09-29 | 2013-04-10 | 北京新媒传信科技有限公司 | Achievement device and method of authority management |
| CN104992118A (en) * | 2015-06-30 | 2015-10-21 | 北京奇虎科技有限公司 | Unified permission management method and system for multiple service systems |
| CN105429999A (en) * | 2015-12-17 | 2016-03-23 | 北京荣之联科技股份有限公司 | Unified identity authentication system based on cloud platform |
| CN110084033A (en) * | 2019-04-19 | 2019-08-02 | 广东中安金狮科创有限公司 | User identity management method, system and computer readable storage medium |
| CN110149328A (en) * | 2019-05-22 | 2019-08-20 | 平安科技（深圳）有限公司 | Interface method for authenticating, device, equipment and computer readable storage medium |
| CN110363012A (en) * | 2019-05-28 | 2019-10-22 | 石化盈科信息技术有限责任公司 | Method, permission system and the storage medium of authority configuration are carried out to permission resource |
| CN111191221A (en) * | 2019-12-30 | 2020-05-22 | 腾讯科技（深圳）有限公司 | Method and device for configuring authority resources and computer readable storage medium |
| CN111935260A (en) * | 2020-07-30 | 2020-11-13 | 珠海大横琴科技发展有限公司 | Account synchronization method and device, electronic equipment and storage medium |
| CN112579997A (en) * | 2020-12-17 | 2021-03-30 | 数字广东网络建设有限公司 | User permission configuration method and device, computer equipment and storage medium |
| CN112818328A (en) * | 2021-02-26 | 2021-05-18 | 重庆度小满优扬科技有限公司 | Multi-system authority management method, device, equipment and storage medium |
| CN113098695A (en) * | 2021-04-21 | 2021-07-09 | 金陵科技学院 | Micro-service unified authority control method and system based on user attributes |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113839960B (en) | 2022-03-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108234505B (en) | Account login method and system | |
| CN105897704B (en) | The methods, devices and systems of permission addition, permission addition request | |
| CN110958256B (en) | Cluster management method and management system | |
| CN107864144A (en) | Obtain method and device, computer installation and the storage medium of dynamic password | |
| CN110008665B (en) | Authority control method and device for blockchain | |
| CN110738479A (en) | Order management method and system based on multi-person ordering | |
| CN112950201B (en) | Node management method and related device applied to block chain system | |
| US20090083382A1 (en) | Real-time presence of online contacts | |
| CN107438054A (en) | The method and system of menu information control are realized based on public platform | |
| CN105373714B (en) | A kind of user authority control method and device | |
| CN106778178A (en) | The call method and device of fingerprint business card | |
| CN107645474B (en) | Method and device for logging in open platform | |
| CN114417278A (en) | Interface unified management system and platform interface management system | |
| CN112579997B (en) | User permission configuration method and device, computer equipment and storage medium | |
| CN113839960B (en) | Method, system and storage medium for managing resource and interface authority | |
| US10326833B1 (en) | Systems and method for processing request for network resources | |
| CN111200645A (en) | Service request processing method, device, equipment and readable storage medium | |
| CN113742369B (en) | Data authority management method, system and storage medium | |
| CN108989418A (en) | A kind of resource amount method of mixed cloud object storage common authentication | |
| CN114528274A (en) | Authority management method and related device | |
| CN112907278B (en) | Rights object distribution control method and device, equipment and medium thereof | |
| CN113312661B (en) | User authorization system, method and device and electronic equipment | |
| CN112069474B (en) | Method for using and forgetting user data and third-party trusted server | |
| CN111383003B (en) | Method, device, computer equipment and storage medium for fast platform access | |
| CN105610687A (en) | Data processing method and 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |