CN111125676B - Joint authorization method and device - Google Patents
Joint authorization method and device Download PDFInfo
- Publication number
- CN111125676B CN111125676B CN201911334179.3A CN201911334179A CN111125676B CN 111125676 B CN111125676 B CN 111125676B CN 201911334179 A CN201911334179 A CN 201911334179A CN 111125676 B CN111125676 B CN 111125676B
- Authority
- CN
- China
- Prior art keywords
- authorization
- product
- joint
- authorization request
- products
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/44—Program or device authentication
Abstract
The embodiment of the application discloses a joint authorization method and a joint authorization device. One embodiment of the method comprises: in response to detecting that a user performs a joint authorization operation on a first product, sending joint authorization requests to a preset number of second products in a second product set so that the joint authorization requests are serially processed and transmitted inside the second product set, wherein the first product runtime provides a target service by calling the second product set; and displaying the authorization success message in response to receiving the authorization success messages sent by the preset number of second products in the second product set. This embodiment simplifies the authorization operation for the user.
Description
Technical Field
The embodiment of the application relates to the technical field of computers, in particular to a joint authorization method and a joint authorization device.
Background
In the internet environment, more and more products need to invoke multiple other products when running. These products require multiple other products that the user invokes to authorize one by one.
Currently, a user typically authorizes a plurality of other products for product invocation by popping up boxes one by one to prompt the user to click on authorization. For example, product X needs to invoke product A, B, C when running, then the user needs to authorize products A, B, C one by one. Specifically, before the user starts using product X, the user is prompted on product X to authorize product a first; after the user authorizes the product A successfully, prompting the user to authorize the product B on the product X; after the user authorizes the product B successfully, prompting the user to authorize the product C on the product X; the user may formally use the target service provided by product X after the products A, B, C are authorized successfully. If the user refuses to authorize any of the products A, B, C, or if the authorization fails for any of the products A, B, C, the user cannot normally use the target service provided by product X.
Disclosure of Invention
The embodiment of the application provides a joint authorization method and a joint authorization device.
In a first aspect, an embodiment of the present application provides a joint authorization method, including: in response to detecting that a user performs a joint authorization operation on a first product, sending joint authorization requests to a preset number of second products in a second product set so that the joint authorization requests are serially processed and transmitted inside the second product set, wherein the first product runtime provides a target service by calling the second product set; and displaying the authorization success message in response to receiving the authorization success messages sent by the preset number of second products in the second product set.
In some embodiments, in response to detecting that the user performed a joint authorization operation on the first product, sending a joint authorization request to a preset number of second products in the second set of products, comprises: displaying a joint authorization page on a first product in response to detecting that a user executes a login operation of the first product; and sending a joint authorization request to a preset number of second products in the second product set in response to detecting that the user performs the joint authorization operation on the joint authorization page.
In some embodiments, sending the joint authorization request to a preset number of second products in the second set of products includes: obtaining an authorization sequence of the second product set; the authorization order is added to the federated authorization request, and the federated authorization request is sent to the second product ordered first in the authorization order, such that the federated authorization request is processed and communicated serially within the second set of products in the authorization order.
In some embodiments, in response to receiving the authorization success message sent by the preset number of second products in the second product set, presenting the authorization success message includes: and displaying the authorization success message in response to receiving the authorization success message sent by the second product which is sequenced at the last position in the authorization sequence.
In some embodiments, the method further comprises: and displaying the authorization failure message in response to receiving the authorization failure message sent by one second product in the second product sequence.
In a second aspect, an embodiment of the present application provides a joint authorization method, including: in response to receiving the joint authorization request, processing the joint authorization request, wherein the joint authorization request is sent by the user on the first product or serially passed by one second product in the second product set, and the first product runtime provides the target service by calling the second product set; if the authorization is successful, determining whether a second product which does not process the joint authorization request exists in the second product set; if there is a second product that has not yet processed the joint authorization request, the joint authorization request is passed to one of the second set of products that has not yet processed the joint authorization request, such that the joint authorization request is serially processed and passed within the second set of products.
In some embodiments, determining whether there is a second product in the second set of products that has not processed the joint authorization request comprises: obtaining an authorization sequence of the second product set from the joint authorization request; determining a ranking of the current second product in the authorization order; if the current second product is ranked at the last position, determining that no second product which has not processed the joint authorization request exists; if the current second product is not ranked at the last, determining that there is a second product that has not processed the joint authorization request.
In some embodiments, communicating the federated authorization request to one of the second set of products that has not processed the federated authorization request comprises: the joint authorization request is passed to a second product that is ordered next in the authorization order to the current second product such that the joint authorization request is processed and passed serially within the second set of products in the authorization order.
In some embodiments, processing a federated authorization request includes: and verifying the joint authorization request, analyzing the authorization parameters and generating authorization information.
In some embodiments, before passing the joint authorization request to the second product of the one of the second set of products that has not processed the joint authorization request, further comprising: authorization information is added to the joint authorization request.
In some embodiments, communicating the joint authorization request to a second product of the second product set that has not yet processed the joint authorization request includes: the joint authorization request is passed through the authorization callback interface to a second product of the second set of products that has not yet processed the joint authorization request.
In some embodiments, the method further comprises: and if the second product which does not process the joint authorization request does not exist, sending an authorization success message to the user.
In some embodiments, the method further comprises: and if the authorization fails, sending an authorization failure message to the user.
In a third aspect, an embodiment of the present application provides a joint authorization apparatus, including: a sending unit, configured to respond to the detection that the user performs the joint authorization operation on the first product, send joint authorization requests to a preset number of second products in the second product set, so that the joint authorization requests are serially processed and transmitted in the second product set, wherein the first product runtime provides the target service by calling the second product set; the first display unit is configured to display the authorization success message in response to receiving the authorization success message sent by the preset number of second products in the second product set.
In some embodiments, the sending unit is further configured to: displaying a joint authorization page on a first product in response to detecting that a user executes a login operation of the first product; and sending a joint authorization request to a preset number of second products in the second product set in response to detecting that the user performs the joint authorization operation on the joint authorization page.
In some embodiments, the sending unit is further configured to: obtaining an authorization sequence of the second product set; the authorization order is added to the federated authorization request, and the federated authorization request is sent to the second product ordered first in the authorization order, such that the federated authorization request is processed and communicated serially within the second set of products in the authorization order.
In some embodiments, the first presentation unit is further configured to: and displaying the authorization success message in response to receiving the authorization success message sent by the second product which is sequenced at the last position in the authorization sequence.
In some embodiments, the apparatus further comprises: and the second display unit is configured to display the authorization failure message in response to receiving the authorization failure message sent by one second product in the second product sequence.
In a fourth aspect, an embodiment of the present application provides a joint authorization apparatus, including: a processing unit configured to process a joint authorization request in response to receiving the joint authorization request, wherein the joint authorization request is transmitted by a user on a first product or serially passed by a second product in a second product set, and the first product runtime provides a target service by calling the second product set; a determining unit configured to determine whether there is a second product in the second product set that has not processed the joint authorization request if the authorization is successful; and the transmission unit is configured to transmit the joint authorization request to one second product which does not process the joint authorization request in the second product set if the second product which does not process the joint authorization request exists, so that the joint authorization request is processed and transmitted in series in the second product set.
In some embodiments, the determining unit is further configured to: obtaining an authorization sequence of the second product set from the joint authorization request; determining a ranking of the current second product in the authorization order; if the current second product is ranked at the last position, determining that no second product which has not processed the joint authorization request exists; if the current second product is not ranked at the last, determining that there is a second product that has not processed the joint authorization request.
In some embodiments, the transfer unit is further configured to: the joint authorization request is passed to a second product that is ordered next in the authorization order to the current second product such that the joint authorization request is processed and passed serially within the second set of products in the authorization order.
In some embodiments, the processing unit is further configured to: and verifying the joint authorization request, analyzing the authorization parameters and generating authorization information.
In some embodiments, the apparatus further comprises: an adding unit configured to add the authorization information to the joint authorization request.
In some embodiments, the transfer unit is further configured to: the joint authorization request is passed through the authorization callback interface to a second product of the second set of products that has not yet processed the joint authorization request.
In some embodiments, the apparatus further comprises: and the first sending unit is configured to send an authorization success message to the user if the second product which does not process the joint authorization request does not exist.
In some embodiments, the apparatus further comprises: and the second sending unit is configured to send an authorization failure message to the user if the authorization fails.
In a fifth aspect, an embodiment of the present application provides an electronic device, including: one or more processors; a storage device having one or more programs stored thereon; when executed by one or more processors, cause the one or more processors to implement a method as described in any implementation of the first aspect or to implement a method as described in any implementation of the second aspect.
In a sixth aspect, the present application provides a computer readable medium, on which a computer program is stored, wherein the computer program, when executed by a processor, implements the method as described in any implementation manner of the first aspect or implements the method as described in any implementation manner of the second aspect.
According to the joint authorization method and the joint authorization device, under the condition that a user is detected to execute joint authorization operation on a first product, joint authorization requests are sent to a preset number of second products in a second product set, so that the joint authorization requests are serially processed and transmitted in the second product set; and displaying the authorization success message under the condition of receiving the authorization success messages sent by the preset number of second products in the second product set. The user only needs to execute one authorization operation, and the combined authorization request can be serially processed and transmitted in the second product set so as to complete the authorization of all the second products called by the first product operation, thereby simplifying the authorization operation of the user, saving the operation cost of the user and improving the user experience.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, made with reference to the accompanying drawings in which:
FIG. 1 is an exemplary system architecture to which the present application may be applied;
FIG. 2 is a flow diagram of one embodiment of a joint authorization method according to the present application;
FIG. 3 is a flow diagram of yet another embodiment of a joint authorization method according to the present application;
FIG. 4 is a flow diagram of another embodiment of a joint authorization method according to the present application;
FIG. 5 is a flow diagram of yet another embodiment of a joint authorization method according to the present application;
FIG. 6 is a schematic diagram of an application scenario of a joint authorization method according to the present application;
FIG. 7 is a schematic diagram of an embodiment of a joint authorization apparatus according to the application;
FIG. 8 is a schematic diagram of the structure of yet another embodiment of a co-authorization device according to the application;
FIG. 9 is a block diagram of a computer system suitable for use in implementing the electronic device of an embodiment of the present application.
Detailed Description
The present application will be described in further detail with reference to the following drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not to be construed as limiting the invention. It should be noted that, for convenience of description, only the portions related to the related invention are shown in the drawings.
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.
Fig. 1 shows an exemplary system architecture 100 to which embodiments of the joint authorization method or joint authorization apparatus of the present application may be applied.
As shown in fig. 1, system architecture 100 may include devices 101, 102, 103, 104, 105 and network 106. Network 106 is the medium used to provide communication links between devices 101, 102, 103, 104, 105. Network 106 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
The devices 101, 102, 103, 104, 105 may be hardware devices or software that support network connectivity to provide various network services. When the device is hardware, it can be a variety of electronic devices including, but not limited to, smart phones, tablets, laptop portable computers, desktop computers, servers, and the like. In this case, the hardware device may be implemented as a distributed device group including a plurality of devices, or may be implemented as a single device. When the device is software, the software can be installed in the electronic devices listed above. At this time, as software, it may be implemented as a plurality of software or software modules for providing a distributed service, for example, or as a single software or software module. And is not particularly limited herein.
In practice, a device may provide a respective network service by installing a respective client application or server application. After the device has installed the client application, it may be embodied as a client in network communications. Accordingly, after the server application is installed, it may be embodied as a server in network communications.
As an example, in fig. 1, device 101 is embodied as a client, while devices 102, 103, 104, 105 are embodied as servers. For example, the device 101 may be a client installed with an applet platform, the device 102 may be a server of the applet platform, and the devices 103, 104, 105 may be servers of other products called by the applet platform when running.
It should be noted that the joint authorization method provided in the embodiment of the present application may be executed by the device 101, and may also be executed by the devices 103, 104, and 105.
It should be understood that the number of networks and devices in fig. 1 is merely illustrative. There may be any number of networks and devices, as desired for implementation.
With continued reference to FIG. 2, a flow 200 of one embodiment of a joint authorization method according to the present application is shown. The joint authorization method comprises the following steps:
In this embodiment, in the case that it is detected that the user performs the joint authorization operation on the first product, the terminal device (e.g., the device 101 shown in fig. 1) on which the joint authorization method operates may send joint authorization requests to a preset number of second products in the second product set, so that the joint authorization requests are serially processed and transmitted within the second product set. Wherein the preset number may be any number not greater than the number of products in the second set of products. While a predetermined number of serial processing and delivery processes may exist within the second product set.
Here, a product may be an Application (App), or may be one or more functional components in an Application. Generally, one or more services may be provided while a product is operating normally. The terminal device can be provided with a first product, and a user of the first product can log in the first product by using an account number and a password of the user. The first product runtime requires the target service to be provided by invoking the second set of products. Wherein the target service may be a specific service or services. For example, the first product may be an applet platform, and if it is required to provide cloud development services, the applet platform needs to call a plurality of second products such as a Cloud Function (CFC), a cloud storage (BOS), and a cloud database (MongoDB) when running.
In some optional implementations of the embodiment, in response to detecting that the user performs the login operation of the first product, the terminal device may send a joint authorization request to a preset number of second products in the second product set. Here, the login operation of the first product is a joint authorization operation.
In some optional implementations of this embodiment, in response to detecting that the user performs a login operation of the first product, the terminal device may display a joint authorization page on the first product; in response to detecting that the user performs the joint authorization operation on the joint authorization page, the terminal device may send joint authorization requests to a preset number of second products in the second product set. The joint authorization page can be a homepage of a first product displayed after login, and can also be an authorization prompt page popped up after login.
Typically, after the user logs on to the first product, a joint authorization page may be presented on the terminal device. Wherein the joint authorization page may be used to prompt the user to authorize the second set of products invoked at the runtime of the first product. Specifically, an authorization key may be disposed on the joint authorization page. When the user clicks the authorization button, the user may be considered to have performed a joint authorization operation. In addition, the name of the second product in the second product set can be displayed on the joint authorization page, so that the user can determine the product authorized by the operation.
In general, upon detecting the joint authorization operation, the terminal device may communicate a joint authorization request to a preset number of second products in the second set of products. The specific implementation manner of the joint authorization request may be REST (embodied as nested concatenation of URLs) or a nested request of RPCs, and the like. The joint authorization request may include user information such as a user account, a user signature, and a user role. The terminal device may determine a preset number of second products from the second set of products and send a joint authorization request to the determined second products. Then, for each second product receiving the joint authorization request, the second product can process the joint authorization request, perform authorization processing, and after authorization is successful, serially transmit the joint authorization request in the second product set until all the second products in the second product set complete processing of the joint authorization request.
It should be noted that each second product in the second product set will only deliver the joint authorization request when authorization is successful. If there is a second product authorization failure, the delivery of the joint authorization request is stopped.
In this embodiment, the terminal device may display the authorization success message when receiving the authorization success messages sent by the preset number of second products in the second product set.
Typically, joint authorization is only completed if all second products in the second set of products are successfully authorized. Thus, for each serial processing and delivery process, the last successfully authorized second product in the process will send an authorization success message to the terminal device. If a preset number of successful authorization messages are received, the terminal device will display the successful authorization messages to prompt the user that the first product can normally operate to provide the target service.
In the joint authorization method provided by the embodiment of the application, under the condition that a user is detected to execute joint authorization operation on a first product, joint authorization requests are sent to a preset number of second products in a second product set, so that the joint authorization requests are serially processed and transmitted in the second product set; and displaying the authorization success message under the condition of receiving the authorization success messages sent by the preset number of second products in the second product set. The user only needs to execute one authorization operation, and the combined authorization request can be serially processed and transmitted in the second product set to complete the authorization of all the second products called by the first product operation, so that the authorization operation of the user is simplified, the operation cost of the user is saved, and the user experience is improved.
With further reference to FIG. 3, a flow 300 of yet another embodiment of a joint authorization method according to the present application is shown. The joint authorization method comprises the following steps:
in step 301, in response to detecting that the user performs the joint authorization operation on the first product, the authorization order of the second set of products is obtained.
In this embodiment, in the case that it is detected that the user performs the joint authorization operation on the first product, the terminal device (for example, the device 101 shown in fig. 1) on which the joint authorization method operates may acquire the authorization order of the second product set.
In general, the second product set may include a plurality of second products, which may be in a pre-agreed order. The predetermined sequence can be any sequence, and the second product sequence in any sequence is suitable for the embodiment. For example, the first product run depends on the second product A, B, C, and the predetermined order may be { product A, product B, product C }, or { product C, product B, product A }.
In this embodiment, the terminal device may add the authorization order to the joint authorization request, and send the joint authorization request to the second product ordered at the first position in the authorization order, so that the joint authorization request is processed and transmitted serially within the second product set according to the authorization order.
Specifically, the terminal device may determine the second products ranked at the first place according to the authorization sequence, and send the joint authorization request to the second products ranked at the first place. Then, the second product ordered at the first position can process the joint authorization request, perform authorization processing, after authorization is successful, determine the product ordered at the next position (second position) according to the authorization sequence, and transmit the joint authorization request to the product ordered at the next position, so that the product ordered at the next position processes the joint authorization request, perform authorization processing, and after authorization is successful, continue to transmit the joint authorization request in series in the second product set according to the authorization sequence until the second product ordered at the last position in the second product set finishes processing the joint authorization request.
It should be noted that each second product in the second product set will deliver the joint authorization request to the next product in the second product set when authorization is successful. And if a second product authorization failure exists, stopping transmitting the joint authorization request downwards.
In this embodiment, in the case of receiving the authorization success message sent by the second product ordered in the last order in the authorization order, the terminal device may present the authorization success message.
Generally, in case all second products in the second set of products are successfully authorized, the second product ordered last will send an authorization success message to the terminal device. At this point, the terminal device may present an authorization success message to prompt the user that the first product is operable to provide the target service.
In this embodiment, in the case of receiving an authorization failure message sent by one second product in the second product sequence, the terminal device may display the authorization failure message.
In general, any one of the second products in the second set of products may send an authorization failure message to the terminal device after the authorization fails. At this time, the terminal device may display an authorization failure message to prompt the user that the first product cannot provide the target service.
As can be seen from fig. 3, compared with the corresponding embodiment of fig. 2, the flow 300 of the joint authorization method in this embodiment highlights the step of delivering the joint authorization request based on the authorization order. Therefore, the scheme described in the embodiment transfers the joint authorization request based on the authorization sequence, and realizes that the joint authorization request is quickly and serially transferred in the second product sequence.
With further reference to FIG. 4, a flow 400 of another embodiment of a joint authorization method according to the present application is shown. The joint authorization method comprises the following steps:
In this embodiment, in the case of receiving the joint authorization request, the server (for example, the devices 103, 104, and 105 shown in fig. 1) on which the joint authorization method operates may process the joint authorization request, and perform authorization processing.
Here, a product may be an application, and may also be one or more functional components in an application. Generally, one or more services may be provided while a product is operating normally. A terminal device (e.g., device 101 shown in fig. 1) may have a first product installed thereon, and a user of the first product may log in to the first product using his account number and password. The first product runtime requires the target service to be provided by invoking the second set of products. Wherein the target service may be a specific service or services. For example, the first product may be an applet platform, and if it is required to provide a cloud development service, the applet platform needs to call a plurality of second products such as a cloud function, a cloud storage, and a cloud database when running.
In general, upon detecting the joint authorization operation, the terminal device may communicate a joint authorization request to a preset number of second products in the second set of products. The specific implementation manner of the joint authorization request may be a nested request of REST or RPC, and the like. The joint authorization request may include user information such as a user account, a user signature, and a user role. The terminal device may determine a preset number of second products from the second set of products and send a joint authorization request to the determined second products. Then, for each second product that receives the joint authorization request, the second product may process the joint authorization request, perform authorization processing, and after authorization is successful, transmit the joint authorization request to another second product in the second product set, so that the second product processes the joint authorization request, performs authorization processing, and after authorization is successful, continue to serially transmit the joint authorization request in the second product set until all second products in the second product set have processed the joint authorization request. Wherein the preset number may be any number not greater than the number of products in the second set of products. While a preset number of serial processing and delivery processes may exist within the second product set.
Here, the joint authorization request may be sent by the user on the first product or communicated serially with one of the second products in the second set of products. Typically, if the server is the first second product in the second product set to process the joint authorization request, then the authorization request is sent by the user on the first product; otherwise, the joint authorization request is communicated serially with a second product in the second set of products.
In some optional implementation manners of this embodiment, the server may verify the joint authorization request, analyze the authorization parameter, and generate the authorization information. The joint authorization request may include user information such as a user account, a user signature, and a user role. Here, the server verifies the user information in the joint authorization request to determine whether the user has the right to use the second product. If the user has the right to use the second product, the Identification (ID) of the specific service of the second product called when the first product is operated is analyzed, so that the user is granted the right to call the second product when the first product is operated.
If the authorization is successful, step 402 determines whether a second product exists in the second product set that has not yet processed the joint authorization request.
In this embodiment, if the authorization is successful, the server may determine whether there is a second product in the second product set that has not processed the joint authorization request. If there is a second product that has not yet processed the federated authorization request, execution continues to step 403.
In step 403, if there is a second product that has not processed the joint authorization request, the joint authorization request is transmitted to a second product that has not processed the joint authorization request in the second product set, so that the joint authorization request is processed and transmitted serially within the second product set.
In this embodiment, if there is a second product that has not processed the joint authorization request, the server may transmit the joint authorization request to a second product in the second product set that has not processed the joint authorization request, so that the joint authorization request is processed and transmitted serially within the second product set.
Generally, a second product that has not processed the joint authorization request can process the joint authorization request, perform authorization processing, and after successful authorization, continue to serially pass the joint authorization request through the second product set until all second products in the second product set have processed the joint authorization request.
It should be noted that each second product in the second product set will only deliver the joint authorization request when authorization is successful. If there is a second product authorization failure, the delivery of the joint authorization request is stopped.
In some optional implementation manners of this embodiment, the server may verify the joint authorization request, analyze the authorization parameter, and generate the authorization information. The server may then add the authorization information to the federated authorization request and continue the federated authorization request with the added authorization information serially in the second product set.
In some optional implementations of the embodiment, the server may pass the joint authorization request to one of the second product sets that has not processed the joint authorization request through the authorization callback interface. Specifically, an authorization callback interface is implemented inside each second product in the second product set, and joint authorization requests of all second products in the second product set can be concatenated through the authorization callback interface.
The joint authorization method provided by the embodiment of the application processes the joint authorization request under the condition of receiving the joint authorization request; in the case of successful authorization, determining whether a second product exists in the second product set that has not yet processed the joint authorization request; in the case where there is a second product that has not yet processed the joint authorization request, the joint authorization request is passed to one of the second set of products that has not yet processed the joint authorization request such that the joint authorization request is processed and passed serially within the second set of products. The user only needs to execute one authorization operation, and the combined authorization request can be serially processed and transmitted in the second product set so as to complete the authorization of all the second products called by the first product operation, thereby simplifying the authorization operation of the user, saving the operation cost of the user and improving the user experience.
With further reference to FIG. 5, a flow 500 of yet another embodiment of a joint authorization method according to the present application is shown. The joint authorization method comprises the following steps:
In this embodiment, the specific operation of step 501 has been described in detail in step 401 in the embodiment shown in fig. 4, and is not described herein again.
In this embodiment, if the authorization is successful, the server (e.g., the devices 103, 104, 105 shown in fig. 1) may obtain the authorization order of the second product set from the joint authorization request. Wherein the joint authorization request may include an authorization order for the second set of products.
In general, the second product set may include a plurality of second products, which may be in a pre-agreed order. The predetermined sequence can be any sequence, and the second product sequence in any sequence is suitable for the embodiment. For example, the first product run depends on the second product A, B, C, and the predetermined order may be { product A, product B, product C }, or { product C, product B, product A }.
At step 503, the current second product's rank in the authorization order is determined.
In this embodiment, the server may determine the ordering of the current two products in the authorization order. If the current second product is not sorted in the last order, go to step 504; if the current second product is ranked at the last position, go to step 505.
In this embodiment, if the current second product is not ranked last, the server may determine that there is a second product that has not processed the joint authorization request. At this point, the server may pass the joint authorization request to the second product ordered next in the authorization order to the current second product, such that the joint authorization request is processed and passed serially within the second set of products in the authorization order.
Specifically, the server may determine the second product ordered next in the authorization order and send the joint authorization request to the second product ordered next in the authorization order. Then, the second product ordered next to the second product can process the joint authorization request, perform authorization processing, and after authorization is successful, continue to serially transfer the joint authorization request in the second product set until the second product ordered last in the second product set finishes processing the joint authorization request.
It should be noted that each second product in the second product set will only pass the joint authorization request to the next product in the product set when authorization is successful. And if a second product authorization failure exists, stopping transmitting the joint authorization request downwards.
In this embodiment, if the current second product is ranked at the last, the server may determine that there is no second product that has not processed the joint authorization request. At this time, the server may send an authorization success message to the user.
Generally, in case all second products in the second set of products are successfully authorized, the second product ordered last will send an authorization success message to the terminal device. At this point, the terminal device may present an authorization success message to prompt the user that the first product is operable to provide the target service.
In this embodiment, if the authorization fails, the server may send an authorization failure message to the user.
In general, any one of the second products in the second set of products may send an authorization failure message to the terminal device after the authorization fails. At this time, the terminal device may display an authorization failure message to prompt the user that the first product cannot provide the target service.
As can be seen from fig. 5, compared with the corresponding embodiment of fig. 4, the flow 500 of the joint authorization method in this embodiment highlights the steps of delivering the joint authorization request based on the authorization order. Therefore, the scheme described in the embodiment transfers the joint authorization request based on the authorization sequence, and realizes that the joint authorization request is quickly and serially transferred in the second product sequence.
With continued reference to FIG. 6, a schematic diagram of one application scenario of the joint authorization method according to the present application is shown. As shown in FIG. 6, product X runtime requires product A, B, C to be invoked to provide the target service. The user logs in the product X by using the mobile phone. Subsequently, a joint authorization page is presented on product X. And the user clicks an authorization key on the joint authorization page to send a joint authorization request to the product A. And the product A verifies the joint authorization request and carries out authorization processing. If the authorization fails, an authorization failure message is sent to the user, and if the authorization succeeds, a joint authorization request is transmitted to the product B. And the product B verifies the joint authorization request and carries out authorization processing. If the authorization fails, an authorization failure message is sent to the user, and if the authorization succeeds, a joint authorization request is transmitted to the product C. And the product C verifies the joint authorization request and carries out authorization processing. If the authorization fails, an authorization failure message is sent to the user, and if the authorization succeeds, an authorization success message is sent to the user A.
With further reference to fig. 7, as an implementation of the methods shown in the above-mentioned figures, the present application provides an embodiment of a joint authorization apparatus, which corresponds to the embodiment of the method shown in fig. 2, and which can be applied in various electronic devices.
As shown in fig. 7, the joint authorization apparatus 700 of the present embodiment may include: a sending unit 701 and a first presentation unit 702. The sending unit 701 is configured to send joint authorization requests to a preset number of second products in a second product set in response to detecting that a user performs joint authorization operation on a first product, so that the joint authorization requests are serially processed and transmitted inside the second product set, wherein the first product runtime provides services by calling the second product set; the first presentation unit 702 is configured to present an authorization success message in response to receiving an authorization success message sent by a preset number of second products in the second product set.
In this embodiment, the joint authorization apparatus 700: the specific processing of the sending unit 701 and the first displaying unit 702 and the technical effects thereof can be referred to the related description of step 201 and 202 in the corresponding embodiment of fig. 2, and are not repeated herein.
In some optional implementations of this embodiment, the sending unit 701 is further configured to: displaying a joint authorization page on a first product in response to detecting that a user executes a login operation of the first product; and sending a joint authorization request to a preset number of second products in the second product set in response to detecting that the user performs the joint authorization operation on the joint authorization page.
In some optional implementations of this embodiment, the sending unit 701 is further configured to: obtaining an authorization sequence of the second product set; the authorization order is added to the federated authorization request, and the federated authorization request is sent to the second product ordered first in the authorization order, such that the federated authorization request is processed and communicated serially within the second set of products in the authorization order.
In some optional implementations of this embodiment, the first presentation unit 702 is further configured to: and displaying the authorization success message in response to receiving the authorization success message sent by the second product which is sequenced at the last position in the authorization sequence.
In some optional implementations of this embodiment, the joint authorization apparatus 700 further includes: and a second presentation unit (not shown in the figure) configured to present the authorization failure message in response to receiving the authorization failure message sent by one of the second products in the second product sequence.
With further reference to fig. 8, as an implementation of the methods shown in the above-mentioned figures, the present application provides an embodiment of a joint authorization apparatus, which corresponds to the method embodiment shown in fig. 4, and which can be applied in various electronic devices.
As shown in fig. 8, the joint authorization apparatus 800 of the present embodiment may include: a processing unit 801, a determination unit 802, and a transfer unit 803. Wherein the processing unit 801 is configured to process the joint authorization request in response to receiving the joint authorization request, wherein the joint authorization request is serially passed by one second product of the first product or the second product set sent by the user, and wherein the first product runtime provides the service by calling the second product set; a determining unit 802 configured to determine whether there is a second product in the second product set that has not processed the joint authorization request if the authorization is successful; the delivery unit 803 is configured to deliver the joint authorization request to a second product in the second product set that has not processed the joint authorization request, if there is a second product that has not processed the joint authorization request, so that the joint authorization request is processed and delivered serially within the second product set.
In the present embodiment, in the joint authorization apparatus 800: the detailed processing of the processing unit 801, the determining unit 802, and the transferring unit 803 and the technical effects thereof can be referred to the related descriptions of steps 401 and 403 in the corresponding embodiment of fig. 4, and are not repeated herein.
In some optional implementations of the present embodiment, the determining unit 802 is further configured to: obtaining an authorization sequence of the second product set from the joint authorization request; determining a ranking of the current second product in the authorization order; if the current second product is ranked at the last position, determining that no second product which has not processed the joint authorization request exists; if the current second product is not ranked at the last, determining that there is a second product that has not processed the joint authorization request.
In some optional implementations of this embodiment, the transferring unit 803 is further configured to: the joint authorization request is passed to a second product that is ordered next in the authorization order to the current second product such that the joint authorization request is processed and passed serially within the second set of products in the authorization order.
In some optional implementations of this embodiment, the processing unit 801 is further configured to: and verifying the joint authorization request, analyzing the authorization parameters and generating authorization information.
In some optional implementations of this embodiment, the joint authorization apparatus 800 further includes: an adding unit (not shown in the figure) configured to add the authorization information to the joint authorization request.
In some optional implementations of this embodiment, the transferring unit 803 is further configured to: the joint authorization request is passed through the authorization callback interface to a second product of the second set of products that has not yet processed the joint authorization request.
In some optional implementations of this embodiment, the joint authorization apparatus 800 further includes: a first sending unit (not shown in the figure) configured to send an authorization success message to the user if there is no second product that has not processed the joint authorization request.
In some optional implementations of this embodiment, the joint authorization apparatus 800 further includes: and a second sending unit (not shown in the figure) configured to send an authorization failure message to the user if the authorization fails.
Referring now to FIG. 9, a block diagram of a computer system 900 suitable for implementing an electronic device (e.g., the terminal device 101 or the servers 103, 104, 105 shown in FIG. 1) of an embodiment of the present application is shown. The electronic device shown in fig. 9 is only an example, and should not bring any limitation to the functions and the use range of the embodiment of the present application.
As shown in fig. 9, the computer system 900 includes a Central Processing Unit (CPU)901 that can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)902 or a program loaded from a storage section 908 into a Random Access Memory (RAM) 903. In the RAM 903, various programs and data necessary for the operation of the system 900 are also stored. The CPU 901, ROM 902, and RAM 903 are connected to each other via a bus 904. An input/output (I/O) interface 905 is also connected to bus 904.
The following components are connected to the I/O interface 905: an input portion 906 including a keyboard, a mouse, and the like; an output section 907 including components such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 908 including a hard disk and the like; and a communication section 909 including a network interface card such as a LAN card, a modem, or the like. The communication section 909 performs communication processing via a network such as the internet. The drive 910 is also connected to the I/O interface 905 as necessary. A removable medium 911 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 910 as necessary, so that a computer program read out therefrom is mounted into the storage section 908 as necessary.
In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 909, and/or installed from the removable medium 911. The computer program performs the above-described functions defined in the method of the present application when executed by a Central Processing Unit (CPU) 901.
It should be noted that the computer readable medium described herein can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present application, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In this application, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present application may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or electronic device. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units described in the embodiments of the present application may be implemented by software or hardware. The described units may also be provided in a processor, and may be described as: a processor includes a sending unit and a first presentation unit. Where the names of these units do not constitute a limitation on the units themselves in such cases, for example, the sending unit may also be described as "sending a joint authorization request to a preset number of second products in the second product set in response to detecting that a user performs a joint authorization operation on a first product, such that the joint authorization request is processed and passed serially within the second product set". As another example, it can be described as: a processor includes a processing unit, a determination unit, and a transfer unit. Where the names of the units do not constitute a limitation on the units themselves in this case, for example, a processing unit may also be described as a "unit that processes a joint authorization request in response to receiving the joint authorization request".
As another aspect, the present application also provides a computer-readable medium, which may be contained in the electronic device described in the above embodiments; or may exist separately without being assembled into the electronic device. The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: in response to detecting that a user performs a joint authorization operation on a first product, sending joint authorization requests to a preset number of second products in a second product set so that the joint authorization requests are serially processed and transmitted inside the second product set, wherein the first product runtime provides services by calling the second product set; and displaying the authorization success message in response to receiving the authorization success messages sent by the preset number of second products in the second product set. Or cause the electronic device to: in response to receiving the joint authorization request, processing the joint authorization request, wherein the joint authorization request is sent by the user on the first product or serially passed by one second product in the second product set, and the first product runtime provides the service by calling the second product set; if the authorization is successful, determining whether a second product which does not process the joint authorization request exists in the second product set; if there is a second product that has not yet processed the joint authorization request, the joint authorization request is passed to one of the second set of products that has not yet processed the joint authorization request, such that the joint authorization request is serially processed and passed within the second set of products.
The above description is only a preferred embodiment of the application and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the invention herein disclosed is not limited to the particular combination of features described above, but also encompasses other arrangements formed by any combination of the above features or their equivalents without departing from the spirit of the invention. For example, the above features may be replaced with (but not limited to) features having similar functions disclosed in the present application.
Claims (28)
1. A federated authorization method, comprising:
in response to detecting that a user performs a joint authorization operation on a first product, sending a joint authorization request to a preset number of second products in a second product set, so that the joint authorization request is serially processed and transferred in the second product set, wherein the first product runtime provides a target service by calling the second product set, and the serial processing and transfer comprises processing the joint authorization request by the second products in the second product set and continuing the serial transfer of the joint authorization request in the second product set after successful authorization;
in response to receiving the authorization success messages sent by the preset number of second products in the second product set, displaying the authorization success messages.
2. The method of claim 1, wherein sending joint authorization requests to a preset number of second products in a second set of products in response to detecting that a user performs a joint authorization operation on a first product comprises:
in response to detecting that the user performs a login operation of a first product, displaying a joint authorization page on the first product;
in response to detecting that the user performs the joint authorization operation on the joint authorization page, sending the joint authorization request to a preset number of second products in the second product set.
3. The method of claim 1, wherein said sending joint authorization requests to a preset number of second products in a second set of products comprises:
obtaining an authorization sequence of the second set of products;
the authorization order is added to the federated authorization request, and the federated authorization request is sent to a second product ordered first in the authorization order, such that the federated authorization request is serially processed and communicated within the second set of products in the authorization order.
4. The method of claim 3, wherein the presenting of the authorization success message in response to receiving the authorization success message sent by the preset number of second products in the second set of products comprises:
and displaying the authorization success message in response to receiving the authorization success message sent by the second product which is sequenced at the last position in the authorization sequence.
5. The method according to one of claims 1-4, wherein the method further comprises:
and displaying the authorization failure message in response to receiving the authorization failure message sent by one second product in the second product sequence.
6. A joint authorization method, comprising:
in response to receiving a joint authorization request, processing the joint authorization request, wherein the joint authorization request is transmitted by a user on a first product or serially passed by a second product in a second product set, and the first product runtime provides a target service by calling the second product set;
if the authorization is successful, determining whether a second product which does not process the joint authorization request exists in the second product set;
if there is a second product that has not yet processed the joint authorization request, the joint authorization request is passed to a second product of the second product set that has not yet processed the joint authorization request, such that the joint authorization request is processed and passed serially within the second product set.
7. The method of claim 6, wherein the determining whether there is a second product in the second set of products that has not processed the joint authorization request comprises:
obtaining an authorization order for the second set of products from the joint authorization request;
determining a ranking of a current second product in the authorization order;
if the current second product is ranked at the last position, determining that no second product which does not process the joint authorization request exists;
if the current second product is not ranked in the last place, determining that there is a second product that has not yet processed the joint authorization request.
8. The method of claim 7, wherein said communicating the joint authorization request to one of the second set of products that has not yet processed the joint authorization request comprises:
passing the joint authorization request to a second product ordered next in the authorization order to the current second product such that the joint authorization request is processed and passed serially within the second set of products in the authorization order.
9. The method of claim 6, wherein the processing the joint authorization request comprises:
and verifying the joint authorization request, analyzing authorization parameters and generating authorization information.
10. The method of claim 9, wherein prior to said communicating the joint authorization request to one of the second set of products that has not yet processed the joint authorization request, further comprising:
adding the authorization information to the joint authorization request.
11. The method of claim 6, wherein said communicating the joint authorization request to one of the second set of products that has not processed the joint authorization request comprises:
passing the federated authorization request through an authorization callback interface to one of the second set of products that has not processed the federated authorization request.
12. The method of claim 6, wherein the method further comprises:
and if the second product which does not process the combined authorization request does not exist, sending an authorization success message to the user.
13. The method of claim 6, wherein the method further comprises:
and if the authorization fails, sending an authorization failure message to the user.
14. A joint authorization apparatus, comprising:
a sending unit, configured to respond to the detection that the user performs the joint authorization operation on the first product, send a joint authorization request to a preset number of second products in a second product set, so that the joint authorization request is serially processed and transferred in the second product set, wherein the first product runtime provides a target service by calling the second product set, the serial processing and transfer includes the second products in the second product set processing the joint authorization request, and the joint authorization request is continuously serially transferred in the second product set after the authorization is successful;
a first presentation unit configured to present the authorization success message in response to receiving the authorization success message sent by the preset number of second products in the second product set.
15. The apparatus of claim 14, wherein the transmitting unit is further configured to:
in response to detecting that the user performs a login operation of a first product, displaying a joint authorization page on the first product;
in response to detecting that the user performs the joint authorization operation on the joint authorization page, sending the joint authorization request to a preset number of second products in the second product set.
16. The apparatus of claim 14, wherein the transmitting unit is further configured to:
obtaining an authorization sequence of the second set of products;
the authorization order is added to the joint authorization request, and the joint authorization request is sent to a second product ordered at the first position in the authorization order, so that the joint authorization request is processed and transmitted in series in the second product set according to the authorization order.
17. The apparatus of claim 16, wherein the first presentation unit is further configured to:
and displaying the authorization success message in response to receiving the authorization success message sent by the second product which is sequenced at the last position in the authorization sequence.
18. The apparatus according to one of claims 14-17, wherein the apparatus further comprises:
the second display unit is configured to respond to the receiving of the authorization failure message sent by one second product in the second product sequence and display the authorization failure message.
19. A joint authorization apparatus, comprising:
a processing unit configured to process a joint authorization request in response to receiving the joint authorization request, wherein the joint authorization request is serially passed by one second product of a second product set or a first product sent by a user on the first product, and the first product runtime provides a target service by calling the second product set;
a determining unit configured to determine whether there is a second product in the second product set that has not processed the joint authorization request if authorization is successful;
a delivery unit configured to deliver the joint authorization request to a second product of the second product set that has not processed the joint authorization request if there is a second product that has not processed the joint authorization request, such that the joint authorization request is processed and delivered serially within the second product set.
20. The apparatus of claim 19, wherein the determining unit is further configured to:
obtaining an authorization order for the second set of products from the joint authorization request;
determining a ranking of a current second product in the authorization order;
if the current second product is ranked at the last position, determining that no second product which does not process the joint authorization request exists;
if the current second product is not ranked in the last place, determining that there is a second product that has not yet processed the joint authorization request.
21. The apparatus of claim 20, wherein the transfer unit is further configured to:
passing the joint authorization request to a second product ordered next in the authorization order to the current second product such that the joint authorization request is processed and passed serially within the second set of products in the authorization order.
22. The apparatus of claim 19, wherein the processing unit is further configured to:
and verifying the joint authorization request, analyzing authorization parameters and generating authorization information.
23. The apparatus of claim 22, wherein the apparatus further comprises:
an adding unit configured to add the authorization information to the joint authorization request.
24. The apparatus of claim 19, wherein the transfer unit is further configured to:
passing the joint authorization request through an authorization callback interface to a second product of the second set of products that has not processed the joint authorization request.
25. The apparatus of claim 19, wherein the apparatus further comprises:
a first sending unit configured to send an authorization success message to the user if there is no second product that has not processed the joint authorization request.
26. The apparatus of claim 19, wherein the apparatus further comprises:
and the second sending unit is configured to send an authorization failure message to the user if the authorization fails.
27. An electronic device, comprising:
one or more processors;
a storage device having one or more programs stored thereon,
the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method of any of claims 1-5 or to implement the method of any of claims 6-13.
28. A computer-readable medium, on which a computer program is stored, wherein the computer program, when being executed by a processor, carries out the method according to any one of claims 1-5 or carries out the method according to any one of claims 6-13.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911334179.3A CN111125676B (en) | 2019-12-23 | 2019-12-23 | Joint authorization method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911334179.3A CN111125676B (en) | 2019-12-23 | 2019-12-23 | Joint authorization method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111125676A CN111125676A (en) | 2020-05-08 |
| CN111125676B true CN111125676B (en) | 2022-06-03 |
Family
ID=70501333
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911334179.3A Active CN111125676B (en) | 2019-12-23 | 2019-12-23 | Joint authorization method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111125676B (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103560888A (en) * | 2013-11-05 | 2014-02-05 | 江苏先安科技有限公司 | Digital certificate-based unified authentication login method for integrating multiple application systems |
| CN103902923A (en) * | 2014-03-19 | 2014-07-02 | 广东工业大学 | Method for acquiring optimal authorization path based on RBAC model |
| CN104112085A (en) * | 2013-04-19 | 2014-10-22 | 阿里巴巴集团控股有限公司 | Data permission control method and device for application system clusters |
| CN104200159A (en) * | 2014-09-05 | 2014-12-10 | 北京奇虎科技有限公司 | Method and device for configuring application program permission |
| CN106453395A (en) * | 2016-11-16 | 2017-02-22 | 航天信息股份有限公司 | Hierarchical management method and system for cloud platform resource access authorities |
| CN109033803A (en) * | 2018-08-28 | 2018-12-18 | 南京南瑞信息通信科技有限公司 | A kind of movement based on portal APP is micro- to apply login management method |
| CN109388922A (en) * | 2017-08-04 | 2019-02-26 | 镇江雅迅软件有限责任公司 | A kind of user management based on RBAC model and a key log in realizing method |
| CN110209984A (en) * | 2019-05-31 | 2019-09-06 | 上海掌门科技有限公司 | Information interacting method, electronic equipment and computer-readable medium |
| CN110309661A (en) * | 2019-04-19 | 2019-10-08 | 中国科学院信息工程研究所 | A kind of sensitive data access right management method and device based on control stream |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8117643B2 (en) * | 2008-06-12 | 2012-02-14 | International Business Machines Corporation | Mathematical definition of roles and authorizations in RBAC system |
| US8196211B2 (en) * | 2008-08-14 | 2012-06-05 | International Business Machines Corporation | Authorized authorization set in RBAC model |
| US8474018B2 (en) * | 2010-09-03 | 2013-06-25 | Ebay Inc. | Role-based attribute based access control (RABAC) |
-
2019
- 2019-12-23 CN CN201911334179.3A patent/CN111125676B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104112085A (en) * | 2013-04-19 | 2014-10-22 | 阿里巴巴集团控股有限公司 | Data permission control method and device for application system clusters |
| CN103560888A (en) * | 2013-11-05 | 2014-02-05 | 江苏先安科技有限公司 | Digital certificate-based unified authentication login method for integrating multiple application systems |
| CN103902923A (en) * | 2014-03-19 | 2014-07-02 | 广东工业大学 | Method for acquiring optimal authorization path based on RBAC model |
| CN104200159A (en) * | 2014-09-05 | 2014-12-10 | 北京奇虎科技有限公司 | Method and device for configuring application program permission |
| CN106453395A (en) * | 2016-11-16 | 2017-02-22 | 航天信息股份有限公司 | Hierarchical management method and system for cloud platform resource access authorities |
| CN109388922A (en) * | 2017-08-04 | 2019-02-26 | 镇江雅迅软件有限责任公司 | A kind of user management based on RBAC model and a key log in realizing method |
| CN109033803A (en) * | 2018-08-28 | 2018-12-18 | 南京南瑞信息通信科技有限公司 | A kind of movement based on portal APP is micro- to apply login management method |
| CN110309661A (en) * | 2019-04-19 | 2019-10-08 | 中国科学院信息工程研究所 | A kind of sensitive data access right management method and device based on control stream |
| CN110209984A (en) * | 2019-05-31 | 2019-09-06 | 上海掌门科技有限公司 | Information interacting method, electronic equipment and computer-readable medium |
Non-Patent Citations (8)
| Title |
|---|
| IOS开发APP启动原理及视图和控制器的函数调用顺序;会飞的盖伦;《https://www.cnblogs.com/huayuan320/p/6064865.html》;20161115;全文 * |
| RPC and REST Dilemma, Disruption, and Displacement;Steve Vinoski;《IEEE INTERNET COMPUTING》;20080909;第12卷(第5期);第92-95页 * |
| 一张图清晰解释微信三方平台获取授权流程;腾讯后台开发;《https://cloud.tencent.com/developer/article/1368038》;20181205;全文 * |
| 一种统一授权和访问控制模型的设计实现;李栋栋;《计算机工程与应用》;20040416;第40卷(第6期);第80-83,123页 * |
| 基于角色的访问控制模型的研究与应用;张伟;《中国优秀博硕士学位论文全文数据库（硕士）信息科技辑》;20130215;全文 * |
| 对应用程序启动时所有方法的调用顺序分析;董铂然;《https://www.cnblogs.com/dsxniubility/p/4322525.html》;20150309;全文 * |
| 梳理微信小程序登录时序图：授权与 Oauth2.0;dkvirus;《https://www.jianshu.com/p/b9384fcb04b》;20171217;全文 * |
| 用例驱动的角色访问控制安全授权设计与研究;林鹃;《Proceedings of the 26th Chinese Control Conference》;20070731;文章第2-4节，图2-4 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111125676A (en) | 2020-05-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110708346B (en) | Information processing system and method | |
| US11237844B2 (en) | Method and apparatus for loading kernel module | |
| CN109684188B (en) | Test method and device | |
| CN110377440B (en) | Information processing method and device | |
| CN109873863B (en) | Asynchronous calling method and device of service | |
| WO2019015272A1 (en) | Information processing method and device | |
| CN110007936B (en) | Data processing method and device | |
| CN110618768B (en) | Information presentation method and device | |
| CN107645476B (en) | Request processing method and device | |
| CN110069185B (en) | Method and apparatus for co-running hosted applications | |
| CN111030900A (en) | Authentication-free login method and device and electronic equipment | |
| CN109145591B (en) | Plug-in loading method of application program | |
| CN111125676B (en) | Joint authorization method and device | |
| CN110855655B (en) | Information verification method, device, equipment and storage medium | |
| CN114840379A (en) | Log generation method, device, server and storage medium | |
| CN110765445B (en) | Method and device for processing request | |
| CN114417318A (en) | Third-party page jumping method and device and electronic equipment | |
| CN109669679B (en) | Service detection and processing method and device and electronic equipment | |
| CN108804713B (en) | Image output method, electronic device, and computer-readable medium | |
| CN113079085A (en) | Business service interaction method, business service interaction device, business service interaction equipment and storage medium | |
| CN108287792B (en) | Method and apparatus for outputting information | |
| CN109840073B (en) | Method and device for realizing business process | |
| WO2019223759A1 (en) | Method and device for displaying wireless access point information | |
| CN112306858A (en) | Test method and device and electronic equipment | |
| CN111786936A (en) | Method and device for authentication |
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 |