Webpage access method, apparatus, device, storage medium, and program product

Abstract

The application discloses a webpage access method and device, equipment, a storage medium and a program product, and applies to the technical field of safe access. The method is applied to a business end and includes the following steps: acquiring webpage jump parameters sent by a third-party client, wherein the webpage jump parameters comprise authentication information, and the authentication information is authentication information that the business end previously issues to the third-party client through a trusted third-party server; checking the authentication information of the webpage jump parameters; in the case that the authentication information of the webpage jump parameters passes the check, returning webpage static resources corresponding to the webpage jump parameters to the third-party client, so that the third-party client accesses a target webpage based on the webpage static resources. According to the embodiment of the application, the safe access to the webpage of the business end can be realized in the case that the third-party client does not integrate a webpage SDK.

Description

TECHNICAL FIELD

[0001] The application belongs to the technical field of secure access, and particularly relates to a webpage access method and device, equipment, a storage medium and a program product. BACKGROUND

[0002] Due to high privacy of the business carried by the bank system, when the bank system is accessed by an external third party, there is a high security requirement, and the identity of the access party needs to be verified, and the content needs to be encrypted.

[0003] To solve the problems of security and encryption when the bank system is accessed by a third party, many banks provide a software development kit (SDK) for external third parties to integrate. Among them, a webpage SDK for accessing bank webpages can be integrated by a client of an external third party. The integrated webpage SDK has the ability to authenticate a jump party and encrypt data, and data transmitted by a webpage is considered difficult to intercept and tamper. In actual use scenarios, there are many clients operated by a third-party company. To ensure that the client can normally access the bank webpage, the webpage SDK needs to be integrated in each client.

[0004] However, integrating the webpage SDK may cause a burden to the third-party company, such as expansion of the client size, increase of internal administrative approval of the third-party company, and the like, which causes some third-party companies to be difficult to integrate the webpage SDK in the client. In the case that the third-party client does not integrate the webpage SDK, how to realize secure access to the webpage becomes a problem to be solved at present. SUMMARY

[0005] Embodiments of the application provide a webpage access method, device, equipment and computer storage medium, which can realize secure access to a business-end webpage in the case that a third-party client does not integrate a webpage SDK.

[0006] In a first aspect, embodiments of the application provide a webpage access method, which is applied to a business end, and the method comprises:

[0007] obtaining webpage jump parameters sent by a third-party client, wherein the webpage jump parameters comprise authentication information, and the authentication information is authentication information issued by a trusted third-party service end to the third-party client in advance by the business end;

[0008] verifying the authentication information of the webpage jump parameters;

[0009] in a case that the authentication information of the webpage jump parameters passes the verification, returning webpage static resources corresponding to the webpage jump parameters to the third-party client, so as to enable the third-party client to access a target webpage based on the webpage static resources.

[0010] In some possible implementation manners, before the web page jump parameter sent by the third-party client is acquired, the method further includes:

[0011] receiving an authentication information acquisition request sent by the trusted third-party server, the authentication information acquisition request being generated by the trusted third-party server in response to an authentication information acquisition notification sent by the third-party client;

[0012] generating authentication information corresponding to the authentication information acquisition request;

[0013] sending the authentication information to the trusted third-party server, so that the trusted third-party server forwards the authentication information to the third-party client.

[0014] In some possible implementation manners, the trusted third-party server communicates with the business server through an interface software development kit (SDK), and the interface SDK is provided by the business server to the trusted third-party server.

[0015] receiving an authentication information acquisition request sent by the trusted third-party server, including:

[0016] receiving an authentication information acquisition request sent by the trusted third-party server through the interface SDK.

[0017] In some possible implementation manners, after the authentication information corresponding to the authentication information acquisition request is generated, the method further includes:

[0018] recording an expiration time of the authentication information;

[0019] verifying the authentication information, including:

[0020] verifying validity of the authentication information according to the expiration time of the authentication information and a sending time of the web page jump parameter.

[0021] In some possible implementation manners, in a case where the authentication information of the web page jump parameter passes verification, the method further includes:

[0022] acquiring a data acquisition request sent by the third-party client, the data acquisition request being generated based on a web page operation of the user on the target web page, and the data acquisition request including the authentication information;

[0023] verifying the authentication information of the data acquisition request;

