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

By using authentication information verification and trusted third-party server authentication mechanisms when the third-party client does not integrate the web page SDK, secure access to bank system web pages is achieved, and secure access in the case of unintegrated security is solved The problem reduces the burden on third-party platforms and improves security and user experience.

CN118940247AActive Publication Date: 2024-11-12CHINA CONSTRUCTION BANK +1

Patent Information

Application Number
CN202410932249.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-12
Publication Date
2024-11-12
Estimated Expiration
2044-07-12

AI Technical Summary

Technical Problem

When third-party clients do not integrate the web page SDK, how to achieve secure access to bank system web pages to avoid the risk of overprivileged attacks or data tampering.

Method used

By obtaining the authentication information in the web page jump parameters sent by the third-party client, performing verification, and returning to the web page static resources when the authentication is passed, allowing the third-party client to access the destination web page and using trusted third-party services The authentication information provided by the end is authenticated and data encryption to ensure the security of access.

Benefits of technology

When the third-party client does not integrate the web page SDK, secure access to the banking system web pages is achieved, reducing the burden on the third-party platform, improving access security and user experience, and reducing integration complexity.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118940247A_ABST
    Figure CN118940247A_ABST
Patent Text Reader

Abstract

The invention discloses a webpage access method and device, equipment, a storage medium and a program product, and is applied to the technical field of security access, the method is applied to a service end, and the method comprises the steps that webpage jump parameters sent by a third-party client are acquired, and the webpage jump parameters comprise authentication information; the authentication information is authentication information issued to the third-party client by the service end in advance through a trusted third-party server; verifying the authentication information of the webpage jump parameter; and under the condition that the authentication information of the webpage jump parameter passes verification, returning a webpage static resource corresponding to the webpage jump parameter to the third-party client, so that the third-party client accesses the target webpage based on the webpage static resource. According to the embodiment of the invention, safe access to the webpage of the service end can be realized under the condition that the third-party client is not integrated with the webpage SDK.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application belongs to the field of secure access technology, and in particular, relates to a web page access method, device, equipment, storage medium and program product. Background Art

[0002] Due to the high privacy of the business carried by the banking system, there are high security requirements when external third parties access it, and the identity of the accessing party must be verified and the content must be encrypted.

[0003] In order to solve the security and encryption issues when third parties access bank systems, many banks provide software development kits (SDKs) for external third parties to integrate. Among them, the web SDK used to access the bank's webpage can be integrated by the client of an external third party. The integrated web SDK has the ability to authenticate the redirecting party and encrypt the data, and the data transmitted on the webpage is considered difficult to intercept and tamper with. In actual usage scenarios, some third-party companies operate more clients. In order to ensure that the client can access the bank's webpage normally, the web SDK needs to be integrated in each client.

[0004] However, integrating a web SDK may impose a burden on third-party companies, such as increasing the size of the client and the number of internal administrative approvals of third-party companies, which makes it difficult for some third-party companies to integrate the web SDK on the client. In the case that the third-party client does not integrate the web SDK, how to achieve secure access to the web page has become an urgent problem to be solved. Summary of the invention

[0005] The embodiments of the present application provide a web page access method, apparatus, device and computer storage medium, which can realize secure access to business-end web pages when a third-party client does not integrate a web page SDK.

[0006] In a first aspect, an embodiment of the present application provides a web page access method, which is applied to a service end and includes:

[0007] Obtaining web page jump parameters sent by the third-party client, the web page jump parameters include authentication information, and the authentication information is the authentication information that the business end pre-issues to the third-party client through the trusted third-party server;

[0008] Verify the authentication information of the web page jump parameters;

[0009] When the authentication information of the web page jump parameter passes the verification, the web page static resource corresponding to the web page jump parameter is returned to the third-party client, so that the third-party client can access the target web page based on the web page static resource.

[0010] In some possible implementations, before obtaining the web page jump parameter sent by the third-party client, the method further includes:

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

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

[0013] The authentication information is sent to a trusted third-party server, so that the trusted third-party server can forward the authentication information to a third-party client.

[0014] In some possible implementations, 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;

[0015] Receive authentication information acquisition request sent by a trusted third-party server, including:

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

