Application access method and device, equipment and storage medium

Abstract

The embodiment of the invention provides an application access method and device, equipment and a storage medium. The method comprises the following steps: in response to an access trigger request relative to a first application item under a current account, sending an access link acquisition request of the first application item to a software server, the access link acquisition request comprising authorized account information of the current account relative to a second application item, the account information of the second application item and the account information of the first application item are recorded in an open platform provided by the same identity provider, and the second application item completes authorization with the current account through the open platform; receiving an application access link of the software server; and accessing the application server of the first application item based on the application access link to display the application data information sent by the application server. By means of the method, re-authorization operation of the software client and the first application item is omitted, the number of authorization operation times and repeatability for accessing the first application item are effectively reduced, and the convenience for accessing the first application item product by the native application software is improved.

Description

Technical Field

[0001] The embodiments of the present disclosure relate to the field of computer application technology, and in particular, to an application access method, apparatus, device, and storage medium. Background Art

[0002] With the development of computer application technology and company business, a native application software will need to connect more internal or external third-party application products to enrich the functions of the native application software. Generally, native application software has an independent open platform, and these third-party application products themselves also have corresponding open platforms.

[0003] When access to a third-party application product is triggered in the native application software, the account login operation or application authorization operation of the third-party application product is required to ensure access security. However, in the existing technology implementation, even if the account information of multiple third-party application products is recorded on the open platform provided by the same identity provider, for each third-party application product to be accessed, the account login or authorization operation needs to be performed again. This causes the duplication of account login or authorization operations, which affects the access convenience of third-party application products and also affects the user experience of native application software. Summary of the invention

[0004] The present disclosure provides an application access method, apparatus, device and storage medium, which can realize authorization-free direct login to other third-party application products subsequently accessed after completing authorization with one of the third-party application products, for multiple third-party application products whose account information is recorded in an open platform provided by the same identity provider.

[0005] In a first aspect, an embodiment of the present disclosure provides an application access method, which is applied to a software client, and the method includes:

[0006] In response to an access trigger request for a first application item under the current account, an access link acquisition request for the first application item is sent to a software server, wherein the access link acquisition request includes the authorized account information of the current account for a second application item, the account information of the second application item and the first application item are both recorded in an open platform provided by the same identity provider, and the second application item has completed the authorization with the current account through the open platform, and the software server is the background server of the software client;

[0007] Receive an application access link fed back by the software server, wherein the application access link includes account signature information generated based on the authorized account information;

[0008] The application server of the first application item is accessed based on the application access link, and the application data information sent by the application server is displayed, wherein the application data information is fed back by the application server after the authorization of the current account to the first application item is completed based on the account signature information.

[0009] In a second aspect, an embodiment of the present disclosure provides an application access method, which is applied to a software server, and the method includes:

[0010] Receive an access link acquisition request sent by a software client to a first application item, wherein the access link acquisition request is generated by the software client after receiving an access trigger request to the first application item under a current account, and includes authorized account information of the current account to a second application item, wherein the account information of the second application item and the first application item are both recorded in an open platform provided by the same identity provider, and the second application item has completed authorization with the current account through the open platform, and the software server is a backend server of the software client;

[0011] Generate an application access link containing account signature information based on the authorized account information and feed it back to the software client, so that the software client can access the application server of the first application item through the application access link;

[0012] Receiving an account authorization request sent by the application server, wherein the account authorization request carries the account signature information;

[0013] Based on the account authorization request, target authorization information for authorizing the current account to the first application item is determined, and the target authorization information is fed back to the application server, so that the application server sends application data information to the software client based on the target authorization information.

[0014] In a third aspect, an embodiment of the present disclosure provides an application access method, which is applied to an application server of a first application item, and the method includes:

[0015] In response to the software client's access to the application access link, obtaining the account signature information contained therein and generating an account authorization request, the application access link is obtained from the software server after being triggered by the software client's access to the first application item under the current account, the account signature information is generated by the software server through the authorized account information of the current account relative to the second application item, and the second application item and the first application item are authorized applications on the same open platform;

[0016] Sending the account authorization request to the software server, and receiving target authorization information sent by the software server, the target authorization information being determined by the software server when authorizing the current account to the first application item based on the account authorization request;

[0017] Based on the target authorization information, the application data information of the first application item is queried from the open platform and sent to the software client.

[0018] In a fourth aspect, the embodiment of the present disclosure further provides an application access device, which is configured on a software client, and the device includes:

[0019] A request sending module, used for sending an access link acquisition request for a first application item to a software server in response to an access trigger request for the first application item under the current account, wherein the access link acquisition request includes the authorized account information of the current account for a second application item, the account information of the second application item and the first application item are both recorded in an open platform provided by the same identity provider, and the second application item has completed the authorization with the current account through the open platform, and the software server is the background server of the software client;

[0020] A link receiving module, used to receive an application access link fed back by the software server, wherein the application access link includes account signature information generated based on the authorized account information;

[0021] An information display module is used to access the application server of the first application item based on the application access link and display the application data information sent by the application server, wherein the application data information is fed back by the application server after the authorization of the current account to the first application item is completed based on the account signature information.

[0022] In a fifth aspect, the embodiment of the present disclosure further provides an application access device, which is configured on a software server, and the device includes:

[0023] A first receiving module is used to receive an access link acquisition request sent by a software client to a first application item, wherein the access link acquisition request is generated by the software client after receiving an access trigger request to the first application item under a current account, and includes the authorized account information of the current account to a second application item, the account information of the second application item and the first application item are both recorded in an open platform provided by the same identity provider, and the second application item has completed the authorization with the current account through the open platform, and the software server is a background server of the software client;

[0024] A first feedback module, configured to generate an application access link including account signature information based on the authorized account information and feed the link back to the software client, so that the software client can access the application server of the first application item through the application access link;

[0025] A second receiving module is used to receive an account authorization request sent by the application server, wherein the account authorization request carries the account signature information;

[0026] The second feedback module is used to determine the target authorization information for authorizing the current account to the first application item based on the account authorization request, and feed back the target authorization information to the application server, so that the application server sends application data information to the software client based on the target authorization information.

[0027] In a sixth aspect, the embodiment of the present disclosure further provides an application access device, which is configured in an application server of a first application item, and the device includes:

[0028] A request generation module, for responding to the software client's access to the application access link, obtaining the account signature information contained therein and generating an account authorization request, wherein the application access link is obtained from the software server after being triggered by the software client's access to the first application item under the current account, and the account signature information is generated by the software server through the authorized account information of the current account relative to the second application item, and the second application item and the first application item are authorized applications on the same open platform;

[0029] a third receiving module, configured to send the account authorization request to the software server, and receive target authorization information sent by the software server, wherein the target authorization information is determined by the software server when authorizing the current account to the first application item based on the account authorization request;

[0030] An information sending module is used to query the application data information of the first application item from the open platform based on the target authorization information and send the information to the software client.

[0031] In a seventh aspect, an embodiment of the present disclosure further provides an electronic device, the electronic device comprising:

[0032] one or more processors;

[0033] a storage device for storing one or more programs,

[0034] When the one or more programs are executed by the one or more processors, the one or more processors implement the application access method provided by the first aspect to the third aspect of the embodiments of the present disclosure.

[0035] In an eighth aspect, an embodiment of the present disclosure further provides a storage medium containing computer executable instructions, which, when executed by a computer processor, are used to execute the application access method provided by the first to third aspects of the embodiment of the present disclosure.