[0024] in a case where the authentication information of the data acquisition request passes verification, returning target data corresponding to the data acquisition request to the target web page.

[0025] In some possible implementation manners, the authentication information includes a token.

[0026] In a second aspect, an embodiment of the present application provides a webpage access device, the device being applied to a business end, and the device comprises:

[0027] The obtaining module is configured to obtain webpage jump parameters sent by the third-party client, the webpage jump parameters comprising authentication information, the authentication information being authentication information sent by the business end to the third-party client in advance through a trusted third-party server;

[0028] The checking module is configured to check the authentication information of the webpage jump parameters;

[0029] The returning module is configured to return webpage static resources corresponding to the webpage jump parameters to the third-party client in a case where the authentication information of the webpage jump parameters passes the check, so as to enable the third-party client to access a target webpage based on the webpage static resources.

[0030] In a third aspect, an embodiment of the present application provides a webpage access device, the device comprising:

[0031] A processor and a memory storing computer program instructions; the processor implements the webpage access method of any one of the above aspects when executing the computer program instructions.

[0032] In a fourth aspect, an embodiment of the present application provides a computer storage medium, the computer readable storage medium storing computer program instructions, the computer program instructions being executed by a processor to implement the webpage access method of any one of the above aspects.

[0033] In a fifth aspect, an embodiment of the present application provides a computer program product, instructions in the computer program product being executed by a processor of an electronic device to enable the electronic device to execute the webpage access method of any one of the above aspects.

[0034] The webpage access method, device, equipment and computer storage medium provided by the embodiments of the present application can be applied to a business system. The embodiments of the present application can obtain webpage jump parameters sent by a third-party client, the webpage jump parameters comprising authentication information. The authentication information is authentication information sent by a business end to a third-party client in advance through a trusted third-party server, and has high credibility. Then, the authentication information can be checked. In a case where the authentication information passes the check, webpage static resources corresponding to the webpage jump parameters are returned to the third-party client, so as to enable the third-party client to access a target webpage based on the webpage static resources. In this way, in a case where the third-party client does not integrate a webpage SDK provided by the business end, the business end can authenticate the third-party client through the authentication information, and allow the third-party client to access a webpage in a case where the authentication passes. In this way, the secure access to the business end webpage can be realized in a case where the third-party client does not integrate the webpage SDK. BRIEF DESCRIPTION OF DRAWINGS

[0035] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the embodiments of the present application will be briefly introduced as follows, and other drawings can be obtained by those of ordinary skill in the art without any creative effort on the premise that no creative effort is needed.

[0036] Figure 1 is a flow diagram of a webpage access method provided by an embodiment of the present application;

[0037] Figure 2 is a flow diagram of a webpage access method provided by another embodiment of the present application;

[0038] Figure 3 is a structural diagram of a webpage access device provided by another embodiment of the present application;

[0039] Figure 4 is a structural diagram of a webpage access device provided by another embodiment of the present application. DETAILED DESCRIPTION

[0040] The features and exemplary embodiments of various aspects of the present application will be described in detail below, in order to make the purposes, technical solutions and advantages of the present application more clear and apparent, the present application will be further described in detail below in combination with the drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain the present application, but not to limit the present application. The present application can be implemented without some of these specific details by those skilled in the art. The following description of the embodiments is only to provide a better understanding of the present application by showing examples of the present application.

[0041] It should be noted that, in this paper, relationship terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between the entities or operations. Moreover, the terms "include", "contain" or any other variants thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements not only includes those elements, but also includes other elements not explicitly listed or inherent to such process, method, article or device. Without more limitation, the elements defined by the statement "include" do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0042] It should be noted that the acquisition, storage, use and processing of data in the embodiments of the present application all comply with the relevant provisions of national laws and regulations.

[0043] It should be noted that in the embodiments of the present application, some software, components, models and the like in the prior art may be mentioned, which should be considered as exemplary, and the purpose is only to illustrate the feasibility of the implementation of the technical solutions of the present application, but does not mean that the applicant has or will necessarily use the scheme.