[0017] In some possible implementations, after generating the authentication information corresponding to the authentication information acquisition request, the method further includes:

[0018] Record the expiration time of authentication information;

[0019] Verify the authentication information, including:

[0020] The validity of the authentication information is verified based on the expiration time of the authentication information and the sending time of the web page jump parameter.

[0021] In some possible implementations, when the authentication information of the web page jump parameter passes the verification, a web page static resource corresponding to the web page jump parameter is returned to the third-party client for the third-party client to access the web page based on the web page static resource. The method further includes:

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

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

[0024] When the authentication information of the data acquisition request passes the verification, the target data corresponding to the data acquisition request is returned to the target web page.

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

[0026] In a second aspect, an embodiment of the present application provides a web page access device, which is applied to a service end, and the device includes:

[0027] The acquisition module is used to acquire the web page jump parameters sent by the third-party client. The web page jump parameters include authentication information. The authentication information is the authentication information that the business end pre-issues to the third-party client through the trusted third-party server.

[0028] A verification module, used to verify the authentication information of the web page jump parameters;

[0029] The return module is used to return the web page static resources corresponding to the web page jump parameters to the third-party client when the authentication information of the web page jump parameters passes the verification, so that the third-party client can access the target web page based on the web page static resources.

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

[0031] A processor and a memory storing computer program instructions; when the processor executes the computer program instructions, any one of the above web page access methods is implemented.

[0032] In a fourth aspect, an embodiment of the present application provides a computer storage medium, on which computer program instructions are stored. When the computer program instructions are executed by a processor, any of the above-mentioned web page access methods is implemented.

[0033] In a fifth aspect, an embodiment of the present application provides a computer program product. When instructions in the computer program product are executed by a processor of an electronic device, the electronic device is enabled to execute any one of the above-mentioned web page access methods.

[0034] The web page access method, device, equipment and computer storage medium of the embodiment of the present application can be applied to a business system. The embodiment of the present application can obtain the web page jump parameter sent by the third-party client, and the web page jump parameter includes authentication information. The authentication information is the authentication information that the business end pre-issues to the third-party client through the trusted third-party service end, and has a high degree of credibility. Then, the authentication information can be verified. When the authentication information passes the verification, the web page static resource corresponding to the web page jump parameter is returned to the third-party client, so that the third-party client can access the target web page based on the web page static resource. In this way, when the third-party client does not integrate the web page 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 web page when the authentication passes. In this way, secure access to the business end web page can be achieved when the third-party client does not integrate the web page SDK. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] In order to more clearly illustrate the technical solution of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0036] Figure 1 It is a flowchart of a web page access method provided by an embodiment of the present application;

[0037] Figure 2 is a flowchart of a web page access method provided by another embodiment of the present application;

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

[0039] Figure 4 It is a structural diagram of a web page access device provided in yet 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 purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain the present application, rather than to limit the present application. For those skilled in the art, the present application can be implemented without the need for some of these specific details. The following description of the embodiments is only to provide a better understanding of the present application by illustrating the examples of the present application.

[0041] It should be noted that, in this article, relational terms such as first and second, etc. 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 these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, 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 are in compliance with the relevant provisions of national laws and regulations.

[0043] It should be noted that in the embodiments of the present application, certain software, components, models and other existing solutions in the industry may be mentioned, and they should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0044] In order to solve the security and encryption issues when third parties access bank systems, many banks provide software development kits (SDKs) for external third parties to integrate. Among them, the web SDK used to access the bank's webpage can be integrated by the client of an external third party. The integrated web SDK has the ability to authenticate the redirecting party and encrypt the data, and the data transmitted on the webpage is considered difficult to intercept and tamper with. In actual usage scenarios, some third-party companies operate more clients. In order to ensure that the client can access the bank's webpage normally, the web SDK needs to be integrated in each client.

[0045] However, integrating a web SDK may impose a burden on third-party companies, such as the expansion of the client size, an increase in administrative approvals within the third-party company, etc., making it difficult for some third-party companies to integrate the web SDK on the client side.