[0036] The disclosed embodiments provide an application access method, apparatus, device and storage medium. The method can be applied to a software client, a software server and an application server of a first application item. The method logic executed by the three execution ends in cooperation with each other includes: first, the software client responds to an access trigger request for the first application item under the current account, and sends an access link acquisition request for the first application item to the software server. The software server receives the access link acquisition request sent by the software client for the first application item, and then generates an application access link containing account signature information based on the authorized account information and feeds it back to the software client; then the software client receives the application access link and accesses the application server of the first application item based on the application access link, and then the application The server responds to the software client's access to the application access link, obtains the account signature information contained therein and generates an account authorization request, and sends the account authorization request to the software server; the software server determines the target authorization information for authorizing the current account to the first application item based on the received account authorization request, and feeds back the target authorization information to the application server, and the application server queries the application data information of the first application item from the open platform based on the received target authorization information and sends it to the software client, and finally the software client displays the application data information sent by the application server, wherein the access link acquisition request contains the authorized account information of the current account relative to the second application item, and the second application item is an authorized application on the same open platform as the first application item. Based on the above technical solution of this embodiment, for the software client, after having the access demand for the first application item, as long as there is a second application item that has completed the authorization, and the account information of the second application item and the first application item are recorded in the open platform provided by the same identity provider, it is possible to access the application server of the first application item based on the authorized account information of the second application item, and obtain the relevant application data information fed back by the application server to the first application item. This technical solution is equivalent to directly realizing the invisible authorization of the first application item based on the interaction between the software server and the application server, eliminating the need for the software client to re-authorize the first application item. Compared with the existing access to the first application item, it effectively reduces the number and repeatability of authorization operations for accessing the first application item, better improves the convenience of native application software to access the first application item product, and also better improves the user experience after the first application item is integrated into the native application software. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the accompanying drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and the originals and elements are not necessarily drawn to scale.

[0038] Figure 1 A flowchart of an application access method provided by an embodiment of the present disclosure;

[0039] Figure 2 A flowchart of an application access method provided by an embodiment of the present disclosure;

[0040] Figure 3 A flowchart of an application access method provided by an embodiment of the present disclosure;

[0041] Figure 4 An interactive diagram of an application access method provided by an embodiment of the present disclosure

[0042] Figure 5 A schematic diagram of the structure of an application access device provided by an embodiment of the present disclosure;

[0043] Figure 6 A schematic diagram of the structure of an application access device provided by an embodiment of the present disclosure;

[0044] Figure 7 A schematic diagram of the structure of an application access device provided by an embodiment of the present disclosure;

[0045] Figure 8 A schematic diagram of the structure of an electronic device provided by an embodiment of the present disclosure. DETAILED DESCRIPTION

[0046] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments described herein, which are instead provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.

[0047] It should be understood that the various steps described in the method embodiments of the present disclosure may be performed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present disclosure is not limited in this respect.

[0048] The term "including" and its variations used herein are open inclusions, i.e., "including but not limited to". The term "based on" means "based at least in part on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". The relevant definitions of other terms will be given in the following description.

[0049] It should be noted that the concepts such as "first" and "second" mentioned in the present disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0050] It should be noted that the modifications of "one" and "plurality" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, it should be understood as "one or more".

[0051] The names of the messages or information exchanged between multiple devices in the embodiments of the present disclosure are only used for illustrative purposes and are not used to limit the scope of these messages or information.

[0052] It is understandable that before using the technical solutions disclosed in the embodiments of the present disclosure, the types, scope of use, usage scenarios, etc. of the personal information involved in the present disclosure should be informed to the user and the user's authorization should be obtained in an appropriate manner in accordance with relevant laws and regulations.

[0053] For example, in response to receiving an active request from a user, a prompt message is sent to the user to clearly prompt the user that the operation requested to be performed will require obtaining and using the user's personal information. Thus, the user can autonomously choose whether to provide personal information to software or hardware such as an electronic device, application, server, or storage medium that performs the operation of the technical solution of the present disclosure according to the prompt message.

[0054] As an optional but non-limiting implementation, in response to receiving an active request from the user, the prompt information may be sent to the user in the form of a pop-up window, in which the prompt information may be presented in text form. In addition, the pop-up window may also carry a selection control for the user to choose "agree" or "disagree" to provide personal information to the electronic device.

[0055] It is understandable that the above notification and the process of obtaining user authorization are merely illustrative and do not constitute a limitation on the implementation of the present disclosure. Other methods that meet the relevant laws and regulations may also be applied to the implementation of the present disclosure.

[0056] It should be noted that in an application scenario, at least two third-party application products are integrated on the native application software, such as the first application product and the second application product, wherein the account information used to log in to the first application product and the account information used to log in to the second application product are both recorded in the open platform provided by the same identity provider, and belong to a different open platform from the native application software. In the existing implementation, the native application software needs to obtain access rights to the first application product and the second application product before it can perform subsequent interaction logic, wherein the access rights can be obtained through an open authorization protocol, but in the authorization implementation based on the open authorization protocol, even if the native application software has established an authorization relationship with the first application product, when it has access requirements to the second application product, it still needs to perform the authorization operation with the second application product again, or the account login operation of the second application product.

[0057] Continuing with the above description, another way to obtain access rights can be based on a single sign-on identity authentication method. Although single sign-on can achieve login-free secure access to multiple related applications and services through a set of login credentials, single sign-on has limitations in its scope of use. Its use premise is that the account information of the native application software and the first application product and the second application product should all be recorded in the open platform provided by the same identity provider. Therefore, this method cannot achieve the joint authorization-free login of the application scenario described above.

[0058] Based on this, this embodiment provides an application access method that can solve the problems existing in the above-mentioned existing permission acquisition methods.

[0059] Specifically, Figure 1 A flow chart of an application access method provided in an embodiment of the present disclosure is provided. The embodiment of the present disclosure is applied to a software client and can be applicable to a situation where the installed native application software determines access rights for accessing a first application item. The method can be executed by an application access device, which can be implemented in the form of software and / or hardware. Optionally, it can be implemented by an electronic device as an execution terminal, which can be a mobile terminal, a PC or a server, etc.

[0060] like Figure 1 As shown, an application access method provided by an embodiment of the present disclosure specifically includes the following operations:

[0061] S110. In response to an access trigger request for the first application item under the current account, an access link acquisition request for the first application item is sent to the software server. The access link acquisition request includes the authorized account information of the current account relative to the second application item. The account information of the second application item and the first application item are both recorded in an open platform provided by the same identity provider, and the second application item has completed the authorization with the current account through the open platform. The software server is the background server of the software client.

[0062] In this embodiment, the current account can be understood as the account currently logged in in the software client. The first application item can be understood as an application item developed by a third party that is independent of the native application software corresponding to the software client, and can be used to provide corresponding functions, information, etc. for the native application software. The first application item can be an application program placed in an application product in the form of a plug-in to present the corresponding content in the application product, or it can be in the form of a web link, triggering the corresponding content through a web link to present the corresponding content in the application product. The open platform corresponding to the first application item may be inconsistent with the open platform corresponding to the software client. Among them, the open platform refers to a platform responsible for collecting and storing account information to provide user identity authentication services when the user logs in, that is, determining whether the logged-in account has the authority to access the application served by the open platform through the open platform.

[0063] In this embodiment, the access trigger request is a request generated when the software client receives a user trigger to access the first application item. For example, the user wants to open the page provided by the first application item in the interface or page provided by the native application software, and the access trigger request is generated by clicking the corresponding control or other triggering methods.