[0044] To solve the security, encryption and other problems when the third party accesses the bank system, many banks provide a software development kit (Software Development Kit, SDK) for external third parties to integrate. Among them, the web SDK for accessing the bank webpage can be integrated by the client of the external third party. The integrated web SDK has the ability to authenticate the jump party and encrypt data, and the data transmitted by the webpage is considered to be difficult to intercept and tamper. In actual use scenarios, there are many clients operated by third-party companies. In order to ensure that the client can normally access the bank webpage, it is necessary to integrate the web SDK in each client.

[0045] However, integrating the web SDK may cause burden to the third-party company, such as client volume expansion, increase of internal administrative approval of the third-party company, etc., resulting in that some third-party companies are difficult to integrate the web SDK in the client.

[0046] In the related art, when the client accesses the webpage without integrating the web SDK of the third-party company, the client usually directly jumps to the webpage. This method has the risk of being attacked by unauthorized attack or tampered data.

[0047] To solve the problems in the prior art, the embodiments of the present application provide a webpage access method, device, equipment and computer storage medium.

[0048] Firstly, the webpage access method provided by the embodiments of the present application will be introduced.

[0049] The webpage access method of the embodiments of the present application will be described in detail below in combination with the drawings.

[0050] Figure 1 A flowchart of a webpage access method provided by an embodiment of the present application is shown. The method can be applied to a business end. As shown in Figure 1 The method can include the following steps S110 to S130.

[0051] S110, obtaining webpage jump parameters sent by a third-party client, the webpage jump parameters including authentication information, the authentication information being authentication information issued by a trusted third-party service end to the third-party client in advance by the business end.

[0052] In step S110, the trusted third-party server can include a third-party server trusted by the business server. The trusted third-party server can establish trust with the business server in a manner known in the art, which is not limited in the embodiments of the present application. For example, the business server can generate a self-signed certificate, and for a third-party server that can be trusted, a root certificate can be issued, and the third-party server installed with the root certificate is the trusted third-party server. For example, the business server can provide an interface SDK for accessing the service interface of the business server for a third-party server that can be trusted, and the third-party server with the interface SDK is the trusted third-party server. The third-party client can include a client related to the trusted third-party server, for example, can include but is not limited to a client of a third-party platform that belongs to the same institution, the same group or the same enterprise platform as the trusted third-party server.

[0053] In step S110, the authentication information can include authentication information corresponding to any authentication mechanism. For example, the authentication information can include but is not limited to session control (Session) authentication information or a token.

[0054] S120, the authentication information of the web page jump parameter is checked.

[0055] In step S120, the specific checking method can be selected according to the type of the authentication information, which is not limited herein. For example, the authentication information checking can include but is not limited to at least one of checking the legality (for example, whether the authentication information is listed in the blacklist, etc.) and validity of the authentication information.

[0056] S130, in the case that the authentication information of the web page jump parameter passes the check, the web page static resource corresponding to the web page jump parameter is returned to the third-party client, so as to be used by the third-party client to access the target web page based on the web page static resource.

[0057] For example, the third-party client can present complete web page content based on the web page static resource.

[0058] The webpage access method of the embodiments of the present application can be applied to a business system. The embodiments of the present application can obtain webpage jump parameters sent by a third-party client, the webpage jump parameters comprising authentication information. The authentication information is authentication information issued by a trusted third-party server to the third-party client in advance by the business end, and has high credibility. Then, the authentication information can be checked. In the case that the authentication information passes the check, webpage static resources corresponding to the webpage jump parameters are returned to the third-party client, so as to be used by the third-party client to access a target webpage based on the webpage static resources. In this way, in the case that the third-party client does not integrate a webpage SDK provided by the business end, the business end can authenticate the third-party client through the authentication information, and allow the third-party client to access the webpage in the case that the authentication passes. In this way, the secure access to the webpage of the business end can be realized in the case that the third-party client does not integrate the webpage SDK.

[0059] The webpage access method of the embodiments of the present application can allow the third-party client to realize the secure access to the webpage of the business end in the case of integrating the webpage SDK, and the integration requirement of the third-party client is relatively light. For a third-party platform that operates multiple clients, the embodiments of the present application significantly reduce the burden of the third-party platform, and are beneficial to the rapid application in the clients of the third-party platform.

[0060] In one embodiment, before obtaining the webpage jump parameters sent by the third-party client, the method can further comprise:

[0061] receiving an authentication information obtaining request sent by the trusted third-party server, the authentication information obtaining request being generated by the trusted third-party server in response to an authentication information obtaining notification sent by the third-party client.

[0062] generating authentication information corresponding to the authentication information obtaining request.

[0063] sending the authentication information to the trusted third-party server, so as to be forwarded by the trusted third-party server to the third-party client.

[0064] In the above embodiments, in the case that the third-party client needs to access the webpage, the third-party client can send an authentication information obtaining notification to the trusted third-party server. Correspondingly, the trusted third-party server can send an authentication information obtaining request to the business end to obtain the authentication information. The business end generates corresponding authentication information based on the received authentication information obtaining request, and returns the authentication information to the trusted third-party server, so as to be forwarded by the trusted third-party server to the third-party. In this way, the third-party client can obtain the authentication information from the business end through the trusted third-party server in the case that the third-party client does not integrate the webpage SDK, so as to access the webpage through the authentication information subsequently. In this way, the security of the third-party client accessing the webpage of the business end is improved.

[0065] In an embodiment, the trusted third-party server can communicate with the business server through an interface software development kit (SDK). The interface SDK can be provided by the business server to the trusted third-party server.

[0066] The authentication information acquisition request sent by the trusted third-party server is received, which can specifically include:

[0067] The authentication information acquisition request sent by the trusted third-party server through the interface SDK is received.

[0068] Correspondingly, in an example, the authentication information is sent to the trusted third-party server for forwarding by the trusted third-party server to the third-party client, which can specifically include:

[0069] The authentication information is sent to the trusted third-party server through the interface SDK for forwarding by the trusted third-party server to the third-party client.

[0070] In the above embodiments, the interface SDK can include an SDK provided by the business server for accessing the service interface of the business server. The interface SDK is usually integrated into the server and has the ability to authenticate the calling party and encrypt data after integration. In this way, during communication between the trusted third-party server and the business server, the data transmitted between the two parties is secure and encrypted, making it difficult to be intercepted and tampered with, thereby improving the security and confidentiality of the authentication information. In this way, the credibility of the authentication information can be improved, and the security of the third-party client accessing the business server webpage can be improved.

[0071] In an embodiment, after generating the authentication information corresponding to the authentication information acquisition request, the method can further include:

[0072] The expiration time of the authentication information is recorded.

[0073] The authentication information is verified, which can specifically include:

[0074] The validity of the authentication information is verified according to the expiration time of the authentication information and the sending time of the webpage jump parameter.

[0075] In the above embodiments, after generating the authentication information, the business server can record the expiration time of the authentication information to manage the life cycle of the authentication time. After receiving the webpage jump parameter sent by the third-party client, the authentication information can be verified to determine the validity of the authentication information. In this way, the management of the authentication information can be realized, the accuracy of the authentication information verification can be improved, and the security of the third-party client accessing the business server webpage can be improved.

[0076] In an embodiment, the webpage jump parameter can include encrypted authentication information.

[0077] Before the authentication information of the webpage jump parameter is checked, the method can further include: decrypting the authentication information of the webpage jump parameter. In the above embodiments, the encryption and decryption methods can be known in the art, for example, can be encryption and decryption technologies based on symmetric encryption algorithms, or can be encryption technologies based on asymmetric encryption algorithms, and the embodiments of the present application do not limit this. Illustratively, after the service end generates the authentication information, the decryption key corresponding to the authentication information can also be recorded, and after receiving the webpage jump parameter, the authentication information can be decrypted based on the decryption key.

[0078] The above embodiments can reduce the risk of tampering or being obtained by attackers in the transmission process of the network jump parameter by encrypting the authentication information, thereby further improving the security of webpage access.

[0079] In one embodiment, the method can further include: returning a verification failure result to the third-party client in the case that the authentication information of the webpage jump parameter fails to pass the check.

[0080] In this way, the user can be prompted that the webpage access fails. In some cases, for example, in the case that the authentication information is expired, the user can obtain the authentication information based on the prompt of the verification failure result and send an authentication information obtaining notification to the trusted third-party server to reobtain the authentication information. In this way, the user experience can be improved.

[0081] In one embodiment, the webpage static resource can include a public webpage static resource and a non-public webpage static resource.

[0082] Before the authentication information of the webpage jump parameter is checked, the method can include: returning the public webpage static resource to the third-party client for displaying public information on the third-party client.