[0046] In the related art, when the client of a third-party company does not integrate a web SDK, when the client accesses a web page, it usually jumps directly to the web page. This method has the risk of being attacked by unauthorized persons or having data tampered with.

[0047] In order to solve the problems of the prior art, the embodiments of the present application provide a web page access method, device, equipment and computer storage medium.

[0048] The following first introduces the web page access method provided by the embodiment of the present application.

[0049] The web page access method according to the embodiment of the present application is described in detail below with reference to the accompanying drawings.

[0050] Figure 1 FIG. 1 is a flow chart of a web page access method provided by an embodiment of the present application. The method can be applied to a business end. Figure 1 As shown, the method may include the following steps S110 to S130.

[0051] S110, obtaining web page jump parameters sent by the third-party client, where the web page jump parameters include authentication information, and the authentication information is authentication information that is issued in advance by the business end to the third-party client through the trusted third-party server.

[0052] In step S110, the trusted third-party server may include a third-party server that trusts the business end. The way in which the trusted third-party server establishes trust with the business end may be a technology known in the art, and the embodiments of the present application are not limited thereto. Exemplarily, the business end may generate a self-signed certificate, and a root certificate may be issued to a trusted third-party server, and a third-party server with the root certificate installed is a trusted third-party server. Exemplarily, the business end may provide an interface SDK for accessing the business end service interface to a trusted third-party server, and a third-party server with the interface SDK is a trusted third-party server. The third-party client may include a client related to the trusted third-party server, for example, may include but is not limited to a client of a third-party platform such as the same organization, the same group, or the same enterprise platform as the trusted third party.

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

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

[0055] In step S120, a specific verification method may be selected according to the type of authentication information, which is not limited here. Exemplarily, verification of the authentication information may include but is not limited to verifying at least one of the legitimacy (e.g., whether the authentication information is included in the blacklist, etc.) and validity of the authentication information.

[0056] S130, when the authentication information of the web page jump parameter passes the verification, the web page static resource corresponding to the web page jump parameter is returned to the third-party client, so that the third-party client can access the target web page based on the web page static resource.

[0057] Exemplarily, the third-party client can present complete web page content based on the static resources of the web page.

[0058] The web page access method of the embodiment of the present application can be applied to a business system. The embodiment of the present application can obtain the web page jump parameter sent by the third-party client, and the web page jump parameter includes authentication information. The authentication information is the authentication information that the business end pre-issues to the third-party client through a trusted third-party service end, and has a high degree of credibility. Then, the authentication information can be verified. When the authentication information passes the verification, the web page static resource corresponding to the web page jump parameter is returned to the third-party client, so that the third-party client can access the target web page based on the web page static resource. In this way, when the third-party client is not integrated with the web page 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 web page when the authentication passes. In this way, secure access to the business end web page can be achieved when the third-party client is not integrated with the web page SDK.

[0059] The webpage access method of the embodiment of the present application can allow a third-party client to achieve secure access to the business end webpage when the webpage SDK is integrated, and the integration requirements for the third-party client are relatively light. For a third-party platform that operates multiple clients, the embodiment of the present application significantly reduces the burden on the third-party platform, which is conducive to rapid application in the client of the third-party platform.

[0060] In one embodiment, before obtaining the web page jump parameter sent by the third-party client, the method may further include:

[0061] An authentication information acquisition request sent by a trusted third-party server is received, where the authentication information acquisition request is generated by the trusted third-party server in response to an authentication information acquisition notification sent by a third-party client.

[0062] Generate authentication information corresponding to the authentication information acquisition request.

[0063] The authentication information is sent to a trusted third-party server, so that the trusted third-party server can forward the authentication information to a third-party client.

[0064] In the above implementation, when a third-party client needs to access a web page, it can send an authentication information acquisition notification to a trusted third-party server. Correspondingly, the trusted third-party server can send an authentication information acquisition request to the business end to obtain authentication information. The business end then generates corresponding authentication information based on the received authentication information acquisition request, and returns it to the trusted third-party server, so that the trusted third-party server can forward the authentication information to the third party. In this way, the third-party client can obtain authentication information from the business end through the trusted third-party server without integrating the web SDK, so as to access the web page through the authentication information later. In this way, the security of the third-party client accessing the business end web page is improved.

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