[0064] In this embodiment, the second application item can be understood as an application item that the current account has been authorized to access, which can also refer to a plug-in form or a web link to access a certain application product, etc. The second application item and the first application item are in the open platform provided by the same identity provider. The software server is the server corresponding to the second application item, and the software server can interact with the open platform corresponding to the second application item.

[0065] In this embodiment, the access connection acquisition request refers to a request sent to the software server for querying the access link of the first application product.

[0066] In this embodiment, the authorized account information can be understood as information corresponding to an account having access rights to the second application item. The authorized application can be understood as an application having access rights to the first application item served by the open platform.

[0067] Specifically, as a prerequisite, the second application item is consistent with the open platform of the first application item that the software client wants to access, that is, the account information of the second application item and the first application item are both recorded in the open platform provided by the same identity provider, and the authorization operation has been performed when the software client first accesses the second application item, and the second application item has completed the authorization with the current account through the open platform, and the current account has access rights in the second application item, that is, the open platform determines the authorized account information corresponding to the current account in the second application item. In response to the access trigger request relative to the first application item under the current account, the software client can generate an access link acquisition request for obtaining an access link to access the first application item page according to the authorized account information, and send the access link acquisition request to the software server of the second application item to obtain the access link of the first application item.

[0068] In this embodiment, the authorized account information and the account signature information can be further optimized and limited. Specifically, the authorized account information can be optimized to include the current account identifier and the identity authorization account identifier determined in advance when the current account is authorized to the second application item; the account signature information can be optimized to include: the current account identifier, the identity authorization account identifier, the request reception timestamp and the timeout timestamp; the account signature information is also used for the software server to authenticate the identity of the current account.

[0069] Among them, the current account identifier can be understood as representing the user corresponding to the current account in the form of an identifier. The identity authorization account identifier can be understood as an identifier used to indicate that the current account has been authorized to access the second application item. The request reception timestamp is used to record the time when the access trigger request is received in the form of a timestamp. The timeout timestamp can be understood as a mechanism set in the form of a timestamp that automatically expires if there is no response for a certain period of time.

[0070] In this embodiment, the account signature information may also include a random string to ensure that the signature is unpredictable, thereby providing security for the account signature information. The above authorization account information and account signature information in this embodiment may provide basic support for the subsequent generation of an account authorization request based on the authorization account information and account signature information.

[0071] S120: Receive an application access link fed back by the software server, where the application access link includes account signature information generated based on the authorized account information.

[0072] In this embodiment, the application access link can be understood as a link for accessing the first application item that carries the account signature information, wherein the account signature information is used to trigger the identity authentication information corresponding to the account signature.

[0073] What needs to be known is that when the software client accesses the first application product for the first time through a normal access link, the first application cannot determine whether the current account has the authority to access it, and it will generate an authorization confirmation instruction and feedback it to the software client, so that the user of the software client can perform authorization operations, and then verify the identity corresponding to the current account through the open platform. When the verification passes, the authorized account information and the access rights it has are determined. That is, when accessing different first application products for the first time, the user of the software client is required to perform authorization operations, which is cumbersome.

[0074] Specifically, since the current account has been authorized by the second application, the user of the software client has already authorized the target reference, that is, the identity corresponding to the current account has been verified through the open platform, and the authorized account information has been determined. The account information of the second application and the first application are both recorded in the open platform provided by the same identity provider, and the second application has completed the authorization with the current account through the open platform, so the authorized account information can be directly used. However, in order to ensure security and prevent others from imitating the authorized account information, it is necessary to process the authorized account information and generate more secure account signature information, and place the account signature information in the application access link, so that the first application can perform identity verification on the account signature information contained therein when receiving access through the application access link, without sending the authorization operation to the software client. Since the authorized account information is all in the software server, the process of generating the account signature information based on the authorized account information is performed in the software server, and the software client can receive the application access link fed back by the software server, and the application access link contains the account signature information generated based on the authorized account information.

[0075] S130. Access the application server of the first application item based on the application access link, and display the application data information sent by the application server, wherein the application data information is fed back by the application server after the authorization of the current account to the first application item is completed based on the account signature information.

[0076] In this embodiment, the application data information can be understood as information consisting of display data that can be provided by the authority possessed by the account signature information.

[0077] Specifically, the software client can access the application server of the first application item based on the application access link, and determine the permission based on the account signature information through the application server of the first application item. This process is performed at the application server of the first application item and does not involve the user of the software client to provide operations. It is automatically triggered when the application server receives the application access link including the account signature information. When the application server completes the authorization of the current account to the first application item based on the account signature information, it will feedback the application data information that can be provided by its corresponding permission to the software client, and the software client displays the application data information. In the overall process, the user of the software client only performs the access trigger operation of the first application item once, and can obtain the application data information feedback by the first application item.

[0078] The present embodiment provides an application access method. For a software client, after having access requirements to a first application item, as long as there is a second application item that has been authorized, and the account information of the second application item and the first application item are recorded on the open platform provided by the same identity provider, the application server of the first application item can be accessed based on the authorized account information of the second application item, and the relevant application data information of the first application item can be obtained. It can directly implement the invisible authorization of the first application item based on the interaction between the software server and the application server. The above-mentioned entire implementation process eliminates the need for the software client to re-authorize the first application item on the basis of ensuring the security of access to the first application item. Compared with the existing access implementation to the first application item, it effectively reduces the number and repeatability of authorization operations for accessing the first application item, better improves the convenience of native application software to access the first application item product, and also better improves the user experience after the first application item is integrated into the native application software.

[0079] Figure 2 A flow chart of an application access method provided in an embodiment of the present disclosure is provided. The embodiment of the present disclosure is applied to a software server and can be applicable to a situation where a native application software installed on a client determines access rights for a first application item to be accessed. The method can be executed by an application access device, which can be implemented in the form of software and / or hardware. Optionally, it can be implemented by an electronic device as an execution terminal, which can be a mobile terminal, a PC or a server, etc.

[0080] S210. Receive an access link acquisition request sent by the software client to the first application item. The access link acquisition request is generated by the software client after receiving an access trigger request to the first application item under the current account, and includes the authorized account information of the current account to the second application item. The account information of the second application item and the first application item are both recorded in the open platform provided by the same identity provider, and the second application item has completed the authorization with the current account through the open platform.

[0081] What needs to be known is that as a prerequisite for the software server to perform subsequent permission determination, it is necessary to ensure that the current account has access rights to the software server corresponding to the second application item, that is, the current account has been authenticated by the open platform of the software server, and the account information of the second application item and the first application item are both recorded on the open platform, and the second application item has been authorized on the open platform, that is, the current account currently logged in to the second application item has access rights to the first application item.

[0082] Specifically, in this step, the software server may receive an access link acquisition request sent by the software client to the first application item to trigger the execution of the logic for determining the application access link.

[0083] S220: Generate an application access link including account signature information based on the authorized account information and feed it back to the software client, so that the software client can access the application server of the first application item through the application access link.

[0084] Specifically, when the relationship between the second application item, the first application item and the current account satisfies the above premise, the software server can determine the authorized account information included in the access link acquisition request. In order to prevent the application server of the first application item from sending an instruction to the software client to instruct the user to perform an authorization operation again when the application server is accessed through the application access link, it is necessary to add account signature information in the application access link to indicate that the current account of the application server has authorized access to the second application item and includes its corresponding key information and request time, etc. The software server can then generate an application access link containing the account signature information based on the authorized account information, the time when the access link acquisition request is received, the identifier corresponding to the first application item, and the random string used for identity authentication, and feed it back to the software client.

[0085] S230: Receive an account authorization request sent by the application server, where the account authorization request carries account signature information.