[0083] In the case that the authentication information of the webpage jump parameter passes the check, returning the webpage static resource corresponding to the webpage jump parameter to the third-party client can include: in the case that the authentication information of the webpage jump parameter passes the check, returning the non-public webpage static resource corresponding to the webpage jump parameter to the third-party client.

[0084] In the above embodiments, the public webpage static resource can include a webpage static resource related to public information of the business end, for example, can include push information or advertisements that are public to all users of the business end. The public webpage static resource can include a webpage static resource related to the business corresponding to the webpage jump parameter. In the above embodiments, before the authentication information of the webpage jump parameter is checked, the public webpage static resource can be returned to the third-party client for displaying the public information on the third-party client. In this way, the public webpage static resource can be loaded in advance, and when the non-public webpage static resource is obtained subsequently, only the non-public webpage static resource needs to be loaded. In this way, the loading rate of the webpage static resource can be improved, thereby improving the user experience.

[0085] In one embodiment, in a case where the authentication information of the webpage jump parameter passes the check, the webpage static resource corresponding to the webpage jump parameter is returned to the third-party client for the third-party client to access the webpage based on the webpage static resource. After the webpage static resource, the method can further include:

[0086] Obtaining a data acquisition request sent by the third-party client, the data acquisition request being generated based on a webpage operation of the user on the target webpage, the data acquisition request including authentication information.

[0087] Checking the authentication information of the data acquisition request.

[0088] In a case where the authentication information of the data acquisition request passes the check, returning target data corresponding to the data acquisition request to the target webpage.

[0089] According to the above embodiments, when the user performs an operation on the webpage displayed on the third-party client and triggers a data acquisition request, the authentication information needs to be carried. The business end checks the authentication information, and after the check passes, the target data is returned to the third-party client. In this way, the third-party client can safely acquire the data of the business end through the webpage without integrating the webpage SDK, thereby improving the data interaction security between the third-party client and the business end.

[0090] In one embodiment, after the authentication information of the data acquisition request is checked, the method can further include: in a case where the authentication information of the data acquisition request does not pass the check, returning a rejection information to the target webpage for rejecting the data acquisition request.

[0091] In one embodiment, the authentication information can include a token.

[0092] In the above embodiments, the token can be signed using an encryption algorithm to ensure that it is not tampered with during transmission. At the same time, an expiration time can be set to increase security. This mechanism helps to protect user identity and access rights, reducing the risk of security threats such as session hijacking or cross-site request forgery. In this way, it is beneficial to improve the security of web access and data interaction based on web access.

[0093] To better describe the entire scheme, based on the above embodiments, a specific example is given to explain the web access method of the embodiments of the present application. This will be explained in detail below. It should be noted that the following examples are only for the purpose of explaining the embodiments of the present application and do not limit the embodiments of the present application.

[0094] For example, the web access method of the embodiments of the present application can be based on the scenario of the third-party client jumping to the bank webpage. The bank server can act as a business end. Specifically, the bank server can include a backend server and a front-end component. The backend server can have functions such as token management, authentication, and data management. The front-end component can return web static resources to the third-party client to present corresponding web content on the third-party client.

[0095] In one example, as shown in Figure 2 The web access method can include the following steps S210 to S212.

[0096] S201, the third-party client sends a token request notification to the third-party server.

[0097] S202, the third-party server requests a token from the backend server through an interface SDK.

[0098] S203, the backend server returns the token to the third-party server.

[0099] Specifically, the backend server can generate a corresponding token according to the request of the third-party server and return it. In addition, the backend server can also record the timeout time of the token to manage the life cycle of the token.

[0100] S204, the third-party server returns the token to the third-party client.

[0101] S205, the third-party client jumps to the webpage address provided by the bank, while carrying the token as a parameter when jumping.

[0102] Specifically, the token carried can be encrypted.

[0103] S206, the front-end component sends the token to the backend server for verification.

[0104] S207, the back-end server verifies the legality of the token and whether the token is still within the validity period.

[0105] S208, the back-end server returns a result of successful verification to the front-end component if the token passes the verification.

[0106] Correspondingly, if the token fails the verification, a result of failed verification is returned.

[0107] S209, the front-end component returns complete web static resources to the third-party client.