[0066] Receiving an authentication information acquisition request sent by a trusted third-party server may include:

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

[0068] Accordingly, in one example, sending the authentication information to a trusted third-party server so that the trusted third-party server forwards the authentication information to a third-party client may specifically include:

[0069] The authentication information is sent to the trusted third-party server through the interface SDK, so that the trusted third-party server can forward the authentication information to the third-party client.

[0070] In the above implementation, the interface SDK may include an SDK provided by the business end for accessing the service interface of the business end. The interface SDK is usually integrated with the server end, and after integration, it has the ability to authenticate the caller and encrypt data. In this way, during the communication process between the trusted third-party server end and the business end, the data transmitted by both parties is secure and encrypted, and is 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, thereby improving the security of the third-party client accessing the business end web page.

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

[0072] Record the expiration time of the authentication information.

[0073] Verify the authentication information, which may include:

[0074] The validity of the authentication information is verified based on the expiration time of the authentication information and the sending time of the web page jump parameter.

[0075] In the above implementation, after the service end generates the authentication information, it can record the expiration time of the authentication information and manage the life cycle of the authentication time. After receiving the web page 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 achieved, the accuracy of the authentication information verification can be improved, and the security of the third-party client accessing the service end web page can be improved.

[0076] In one embodiment, the web page jump parameter may include encrypted authentication information.

[0077] Before verifying the authentication information of the web page jump parameter, the method may further include: decrypting the authentication information of the web page jump parameter. In the above implementation, the encryption and decryption methods may be technologies well known in the art, such as encryption and decryption technologies based on symmetric encryption algorithms, or encryption technologies based on asymmetric encryption algorithms, which are not limited in the embodiments of the present application. Exemplarily, after the business end generates the authentication information, it may also record the decryption key corresponding to the authentication information, and after receiving the web page jump parameter, the authentication information may be decrypted based on the decryption key.

[0078] The above implementation method can reduce the risk of network jump parameters being tampered with or obtained by attackers during transmission by encrypting the authentication information, thereby further improving the security of web page access.

[0079] In one embodiment, the method may further include: if the authentication information of the web page jump parameter fails to pass the verification, returning a verification failure result to the third-party client.

[0080] In this way, the user can be prompted that the webpage access failed. In some cases, for example, when the authentication information expires, the user can send an authentication information acquisition notification to the trusted third-party server based on the reminder of the verification failure result to re-acquire the authentication information. In this way, the user experience can be improved.

[0081] In one embodiment, the web page static resources may include public web page static resources and non-public web page static resources.

[0082] Before verifying the authentication information of the web page jump parameter, the method may include: returning a public web page static resource to the third-party client for displaying the public information on the third-party client.

[0083] When the authentication information of the web page jump parameter passes the verification, the web page static resource corresponding to the web page jump parameter is returned to the third-party client, which may include: when the authentication information of the web page jump parameter passes the verification, the non-public web page static resource corresponding to the web page jump parameter is returned to the third-party client.

[0084] In the above implementation, the public web page static resources may include web page static resources related to the public information of the business end, for example, may include push information or advertisements disclosed by the business end to all users. The public web page static resources may include web page static resources related to the business corresponding to the web page jump parameters. In the above implementation, before the authentication information of the web page jump parameters is verified, the public web page static resources may be returned to the third-party client for displaying the public information on the third-party client. In this way, the public web page static resources may be loaded in advance, and when the non-public web page static resources are subsequently obtained, only the non-public web page static resources need to be loaded. In this way, the loading rate of web page static resources can be increased, thereby improving the user experience.

[0085] In one embodiment, when the authentication information of the web page jump parameter passes the verification, the web page static resource corresponding to the web page jump parameter is returned to the third-party client for the third-party client to access the web page based on the web page static resource. The method may also include:

[0086] A data acquisition request sent by a third-party client is obtained. The data acquisition request is generated based on a web page operation performed by a user on a target web page. The data acquisition request includes authentication information.

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

[0088] When the authentication information of the data acquisition request passes the verification, the target data corresponding to the data acquisition request is returned to the target web page.