[0086] In this embodiment, the account authorization request can be understood as a request for determining whether the current account has permission to access the first application item.

[0087] Specifically, the software server may receive an account authorization request sent by the application server, thereby triggering a subsequent step of performing account authority verification based on the account signature information.

[0088] S240: Based on the account authorization request, determine target authorization information for authorizing the current account to the first application item, and feed back the target authorization information to the application server, so that the application server sends application data information to the software client based on the target authorization information.

[0089] In this embodiment, the target authorization information is unified identity authorization information under multiple first application items stored in the open platform.

[0090] What needs to be known is that since the current account logged in in different first application items may be different, but the corresponding user is unique, that is, the case of multiple accounts for one household, the unique user identifier corresponding to the current account can be obtained to determine the unique user identifier corresponding to the current account. The target authorization information corresponding to the unique user identifier is also pre-established in the open platform, so that the target authorization information can be determined in this way.

[0091] Specifically, the software server can determine the unique user identifier obtained during authorization based on the account authorization request, and can search the open platform based on the unique user identifier to determine the target authorization information for authorizing the current account to the first application item, so that the application server obtains the corresponding application data information based on the target authorization information and sends the application data information to the software client.

[0092] The application access method provided in this embodiment is applied to a software server, where the software server receives an access link acquisition request sent by a software client to a first application item, generates an application access link containing account signature information based on the authorized account information and feeds it back to the software client, receives an account authorization request sent by the application server, and determines the target authorization information for authorizing the current account to the first application item based on the account authorization request. The software server replaces the authorization operation of the software client to achieve the generation of the application access link and the determination of the target authorization information. Only one authorization operation needs to be performed on the software client, and access to other first application items whose account information is recorded in the open platform provided by the same identity provider is achieved, thereby improving the user experience.

[0093] As a first optional embodiment of this embodiment, based on the above embodiment, this first optional embodiment can concretize the steps of generating an application access link containing account signature information based on the authorized account information as follows:

[0094] a1) Obtaining a request receiving timestamp of the access link acquisition request, and extracting a current account identifier in the authorized account information and an identity authorization account identifier of the current account relative to the second application item.

[0095] Specifically, in order to complete the automatic invalidation mechanism in the event of a timeout, the software server can obtain the request reception timestamp of the access link acquisition request, and extract the current account identifier in the authorization account information, as well as the identity authorization account identifier of the current account relative to the second application item.

[0096] b1) Generate an account signature result based on the current account ID, identity authorization account ID, request reception timestamp and preset timeout timestamp.

[0097] In this embodiment, the account signature result can be understood as a result including account information in a signature format. The timeout timestamp can be used to limit the duration of the request without response, and start the corresponding processing mechanism in the case of timeout.

[0098] Specifically, the software server can generate an account signature result by combining the current account identifier, the identity authorization account identifier, the request reception timestamp and the preset timeout timestamp through a corresponding signature algorithm.

[0099] c1) Based on the account signature result, the account signature information is formed, combined with the uniform resource identifier of the first application item, and encapsulated to form an application access link.

[0100] In this embodiment, the uniform resource identifier can be understood as a uniform address on the network used to represent information resources, such as a URL.

[0101] Specifically, in order to facilitate the application server of the first application item to directly obtain the account signature information based on the access to the application link, the software server first constructs the account signature information based on the account signature result when forming the application access link, and encapsulates the account signature information in combination with the uniform resource identifier of the first application item into an application access link.

[0102] The above technical solution of this embodiment provides a method for generating an application access link. Through the execution of this implementation method, the encapsulation of the application access link sent to the application server can be effectively realized. This embodiment can realize the encapsulation of the application access link, so that the application server triggers authorization feedback to the software server when receiving the application access link, thereby avoiding the authorization feedback of the application server to the software client, thereby reducing the number of authorization operations.

[0103] As a second optional embodiment of this embodiment, after receiving the account authorization request generated by the application server based on the account signature information, it also includes:

[0104] The identity authentication of the current account is performed based on the account signature information and the pre-stored benchmark verification information, and the benchmark verification information applies the account signature information contained in the access link.

[0105] In this embodiment, the pre-stored benchmark verification information can be understood as backup information for verification stored when the software server generates the account signature information.

[0106] It is important to know that the account signature information is generated by the application server. The account signature information is first sent to the software client, and then sent by the software client to the application server of the first application item. Since it passes through multiple servers, the signature may be forged during the sending process. In order to ensure the security of access, after receiving the account authorization request from the application server, the account signature information in the account authorization request will first be authenticated.

[0107] Specifically, the software server can obtain the pre-stored benchmark verification information from the corresponding database. Since a random string for identity authentication is added to the generated account signature information, that is, the pre-stored benchmark verification information also includes the random string, when the software server receives an account authorization request, it can compare the random string in the account signature information with the random string in the pre-stored benchmark verification information to realize identity authentication of the current account.

[0108] For the received account authorization request, this embodiment can verify the account signature information in the account authorization request through the pre-stored benchmark verification information, thereby realizing the identity verification of the current account and ensuring the security of access to the first application item.

[0109] As a fourth optional embodiment of this embodiment, based on the above embodiment, this fourth optional embodiment can specify the step of determining the target authorization information for authorizing the current account to the first application item based on the account authorization request as follows:

[0110] a2) Extract the identity authorization account identifier contained in the account signature information in the account authorization request.

[0111] What you need to know is that after the current account is authorized in the open platform, the software client will feedback an open identifier to the software server that is authorized to access. The open identifier can be understood as a unique user ID for accessing the software server, that is, the corresponding user can be determined through the open identifier, and when the software server receives the open identifier, it will establish a mapping relationship between the identity authorization account identifier of the current account and the open identifier, and the corresponding open identifier can be determined through the identity authorization account identifier.

[0112] Specifically, in order to determine the open identifier, the software server needs to extract the identity authorization account identifier contained in the account signature information in the account authorization request.

[0113] b2) Searching for the open identifier corresponding to the identity authorization account identifier from the pre-stored authorization account mapping information.

[0114] In this embodiment, the authorized account mapping information may be understood as information for including mapping relationships between multiple identity authorized account identifiers and open identifiers.

[0115] Specifically, the software server may obtain pre-stored authorization account mapping information from a corresponding database, search the authorization account mapping information based on the identity authorization account identifier, and determine the corresponding open identifier.

[0116] c2) Access the open platform, search for the first application authorization identifier corresponding to the open identifier, and use it as the target authorization information.

[0117] In this embodiment, the third-party application authorization identifier can be understood as being used to indicate to the application server, by way of an identifier, the access rights of the current account to the first application item.

[0118] It is important to know that in order to facilitate account management in the open platform, the account permissions of all first application items of the same user are stored and managed in the form of a unified identity ID, that is, an association between the user's open identifier and its corresponding unified identity ID is established. The unified identity ID can be determined through the open identifier, and the access permissions of the user in different first application items can be found through the unified identity ID.

[0119] Specifically, the software server can access the open platform of the first application, search for the unified identity ID corresponding to the open identifier, determine the first application authorization identifier of the open identifier in the first application in the unified identity ID, and use it as the target authorization information to authorize the current account to the first application.

[0120] The above technical solution of this embodiment provides a method for determining the target authorization information. Through the execution of this implementation method, the target authorization information can be determined only by the software server without the software client participating in the operation, thereby reducing the number of authorization operations of the software client.

