CN113922999A - Authority management configuration method and system based on routing management and electronic equipment - Google Patents
Authority management configuration method and system based on routing management and electronic equipment Download PDFInfo
- Publication number
- CN113922999A CN113922999A CN202111154424.XA CN202111154424A CN113922999A CN 113922999 A CN113922999 A CN 113922999A CN 202111154424 A CN202111154424 A CN 202111154424A CN 113922999 A CN113922999 A CN 113922999A
- Authority
- CN
- China
- Prior art keywords
- management
- interface
- annotation
- routing
- authority
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 58
- 230000015654 memory Effects 0.000 claims description 17
- 230000006870 function Effects 0.000 claims description 7
- 238000004590 computer program Methods 0.000 claims description 6
- 238000012423 maintenance Methods 0.000 claims description 3
- 238000012545 processing Methods 0.000 description 5
- 238000011161 development Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000013507 mapping Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
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/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
- H04L63/105—Multiple levels of security
-
- 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
- H04L63/0807—Network architectures or network communication protocols for network security for authentication of entities using tickets, e.g. Kerberos
-
- 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
- H04L63/0815—Network architectures or network communication protocols for network security for authentication of entities providing single-sign-on or federations
Abstract
The invention discloses a method, a system and an electronic device for managing and configuring authority based on routing management, wherein the method comprises the following steps: defining a routing annotation, and associating the routing annotation with an interface type, wherein the interface type comprises an open interface, a background management interface, a front-end App interface and a public interface; defining security class annotations applicable to the open interface and the background management interface; configuring the right management based on the route management based on the combination of the route annotation and the security class annotation. The invention realizes the configuration of the routing management and the authority management by configuring the routing annotation and the security annotation and carrying out the combination configuration of the routing annotation and the security annotation on the authority management based on the routing management, and solves the problem of the need of the repeated authentication of the user by the combination of the routing annotation and the security annotation.
Description
Technical Field
The invention relates to the technical field of rights management configuration, in particular to a rights management configuration method and system based on routing management and an electronic device.
Background
The existing single sign-on scheme only provides a sign-on verification function, so that only information required by sign-on is configured, and configuration of authority management cannot be realized. In addition, in the prior art, each subsystem needs user authentication when logging in, each subsystem needs to consider the complicated logic of repeated authentication when designing, and the repeated authentication can also cause the reduction of user experience when in use.
Aiming at the problems that the configuration of the authority management can not be realized and the user needs to repeatedly authenticate in the related technology, an effective solution is not provided at present.
Disclosure of Invention
The invention mainly aims to provide a method and a system for configuring authority management based on routing management, which are used for solving the problems that the configuration of the authority management cannot be realized and a user needs to repeatedly authenticate in the related technology.
In order to achieve the above object, a first aspect of the present invention provides a rights management configuration method based on route management, including:
defining a routing annotation, and associating the routing annotation with an interface type, wherein the interface type comprises an open interface, a background management interface, a front-end App interface and a public interface;
defining security class annotations applicable to the open interface and the background management interface;
configuring the right management based on the route management based on the combination of the route annotation and the security class annotation.
Optionally, the open interface is invoked by a java program at a server or a user outside a service center;
the background management interface is called from the background management interface through a browser so as to support service operation and system maintenance;
the front-end App interface is called by an application program running on the client terminal;
the public interface does not participate in the authority management and is directly released.
Optionally, the defining security class annotations applicable to the open interface and the background management interface includes:
defining an authority role suitable for a background management interface;
defining authority operation suitable for a background management interface;
defining the scope of rights applicable to the open interface.
Furthermore, the authority role acts on the class, and the acting range is all methods under the class and is used for managing a specified page or a menu group;
the authority operation acts on the method and is used for describing the designated operation and managing the designated resources or function buttons;
the permission range acts on the class or method for verifying the access permission of the specified accesstken.
Optionally, the route annotation and the security class annotation are marked on a method level of the interface to perform configuration of route management and rights management.
Optionally, after configuring the rights management based on the route management, the method further includes:
accessing an external application system;
and configuring a UAA server and a gateway address for the external application system.
Optionally, after configuring the rights management based on the route management, the method further includes:
providing an accessed SDK based on the SpringBoot;
and configuring the UAA server and the gateway address into the SDK so as to carry out the configuration of route management and authority management through the UAA management interface.
The second aspect of the present invention provides a rights management configuration system based on route management, including:
the device comprises a first definition unit, a second definition unit and a third definition unit, wherein the first definition unit is used for defining a route annotation and associating the route annotation with an interface type, and the interface type comprises an open interface, a background management interface, a front-end App interface and a public interface;
the second definition unit is used for defining the security class annotation suitable for the open interface and the background management interface;
and the combination unit is used for configuring the authority management based on the routing annotation based on the combination of the routing annotation and the security class annotation.
A third aspect of the present invention provides a computer-readable storage medium storing computer instructions for causing a computer to execute the method for configuring routing management based rights management provided in any one of the first aspects.
A fourth aspect of the present invention provides an electronic apparatus, comprising: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores a computer program executable by the at least one processor, the computer program being executable by the at least one processor to cause the at least one processor to perform the method for configuring routing management based rights management as provided in any of the first aspects.
In the method for configuring authority management based on routing management provided by the embodiment of the invention, a routing annotation is defined firstly, and the routing annotation is associated with an interface type, wherein the interface type comprises an open interface, a background management interface, a front-end App interface and a public interface; then defining safety class annotation suitable for the open interface and the background management interface; and finally configuring the authority management based on the routing annotation based on the combination of the routing annotation and the security class annotation. The invention realizes the configuration of the routing management and the authority management by configuring the routing annotation and the security annotation and carrying out the combination configuration of the routing annotation and the security annotation on the authority management based on the routing management, and solves the problem of the need of the repeated authentication of the user by the combination of the routing annotation and the security annotation.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and other drawings can be obtained by those skilled in the art without creative efforts.
Fig. 1 is a schematic flow chart of a rights management configuration method based on route management according to an embodiment of the present invention;
fig. 2 is a block diagram of a rights management configuration system based on route management according to an embodiment of the present invention;
fig. 3 is a block diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the 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 invention.
It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged under appropriate circumstances in order to facilitate the description of the embodiments of the invention herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
In the present invention, the terms "upper", "lower", "left", "right", "front", "rear", "top", "bottom", "inner", "outer", "center", "vertical", "horizontal", "lateral", "longitudinal", and the like indicate an orientation or positional relationship based on the orientation or positional relationship shown in the drawings. These terms are used primarily to better describe the invention and its embodiments and are not intended to limit the indicated systems, elements or components to a particular orientation or to be constructed and operated in a particular orientation.
Moreover, some of the above terms may be used to indicate other meanings besides the orientation or positional relationship, for example, the term "on" may also be used to indicate some kind of attachment or connection relationship in some cases. The specific meanings of these terms in the present invention can be understood by those skilled in the art as appropriate.
Furthermore, the terms "mounted," "disposed," "provided," "connected," and "sleeved" are to be construed broadly. For example, it may be a fixed connection, a removable connection, or a unitary construction; can be a mechanical connection, or an electrical connection; may be directly connected, or indirectly connected through intervening media, or may be in communication between two systems, components or parts. The specific meanings of the above terms in the present invention can be understood by those of ordinary skill in the art according to specific situations.
It should be noted that the embodiments and features of the embodiments may be combined with each other without conflict. The present invention will be described in detail below with reference to the embodiments with reference to the attached drawings.
The existing single sign-on scheme only provides a sign-on verification function, so that only information required by sign-on is configured, and configuration of authority management cannot be realized. In addition, in the prior art, each subsystem needs user authentication when logging in, each subsystem needs to consider the complicated logic of repeated authentication when designing, and the repeated authentication can also cause the reduction of user experience when in use.
In order to solve the foregoing problems, embodiments of the present invention provide a rights management configuration method based on route management, which completes configuration management of a route and rights by combining route and rights related configuration with RBAC (Role-based rights access control), that is, associates a menu and a resource in the route with a Role in the RBAC, and binds rights data on the menu and the resource to complete rights management of a user.
As shown in fig. 1, the method includes steps S101 to S103 as follows:
step S101: defining a routing annotation, and associating the routing annotation with an interface type, wherein the interface type comprises an open interface, a background management interface, a front-end App interface and a public interface; the defined routing annotations are shown in table 1:
TABLE 1
Specifically, the open interface is called by a java program at a server or a user outside a service center;
the background management interface is called from the background management interface through a browser so as to support service operation and system maintenance;
the front-end App interface is called by an application program running on the client terminal;
the public interface does not participate in the authority management and is directly released.
Step S102: defining security class annotations applicable to the open interface and the background management interface; the components required to define the security class annotations are shown in Table 2:
TABLE 2
Based on the above components, the defined security class annotations are shown in table 3:
TABLE 3
Specifically, the step S102 includes:
defining an authority role suitable for a background management interface;
defining authority operation suitable for a background management interface;
defining the scope of rights applicable to the open interface.
Furthermore, the authority role acts on the class, and the acting range is all methods under the class and is used for managing a specified page or a menu group;
the authority operation acts on the method and is used for describing the designated operation and managing the designated resources or function buttons;
the permission range acts on the class or method for verifying the access permission of the specified accesstken.
Step S103: configuring the right management based on the route management based on the combination of the route annotation and the security class annotation.
In one embodiment provided by the present invention, the route annotation and the security class annotation are marked on the method level of the interface to perform configuration of route management and rights management.
The method comprises the steps of marking a route annotation, wherein the route annotation can be used for carrying out route dynamic management and control and verifying user login information; the dynamic authority control can be realized by marking security class annotation, and the authority information of the user can be verified;
when the embodiment of the invention verifies the user login information and the user permission information, no code is required to be added, only the code is required to be added in an annotation form, and the route annotation and the security annotation are marked on the interface method level, so that the route management and control and the permission management and control can be simultaneously realized, and the intrusiveness to the system is small.
In an embodiment provided by the present invention, after configuring the rights management based on the route management in step S103, the method further includes:
accessing an external application system;
and configuring a UAA server and a gateway address for the external application system.
The embodiment of the invention integrates the internal system configured with the authority management based on the routing management, can provide service to access the external application system, takes the integrated internal system as authentication service, configures the relevant information of the internal system service end such as UAA server, gateway address and the like for the external application system, takes the internal system UAA as the authentication end to complete the access, and performs the configuration of the routing management and the authority management on the user information login, the session management and the authority management of the external application system through a UAA management interface.
In an embodiment provided by the present invention, after configuring the rights management based on the route management in step S103, the method further includes:
providing an accessed SDK based on the SpringBoot;
and configuring the UAA server and the gateway address into the SDK so as to carry out the configuration of route management and authority management through the UAA management interface.
The SDK which is quickly accessed is provided based on the Springboot, development is supported, the system can be quickly accessed with extremely low cost through a mode that a configuration file is annotated, login management, authority control and the like are achieved, and development efficiency and system stability are greatly improved.
After the configuration is completed, the application under the UAA platform collects the resource and menu based on the RBAC through the authority management; when accessing the resource, the route annotation defines the address of the resource mapping; the security class annotation judges whether the user has access authority; the method comprises the steps of performing routing annotation, defining a routing rule corresponding to a resource, wherein the routing rule comprises a url address and an http _ method of resource mapping, and accessing the corresponding resource for authority management; the security annotation is to construct the information into resource information, store the resource information in UAA application, authenticate, judge the access authority of the resource and verify whether the user can access the resource; the authority management of the user is completed by combining the RBAC, namely, the menu and the resource in the route are associated by the role in the RBAC, and the authority data on the menu and the resource are bound to complete the authority management of the user.
In addition, the route collector is used for collecting route information and synchronizing the route information to the gateway or the security core module for access authentication processing; if a gateway or a micro-service scene is introduced, calling link tracking is introduced to facilitate interface calling analysis, routing information in a cluster is dynamically analyzed by a corresponding adapter and automatically synchronized to the gateway, so that the real-time performance and consistency of routing are achieved.
From the above description, it can be seen that the present invention achieves the following technical effects:
the invention configures the route annotation and the security annotation, and performs combined configuration on the route annotation and the security annotation to configure the authority management based on the route management, thereby realizing the configuration of the route management and the authority management, and solving the problem of needing the repeated authentication of the user through the combination of the route annotation and the security annotation;
when the embodiment of the invention verifies the user login information and the user permission information, no code is required to be added, only the code is required to be added in an annotation form, and the route annotation and the security annotation are marked on the interface method level, so that the route management and control and the permission management and control can be simultaneously realized, and the intrusiveness to the system is small;
the invention provides the rapidly accessed SDK based on the SpringBoot, supports development with extremely low cost, can rapidly access the system by a mode of annotating the configuration file, realizes login management, authority control and the like, and greatly improves the development efficiency and the system stability.
It should be noted that the steps illustrated in the flowcharts of the figures may be performed in a computer system such as a set of computer-executable instructions and that, although a logical order is illustrated in the flowcharts, in some cases, the steps illustrated or described may be performed in an order different than presented herein.
An embodiment of the present invention further provides a rights management configuration system based on route management, for implementing the rights management configuration method based on route management, as shown in fig. 2, the system includes:
the first defining unit 21 is configured to define a route annotation and associate the route annotation with an interface type, where the interface type includes an open interface, a background management interface, a front-end App interface, and a public interface;
a second definition unit 22, configured to define security class annotations applicable to the open interface and the background management interface;
a combination unit 23, configured to configure rights management based on route management based on the combination of the route annotation and the security class annotation.
An embodiment of the present invention further provides an electronic device, as shown in fig. 3, the electronic device includes one or more processors 31 and a memory 32, where one processor 31 is taken as an example in fig. 3.
The controller may further include: an input device 33 and an output device 34.
The processor 31, the memory 32, the input device 33 and the output device 34 may be connected by a bus or other means, and fig. 3 illustrates the connection by a bus as an example.
The Processor 31 may be a Central Processing Unit (CPU), the Processor 31 may also be other general-purpose processors, Digital Signal Processors (DSP), Application Specific Integrated Circuits (ASIC), Field Programmable Gate Arrays (FPGA), other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components, or any combination thereof, and the general-purpose Processor may be a microprocessor or any conventional Processor.
The memory 32, which is a non-transitory computer readable storage medium, may be used for storing non-transitory software programs, non-transitory computer executable programs, and modules, such as program instructions/modules corresponding to the control method in the embodiments of the present invention. The processor 31 executes various functional applications of the server and data processing by running non-transitory software programs, instructions and modules stored in the memory 32, that is, implements the rights management configuration method based on route management of the above-described method embodiment.
The memory 32 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to use of a processing device operated by the server, and the like. Further, the memory 32 may include high speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, the memory 32 may optionally include memory located remotely from the processor 31, which may be connected to a network connection device via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The input device 33 may receive input numeric or character information and generate key signal inputs related to user settings and function control of the processing device of the server. The output device 34 may include a display device such as a display screen.
One or more modules are stored in the memory 32, which when executed by the one or more processors 31 perform the method as shown in fig. 1.
Those skilled in the art will appreciate that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium, and the processes of the embodiments of the motor control methods described above can be included when the computer program is executed. The storage medium may be a magnetic Disk, an optical Disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a Flash Memory (FM), a Hard Disk (Hard Disk Drive, HDD), or a Solid-State Drive (SSD); the storage medium may also comprise a combination of memories of the kind described above.
Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the invention, and such modifications and variations fall within the scope defined by the appended claims.
Claims (10)
1. A right management configuration method based on routing management is characterized by comprising the following steps:
defining a routing annotation, and associating the routing annotation with an interface type, wherein the interface type comprises an open interface, a background management interface, a front-end App interface and a public interface;
defining security class annotations applicable to the open interface and the background management interface;
configuring the right management based on the route management based on the combination of the route annotation and the security class annotation.
2. The method of claim 1, wherein the open interface is invoked by a user other than a server java program or a service center;
the background management interface is called from the background management interface through a browser so as to support service operation and system maintenance;
the front-end App interface is called by an application program running on the client terminal;
the public interface does not participate in the authority management and is directly released.
3. The method of claim 1, wherein defining security class annotations applicable to the open interface and the background management interface comprises:
defining an authority role suitable for a background management interface;
defining authority operation suitable for a background management interface;
defining the scope of rights applicable to the open interface.
4. The method of claim 3, wherein the authority role acts on a class, and the scope of action is all methods under the class, for managing a specified page or menu group;
the authority operation acts on the method and is used for describing the designated operation and managing the designated resources or function buttons;
the permission range acts on the class or method for verifying the access permission of the specified accesstken.
5. The method of claim 1, wherein the routing annotation and security class annotation are printed on a method level of the interface for configuration of routing management and rights management.
6. The method of claim 1, wherein after configuring routing management based rights management, the method further comprises:
accessing an external application system;
and configuring a UAA server and a gateway address for the external application system.
7. The method of claim 1, wherein after configuring routing management based rights management, the method further comprises:
providing an accessed SDK based on the SpringBoot;
and configuring the UAA server and the gateway address into the SDK so as to carry out the configuration of route management and authority management through the UAA management interface.
8. A rights management configuration system based on routing management, comprising:
the device comprises a first definition unit, a second definition unit and a third definition unit, wherein the first definition unit is used for defining a route annotation and associating the route annotation with an interface type, and the interface type comprises an open interface, a background management interface, a front-end App interface and a public interface;
the second definition unit is used for defining the security class annotation suitable for the open interface and the background management interface;
and the combination unit is used for configuring the authority management based on the routing annotation based on the combination of the routing annotation and the security class annotation.
9. A computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions for causing a computer to execute the method for configuring rights management based on routing management of any one of claims 1 to 7.
10. An electronic device, characterized in that the electronic device comprises: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores a computer program executable by the at least one processor, the computer program being executable by the at least one processor to cause the at least one processor to perform the method of routing management based rights management configuration of any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111154424.XA CN113922999A (en) | 2021-09-29 | 2021-09-29 | Authority management configuration method and system based on routing management and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111154424.XA CN113922999A (en) | 2021-09-29 | 2021-09-29 | Authority management configuration method and system based on routing management and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113922999A true CN113922999A (en) | 2022-01-11 |
Family
ID=79237013
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111154424.XA Pending CN113922999A (en) | 2021-09-29 | 2021-09-29 | Authority management configuration method and system based on routing management and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113922999A (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102932431A (en) * | 2012-10-12 | 2013-02-13 | 宁夏电力公司电力科学研究院 | Message-routing-based state monitoring data interface configuration method |
| CN108196837A (en) * | 2017-12-25 | 2018-06-22 | 国云科技股份有限公司 | A kind of system authority control method |
| CN111752644A (en) * | 2020-06-18 | 2020-10-09 | 北京字节跳动网络技术有限公司 | Interface simulation method, device, equipment and storage medium |
| CN112395575A (en) * | 2020-12-08 | 2021-02-23 | 深圳前海微众银行股份有限公司 | Authority management method, device, equipment and storage medium |
| CN112769706A (en) * | 2020-12-24 | 2021-05-07 | 平安银行股份有限公司 | Componentized routing method and system |
| US20210208917A1 (en) * | 2020-01-06 | 2021-07-08 | International Business Machines Corporation | Network performance optimization in a hypervisor-based system |
-
2021
- 2021-09-29 CN CN202111154424.XA patent/CN113922999A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102932431A (en) * | 2012-10-12 | 2013-02-13 | 宁夏电力公司电力科学研究院 | Message-routing-based state monitoring data interface configuration method |
| CN108196837A (en) * | 2017-12-25 | 2018-06-22 | 国云科技股份有限公司 | A kind of system authority control method |
| US20210208917A1 (en) * | 2020-01-06 | 2021-07-08 | International Business Machines Corporation | Network performance optimization in a hypervisor-based system |
| CN111752644A (en) * | 2020-06-18 | 2020-10-09 | 北京字节跳动网络技术有限公司 | Interface simulation method, device, equipment and storage medium |
| CN112395575A (en) * | 2020-12-08 | 2021-02-23 | 深圳前海微众银行股份有限公司 | Authority management method, device, equipment and storage medium |
| CN112769706A (en) * | 2020-12-24 | 2021-05-07 | 平安银行股份有限公司 | Componentized routing method and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109314704B (en) | Single sign-on and single sign-off functions for multi-tenant identity and data security management cloud services | |
| CN102447677B (en) | Resource access control method, system and equipment | |
| CN102857484B (en) | A kind of method, system and device realizing single-sign-on | |
| US8850550B2 (en) | Using cached security tokens in an online service | |
| EP3694175B1 (en) | System and method for delegating authority through coupled devices | |
| CN109635550B (en) | Permission verification method, gateway and system for cluster data | |
| CN105450636A (en) | Cloud computing management system and management method of cloud computing management system | |
| US20150026236A1 (en) | Common Interface Communicating with Multiple Back-End Services via Gateway Application | |
| CN113015165A (en) | Internet of things platform device access method, device and system | |
| US20140019957A1 (en) | Method, apparatus, and system for sharing software among terminals | |
| CN114025021A (en) | Communication method, system, medium and electronic device across Kubernetes cluster | |
| CN105871822A (en) | B/C/S blending mode based single sign-on system development model | |
| CN102710559B (en) | A kind of reversed proxy server realizes the method for Digital Document Resource gateway | |
| CN110034979A (en) | A kind of proxy resources monitoring method, device, electronic equipment and storage medium | |
| US8949930B1 (en) | Template representation of security resources | |
| CN102420808A (en) | Method for realizing single signon on telecom on-line business hall | |
| CN113901429A (en) | Access method and device of multi-tenant system | |
| WO2023213262A1 (en) | Mesh sidecar expansion method and device | |
| CN101527646B (en) | System and method for WEB network management | |
| CN113922999A (en) | Authority management configuration method and system based on routing management and electronic equipment | |
| CN106209746B (en) | Security service providing method and server | |
| CN106302479A (en) | A kind of single-point logging method for multi-service internet site and system | |
| CN109714397A (en) | Internet proxy server management system | |
| CN109218329A (en) | A kind of method and system authenticated using NetData-Auth user authentication frame | |
| CN115189897A (en) | Access processing method and device for zero trust network, electronic equipment and storage medium |
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 |