[0089] According to the above implementation, when a user operates on a web page displayed by a third-party client and triggers a data acquisition request, authentication information must be carried. The business end verifies the authentication information and returns the target data to the third-party client after the verification passes. In this way, the third-party client can also securely obtain business end data through the web page without integrating the web SDK, thereby improving the data interaction security between the third-party client and the business end.

[0090] In one embodiment, after verifying the authentication information of the data acquisition request, the method may further include: if the authentication information of the data acquisition request fails to pass the verification, returning rejection information to the target webpage to reject the data acquisition request.

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

[0092] In the above implementation, 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 protect user identity and access rights and reduce the risks caused by security threats such as session hijacking or cross-site request forgery. This is conducive to improving the security of web page access and data interaction based on web page access.

[0093] In order to better describe the entire solution, based on the above embodiments, a specific example is given to illustrate the webpage access method of the embodiment of the present application. This is explained in detail below. It should be noted that the following example is only for explaining the embodiment of the present application, and does not constitute a limitation on the embodiment of the present application.

[0094] Exemplarily, the web page access method of the embodiment of the present application can be performed based on the scenario of a third-party client jumping to a bank web page. The bank service end can serve as a business end. Specifically, the bank service end can include a back-end service end and a front-end component. Among them, the back-end service end can have functions such as token management, authentication, and data management. The front-end component can return web page static resources to the third-party client to present the corresponding web page content on the third-party client.

[0095] In one example, if Figure 2 As shown, the web page access method may 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 the interface SDK.

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

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

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

[0101] S205, the third-party client jumps to the webpage address provided by the bank, and carries the token as a parameter for the jump.

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

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

[0104] S207, the backend server verifies the legitimacy of the token and whether it is still valid.

[0105] S208, when the token is verified, the backend server returns a verification success result to the frontend component.

[0106] Correspondingly, if the token verification fails, the verification failure result is returned.

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

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

[0109] S210, when the user operates 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 a user operates on a web page and triggers the web page to request data from the backend server, a token is required.

[0111] S211, after receiving the request, the backend server verifies the legitimacy of the token and whether it is still valid.

[0112] S212, when the token is verified, returns data to the front-end component.

[0113] Accordingly, if the token verification fails, the data request will be rejected.

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

[0115] See first Figure 3 The web page access device 300 provided in the embodiment of the present application includes an acquisition module 301, a verification module 302 and a return module 303.

[0116] The acquisition module 301 is used to acquire the web page jump parameters sent by the third-party client. The web page jump parameters include authentication information. The authentication information is the authentication information that the business end pre-issues to the third-party client through the trusted third-party server.

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

[0118] The return module 303 is used to return the web page static resources corresponding to the web page jump parameters to the third-party client when the authentication information of the web page jump parameters passes the verification, so that the third-party client can access the target web page based on the web page static resources.

[0119] The web page access device of the embodiment of the present application can be applied to a business system. The embodiment of the present application can obtain the web page jump parameter sent by the third-party client, and the web page jump parameter includes authentication information. The authentication information is the authentication information that the business end pre-issues to the third-party client through the trusted third-party service end, and has a high degree of credibility. Then, the authentication information can be verified. When the authentication information passes the verification, the web page static resource corresponding to the web page jump parameter is returned to the third-party client, so that the third-party client can access the target web page based on the web page static resource. In this way, when the third-party client has not integrated the web page 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 web page when the authentication passes. In this way, secure access to the business end web page can be achieved when the third-party client has not integrated the web page SDK.

[0120] In one embodiment, the apparatus may further include:

[0121] The receiving module is used to receive an authentication information acquisition request sent by a trusted third-party server, where the authentication information acquisition request is generated by the trusted third-party server in response to an authentication information acquisition notification sent by a third-party client.

[0122] The generation module is used to generate authentication information corresponding to the authentication information acquisition request.

[0123] The sending module is used to send 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.

[0124] In one embodiment, the trusted third-party server may communicate with the business end through an interface software development kit SDK, wherein the interface SDK may be provided by the business end to the trusted third-party server.

[0125] The receiving module is used to receive the authentication information acquisition request sent by the trusted third-party server, which may specifically include:

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