[0121] Figure 3 A flow chart of an application access method provided in an embodiment of the present disclosure. The embodiment of the present disclosure is applied to an application server of a first application item and can be applicable to a situation where the application server determines account permissions. The method can be executed by an application access device, which can be implemented in the form of software and / or hardware. Optionally, it can be implemented by an electronic device as an execution terminal, which can be a mobile terminal, a PC or a server, etc.

[0122] S310. Respond to the software client's access to the application access link, obtain the account signature information contained therein and generate an account authorization request. The application access link is obtained from the software server after being triggered by the software client's access to the first application item under the current account. The account signature information is generated by the software server through the authorized account information of the current account relative to the second application item. The account information of the second application item and the first application item are both recorded in the open platform provided by the same identity provider, and the second application item has completed the authorization with the current account through the open platform.

[0123] In this embodiment, the account authorization request is a request for triggering the software server to determine the account authority.

[0124] Specifically, the application server can respond to the software client's access to the application access link. Since the application server is not sure whether the software client has access rights, it first obtains the account signature information used to determine the access rights in the application access link, and then generates an account authorization request sent to the software server through the account signature information, so that the software server can determine the access rights corresponding to the current account through the account authorization request.

[0125] S320: Send the account authorization request to the software server, and receive the target authorization information sent by the software server, where the target authorization information is determined by the software server when authorizing the current account to the first application item based on the account authorization request.

[0126] Specifically, the application server can send an account authorization request to the software server, determine the access rights corresponding to the current account through the software server, and receive the target authorization information sent by the software server. This process can be completed without the participation of the software client.

[0127] S330: Based on the target authorization information, query the application data information of the first application item from the open platform and send it to the software client.

[0128] Specifically, the application server may query the application data information of the first application item from the open platform based on the target authorization information and send the information to the software client.

[0129] The application access method provided in this embodiment is applied to an application server, and the application server responds to the software client's access to the application access link, obtains the account signature information contained therein and generates an account authorization request, sends the account authorization request to the software server, and receives the target authorization information sent by the software server. Based on the target authorization information, the application data information of the first application item is queried from the open platform that records the account information of the first application item and the second application, and sends it to the software client. This avoids the application server from feeding back the authorization operation to the software client when the access rights of the application access link are unclear, and implements the feedback of the application data information accessed by the software client. Only one authorization operation needs to be performed on the software client, and access to other first application items under the same open platform is implemented, thereby improving the user experience.

[0130] In order to facilitate the understanding of this solution, a specific example of the interaction between the software client, software server and application server is given. Figure 4 An interactive schematic diagram of an application access method provided by an embodiment of the present disclosure, such as Figure 4 As shown, the application access method involves three execution ends, specifically a software client, a software server, and an application server of the first application item. In this example, the implementation steps for accessing the first application item may be:

[0131] S1. The software client receives an access trigger request for a first application item sent by the current account.

[0132] S2, the software client sends an access connection acquisition request including the authorized account information of the current account relative to the second application item to the software server;

[0133] The account information of the second application item and the first application item are both recorded in the open platform provided by the same identity provider, and the second application item has completed the authorization with the current account through the open platform;

[0134] S3. The software server generates an application access link including the account signature information and feeds it back to the software client, wherein the account signature information includes: the current account identifier, the identity authorization account identifier of the second application item, the request receiving timestamp, and the preset timeout timestamp;

[0135] S4. The software client uses the access link to access the application server based on the account signature information;

[0136] S5. The application server generates an account authorization request based on the account signature information and sends it to the software server;

[0137] S6. The software server searches the database for an open identifier corresponding to the identity authorization account identifier of the second application item;

[0138] S7, the database feeds back an open identifier corresponding to the identity authorization account identifier of the second application item to the software server;

[0139] S8. The software server queries the open platform for the first application authorization identifier corresponding to the open identifier;

[0140] S9. The open platform feeds back the authorization identifier of the first application item to the software server;

[0141] S10, the software server sends the target authorization information to the application server;

[0142] S11, the application server queries the application data information in the open platform based on the target authorization information and interacts;

[0143] S12, the application server sends the application data information to the software client;

[0144] S13. The software client displays the application data information.

[0145] It can be seen that during the entire application access process, when the software client accesses the first application item, on the basis that the account information of the authorized second application item and the first application item is recorded on the open platform provided by the same identity provider, the authorization identifier corresponding to the first application item is determined through the identity authorization account identifier of the second application item, so as to determine the target authorization information of the first application item and obtain the corresponding data information. There is no need to perform the authorization operation again. After sending the access departure request relative to the first application item, the application data information of the first application item can be directly obtained and displayed. The authorization and other operations can be completed by the software server and the application server. It is only necessary to perform authorization once on a certain application under the open platform provided by the same identity provider for which the account information is recorded on the software client, so that the unauthorized access to other first application items under the open platform can be realized, which effectively reduces the number of authorization operations for the first application item.

[0146] Figure 5 A schematic diagram of the structure of an application access device provided by an embodiment of the present disclosure, configured in a software client, such as Figure 5 As shown, the device includes: a request sending module 510, a link receiving module 520 and an information display module 530.

[0147] The request sending module 510 is used to send an access link acquisition request for the first application item to the software server in response to an access trigger request for the first application item under the current account, wherein the access link acquisition request includes the authorized account information of the current account for the second application item, and the second application item is an authorized application on the same open platform as the first application item;

[0148] The link receiving module 520 is used to receive the application access link fed back by the software server, where the application access link includes account signature information generated based on the authorized account information;

[0149] The information display module 530 is used to access the application server of the first application item based on the application access link and display the application data information sent by the application server, wherein the application data information is fed back by the application server after the authorization of the current account to the first application item is completed based on the account signature information.

[0150] The technical solution provided by the disclosed embodiment is that, for a software client, after having access requirements to a first application item, as long as there is an authorized second application item, and the account information of the second application item and the first application item are recorded on an open platform provided by the same identity provider, the software client can access the application server of the first application item based on the authorized account information of the second application item, and obtain the relevant application data information fed back by the application server to the first application item. This technical solution is equivalent to directly implementing invisible authorization of the first application item based on the interaction between the software server and the application server, eliminating the need for the software client to re-authorize the first application item. Compared with the existing access implementation to the first application item, this effectively reduces the number and repeatability of authorization operations for accessing the first application item, thereby better improving the convenience of native application software in accessing the first application item product, and better improving the user experience after the first application item is integrated into the native application software.

[0151] Furthermore, the authorized account information includes the current account identifier and the identity authorization account identifier determined in advance when the current account is authorized to the second application item; the account signature information includes: the current account identifier, the identity authorization account identifier, the request reception timestamp and the timeout timestamp; the account signature information is also used by the software server to authenticate the current account.

[0152] The application access device provided in the embodiments of the present disclosure can execute the application access method provided in any embodiment of the present disclosure, and has the corresponding functional modules and beneficial effects of the execution method.

[0153] It is worth noting that the various units and modules included in the above-mentioned device are only divided according to functional logic, but are not limited to the above-mentioned division, as long as the corresponding functions can be achieved; in addition, the specific names of the functional units are only for the convenience of distinguishing each other, and are not used to limit the protection scope of the embodiments of the present disclosure.

[0154] Figure 6 A schematic diagram of the structure of an application access device provided by an embodiment of the present disclosure, configured on a software server, such as Figure 6As shown, the apparatus includes: a first receiving module 610 , a first feedback module 620 , a second receiving module 630 and a second feedback module 640 .

[0155] The first receiving module 610 is used to receive an access link acquisition request sent by the software client to the first application item. The access link acquisition request is generated by the software client after receiving an access trigger request to the first application item under the current account, and includes the authorized account information of the current account to the second application item. The second application item is an authorized application on the same open platform as the first application item.