[0108] Specifically, after receiving the result of successful verification, the front-end component can load all the web static resources and present complete web content on the third-party client. Correspondingly, if a result of failed verification is received, the web resource loading is terminated, and a prompt message of request denied is presented on the web page.

[0109] S210, when the user performs an operation on the web page and triggers the front-end component to request data from the back-end server, the front-end component carries the token to request data from the back-end server.

[0110] When the user performs an operation on the web page and triggers the web page to request data from the back-end server, the token needs to be carried.

[0111] S211, after receiving the request, the back-end server verifies the legality of the token and whether the token is still within the validity period.

[0112] S212, in the case that the token passes the verification, data is returned to the front-end component.

[0113] Correspondingly, if the token fails the verification, the data request is rejected.

[0114] Based on the web access method provided in the above embodiments, the application also provides a specific implementation of a web access device. The device can be applied to a business end. Please refer to the following embodiments.

[0115] First, referring to Figure 3 The web access device 300 provided in the embodiments of the application includes an acquisition module 301, a verification module 302, and a return module 303.

[0116] The acquisition module 301 is configured to acquire web page jump parameters sent by a third-party client, wherein the web page jump parameters include authentication information, and the authentication information is authentication information issued by a trusted third-party server to the third-party client in advance by a business end.

[0117] The verification module 302 is configured to verify the authentication information of the web page jump parameters.

[0118] The returning module 303 is configured to return the webpage static resource corresponding to the webpage jump parameter to the third-party client, for the third-party client to access the target webpage based on the webpage static resource, in a case where the authentication information of the webpage jump parameter is verified.

[0119] The webpage access apparatus of the embodiment of the present application can be applied to a business system. The embodiment of the present application can obtain the webpage jump parameter sent by the third-party client, and the webpage jump parameter comprises authentication information. The authentication information is authentication information issued by the business end to the third-party client through a trusted third-party service end in advance, and has high credibility. Then, the authentication information can be verified. In a case where the authentication information is verified, the webpage static resource corresponding to the webpage jump parameter is returned to the third-party client, for the third-party client to access the target webpage based on the webpage static resource. In this way, in a case where the third-party client does not integrate the webpage SDK provided by the business end, the business end can authenticate the third-party client through the authentication information, and the third-party client is allowed to access the webpage in a case where the authentication is passed. In this way, the secure access to the webpage of the business end can be realized in a case where the third-party client does not integrate the webpage SDK.

[0120] In one embodiment, the apparatus can further comprise:

[0121] The receiving module is configured to receive the authentication information acquisition request sent by the trusted third-party service end, and the authentication information acquisition request is generated by the trusted third-party service end in response to the authentication information acquisition notification sent by the third-party client.

[0122] The generating module is configured to generate the authentication information corresponding to the authentication information acquisition request.

[0123] The sending module is configured to send the authentication information to the trusted third-party service end, so that the trusted third-party service end forwards the authentication information to the third-party client.

[0124] In one embodiment, the trusted third-party service end can communicate with the business end through an interface software development kit (SDK), and the interface SDK can be provided by the business end to the trusted third-party service end.

[0125] The receiving module is configured to receive the authentication information acquisition request sent by the trusted third-party service end, and the authentication information acquisition request can specifically comprise:

[0126] The receiving module is configured to receive the authentication information acquisition request sent by the trusted third-party service end through the interface SDK.

[0127] In one embodiment, the apparatus can further comprise:

[0128] The recording module is configured to record the expiration time of the authentication information.

[0129] The verification module is configured to check the authentication information, and specifically can include:

[0130] The verification module is configured to check the validity of the authentication information according to the expiration time of the authentication information and the sending time of the web page jump parameter.

[0131] In an embodiment, the apparatus can further include:

[0132] The acquisition module is configured to acquire a data acquisition request sent by the third-party client, the data acquisition request being generated based on a web page operation of the user on the target web page, and the data acquisition request including authentication information.

[0133] The verification module is configured to check the authentication information of the data acquisition request.

[0134] The return module is configured to return target data corresponding to the data acquisition request to the target web page in a case where the authentication information of the data acquisition request passes the check.

[0135] In an embodiment, the authentication information can include a token.