[0127] In one embodiment, the apparatus may further include:

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

[0129] The verification module is used to verify the authentication information, which may include:

[0130] The verification module is used to verify 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 one embodiment, the apparatus may further include:

[0132] The acquisition module is used to acquire a data acquisition request sent by a third-party client. The data acquisition request is generated based on a user's web page operation on a target web page. The data acquisition request includes authentication information.

[0133] A verification module, used to verify the authentication information of the data acquisition request;

[0134] The return module is used to return the target data corresponding to the data acquisition request to the target web page when the authentication information of the data acquisition request passes the verification.

[0135] In one embodiment, the authentication information may include a token.

[0136] Each module of the web page access device provided in the embodiment of the present application can realize Figure 1 The functions of each step of the web page access method are provided, and the corresponding technical effects can be achieved. For the sake of brevity, they will not be repeated here.

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

[0138] The web page access device may include a processor 401 and a memory 402 storing computer program instructions.

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

[0140] Memory 402 may include a large capacity memory for data or instructions. By way of example and not limitation, memory 402 may include a hard disk drive (HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a universal serial bus (USB) drive or a combination of two or more of these. In appropriate cases, memory 402 may include a removable or non-removable (or fixed) medium. In appropriate cases, memory 402 may be inside or outside of an integrated gateway disaster recovery device. In a specific embodiment, memory 402 is a non-volatile solid-state memory.

[0141] The memory may include read-only memory (ROM), random access memory (RAM), magnetic disk storage media devices, optical storage media devices, flash memory devices, electrical, optical or other physical / tangible memory storage devices. Thus, typically, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the method according to an aspect of the present disclosure.

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

[0143] In one example, the web page access device may further include a communication interface 403 and a bus 410. Figure 4 As shown, the processor 401, the memory 402, and the communication interface 403 are connected via a bus 410 and communicate with each other.

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

[0145] Bus 410 includes hardware, software or both, and the parts of online data flow billing equipment are coupled to each other. For example, but not limitation, bus may include accelerated graphics port (AGP) or other graphics bus, enhanced industrial standard architecture (EISA) bus, front-end bus (FSB), hypertransport (HT) interconnection, industrial standard architecture (ISA) bus, infinite bandwidth interconnection, low pin count (LPC) bus, memory bus, micro channel architecture (MCA) bus, peripheral component interconnection (PCI) bus, PCI-Express (PCI-X) bus, serial advanced technology attachment (SATA) bus, video electronics standard association local (VLB) bus or other suitable bus or two or more of these combinations. In appropriate cases, bus 710 may include one or more buses. Although the present application embodiment describes and shows a specific bus, the application considers any suitable bus or interconnection.

[0146] The web page access device can execute the web page access method in the embodiment of the present application, thereby realizing the combination Figure 1 and Figure 3 The web page access method and device described in the embodiment. The web page access method in the above embodiment can be implemented by providing a computer storage medium in the embodiment of the present application. The computer storage medium stores computer program instructions; when the computer program instructions are executed by the processor, any of the web page access methods in the above embodiment is implemented.

[0147] An embodiment of the present application further provides a computer program product, including a computer program, which implements any one of the web page access methods in the above embodiments when the computer program is processed and executed.

[0148] It should be clear that the present application is not limited to the specific configuration and processing described above and shown in the figures. For the sake of simplicity, a detailed description of the known method is omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of the present application is not limited to the specific steps described and shown, and those skilled in the art can make various changes, modifications and additions, or change the order between the steps after understanding the spirit of the present application.

[0149] The functional blocks shown in the above-described block diagram can be implemented as hardware, software, firmware or a combination thereof. When implemented in hardware, it can be, for example, an electronic circuit, an application specific integrated circuit (ASIC), appropriate firmware, a plug-in, a function card, etc. When implemented in software, the elements of the present application are programs or code segments that are used to perform the required tasks. The program or code segment can be stored in a machine-readable medium, or transmitted on a transmission medium or a communication link by a data signal carried in a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting 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, optical fiber media, radio frequency (RF) links, etc. The code segment can be downloaded via a computer network such as the Internet, an intranet, etc.

[0150] It should also be noted that the exemplary embodiments mentioned in this application describe some methods or systems based on a series of steps or devices. However, this application is not limited to the order of the above steps, that is, the steps can be performed in the order mentioned in the embodiment, or in a different order from the embodiment, or several steps can be performed simultaneously.

[0151] Aspects of the present disclosure are described above with reference to the flowchart and / or block diagram of the method, device (system) and computer program product according to the embodiment of the present disclosure. It should be understood that each box in the flowchart and / or block diagram and the combination of each box in the flowchart and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine so that these instructions executed by the processor of the computer or other programmable data processing device enable the implementation of the function / action specified in one or more boxes of the flowchart and / or block diagram. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field programmable logic circuit. It can also be understood that each box in the block diagram and / or flowchart and the combination of boxes in the block diagram and / or flowchart can also be implemented by dedicated hardware that performs a specified function or action, or can be implemented by a combination of dedicated hardware and computer instructions.

[0152] The above are only specific implementation methods of the present application. Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the systems, modules and units described above can refer to the corresponding processes in the aforementioned method embodiments, and will not be repeated here. It should be understood that the protection scope of the present application is not limited to this. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed in this application, and these modifications or replacements should be included in the protection scope of this application.

Claims

1. A web page access method, characterized in that: Applied to the business end, the method includes: Acquire a web page jump parameter sent by a third-party client, wherein the web page jump parameter includes authentication information, and the authentication information is authentication information issued in advance by the business end to the third-party client through a trusted third-party service end; Verifying the authentication information of the web page jump parameter; When the authentication information of the web page jump parameter passes the verification, the web page static resource corresponding to the web page jump parameter is returned to the third-party client, so that the third-party client can access the target web page based on the web page static resource.

2. The web page access method according to claim 1, characterized in that: Before obtaining the web page jump parameter sent by the third-party client, the method further includes: 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; Generate authentication information corresponding to the authentication information acquisition request; The authentication information is sent to the trusted third-party server, so that the trusted third-party server forwards the authentication information to the third-party client.

3. The web page access method according to claim 2, characterized in that: 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 receiving of the authentication information acquisition request sent by the trusted third-party server includes: Receive the authentication information acquisition request sent by the trusted third-party server through the interface SDK.

4. The web page access method according to claim 2, characterized in that: After generating the authentication information corresponding to the authentication information acquisition request, the method further includes: Recording the expiration time of the authentication information; The verifying the authentication information includes: The validity of the authentication information is verified according to the expiration time of the authentication information and the sending time of the web page jump parameter.

5. The web page access method according to claim 1, characterized in that: When the authentication information of the web page jump parameter passes the verification, the web page static resource corresponding to the web page jump parameter is returned to the third-party client for the third-party client to access the web page based on the web page static resource. The method further includes: 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 includes the authentication information; Verifying the authentication information of the data acquisition request; When the authentication information of the data acquisition request passes the verification, the target data corresponding to the data acquisition request is returned to the target webpage.

6. The webpage access method according to any one of claims 1 to 5, characterized in that: The authentication information includes a token.

7. A web page access device, characterized in that: Applied to the service end, the device includes: An acquisition module, used 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 in advance by the business end to the third-party client through a trusted third-party service end; A verification module, used to verify the authentication information of the web page jump parameter; The return module is used to return the web page static resource corresponding to the web page jump parameter to the third-party client when the authentication information passes the verification, so that the third-party client can access the target web page based on the web page static resource.

8. A web page access device, characterized in that: The device comprises: a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, the web page access method according to any one of claims 1 to 6 is implemented.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer program instructions, and when the computer program instructions are executed by a processor, the web page access method according to any one of claims 1 to 6 is implemented.

10. A computer program product, characterized in that When the instructions in the computer program product are executed by a processor of an electronic device, the electronic device is enabled to execute the web page access method as described in any one of claims 1 to 6.

Citation Information

Patent Citations

  • Method, client and server for authenticating webpage request

    CN107493250A

  • Data access processing method and device, storage medium and computer program product

    CN118264460A

  • Secure access control system

    US20120054842A1

Cited By

  • Application system, client, server, storage medium, and program product

    CN120880746A