[0156] A first feedback module 620, configured to generate an application access link including account signature information based on the authorized account information and feedback the link to the software client, so that the software client can access the application server of the first application item through the application access link;

[0157] The second receiving module 630 is used to receive an account authorization request sent by the application server, where the account authorization request carries account signature information;

[0158] The second feedback module 640 is used to determine target authorization information for authorizing the current account to the first application item based on the account authorization request, and feed back the target authorization information to the application server so that the application server sends application data information to the software client based on the target authorization information.

[0159] The technical solution provided by the disclosed embodiment is that, for a software client, after having access requirements to a first application item, as long as there is an authorized second application item, and the account information of the second application item and the first application item are recorded on an open platform provided by the same identity provider, the software client can access the application server of the first application item based on the authorized account information of the second application item, and obtain the relevant application data information fed back by the application server to the first application item. This technical solution is equivalent to directly implementing invisible authorization of the first application item based on the interaction between the software server and the application server, eliminating the need for the software client to re-authorize the first application item. Compared with the existing access implementation to the first application item, this effectively reduces the number and repeatability of authorization operations for accessing the first application item, thereby better improving the convenience of native application software in accessing the first application item product, and better improving the user experience after the first application item is integrated into the native application software.

[0160] Furthermore, the first feedback module 620 is specifically used for:

[0161] Obtain a request receiving timestamp of the access link acquisition request, and extract a current account identifier in the authorized account information and an identity authorization account identifier of the current account relative to the second application item;

[0162] Generate an account signature result based on the current account ID, the identity authorization account ID, the request receiving timestamp, and the preset timeout timestamp;

[0163] The account signature information is formed based on the account signature result, combined with the uniform resource identifier of the first application item, and encapsulated to form an application access link.

[0164] Optionally, the device further includes: an identity authentication unit.

[0165] The identity authentication unit is used to perform identity authentication of the current account based on the account signature information and pre-stored benchmark verification information after receiving the account authorization request generated by the application server based on the account signature information. The benchmark verification information application accesses the account signature information contained in the link.

[0166] Furthermore, the second feedback module 640 is specifically used for:

[0167] Extract the identity authorization account identifier contained in the account signature information in the account authorization request;

[0168] Find the open identifier corresponding to the identity authorization account identifier from the pre-stored authorization account mapping information;

[0169] Access the open platform of the third-party application, find the first application authorization identifier corresponding to the open identifier, and use it as the target authorization information.

[0170] The application access device provided in the embodiments of the present disclosure can execute the application access method provided in any embodiment of the present disclosure, and has the corresponding functional modules and beneficial effects of the execution method.

[0171] It is worth noting that the various units and modules included in the above-mentioned device are only divided according to functional logic, but are not limited to the above-mentioned division, as long as the corresponding functions can be achieved; in addition, the specific names of the functional units are only for the convenience of distinguishing each other, and are not used to limit the protection scope of the embodiments of the present disclosure.

[0172] Figure 7 A schematic diagram of the structure of an application access device provided by an embodiment of the present disclosure, configured in an application server of a first application item, such as Figure 7 As shown, the device includes: a request generating module 710, a third receiving module 720 and an information sending module 730.

[0173] The request generation module 710 is used to respond to the software client's access to the application access link, obtain the account signature information contained therein and generate an account authorization request. The application access link is obtained from the software server after being triggered by the software client's access to the first application item under the current account. The account signature information is generated by the software server through the authorized account information of the current account relative to the second application item. The second application item and the first application item are authorized applications on the same open platform;

[0174] The third receiving module 720 is used to send the account authorization request to the software server and receive the target authorization information sent by the software server, where the target authorization information is determined by the software server when authorizing the current account to the first application item based on the account authorization request;

[0175] The information sending module 730 is used to query the application data information of the first application item from the open platform based on the target authorization information and send the information to the software client.

[0176] Furthermore, the authorized account information includes the current account identifier and the identity authorization account identifier determined in advance when the current account is authorized to the second application item; the account signature information includes: the current account identifier, the identity authorization account identifier, the request reception timestamp and the timeout timestamp; the account signature information is also used by the software server to authenticate the current account.

[0177] The application access device provided in the embodiments of the present disclosure can execute the application access method provided in any embodiment of the present disclosure, and has the corresponding functional modules and beneficial effects of the execution method.

[0178] It is worth noting that the various units and modules included in the above-mentioned device are only divided according to functional logic, but are not limited to the above-mentioned division, as long as the corresponding functions can be achieved; in addition, the specific names of the functional units are only for the convenience of distinguishing each other, and are not used to limit the protection scope of the embodiments of the present disclosure.

[0179] Figure 8 This is a schematic diagram of the structure of an electronic device provided by an embodiment of the present disclosure. Figure 8 , which shows an electronic device (eg, Figure 8 The terminal device in the embodiment of the present disclosure may include but is not limited to mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 8The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0180] like Figure 8 As shown, the electronic device 800 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 801, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 802 or a program loaded from a storage device 808 into a random access memory (RAM) 803. In the RAM 803, various programs and data required for the operation of the electronic device 800 are also stored. The processing device 801, the ROM 802, and the RAM 803 are connected to each other via a bus 804. An edit / output (I / O) interface 805 is also connected to the bus 804.

[0181] Typically, the following devices may be connected to the I / O interface 805: input devices 806 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; output devices 807 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; storage devices 808 including, for example, a magnetic tape, a hard disk, etc.; and communication devices 809. The communication device 809 may allow the electronic device 800 to communicate with other devices wirelessly or by wire to exchange data. Although Figure 8 The electronic device 800 is shown with various devices, but it should be understood that it is not required to implement or possess all the devices shown. More or fewer devices may be implemented or possessed instead.

[0182] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a non-transitory computer-readable medium, and the computer program contains program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device 809, or installed from a storage device 808, or installed from a ROM 802. When the computer program is executed by the processing device 801, the above-mentioned functions defined in the method of the embodiment of the present disclosure are executed.

[0183] The names of the messages or information exchanged between multiple devices in the embodiments of the present disclosure are only used for illustrative purposes and are not used to limit the scope of these messages or information.

[0184] The electronic device provided by the embodiment of the present disclosure and the application access method provided by the above embodiment belong to the same inventive concept. The technical details not fully described in this embodiment can be referred to the above embodiment, and this embodiment has the same beneficial effects as the above embodiment.

[0185] The embodiment of the present disclosure provides a computer storage medium on which a computer program is stored. When the program is executed by a processor, the application access method provided by the above embodiment is implemented.

[0186] It should be noted that the computer-readable medium disclosed above may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that may be used by or in combination with an instruction execution system, device or device. In the present disclosure, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, in which a computer-readable program code is carried. This propagated data signal may take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. The computer readable signal medium may also be any computer readable medium other than a computer readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer readable medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0187] In some embodiments, the client and the server may communicate using any currently known or future developed network protocol such as HTTP (HyperText Transfer Protocol), and may be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), an internet (e.g., the Internet), and a peer-to-peer network (e.g., an adhoc peer-to-peer network), as well as any currently known or future developed network.

[0188] The computer-readable medium may be included in the electronic device, or may exist independently without being incorporated into the electronic device.

[0189] The computer-readable medium carries one or more programs. When the one or more programs are executed by the electronic device, the electronic device:

[0190] The above-mentioned computer-readable medium carries one or more programs. When the above-mentioned one or more programs are executed by the electronic device, the electronic device: determines the current resource usage information corresponding to each resource item on the execution terminal during the operation of the application software; determines the target resource items that currently meet the resource allocation warning conditions based on each of the current resource usage information; and adjusts the resource allocation logic of each of the target resource items during the operation of the application software.