[0136] The various modules of the web page access apparatus provided by the embodiments of the present application can achieve Figure 1 the functions of the various steps of the web page access method and achieve the corresponding technical effects. For brevity, the details are not described here.

[0137] Figure 4 A hardware structure schematic diagram of a web page access device provided by an embodiment of the present application is shown.

[0138] The web page access device can include a processor 401 and a memory 402 having computer program instructions stored therein.

[0139] Specifically, the processor 401 can include a central processing unit (CPU), or a specific integrated circuit (ASIC), or can be configured to implement one or more integrated circuits of the embodiments of the present application.

[0140] The memory 402 can include mass storage for data or instructions. As an example and not by way of limitation, the memory 402 can include a hard disk drive (HDD), a floppy disk drive, flash memory, an optical disc (e.g., a compact disc (CD) or a digital versatile disc (DVD)), a solid-state drive (SSD), a USB drive, or a combination of two or more of these. Where appropriate, the memory 402 can include removable or non-removable (or fixed) media. Where appropriate, the memory 402 can be internal or external to the integrated gateway disaster recovery appliance. In particular embodiments, the memory 402 is non-volatile, solid-state memory.

[0141] The memory can include read-only memory (ROM), random-access memory (RAM), magnetic disk storage mediums, optical storage mediums, flash memory devices, electrical, optical, or other physical / tangible memory storage devices. Thus, in general, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., a memory device) encoded with software that, when executed (by one or more processors), is operable to access the operations described with reference to the methods according to an aspect of the present disclosure.

[0142] The processor 401 implements any of the web page access methods in the above-described embodiments by reading and executing computer program instructions stored in the memory 402.

[0143] In one example, the web page access device can further include a communication interface 403 and a bus 410. As shown, the processor 401, the memory 402, and the communication interface 403 are connected through the bus 410 and complete communication therebetween. Figure 4

[0144] The communication interface 403 is mainly used to realize the communication between various modules, devices, units and / or equipment in the embodiments of the present application.

[0145] ​Bus 410 includes hardware, software, or both, to couple components of the online data traffic metering device to each other and to couple components to other components within the online data traffic metering device. While bus 410 is shown for the sake of clarity as a single bus, it can include one or more buses operating together. Bus 410 can be implemented using any suitable type, unidirectional and / or bidirectional, of connection including an address bus, a data bus, a control bus, a graphics bus, a video bus, a signaling bus, a digital signal bus, and the like. Although this application describes and illustrates a particular bus, this application contemplates any suitable bus or interconnect.

[0146] The webpage accessing device can execute the webpage accessing method in the embodiments of the present application, thereby realizing the webpage accessing method and device described in combination with Figure 1 and Figure 3 The webpage accessing method in the above embodiments can be implemented by a computer storage medium in the embodiments of the present application. The computer storage medium stores computer program instructions; the computer program instructions are executed by a processor to implement any of the webpage accessing methods in the above embodiments.

[0147] The embodiments of the present application further provide a computer program product, which comprises a computer program; the computer program is executed by a processor to implement any of the webpage accessing methods in the above embodiments.

[0148] It needs to be made clear that the present application is not limited to the particular configurations and processes described above and shown in the drawings. Detailed descriptions of known methods are omitted here for the sake of brevity. In the above embodiments, several specific steps are described and shown as examples. However, the method processes of the present application are not limited to the specific steps described and shown; those skilled in the art can make various changes, modifications and additions, or change the order of the steps, after understanding the spirit of the present application.

[0149] The functions noted in the description of the structural block diagrams above can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, and the like. When implemented in software, the elements of the present application are program or code segments that are used to perform the required tasks. The program or code segments can be stored in a machine-readable medium, or transmitted through a data signal carried in a carrier wave over a transmission medium or communication link. A "machine-readable medium" includes any medium that can store or transport information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio frequency (RF) links, and the like. The code segments can be downloaded via computer networks such as the Internet, intranets, and the like.

[0150] It is also important to note that the examples mentioned in the present application describe some methods or systems based on a series of steps or devices. However, the present application is not limited to the order of the steps mentioned above, that is, the steps can be performed in the order mentioned in the examples, or in an order different from the examples, or several steps can be performed simultaneously.

[0151] The computer program instructions can also be loaded onto a computer, other programmable data processing apparatus, or other processing device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other processing device to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks. These computer program instructions can also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other processing device to operate in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function / act specified in the flowchart and / or block diagram block or blocks. The computer program instructions can also be loaded onto a computer, other programmable data processing apparatus, or other processing device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other processing device to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks. These computer program instructions can also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other processing device to operate in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function / act specified in the flowchart and / or block diagram block or blocks.

[0152] The above is merely a specific implementation of the present application. As can be clearly understood by a person skilled in the art from the above description, for the convenience and brevity of description, the specific working process of the system, module and unit described above can refer to the corresponding process in the foregoing method embodiments, which will not be described herein again. It should be understood that the protection scope of the present application is not limited in this way, and any person skilled in the art can easily think of various equivalent modifications or replacements within the technical range disclosed in the present application, and these modifications or replacements should be covered in the protection scope of the present application.

Claims

1. A method of accessing a web page, characterized by, Applied to a business end, the method comprises: Obtaining a webpage jump parameter sent by a third-party client, wherein the webpage jump parameter comprises authentication information, and the authentication information is authentication information sent by a trusted third-party server to the third-party client in advance by the business end; Verifying the authentication information of the webpage jump parameter; In the case that the authentication information of the webpage jump parameter passes the verification, returning webpage static resources corresponding to the webpage jump parameter to the third-party client, so as to enable the third-party client to access a target webpage based on the webpage static resources; The trusted third-party server communicates with the business end through an interface software development kit (SDK), wherein the interface SDK is provided by the business end to the trusted third-party server; The authentication information is generated by the business end according to an authentication information acquisition request sent by the trusted third-party server through the interface SDK.

2. The web page access method of claim 1, wherein, Before the obtaining of the webpage jump parameter sent by the third-party client, the method further comprises: Receiving an authentication information acquisition request sent by a trusted third-party server, wherein the authentication information acquisition request is generated by the trusted third-party server in response to an authentication information acquisition notification sent by the third-party client; Generating authentication information corresponding to the authentication information acquisition request; Sending the authentication information to the trusted third-party server, so as to enable the trusted third-party server to forward the authentication information to the third-party client.

3. The web page access method of claim 2, wherein, After the generation of the authentication information corresponding to the authentication information acquisition request, the method further comprises: Recording an expiration time of the authentication information; The verification of the authentication information comprises: Verifying the validity of the authentication information according to the expiration time of the authentication information and the sending time of the webpage jump parameter.

4. The web page access method of claim 1, wherein, After the returning of the webpage static resources corresponding to the webpage jump parameter to the third-party client in the case that the authentication information of the webpage jump parameter passes the verification, so as to enable the third-party client to access the webpage based on the webpage static resources, the method further comprises: Obtaining a data acquisition request sent by a third-party client, wherein the data acquisition request is generated based on a webpage operation of a user on the target webpage, and the data acquisition request comprises the authentication information; Verifying the authentication information of the data acquisition request; In the case that the authentication information of the data acquisition request passes the verification, returning target data corresponding to the data acquisition request to the target webpage.

5. The web page access method according to any one of claims 1-4, wherein, The authentication information comprises a token.

6. A web page access device, characterized by comprising: Applied to a business end, the device comprises: An obtaining module, configured to obtain a webpage jump parameter sent by a third-party client, wherein the webpage jump parameter comprises authentication information, and the authentication information is authentication information sent by a trusted third-party server to the third-party client in advance by the business end; A verification module, configured to verify the authentication information of the webpage jump parameter; The returning module is configured to return a web static resource corresponding to the web jump parameter to the third-party client for the third-party client to access a target web page based on the web static resource when the authentication information is verified. The trusted third-party server communicates with the business server through an interface software development kit (SDK), wherein the interface SDK is provided by the business server to the trusted third-party server. The authentication information is generated by the business server according to an authentication information acquisition request sent by the trusted third-party server through the interface SDK.

7. A web access device, characterized by The device comprises a processor and a memory storing computer program instructions; the processor executes the computer program instructions to implement the web access method of any one of claims 1-5.

8. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer program instructions, and the computer program instructions are executed by the processor to implement the web access method of any one of claims 1-5.

9. A computer program product, characterised in that, The instructions in the computer program product are executed by the processor of the electronic device, so that the electronic device can execute the web access method of any one of claims 1-5.

Images