[0191] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages ​​or a combination thereof, including, but not limited to, object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving 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 may be connected to an external computer (e.g., through the Internet using an Internet service provider).

[0192] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architectures, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flowchart or block diagram may represent an embodiment.

[0193] The units involved in the embodiments described in the present disclosure may be implemented by software or by hardware. The name of the unit does not, in some cases, constitute a limitation on the unit itself. For example, the first acquisition unit may also be described as a "unit for acquiring at least two Internet Protocol addresses". The functions described above in this document may be at least partially performed by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

[0194] In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0195] A module, a program segment, or a portion of a code that contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions marked in the boxes may also occur in an order different from that marked in the accompanying drawings. For example, two boxes represented in succession may actually be executed substantially in parallel, and they may sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flow chart, and the combination of boxes in the block diagram and / or flow chart, may be implemented using a dedicated hardware-based system that performs a specified function or operation, or may be implemented using a combination of dedicated hardware and computer instructions.

[0196] According to one or more embodiments of the present disclosure, [Example 1] provides an application access method, which is applied to a software client, and the method includes: in response to an access trigger request for a first application item under a current account, sending an access link acquisition request for the first application item to a software server, wherein the access link acquisition request includes the authorized account information of the current account relative to the second application item, the account information of the second application item and the first application item are both recorded in an open platform provided by the same identity provider, and the second application item has completed the authorization with the current account through the open platform, and the software server is the background server of the software client; receiving an application access link fed back by the software server, the application access link includes account signature information generated based on the authorized account information; accessing the application server of the first application item based on the application access link, and displaying the application data information sent by the application server, wherein the application data information is fed back by the application server after completing the authorization from the current account to the first application item based on the account signature information.

[0197] According to one or more embodiments of the present disclosure, [Example 2] provides an application access method, which includes: the authorized account information includes the current account identifier and the identity authorization account identifier determined in advance when the current account is authorized to the second application item; the account signature information includes: the current account identifier, the identity authorization account identifier, the request reception timestamp and the timeout timestamp; the account signature information is also used for the software server to authenticate the current account.

[0198] According to one or more embodiments of the present disclosure, [Example Three] provides an application access method, which is applied to a software server, and the method includes: receiving an access link acquisition request sent by a software client to a first application item, the access link acquisition request is generated by the software client after receiving an access trigger request to the first application item under the current account, and includes the authorized account information of the current account to the second application item, the account information of the second application item and the first application item are both recorded in an open platform provided by the same identity provider, and the second application item has completed the authorization with the current account through the open platform, and the software server is the background server of the software client; based on the authorized account information, an application access link including account signature information is generated and fed back to the software client, so that the software client can access the application server of the first application item through the application access link; receiving an account authorization request sent by the application server, the account authorization request carrying the account signature information; based on the account authorization request, determining the target authorization information for authorizing the current account to the first application item, and feeding back the target authorization information to the application server, so that the application server can send application data information to the software client based on the target authorization information.

[0199] According to one or more embodiments of the present disclosure, [Example Four] provides an application access method, which includes further optimization of generating an application access link containing account signature information based on authorized account information, specifically including: obtaining a request reception timestamp of an access link acquisition request, and extracting the current account identifier in the authorized account information and the identity authorization account identifier of the current account relative to the second application item; generating an account signature result based on the current account identifier, the identity authorization account identifier, the request reception timestamp and a preset timeout timestamp; constructing the account signature information based on the account signature result, combining it with the uniform resource identifier of the first application item, and encapsulating it to form an application access link.

[0200] According to one or more embodiments of the present disclosure, [Example Five] provides an application access method. After receiving an account authorization request generated by an application server based on account signature information, the method also includes: performing identity authentication of the current account based on the account signature information and pre-stored benchmark verification information, and the benchmark verification information application access link includes the account signature information.

[0201] According to one or more embodiments of the present disclosure, [Example Six] provides an application access method, which includes further optimizing the target authorization information for authorizing the current account to the first application item based on the account authorization request. Specifically, the optimization can be as follows: extracting the identity authorization account identifier contained in the account signature information in the account authorization request; searching for the open identifier corresponding to the identity authorization account identifier from the pre-stored authorization account mapping information; accessing the open platform of the third-party application, searching for the first application item authorization identifier corresponding to the open identifier, and using it as the target authorization information.

[0202] According to one or more embodiments of the present disclosure, [Example 7] provides an application access method, which is applied to an application server of a first application item, the method comprising: responding to a software client's access to an application access link, obtaining the account signature information contained therein and generating an account authorization request, the application access link is obtained from the software server after being triggered by the software client accessing the first application item under the current account, the account signature information is generated by the software server through the authorized account information of the current account relative to the second application item, the account information of the second application item and the first application item are both recorded in an open platform provided by the same identity provider, and the second application item has completed authorization with the current account through the open platform, and the software server is a background server of the software client;

[0203] An account authorization request is sent to the software server, and target authorization information sent by the software server is received. The target authorization information is determined by the software server when authorizing the current account to the first application item based on the account authorization request; based on the target authorization information, application data information of the first application item is queried from the open platform and sent to the software client.

[0204] According to one or more embodiments of the present disclosure, [Example Eight] provides an application access device, which is configured on a software client and includes: a request sending module, which is used to respond to an access trigger request for a first application item under a current account, and send an access link acquisition request for the first application item to a software server, wherein the access link acquisition request includes the authorized account information of the current account relative to the second application item, and the account information of the second application item and the first application item are both recorded in an open platform provided by the same identity provider, and the second application item has completed the authorization with the current account through the open platform, and the software server is the background server of the software client; a link receiving module, which is used to receive an application access link fed back by the software server, and the application access link includes account signature information generated based on the authorized account information; an information display module, which is used to access the application server of the first application item based on the application access link, and display the application data information sent by the application server, wherein the application data information is fed back by the application server after the authorization of the current account to the first application item is completed based on the account signature information.

[0205] According to one or more embodiments of the present disclosure, [Example Nine] provides an application access device, which is configured on a software server and includes: a first receiving module, which is used to receive an access link acquisition request sent by a software client to a first application item, the access link acquisition request is generated by the software client after receiving an access trigger request to the first application item under the current account, and includes the authorized account information of the current account to the second application item, the account information of the second application item and the first application item are both recorded in an open platform provided by the same identity provider, and the second application item has completed the authorization with the current account through the open platform, and the software server is the background server of the software client; a first feedback module, which is used to generate an application access link including account signature information based on the authorized account information and feedback it to the software client, so that the software client can access the application server of the first application item through the application access link; a second receiving module, which is used to receive an account authorization request sent by the application server, the account authorization request carrying the account signature information; a second feedback module, which is used to determine the target authorization information for authorizing the current account to the first application item based on the account authorization request, and feedback the target authorization information to the application server, so that the application server can send application data information to the software client based on the target authorization information.

[0206] According to one or more embodiments of the present disclosure, [Example 10] provides an application access device, which is configured on an application server of a first application item, including:

[0207] A request generation module is used to respond to the software client's access to the application access link, obtain the account signature information contained therein and generate an account authorization request. The application access link is obtained from the software server after the software client accesses the first application item under the current account. The account signature information is generated by the software server through the authorized account information of the current account relative to the second application item. The account information of the second application item and the first application item are both recorded in the open platform provided by the same identity provider, and the second application item has completed the authorization with the current account through the open platform. The software server is the background server of the software client; a third receiving module is used to send the account authorization request to the software server and receive the target authorization information sent by the software server. The target authorization information is determined when the software server authorizes the current account to the first application item based on the account authorization request; an information sending module is used to query the application data information of the first application item from the open platform based on the target authorization information and send it to the software client.

[0208] The above description is only a preferred embodiment of the present disclosure and an explanation of the technical principles used. Those skilled in the art should understand that the scope of disclosure involved in the present disclosure is not limited to the technical solutions formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above disclosed concept. For example, the above features are replaced with the technical features with similar functions disclosed in the present disclosure (but not limited to) by each other to form a technical solution.

[0209] In addition, although each operation is described in a specific order, this should not be understood as requiring these operations to be performed in the specific order shown or in a sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although some specific implementation details are included in the above discussion, these should not be interpreted as limiting the scope of the present disclosure. Some features described in the context of a separate embodiment can also be implemented in a single embodiment in combination. On the contrary, the various features described in the context of a single embodiment can also be implemented in multiple embodiments individually or in any suitable sub-combination mode.

[0210] Although the subject matter has been described in language specific to structural features and / or methodological logical actions, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. On the contrary, the specific features and actions described above are merely example forms of implementing the claims.

Claims

1. An application access method, characterized in that: Applicable to software clients, including: In response to an access trigger request for a first application item under the current account, an access link acquisition request for the first application item is sent to a software server, wherein the access link acquisition request includes the authorized account information of the current account for a second application item, the account information of the second application item and the first application item are both recorded in an open platform provided by the same identity provider, and the second application item has completed the authorization with the current account through the open platform, and the software server is the background server of the software client; Receive an application access link fed back by the software server, wherein the application access link includes account signature information generated based on the authorized account information; The application server of the first application item is accessed based on the application access link, and the application data information sent by the application server is displayed, wherein the application data information is fed back by the application server after completing the authorization between the current account and the first application item based on the account signature information.

2. The method according to claim 1, characterized in that The authorized account information includes a current account identifier and an identity authorization account identifier determined in advance when the current account is authorized to the second application item; The account signature information includes: the current account identifier, the identity authorization account identifier, the request receiving timestamp and the timeout timestamp; The account signature information is also used by the software server to authenticate the current account.

3. An application access method, characterized in that: Applicable to software servers, including: Receive an access link acquisition request sent by a software client to a first application item, wherein the access link acquisition request is generated by the software client after receiving an access trigger request to the first application item under a current account, and includes authorized account information of the current account to a second application item, wherein the account information of the second application item and the first application item are both recorded in an open platform provided by the same identity provider, and the second application item has completed authorization with the current account through the open platform; Generate an application access link containing account signature information based on the authorized account information and feed it back to the software client, so that the software client can access the application server of the first application item through the application access link; Receiving an account authorization request sent by the application server, wherein the account authorization request carries the account signature information; Based on the account authorization request, target authorization information for authorizing the current account to the first application item is determined, and the target authorization information is fed back to the application server, so that the application server sends application data information to the software client based on the target authorization information.

4. The method according to claim 3, characterized in that The generating an application access link including account signature information based on the authorized account information includes: Obtaining a request receiving timestamp of the access link acquisition request, and extracting a current account identifier and an identity authorization account identifier of the current account relative to the second application item from the authorization account information; Generate an account signature result based on the current account identifier, the identity authorization account identifier, the request receiving timestamp and a preset timeout timestamp; Account signature information is formed based on the account signature result, combined with the uniform resource identifier of the first application item, and encapsulated to form an application access link.

5. The method according to claim 3, characterized in that: After receiving the account authorization request generated by the application server based on the account signature information, the method further includes: The identity verification of the current account is performed based on the account signature information and pre-stored benchmark verification information, where the benchmark verification information is the account signature information included in the application access link.

6. The method according to claim 3, characterized in that The determining, based on the account authorization request, target authorization information for authorizing the current account to the first application item includes: Extract the identity authorization account identifier contained in the account signature information in the account authorization request; Searching for an open identifier corresponding to the identity authorization account identifier from pre-stored authorization account mapping information; The open platform is accessed to search for a first application authorization identifier corresponding to the open identifier and use the first application authorization identifier as the target authorization information.

7. An application access method, characterized in that: The application server applied to the first application item includes: In response to the software client's access to the application access link, obtaining the account signature information contained therein and generating an account authorization request, the application access link is obtained from the software server after being triggered by the software client accessing the first application item under the current account, the account signature information is generated by the software server through the authorized account information of the current account relative to the second application item, the account information of the second application item and the first application item are both recorded in the open platform provided by the same identity provider, and the second application item has completed the authorization with the current account through the open platform; Sending the account authorization request to the software server, and receiving target authorization information sent by the software server, the target authorization information being determined by the software server when authorizing the current account to the first application item based on the account authorization request; Based on the target authorization information, the application data information of the first application item is queried from the open platform and sent to the software client.

8. An application access device, characterized in that: Configured on the software client, including: A request sending module, used for sending an access link acquisition request for a first application item to a software server in response to an access trigger request for the first application item under the current account, wherein the access link acquisition request includes the authorized account information of the current account for a second application item, the account information of the second application item and the first application item are both recorded in an open platform provided by the same identity provider, and the second application item has completed the authorization with the current account through the open platform, and the software server is the background server of the software client; A link receiving module, used to receive an application access link fed back by the software server, wherein the application access link includes account signature information generated based on the authorized account information; An information display module is used to access the application server of the first application item based on the application access link and display the application data information sent by the application server, wherein the application data information is fed back by the application server after the authorization of the current account to the first application item is completed based on the account signature information.

9. An application access device, characterized in that: Configured on the software server, including: A first receiving module, used to receive an access link acquisition request sent by a software client to a first application item, wherein the access link acquisition request is generated by the software client after receiving an access trigger request to the first application item under a current account, and includes authorized account information of the current account to a second application item, wherein the account information of the second application item and the first application item are both recorded in an open platform provided by the same identity provider, and the second application item has completed authorization with the current account through the open platform; A first feedback module, configured to generate an application access link including account signature information based on the authorized account information and feed the link back to the software client, so that the software client can access the application server of the first application item through the application access link; A second receiving module is used to receive an account authorization request sent by the application server, wherein the account authorization request carries the account signature information; The second feedback module is used to determine the target authorization information for authorizing the current account to the first application item based on the account authorization request, and feed back the target authorization information to the application server, so that the application server sends application data information to the software client based on the target authorization information.

10. An application access device, characterized in that: The application server configured in the first application item includes: A request generation module, for responding to the software client's access to the application access link, obtaining the account signature information contained therein and generating an account authorization request, wherein the application access link is obtained from the software server after being triggered by the software client's access to the first application item under the current account, and the account signature information is generated by the software server through the authorized account information of the current account relative to the second application item, the account information of the second application item and the first application item are both recorded in an open platform provided by the same identity provider, and the second application item has completed the authorization with the current account through the open platform; a third receiving module, configured to send the account authorization request to the software server, and receive target authorization information sent by the software server, wherein the target authorization information is determined by the software server when authorizing the current account to the first application item based on the account authorization request; An information sending module is used to query the application data information of the first application item from the open platform based on the target authorization information and send the information to the software client.

11. An electronic device, characterized in that: The electronic device comprises: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the application access method as described in any one of claims 1-7.

12. A storage medium containing computer executable instructions, characterized in that: The computer executable instructions are used to perform the application access method according to any one of claims 1 to 7 when executed by a computer processor.

Images