Application login processing method, device, electronic device and storage medium

Abstract

The embodiment of the present invention provides a login processing method, device, electronic device and storage medium for an application. The method includes: in response to a login instruction for a first application, after successful login in the first application, obtaining a first browser fingerprint corresponding to the first application, and generating a login Token identifier corresponding to the login instruction according to the first browser fingerprint; generating a first heartbeat packet corresponding to the first browser fingerprint according to the login Token identifier; in response to an access instruction for a second application in the same browser, obtaining a second browser fingerprint corresponding to the second application, and generating a second heartbeat packet corresponding to the second browser fingerprint; comparing the first heartbeat packet with the second heartbeat packet, and if the comparison result of the two indicates that the first browser fingerprint and the second browser fingerprint are the same browser fingerprint, automatically logging in to the second application based on the login Token identifier.

Description

Technical Field

[0001] The present invention relates to the field of network security technology, and in particular to a login processing method for an application in a browser, a login processing device for an application in a browser, an electronic device, and a computer-readable storage medium. Background Art

[0002] As time goes by and needs accumulate, a complete front-end application will become larger and more complex, making iterative problems in applications more difficult to access and increasing maintenance costs. In this case, many front-end technology teams will split a front-end application into multiple sub-applications, and multiple sub-applications share some data states, such as user information, transaction information, etc. Among them, for the aforementioned multiple sub-applications, it does not refer to web pages under the same domain, but to web pages under different domains. In essence, multiple projects form a complete application, and their domain names are different, so there will be problems with cross-domain and data communication. For example, sub-application A has been logged in, but after jumping to sub-application B, you have to log in again. Although the user data after logging in is the same for both, you have to log in again for identity authentication after switching sub-applications due to cross-domain issues.

[0003] When an application is split into multiple sub-applications, although the functions of the sub-applications can be customized, it also means that completing different transactions may require arbitrary switching between different sub-applications, resulting in cross-domain and data communication problems. Specifically, in the switching process, it will involve account login issues for different sub-applications. If a transaction needs to be completed by multiple sub-applications in collaboration, users are required to log in to each sub-application separately, which undoubtedly brings huge login work to users and reduces the efficiency of transaction processing. Summary of the invention

[0004] The embodiments of the present invention provide a method, device, electronic device and computer-readable storage medium for processing login of an application within a browser, so as to solve or partially solve the problem that during transaction processing of different sub-applications in the same browser, account login has a cumbersome login process, poor convenience and leads to low transaction processing efficiency.

[0005] The embodiment of the present invention discloses a method for processing login of an application in a browser, comprising:

[0006] In response to a login instruction for a first application, after successful login in the first application, obtaining a first browser fingerprint corresponding to the first application, and generating a login Token identifier corresponding to the login instruction according to the first browser fingerprint;

[0007] Generate a first heartbeat packet corresponding to the first browser fingerprint according to the login Token identifier;

[0008] In response to an access instruction to a second application in the same browser, obtaining a second browser fingerprint corresponding to the second application, and generating a second heartbeat packet corresponding to the second browser fingerprint;

[0009] The first heartbeat packet is compared with the second heartbeat packet. If the comparison result indicates that the first browser fingerprint and the second browser fingerprint are the same, the second application is automatically logged in based on the login Token identifier.

[0010] The embodiment of the present invention further discloses a method for processing login of an application in a browser, which is applied to the browser and includes:

[0011] In response to a login instruction for a first application, after successful login in the first application, obtaining a first browser fingerprint corresponding to the first application, generating a login Token identifier corresponding to the login instruction according to the first browser fingerprint, and sending the login Token identifier to a server;

[0012] In response to an access instruction to a second application in the same browser, obtaining a second browser fingerprint corresponding to the second application, and generating a second heartbeat packet corresponding to the second browser fingerprint;

[0013] Sending the second heartbeat packet to the server, and receiving a login instruction for the second heartbeat packet returned by the server, wherein the login instruction is an instruction generated based on the login Token identifier;

[0014] If the login instruction is an automatic login instruction, the second application is automatically logged in based on the login Token identifier.

[0015] The embodiment of the present invention further discloses a method for processing login of an application in a browser, which is applied to a server, and the method comprises:

[0016] Receive the login Token sent by the browser;

[0017] Parsing the login Token to obtain a first browser fingerprint corresponding to the first application, and generating a first heartbeat packet corresponding to the first browser fingerprint;

[0018] receiving a second heartbeat packet corresponding to a second application sent by the browser, and comparing the first heartbeat packet with the second heartbeat packet, and generating an automatic login instruction for the second heartbeat packet if the comparison result indicates that the first browser fingerprint and the second browser fingerprint are the same browser fingerprint, wherein the first application and the second application are different applications that belong to the same system and run in the same browser;

[0019] The automatic login instruction is returned to the browser to log in to the second application.

[0020] The embodiment of the present invention further discloses a login processing device for an application in a browser, comprising:

[0021] an identification generating module, configured to, in response to a login instruction for a first application, obtain a first browser fingerprint corresponding to the first application after successful login in the first application, and generate a login Token identification corresponding to the login instruction according to the first browser fingerprint;

[0022] A first heartbeat packet generating module, used to generate a first heartbeat packet corresponding to the first browser fingerprint according to the login Token identifier;

[0023] A second heartbeat packet generating module, configured to obtain a second browser fingerprint corresponding to the second application in response to an access instruction to the second application in the same browser, and generate a second heartbeat packet corresponding to the second browser fingerprint;

[0024] The application login module is used to compare the first heartbeat packet with the second heartbeat packet. If the comparison result between the two indicates that the first browser fingerprint and the second browser fingerprint are the same browser fingerprint, the second application is automatically logged in based on the login Token identifier.

[0025] The embodiment of the present invention further discloses a login processing device for an application in a browser, which is applied to a browser, and the device includes:

[0026] an identification generation module, configured to respond to a login instruction for a first application, obtain a first browser fingerprint corresponding to the first application after successful login in the first application, generate a login Token identification corresponding to the login instruction according to the first browser fingerprint, and send the login Token identification to a server;

[0027] A heartbeat packet generation module, configured to obtain a second browser fingerprint corresponding to the second application in response to an access instruction to the second application in the same browser, and generate a second heartbeat packet corresponding to the second browser fingerprint;

[0028] A login instruction receiving module, used for sending the second heartbeat packet to the server, and receiving a login instruction for the second heartbeat packet returned by the server, wherein the login instruction is an instruction generated based on the login Token identifier;

[0029] The application login module is used to automatically log in to the second application based on the login Token identifier if the login instruction is an automatic login instruction.

[0030] The embodiment of the present invention further discloses a login processing device for an application in a browser, which is applied to a server, and the device includes:

[0031] The identification receiving module is used to receive the login Token identification sent by the browser;

[0032] A heartbeat packet generation module, used to parse the login Token identifier to obtain a first browser fingerprint corresponding to the first application, and generate a first heartbeat packet corresponding to the first browser fingerprint;

[0033] a heartbeat packet comparison module, configured to receive a second heartbeat packet corresponding to a second application and sent by the browser, and compare the first heartbeat packet with the second heartbeat packet, and generate an automatic login instruction for the second heartbeat packet if the comparison result indicates that the first browser fingerprint and the second browser fingerprint are the same browser fingerprint, and the first application and the second application are different applications that belong to the same system and run in the same browser;

[0034] An instruction sending module is used to return the automatic login instruction to the browser to log in to the second application.

[0035] The embodiment of the present invention further discloses an electronic device, comprising a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus;

[0036] The memory is used to store computer programs;

[0037] The processor is used to implement the method described in the embodiment of the present invention when executing the program stored in the memory.

[0038] The embodiment of the present invention further discloses a computer-readable storage medium having instructions stored thereon, which, when executed by one or more processors, enables the processors to execute the method described in the embodiment of the present invention.

[0039] The embodiments of the present invention include the following advantages:

[0040] In an embodiment of the present invention, when a user uses a plurality of associated applications in a browser, a first browser fingerprint corresponding to the first application can be obtained in response to a login instruction for the first application and a login Token identifier corresponding to the login instruction can be generated according to the first browser fingerprint. Then, a first heartbeat packet corresponding to the first browser fingerprint can be generated according to the login Token identifier. When the user uses another application, a second browser fingerprint corresponding to the second application can be obtained in response to an access instruction for the second application in the same browser and a second heartbeat packet corresponding to the second browser fingerprint can be generated. Then, the first heartbeat packet can be associated with the first application. If the comparison result between the first browser fingerprint and the second browser fingerprint indicates that they are the same browser fingerprint, the second application is automatically logged in based on the login Token identifier. Therefore, when the user uses multiple associated applications in the same browser, the browser fingerprint is used as the user's login status identifier, and the browser fingerprints corresponding to different applications are verified for cross-application login based on the heartbeat packet corresponding to the browser fingerprint. The login information in the logged-in application is shared with other applications in the same browser to realize automatic login of the application, simplify the application login process, improve login efficiency, and further improve the efficiency of processing transactions based on different applications. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Figure 1 It is a flowchart of the steps of a login processing method for an in-browser application provided in an embodiment of the present invention;

[0042] Figure 2 It is a flowchart of the steps of a login processing method for an in-browser application provided in an embodiment of the present invention;

[0043] Figure 3 It is a flowchart of the steps of a login processing method for an in-browser application provided in an embodiment of the present invention;

[0044] Figure 4 is a processing flow chart of application login provided in an embodiment of the present invention;

[0045] Figure 5 It is a structural block diagram of a login processing device for an in-browser application provided in an embodiment of the present invention;

[0046] Figure 6 It is a structural block diagram of a login processing device for an in-browser application provided in an embodiment of the present invention;

[0047] Figure 7 It is a structural block diagram of a login processing device for an in-browser application provided in an embodiment of the present invention;

[0048] Figure 8 It is a block diagram of an electronic device provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0049] In order to make the above-mentioned objects, features and advantages of the present invention more obvious and easy to understand, the present invention is further described in detail below with reference to the accompanying drawings and specific embodiments.

[0050] As an example, a complete front-end application will become larger and more complex as time goes by and user needs accumulate, so the iteration problem of the application will lead to increasing difficulty in demand access and subsequent maintenance costs. For example, if a company grows and develops its business, the internal system will gradually be divided into office management system A, personnel management system B, process management system C and project management system D. Each application performs its own functions and does not affect each other. Although the data between applications are interoperable, some applications may need to be authorized by another application before they can continue to execute a certain function. Specifically, student X has just joined the company and now needs to enter system A to fill in personal information. Student Y is the company's internal system administrator. At this time, he logs in to system B to add student X's account and then notifies him to log in to system A. After student X logs in to system A and fills in personal information, he is soon notified that there is a new project development and needs to apply for development funds. At this time, he has to switch to system C to log in (you can log in to each subsystem after registration) and submit the process of development funds after logging in. Soon, he is notified that the development funds have been approved. At this time, he has to switch to system D to log in and submit the development task after logging in.

[0051] It can be seen that a complete system has transaction coordination, so a single application will definitely depend on certain applications. It is precisely because of the cross-domain communication between applications that the login logic developed based on Cookie technology will be completely invalid. Because Cookies cannot be transmitted across domain names and windows, switching systems at this time must re-login to verify the user's identity. In other words, switching between applications requires re-login every time. From a side view, these applications belong to the same system. For users, the same system should not require re-login verification when switching functions (essentially switching applications). This situation greatly affects the user experience. If the system consists of 20 applications, and there happens to be a transaction that is dependent on each of the 20 applications, the user needs to log in separately in each sub-application, which undoubtedly brings a huge login workload to the user and reduces the efficiency of transaction processing.

[0052] In this regard, one of the core inventions of the present invention is that when a user uses multiple applications that are associated with each other in a browser, the user can respond to a login instruction for a first application, and when the user successfully logs in to the first application, obtain a first browser fingerprint corresponding to the first application, and generate a login Token identifier corresponding to the login instruction according to the first browser fingerprint, and then generate a first heartbeat packet corresponding to the first browser fingerprint according to the login Token identifier. When the user uses another application, the user can respond to an access instruction for a second application in the same browser, obtain a second browser fingerprint corresponding to the second application, and generate a second heartbeat packet corresponding to the second browser fingerprint, and then generate the first heartbeat packet corresponding to the second browser fingerprint. The heartbeat packet is compared with the second browser fingerprint. If the comparison result of the two indicates that the first browser fingerprint and the second browser fingerprint are the same browser fingerprint, the second application is automatically logged in based on the login Token identifier. Therefore, when the user uses multiple related applications in the same browser, the browser fingerprint is used as the user's login status identifier, and the browser fingerprints corresponding to different applications are verified across applications based on the heartbeat packet corresponding to the browser fingerprint. The login information in the logged-in application is shared with other applications in the same browser to realize automatic login of the application, simplify the application login process, improve login efficiency, and thus improve the efficiency of processing transactions based on different applications.

[0053] Reference Figure 1 , shows a flowchart of a login processing method for an in-browser application provided in an embodiment of the present invention, which may specifically include the following steps:

[0054] Step 101, in response to a login instruction for a first application, after successful login in the first application, obtaining a first browser fingerprint corresponding to the first application, and generating a login Token identifier corresponding to the login instruction according to the first browser fingerprint;

[0055] Optionally, the first application and the second application, etc., may belong to different sub-applications under the same system, or may be different applications with corresponding associations. In relevant actual transactions, the first application and the second application need to cooperate with each other to complete the corresponding transactions, and the same user may have different login information in different applications. In order to avoid the user from repeatedly logging in to different applications in one transaction, it is necessary to simplify the application login process to improve processing efficiency.

[0056] It should be noted that in the embodiments of the present invention, the first application and the second application are different sub-applications under the same system. A transaction is completed through the cooperation between the first application and the second application, and the present invention does not limit this.

[0057] In an embodiment of the present invention, a user can log in to a first application in a browser running on a user terminal. The terminal can respond to a login instruction for the first application, obtain login information corresponding to the login instruction, and log in to the first application based on the login information. After successfully logging in to the first application, the terminal can obtain a first browser fingerprint corresponding to the first application, and generate a login Token identifier corresponding to the login instruction based on the first browser fingerprint.

[0058] Among them, browser fingerprints can be information that can be used to locate users through various information of the browser without the need for Cookie technology. The browser fingerprint can be used to locate a certain user account. It is a way to passively identify users. For browser fingerprints, it can include screen resolution, system fonts, image content generation methods, browser plug-ins, and Canvas fingerprints, etc.

[0059] Optionally, in an embodiment of the present invention, the browser fingerprint can be a Canvas fingerprint, which can generate dynamic images. The image contents generated in different operating systems, different device platforms, different browser kernels, and different browser shells are not completely the same (although the images look the same to the naked eye); in pixel rendering, different operating systems use different algorithms for anti-aliasing and sub-pixel rendering operations to generate image contents that are not completely the same; in image format, different browsers use different graphics processing engines, different compression levels, and different image export options to generate image contents that are not completely the same; even if the CRC check of the image data generated by the same drawing operation is different, the generated image contents are not completely the same. Therefore, by using the Canvas fingerprint of the browser fingerprint as a unique user identifier, it is ensured that the switching between sub-applications is completed in the current browser and the correct distribution of the login status is guaranteed.

[0060] In a specific implementation, for the first application and the second application that are related to each other, a common container can be packaged in the outer layer of each application, and application registration, application management and route navigation can be performed through the common container. In addition, an event dispatching center based on the HTML5 standard WebSocket server for cross-domain communication is created in the common container, integrating communication events such as login status management, user information management, route authentication, authority distribution, log embedding, and watermark monitoring, so as to extract the modules involved in data communication in each sub-application and hand them over to the event dispatching center of the common container for processing. Specifically, when the user successfully logs in in the first application, the login status management event of the event dispatching center can be triggered, and the event dispatching center responds to the login instruction for the first application, and verifies the login information obtained in the login page of the first application. If the login is successful, the first browser fingerprint corresponding to the first application is obtained, and a login Token corresponding to the login instruction is generated according to the first browser fingerprint. The login Token can be used to identify the login status corresponding to the user account currently logged in by the first application, such as successful login and currently valid.

[0061] In one example, the login Token identifier generated by the first browser fingerprint may be generated by a related algorithm, such as a hash encryption algorithm, a symmetric encryption algorithm, an asymmetric encryption algorithm, etc., and the present invention does not limit this.

[0062] Step 102, generating a first heartbeat packet corresponding to the first browser fingerprint according to the login Token identifier;

[0063] In a specific implementation, based on the generated login Token identifier corresponding to the first application, the login Token identifier can be sent to the server through the login interface, so that the server can generate a corresponding first heartbeat packet based on the login Token identifier and start a detection service for the first heartbeat packet to dynamically detect the validity of the login Token identifier.

[0064] Specifically, after receiving the login Token identifier, the server can parse the first browser fingerprint from the login Token identifier, and generate a first heartbeat packet corresponding to the first browser fingerprint, and then set a validity period for the login Token identifier to detect whether the identifier is valid, and start the heartbeat packet detection service at the same time. By performing heartbeat detection on the first heartbeat packet corresponding to the login Token identifier, it is possible to dynamically detect whether the login status of the first application is still valid, so as to determine whether login to other applications can be achieved based on the login status of the first application.

[0065] It should be noted that there may be a specific pointing between the login Token identifier and the first heartbeat packet, that is, the above generation process is a superset of the first heartbeat packet for the login Token identifier. Then, in the subsequent login processing process, it is possible to find out whether there is a corresponding login Token identifier based on the heartbeat packet.

[0066] Step 103, in response to an access instruction to a second application in the same browser, obtaining a second browser fingerprint corresponding to the second application, and generating a second heartbeat packet corresponding to the second browser fingerprint;

[0067] For a browser, a user can access multiple applications in the same browser to complete a transaction. When the user successfully logs into the first application and then accesses another application in the same browser, the terminal can respond to the access instruction to the second application in the same browser through the event dispatch center, obtain the second browser fingerprint corresponding to the second application, and generate a second heartbeat packet corresponding to the second browser fingerprint. Specifically, the browser fingerprint can be processed by a preset algorithm to generate a corresponding second heartbeat packet, such as a hash encryption algorithm, a symmetric encryption algorithm, an asymmetric encryption algorithm, etc., and the present invention does not limit this.

[0068] It should be noted that, for the first browser fingerprint and the second browser fingerprint, for the same browser, the two may be the same browser fingerprint, and for different browsers, they may correspond to different browser fingerprints, and the present invention does not limit this.

[0069] Step 104: compare the first heartbeat packet with the second heartbeat packet. If the comparison result indicates that the first browser fingerprint and the second browser fingerprint are the same, automatically log in the second application based on the login Token identifier.

[0070] In an embodiment of the present invention, after generating a second heartbeat packet corresponding to a second application, the browser may send the second heartbeat packet to a server, and the server compares the first heartbeat packet with the second heartbeat packet, and based on the comparison result of the two, determines whether the browser fingerprints corresponding to the first heartbeat packet and the second heartbeat packet are the same browser fingerprint. If the comparison result of the two indicates that the first browser fingerprint and the second browser fingerprint are the same browser fingerprint, the second application is automatically logged in based on the login Token identifier, so that when a user uses multiple applications with an associated relationship in the same browser, the browser fingerprint is used as the user's login status identifier, and the browser fingerprints corresponding to different applications are cross-application login verification based on the heartbeat packet corresponding to the browser fingerprint, and the login information in the logged-in application is shared with other applications in the same browser, so as to realize automatic login of the application, simplify the application login process, improve the login efficiency, and further improve the efficiency of processing transactions based on different applications.

[0071] In addition, if the comparison result between the two indicates that the first browser fingerprint and the second browser fingerprint are different browser fingerprints, a login page corresponding to the second application is displayed to respond to the user entering corresponding login information in the login page to complete the login to the second application.

[0072] In the specific implementation, since there is a specific pointing between the heartbeat packet and the login Token identifier, after receiving the second heartbeat packet, the server can parse the second heartbeat packet to obtain the second browser fingerprint, and parse the first heartbeat packet to obtain the first browser fingerprint, and then compare the two to determine whether they are the same. If they are the same, it can be found whether there is a login Token identifier associated with the first heartbeat packet. Specifically, if the comparison result of the two indicates that the first browser fingerprint and the second browser fingerprint are the same browser fingerprint, and there is a login Token identifier associated with the first browser fingerprint and the login Token identifier is still within the validity period, the server can generate an automatic login instruction for the second heartbeat packet, and then return the automatic login instruction to the browser, so that the browser parses the automatic login instruction to obtain the corresponding login Token identifier, and automatically logs in to the second application based on the login Token identifier; if the comparison result of the two indicates that the first browser fingerprint and the second browser fingerprint are the same browser fingerprint, and there is a login Token identifier associated with the first browser fingerprint but the login Token identifier is not within the validity period, the server can generate a manual login instruction for the second heartbeat packet, and return the manual login instruction to the browser, so that the browser displays the login page corresponding to the second application according to the manual display instruction, so as to respond to the user entering the corresponding login information in the login page to complete the login to the second application. Accordingly, if the comparison result between the two indicates that the first browser fingerprint and the second browser fingerprint are different browser fingerprints, the server can generate a manual login instruction for the second heartbeat packet and return the manual login instruction to the browser, so that the browser can display the login page corresponding to the second application according to the manual display instruction, so as to respond to the user entering the corresponding login information in the login page to complete the login to the second application.

[0073] In one example, when a user successfully logs in to a sub-application, a login status management event of the event dispatch center is triggered. The browser where the sub-application is located generates a login status Token based on the browser fingerprint using a preset algorithm. The Token notifies the server through the login interface. At the server layer, a specific heartbeat packet Heartbeat① is generated through the WebSocket server based on the browser fingerprint information carried by the Token. At the same time, the token is set to have a valid time and the heartbeat packet detection service is started. When the user switches to another sub-application in the same browser, the login status management event of the event dispatch center is triggered. The browser generates a Heartbeat② based on the browser fingerprint using a preset algorithm. The Heartbeat② is sent to the server through the WebSocket protocol. When the Heartbeat② is parsed and the corresponding Token is found in the server and the Token has not expired, the current Token is dispatched to the browser, so that another sub-application can automatically request the login interface to log in with the Token. If it is found during the detection that the Token has expired, the token issuance will be canceled and the heartbeat packet detection service will be closed. Therefore, when the user uses multiple related applications in the same browser, the browser fingerprint will be used as the user's login status identifier, and the browser fingerprint corresponding to different applications will be verified across applications based on the heartbeat packet corresponding to the browser fingerprint. The login information of the logged-in application will be shared with other applications in the same browser to achieve automatic login of the application, simplifying the application login process, improving login efficiency, and thus improving the efficiency of processing transactions based on different applications.

[0074] It should be noted that the embodiments of the present invention include but are not limited to the above examples. It is understandable that those skilled in the art can also make settings according to actual needs under the guidance of the ideas of the embodiments of the present invention, and the present invention is not limited to this.

[0075] In an embodiment of the present invention, when a user uses a plurality of associated applications in a browser, a first browser fingerprint corresponding to the first application can be obtained in response to a login instruction for the first application and a login Token identifier corresponding to the login instruction can be generated according to the first browser fingerprint. Then, a first heartbeat packet corresponding to the first browser fingerprint can be generated according to the login Token identifier. When the user uses another application, a second browser fingerprint corresponding to the second application can be obtained in response to an access instruction for the second application in the same browser and a second heartbeat packet corresponding to the second browser fingerprint can be generated. Then, the first heartbeat packet can be associated with the first application. If the comparison result between the first browser fingerprint and the second browser fingerprint indicates that they are the same browser fingerprint, the second application is automatically logged in based on the login Token identifier. Therefore, when the user uses multiple associated applications in the same browser, the browser fingerprint is used as the user's login status identifier, and the browser fingerprints corresponding to different applications are verified for cross-application login based on the heartbeat packet corresponding to the browser fingerprint. The login information in the logged-in application is shared with other applications in the same browser to realize automatic login of the application, simplify the application login process, improve login efficiency, and further improve the efficiency of processing transactions based on different applications.

[0076] Reference Figure 2 , shows a flowchart of a login processing method for an application in a browser provided in an embodiment of the present invention, which is applied to a browser and may specifically include the following steps:

[0077] Step 201, in response to a login instruction for a first application, after successful login in the first application, obtaining a first browser fingerprint corresponding to the first application, generating a login Token identifier corresponding to the login instruction according to the first browser fingerprint, and sending the login Token identifier to a server;

[0078] Step 202, in response to an access instruction to a second application in the same browser, obtaining a second browser fingerprint corresponding to the second application, and generating a second heartbeat packet corresponding to the second browser fingerprint;

[0079] Step 203, sending the second heartbeat packet to the server, and receiving a login instruction for the second heartbeat packet returned by the server, wherein the login instruction is an instruction generated based on the login Token identifier;

[0080] Step 204: If the login instruction is an automatic login instruction, the second application is automatically logged in based on the login Token identifier.

[0081] In an optional embodiment, it also includes:

[0082] If the login instruction is the manual login instruction, a login page corresponding to the second application is displayed in response to the user entering corresponding login information in the login page to complete the login to the second application.

[0083] In an optional embodiment, the first application and the second application belong to the same system, the system includes a common container corresponding to the first application and the second application, a corresponding event dispatch center is created in the common container, and the response to the login instruction for the first application, after successful login in the first application, obtaining a first browser fingerprint corresponding to the first application, and generating a login Token identifier corresponding to the login instruction according to the first browser fingerprint, includes:

[0084] In response to the login instruction for the first application, the event scheduling center verifies the login information obtained in the login page of the first application. If the login is successful, the first browser fingerprint corresponding to the first application is obtained, and a login Token identifier corresponding to the login instruction is generated based on the first browser fingerprint.

[0085] In an optional embodiment, in response to an access instruction to a second application in the same browser, obtaining a second browser fingerprint corresponding to the second application, and generating a second heartbeat packet corresponding to the second browser fingerprint includes:

[0086] In response to an access instruction to a second application in the same browser, the event dispatch center obtains a second browser fingerprint corresponding to the second application and generates a second heartbeat packet corresponding to the second browser fingerprint.

[0087] In an embodiment of the present invention, when a user uses a plurality of associated applications in a browser, a first browser fingerprint corresponding to the first application can be obtained in response to a login instruction for the first application and a login Token identifier corresponding to the login instruction can be generated according to the first browser fingerprint. Then, a first heartbeat packet corresponding to the first browser fingerprint can be generated according to the login Token identifier. When the user uses another application, a second browser fingerprint corresponding to the second application can be obtained in response to an access instruction for the second application in the same browser and a second heartbeat packet corresponding to the second browser fingerprint can be generated. Then, the first heartbeat packet can be associated with the first application. If the comparison result between the first browser fingerprint and the second browser fingerprint indicates that they are the same browser fingerprint, the second application is automatically logged in based on the login Token identifier. Therefore, when the user uses multiple associated applications in the same browser, the browser fingerprint is used as the user's login status identifier, and the browser fingerprints corresponding to different applications are verified for cross-application login based on the heartbeat packet corresponding to the browser fingerprint. The login information in the logged-in application is shared with other applications in the same browser to realize automatic login of the application, simplify the application login process, improve login efficiency, and further improve the efficiency of processing transactions based on different applications.

[0088] Reference Figure 3 , shows a flowchart of a login processing method for an in-browser application provided in an embodiment of the present invention, which is applied to a server and may specifically include the following steps:

[0089] Step 301, receiving a login Token sent by a browser;

[0090] Step 302: parse the login Token to obtain a first browser fingerprint corresponding to the first application, and generate a first heartbeat packet corresponding to the first browser fingerprint;

[0091] Step 303, receiving a second heartbeat packet corresponding to a second application sent by the browser, and comparing the first heartbeat packet with the second heartbeat packet, and if the comparison result between the two indicates that the first browser fingerprint and the second browser fingerprint are the same browser fingerprint, then generating an automatic login instruction for the second heartbeat packet, and the first application and the second application are different applications that belong to the same system and run in the same browser;

[0092] Step 304: Return the automatic login instruction to the browser to log in to the second application.

[0093] In an optional embodiment, it also includes:

[0094] If the comparison result between the two indicates that the first browser fingerprint and the second browser fingerprint are different browser fingerprints, a manual login instruction for the second heartbeat packet is generated and the manual login instruction is returned to the browser.

[0095] In an optional embodiment, after generating the first heartbeat packet corresponding to the first browser fingerprint, the method further includes:

[0096] The login Token identifier is set with a validity period for detecting whether the identifier is valid.

[0097] In an optional embodiment, if the comparison result between the two indicates that the first browser fingerprint and the second browser fingerprint are the same browser fingerprint, then generating an automatic login instruction for the second heartbeat packet includes:

[0098] If the comparison result between the two indicates that the first browser fingerprint and the second browser fingerprint are the same browser fingerprint, and the login Token identification is still within the validity period, an automatic login instruction for the second heartbeat packet is generated.

[0099] In an optional embodiment, it also includes:

[0100] If the comparison result between the two indicates that the first browser fingerprint and the second browser fingerprint are the same browser fingerprint, and the login Token identifier is not within the validity period, a manual login instruction for the second heartbeat packet is generated.

[0101] In an embodiment of the present invention, when a user uses a plurality of associated applications in a browser, a first browser fingerprint corresponding to the first application can be obtained in response to a login instruction for the first application and a login Token identifier corresponding to the login instruction can be generated according to the first browser fingerprint. Then, a first heartbeat packet corresponding to the first browser fingerprint can be generated according to the login Token identifier. When the user uses another application, a second browser fingerprint corresponding to the second application can be obtained in response to an access instruction for the second application in the same browser and a second heartbeat packet corresponding to the second browser fingerprint can be generated. Then, the first heartbeat packet can be associated with the first application. If the comparison result between the first browser fingerprint and the second browser fingerprint indicates that they are the same browser fingerprint, the second application is automatically logged in based on the login Token identifier. Therefore, when the user uses multiple associated applications in the same browser, the browser fingerprint is used as the user's login status identifier, and the browser fingerprints corresponding to different applications are verified for cross-application login based on the heartbeat packet corresponding to the browser fingerprint. The login information in the logged-in application is shared with other applications in the same browser to realize automatic login of the application, simplify the application login process, improve login efficiency, and further improve the efficiency of processing transactions based on different applications.

[0102] In order to enable those skilled in the art to better understand the technical solution in the embodiments of the present invention, an example is given below for illustrative explanation:

[0103] Reference Figure 4 , shows a processing flow chart of application login provided in an embodiment of the present invention. Different sub-applications in the same system include: applications A to E (a.xyz.com, b.xyz.com, c.xyz.com, d.xyz.com, e.xyz.com, etc.), each sub-application independently performs its own functions, but communicates through the technical solutions involved in the embodiment of the present invention. A common container is packaged in the outer layer of each sub-application, and the sub-application is processed from P1 to P3 through the common container.

[0104] P1: Access the API of the technical solution of the present invention during development. Deploy the developed application to the server (without limiting the deployment rules), exist as a registered sub-application and inject relevant information of the sub-application into the public container.

[0105] P2: Manage the sub-applications connected to the technical solution of the present invention to facilitate the management personnel to add, delete and query the information of the sub-applications.

[0106] P3: Configure routing for sub-applications. When you visit a sub-page in the system, you will jump to the corresponding sub-application. For example, when you visit / a, you will jump to application A; when you visit / b, you will jump to application B; and when you visit / c, you will jump to application C.

[0107] S: After the relevant applications are configured based on route navigation, an event dispatching center based on the HTML5 standard postMessage for cross-domain communication is created in the public container. It integrates communication events such as login status management, user information management, route authentication, permission distribution, log tracking, and watermark monitoring. The modules involved in data communication in each sub-application are extracted and handed over to the event dispatching center of the public container for processing. S1~S6 are event instances in S.

[0108] Y: The event instance in S can be called by each sub-application (application A~E) through the event communication agent (marked as Y). Y, as the general stack of the event communication agent, is responsible for coordinating the two-way communication between S and applications A~E.

[0109] X: A sub-application performs user login verification by scheduling S1 (login status management) in S. After successful login, the current user's login status (a login status Token is generated based on the browser fingerprint using a preset algorithm) is submitted to the server's record database (marked as X, used to record the correspondence between the Token and the Heartbeat).

[0110] After the above situation is completed: when switching to other sub-applications, first generate the Heartbeat corresponding to the browser accessing the sub-application, schedule S1 through Y, S1 compares the browser fingerprint parsed by Heartbeat with X in the server, if there is a corresponding user login status Token and it is verified that it is still within the effective time, then send the Token to the sub-application through Y, the sub-application automatically logs in by storing the Token locally, and brings the Token when requesting other interfaces subsequently, if there is no corresponding user login status Token or the verification Token has expired, it is sent to the sub-application through Y, requiring the sub-application to log in again for verification.

[0111] It should be noted that, for the sake of simplicity, the method embodiments are described as a series of action combinations, but those skilled in the art should be aware that the embodiments of the present invention are not limited by the order of the actions described, because according to the embodiments of the present invention, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions involved are not necessarily required by the embodiments of the present invention.

[0112] Reference Figure 5, shows a structural block diagram of a login processing device for an in-browser application provided in an embodiment of the present invention, which may specifically include the following modules:

[0113] The identification generating module 501 is used for, in response to a login instruction for a first application, obtaining a first browser fingerprint corresponding to the first application after successful login in the first application, and generating a login Token identification corresponding to the login instruction according to the first browser fingerprint;

[0114] A first heartbeat packet generating module 502, configured to generate a first heartbeat packet corresponding to the first browser fingerprint according to the login Token identifier;

[0115] A second heartbeat packet generating module 503, configured to obtain a second browser fingerprint corresponding to the second application in response to an access instruction to the second application in the same browser, and generate a second heartbeat packet corresponding to the second browser fingerprint;

[0116] The application login module 504 is used to compare the first heartbeat packet with the second heartbeat packet. If the comparison result indicates that the first browser fingerprint and the second browser fingerprint are the same, the second application is automatically logged in based on the login Token identifier.

[0117] In an optional embodiment, it also includes:

[0118] The login page display module is used to display the login page corresponding to the second application if the comparison result between the two indicates that the first browser fingerprint and the second browser fingerprint are different browser fingerprints, so as to respond to the user entering corresponding login information in the login page to complete the login to the second application.

[0119] In an optional embodiment, the first heartbeat packet generating module 502 is specifically used to:

[0120] Parsing the first browser fingerprint from the login Token identifier and generating a first heartbeat packet corresponding to the first browser fingerprint;

[0121] The login Token identifier is set with a validity period for detecting whether the identifier is valid.

[0122] In an optional embodiment, the application login module 504 is specifically used for:

[0123] If the comparison result between the two indicates that the first browser fingerprint and the second browser fingerprint are the same browser fingerprint, and the login Token identifier is still within the validity period, the second application is automatically logged in based on the login Token identifier.

[0124] In an optional embodiment, it also includes:

[0125] The page display module is used to display the login page corresponding to the second application if the comparison result between the two indicates that the first browser fingerprint and the second browser fingerprint are the same browser fingerprint and the login Token identifier is not within the validity period.

[0126] In an optional embodiment, the first application and the second application belong to the same system, the system includes a common container corresponding to the first application and the second application, a corresponding event scheduling center is created in the common container, and the identifier generation module 501 is specifically used to:

[0127] In response to the login instruction for the first application, the event scheduling center verifies the login information obtained in the login page of the first application. If the login is successful, the first browser fingerprint corresponding to the first application is obtained, and a login Token identifier corresponding to the login instruction is generated based on the first browser fingerprint.

[0128] In an optional embodiment, the second heartbeat packet generating module 503 is specifically used to:

[0129] In response to an access instruction to a second application in the same browser, the event dispatch center obtains a second browser fingerprint corresponding to the second application and generates a second heartbeat packet corresponding to the second browser fingerprint.

[0130] Reference Figure 6 , shows a structural block diagram of a login processing device for an application in a browser provided in an embodiment of the present invention, which is applied to a browser and may specifically include the following modules:

[0131] The identification generating module 601 is used for, in response to a login instruction for a first application, obtaining a first browser fingerprint corresponding to the first application after successful login in the first application, generating a login Token identification corresponding to the login instruction according to the first browser fingerprint, and sending the login Token identification to a server;

[0132] A heartbeat packet generation module 602, configured to obtain a second browser fingerprint corresponding to the second application in response to an access instruction to the second application in the same browser, and generate a second heartbeat packet corresponding to the second browser fingerprint;

[0133] A login instruction receiving module 603, used to send the second heartbeat packet to the server, and receive a login instruction for the second heartbeat packet returned by the server, wherein the login instruction is an instruction generated based on the login Token identifier;

[0134] The application login module 604 is used to automatically log in the second application based on the login Token identifier if the login instruction is an automatic login instruction.

[0135] In an optional embodiment, it also includes:

[0136] The page display module is used to display the login page corresponding to the second application if the login instruction is the manual login instruction, so as to respond to the user entering corresponding login information in the login page to complete the login to the second application.

[0137] In an optional embodiment, the first application and the second application belong to the same system, the system includes a common container corresponding to the first application and the second application, a corresponding event scheduling center is created in the common container, and the identifier generation module 601 is specifically used to:

[0138] In response to the login instruction for the first application, the event scheduling center verifies the login information obtained in the login page of the first application. If the login is successful, the first browser fingerprint corresponding to the first application is obtained, and a login Token identifier corresponding to the login instruction is generated based on the first browser fingerprint.

[0139] In an optional embodiment, the heartbeat packet generation module 602 is specifically used to:

[0140] In response to an access instruction to a second application in the same browser, the event dispatch center obtains a second browser fingerprint corresponding to the second application and generates a second heartbeat packet corresponding to the second browser fingerprint.

[0141] Reference Figure 7 , shows a structural block diagram of a login processing device for an application in a browser provided in an embodiment of the present invention, which is applied to a server and may specifically include the following modules:

[0142] The identification receiving module 701 is used to receive the login Token identification sent by the browser;

[0143] A heartbeat packet generation module 702, configured to parse the login Token identifier to obtain a first browser fingerprint corresponding to the first application, and generate a first heartbeat packet corresponding to the first browser fingerprint;

[0144] The heartbeat packet comparison module 703 is used to receive the second heartbeat packet corresponding to the second application sent by the browser, and compare the first heartbeat packet with the second heartbeat packet. If the comparison result between the two indicates that the first browser fingerprint and the second browser fingerprint are the same browser fingerprint, an automatic login instruction for the second heartbeat packet is generated, and the first application and the second application are different applications that belong to the same system and run in the same browser;

[0145] The instruction sending module 704 is used to return the automatic login instruction to the browser to log in to the second application.

[0146] In an optional embodiment, it also includes:

[0147] The manual instruction generation module is used to generate a manual login instruction for the second heartbeat packet if the comparison result between the two indicates that the first browser fingerprint and the second browser fingerprint are different browser fingerprints, and return the manual login instruction to the browser.

[0148] In an optional embodiment, the device further includes:

[0149] The validity period detection module is used to set a validity period for the login Token identifier to detect whether the identifier is valid.

[0150] In an optional embodiment, the heartbeat packet comparison module 703 is specifically used for:

[0151] If the comparison result between the two indicates that the first browser fingerprint and the second browser fingerprint are the same browser fingerprint, and the login Token identification is still within the validity period, an automatic login instruction for the second heartbeat packet is generated.

[0152] In an optional embodiment, it also includes:

[0153] The instruction generation module is used to generate a manual login instruction for the second heartbeat packet if the comparison result between the two indicates that the first browser fingerprint and the second browser fingerprint are the same browser fingerprint and the login Token identifier is not within the validity period.

[0154] As for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0155] In addition, an embodiment of the present invention further provides an electronic device, comprising: a processor, a memory, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, each process of the above-mentioned login processing method embodiment for an in-browser application is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be described here.

[0156] The embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, each process of the above-mentioned login processing method embodiment of the browser application is implemented, and the same technical effect can be achieved. To avoid repetition, it is not repeated here. The computer-readable storage medium is, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0157] Figure 8 A schematic diagram of the hardware structure of an electronic device for implementing various embodiments of the present invention.

[0158] The electronic device 800 includes but is not limited to: a radio frequency unit 801, a network module 802, an audio output unit 803, an input unit 804, a sensor 805, a display unit 806, a user input unit 807, an interface unit 808, a memory 809, a processor 810, and a power supply 811. Those skilled in the art will appreciate that the electronic device structure involved in the embodiments of the present invention does not constitute a limitation on the electronic device, and the electronic device may include more or fewer components than shown in the figure, or combine certain components, or arrange components differently. In the embodiments of the present invention, the electronic device includes but is not limited to a mobile phone, a tablet computer, a laptop computer, a PDA, a vehicle-mounted terminal, a wearable device, and a pedometer.

[0159] It should be understood that in the embodiment of the present invention, the radio frequency unit 801 can be used for receiving and sending signals during information transmission or communication. Specifically, after receiving downlink data from the base station, it is sent to the processor 810 for processing; in addition, uplink data is sent to the base station. Generally, the radio frequency unit 801 includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc. In addition, the radio frequency unit 801 can also communicate with the network and other devices through a wireless communication system.

[0160] The electronic device provides users with wireless broadband Internet access through the network module 802, such as helping users to send and receive emails, browse web pages, and access streaming media.

[0161] The audio output unit 803 can convert the audio data received by the RF unit 801 or the network module 802 or stored in the memory 809 into an audio signal and output it as sound. Moreover, the audio output unit 803 can also provide audio output related to a specific function performed by the electronic device 800 (for example, a call signal reception sound, a message reception sound, etc.). The audio output unit 803 includes a speaker, a buzzer, a receiver, etc.

[0162] The input unit 804 is used to receive audio or video signals. The input unit 804 may include a graphics processor (GPU) 8041 and a microphone 8042, and the graphics processor 8041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The processed image frame can be displayed on the display unit 806. The image frame processed by the graphics processor 8041 can be stored in the memory 809 (or other storage medium) or sent via the radio frequency unit 801 or the network module 802. The microphone 8042 can receive sound and can process such sound into audio data. The processed audio data can be converted into a format output that can be sent to a mobile communication base station via the radio frequency unit 801 in the case of a telephone call mode.

[0163] The electronic device 800 also includes at least one sensor 805, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor and a proximity sensor, wherein the ambient light sensor can adjust the brightness of the display panel 8061 according to the brightness of the ambient light, and the proximity sensor can turn off the display panel 8061 and / or the backlight when the electronic device 800 is moved to the ear. As a type of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally three axes), and can detect the magnitude and direction of gravity when stationary, which can be used to identify the posture of the electronic device (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc.; the sensor 805 can also include a fingerprint sensor, a pressure sensor, an iris sensor, a molecular sensor, a gyroscope, a barometer, a hygrometer, a thermometer, an infrared sensor, etc., which will not be repeated here.

[0164] The display unit 806 is used to display information input by the user or information provided to the user. The display unit 806 may include a display panel 8061, which may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.

[0165] The user input unit 807 can be used to receive input digital or character information, and to generate key signal input related to user settings and function control of the electronic device. Specifically, the user input unit 807 includes a touch panel 8071 and other input devices 8072. The touch panel 8071, also known as a touch screen, can collect the user's touch operation on or near it (such as the user's operation on the touch panel 8071 or near the touch panel 8071 using any suitable object or accessory such as a finger, stylus, etc.). The touch panel 8071 may include two parts: a touch detection device and a touch controller. Among them, the touch detection device detects the user's touch orientation, detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into the contact point coordinates, and then sends it to the processor 810, receives the command sent by the processor 810 and executes it. In addition, the touch panel 8071 can be implemented using multiple types such as resistive, capacitive, infrared and surface acoustic waves. In addition to the touch panel 8071, the user input unit 807 may also include other input devices 8072. Specifically, other input devices 8072 may include but are not limited to a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be described in detail here.

[0166] Further, the touch panel 8071 may be covered on the display panel 8061. When the touch panel 8071 detects a touch operation on or near it, it is transmitted to the processor 810 to determine the type of the touch event, and then the processor 810 provides a corresponding visual output on the display panel 8061 according to the type of the touch event. It can be understood that in one embodiment, the touch panel 8071 and the display panel 8061 are used as two independent components to implement the input and output functions of the electronic device, but in some embodiments, the touch panel 8071 and the display panel 8061 can be integrated to implement the input and output functions of the electronic device, which is not limited here.

[0167] The interface unit 808 is an interface for connecting an external device to the electronic device 800. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, an audio input / output (I / O) port, a video I / O port, a headphone port, etc. The interface unit 808 may be used to receive input (e.g., data information, power, etc.) from an external device and transmit the received input to one or more elements within the electronic device 800 or may be used to transmit data between the electronic device 800 and an external device.

[0168] The memory 809 can be used to store software programs and various data. The memory 809 can mainly include a program storage area and a data storage area, wherein the program storage area can store an operating system, at least one application required for a function (such as a sound playback function, an image playback function, etc.), etc.; the data storage area can store data created according to the use of the mobile phone (such as audio data, a phone book, etc.), etc. In addition, the memory 809 can include a high-speed random access memory, and can also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage devices.

[0169] The processor 810 is the control center of the electronic device. It uses various interfaces and lines to connect various parts of the entire electronic device. By running or executing software programs and / or modules stored in the memory 809 and calling data stored in the memory 809, it performs various functions of the electronic device and processes data, thereby monitoring the electronic device as a whole. The processor 810 may include one or more processing units; preferably, the processor 810 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs, and the modem processor mainly processes wireless communications. It is understandable that the above-mentioned modem processor may not be integrated into the processor 810.

[0170] The electronic device 800 may also include a power supply 811 (such as a battery) for supplying power to each component. Preferably, the power supply 811 may be logically connected to the processor 810 through a power management system, thereby implementing functions such as charging, discharging, and power consumption management through the power management system.

[0171] In addition, the electronic device 800 includes some functional modules not shown, which will not be described in detail here.

[0172] It should be noted that, in this article, the terms "include", "comprises" or any other variations 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, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0173] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for enabling a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in each embodiment of the present invention.

[0174] The embodiments of the present invention are described above in conjunction with the accompanying drawings, but the present invention is not limited to the above-mentioned specific implementation modes, which are merely illustrative rather than restrictive. Under the guidance of the present invention, ordinary technicians in this field can also make many forms without departing from the scope of protection of the present invention and the claims, all of which are within the protection of the present invention.

[0175] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed in the embodiments of the present invention can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.

[0176] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0177] In the embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0178] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0179] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0180] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard disks, ROM, RAM, magnetic disks, or optical disks.

[0181] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present invention, which should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims

1. A method for processing login of an application in a browser, characterized in that: include: In response to a login instruction for a first application, after successful login in the first application, obtaining a first browser fingerprint corresponding to the first application, and generating a login Token identifier corresponding to the login instruction according to the first browser fingerprint; The first browser fingerprint is obtained by parsing the login Token identifier, and a first heartbeat packet corresponding to the first browser fingerprint is generated; the login Token identifier is a superset of the first heartbeat packet; Setting a validity period for the login Token identifier to detect whether the identifier is valid, and detecting whether the login Token identifier is within the validity period by performing a heartbeat detection on the first heartbeat packet corresponding to the login Token identifier; In response to an access instruction to a second application in the same browser, a second browser fingerprint corresponding to the second application is obtained, and a second heartbeat packet corresponding to the second browser fingerprint is generated; the first browser fingerprint and the second browser fingerprint both include a Canvas fingerprint; the Canvas fingerprint is used to generate a dynamic image; the Canvas fingerprints of browsers with different operating systems, different device platforms, different browser kernels, and different browser shells have different contents of the dynamic images corresponding to them; The first heartbeat packet is compared with the second heartbeat packet. If the comparison result indicates that the first browser fingerprint and the second browser fingerprint are the same and the login Token identifier is still within the validity period, the second application is automatically logged in based on the login Token identifier.

2. The method according to claim 1, characterized in that Also includes: If the comparison result between the two indicates that the first browser fingerprint and the second browser fingerprint are different browser fingerprints, a login page corresponding to the second application is displayed in response to the user entering corresponding login information in the login page to complete the login to the second application.

3. The method according to claim 1, characterized in that Also includes: If the comparison result between the two indicates that the first browser fingerprint and the second browser fingerprint are the same browser fingerprint, and the login Token identifier is not within the validity period, the login page corresponding to the second application is displayed.

4. The method according to claim 1, characterized in that: The first application and the second application belong to the same system, the system includes a common container corresponding to the first application and the second application, a corresponding event dispatch center is created in the common container, and the response to the login instruction for the first application, after successful login in the first application, a first browser fingerprint corresponding to the first application is obtained, and a login Token identifier corresponding to the login instruction is generated according to the first browser fingerprint, including: In response to the login instruction for the first application, the event scheduling center verifies the login information obtained in the login page of the first application. If the login is successful, the first browser fingerprint corresponding to the first application is obtained, and a login Token identifier corresponding to the login instruction is generated based on the first browser fingerprint.

5. The method according to claim 4, characterized in that The step of obtaining a second browser fingerprint corresponding to the second application in response to an access instruction to the second application in the same browser, and generating a second heartbeat packet corresponding to the second browser fingerprint includes: In response to an access instruction to a second application in the same browser, the event dispatch center obtains a second browser fingerprint corresponding to the second application and generates a second heartbeat packet corresponding to the second browser fingerprint.

6. A method for processing login of an application in a browser, characterized in that: Applied to a browser, the method comprises: In response to a login instruction for a first application, after successful login in the first application, a first browser fingerprint corresponding to the first application is obtained, and a login Token identifier corresponding to the login instruction is generated according to the first browser fingerprint, and the login Token identifier is sent to a server; the first browser fingerprint is used to generate a first heartbeat packet corresponding to the first browser fingerprint; the login Token identifier includes the first browser fingerprint, and the login Token identifier is a superset of the first heartbeat packet; In response to an access instruction to a second application in the same browser, a second browser fingerprint corresponding to the second application is obtained, and a second heartbeat packet corresponding to the second browser fingerprint is generated; the first browser fingerprint and the second browser fingerprint both include a Canvas fingerprint; the Canvas fingerprint is used to generate a dynamic image; the Canvas fingerprints of browsers with different operating systems, different device platforms, different browser kernels, and different browser shells have different contents of the dynamic images corresponding to them; The second heartbeat packet is sent to the server, and a login instruction for the second heartbeat packet returned by the server is received; the server is used to compare the first heartbeat packet with the second heartbeat packet, and if the comparison result between the two indicates that the first browser fingerprint and the second browser fingerprint are the same browser fingerprint, and the login Token identification is still within the validity period, then a login instruction for the second heartbeat packet is generated; If the login instruction is an automatic login instruction, the second application is automatically logged in based on the login Token identifier.

7. The method according to claim 6, characterized in that Also includes: If the login instruction is a manual login instruction, a login page corresponding to the second application is displayed in response to the user entering corresponding login information in the login page to complete the login to the second application.

8. The method according to claim 6 or 7, characterized in that: The first application and the second application belong to the same system, the system includes a common container corresponding to the first application and the second application, a corresponding event dispatch center is created in the common container, and the response to the login instruction for the first application, after successful login in the first application, a first browser fingerprint corresponding to the first application is obtained, and a login Token identifier corresponding to the login instruction is generated according to the first browser fingerprint, including: In response to the login instruction for the first application, the event scheduling center verifies the login information obtained in the login page of the first application. If the login is successful, the first browser fingerprint corresponding to the first application is obtained, and a login Token identifier corresponding to the login instruction is generated based on the first browser fingerprint.

9. The method according to claim 8, characterized in that The step of obtaining a second browser fingerprint corresponding to the second application in response to an access instruction to the second application in the same browser, and generating a second heartbeat packet corresponding to the second browser fingerprint includes: In response to an access instruction to a second application in the same browser, the event dispatch center obtains a second browser fingerprint corresponding to the second application and generates a second heartbeat packet corresponding to the second browser fingerprint.

10. A method for processing login of an application in a browser, characterized in that: Applied to a server, the method comprises: Receive the login Token sent by the browser; A first browser fingerprint corresponding to the first application is obtained by parsing the login Token identifier, and a first heartbeat packet corresponding to the first browser fingerprint is generated; the login Token identifier is a superset of the first heartbeat packet; Setting a validity period for the login Token identifier to detect whether the identifier is valid, and detecting whether the login Token identifier is within the validity period by performing a heartbeat detection on the first heartbeat packet corresponding to the login Token identifier; Receive a second heartbeat packet corresponding to the second application sent by the browser, and compare the first heartbeat packet with the second heartbeat packet. If the comparison result between the two indicates that the first browser fingerprint and the second browser fingerprint are the same browser fingerprint, and the login Token identifier is still within the validity period, then generate an automatic login instruction for the second heartbeat packet, wherein the first application and the second application are different applications belonging to the same system and running in the same browser; the first browser fingerprint and the second browser fingerprint both include Canvas fingerprints; the Canvas fingerprints are used to generate dynamic images; the contents of the dynamic images corresponding to the Canvas fingerprints of browsers with different operating systems, different device platforms, different browser kernels, and different browser shells are different; The automatic login instruction is returned to the browser to log in to the second application.

11. The method according to claim 10, characterized in that Also includes: If the comparison result between the two indicates that the first browser fingerprint and the second browser fingerprint are different browser fingerprints, a manual login instruction for the second heartbeat packet is generated and the manual login instruction is returned to the browser.

12. The method according to claim 10, characterized in that Also includes: If the comparison result between the two indicates that the first browser fingerprint and the second browser fingerprint are the same browser fingerprint, and the login Token identifier is not within the validity period, a manual login instruction for the second heartbeat packet is generated.

13. A login processing device for an application in a browser, characterized in that: include: an identification generating module, configured to, in response to a login instruction for a first application, obtain a first browser fingerprint corresponding to the first application after successful login in the first application, and generate a login Token identification corresponding to the login instruction according to the first browser fingerprint; A first heartbeat packet generating module, configured to parse the login Token to obtain the first browser fingerprint, and generate a first heartbeat packet corresponding to the first browser fingerprint; the login Token is a superset of the first heartbeat packet; A first validity period setting module, used to set a validity period for the login Token identifier for detecting whether the identifier is valid, and detect whether the login Token identifier is within the validity period by performing a heartbeat detection on a first heartbeat packet corresponding to the login Token identifier; A second heartbeat packet generation module is used to obtain a second browser fingerprint corresponding to the second application in response to an access instruction to the second application in the same browser, and generate a second heartbeat packet corresponding to the second browser fingerprint; the first browser fingerprint and the second browser fingerprint both include a Canvas fingerprint; the Canvas fingerprint is used to generate a dynamic image; the Canvas fingerprint of browsers with different operating systems, different device platforms, different browser kernels and different browser shells corresponds to different contents of the dynamic image; The application login module is used to compare the first heartbeat packet with the second heartbeat packet. If the comparison result between the two indicates that the first browser fingerprint and the second browser fingerprint are the same browser fingerprint, and the login Token identifier is still within the validity period, the second application is automatically logged in based on the login Token identifier.

14. A login processing device for an application in a browser, characterized in that: Applied to a browser, the device comprises: an identification generation module, configured to, in response to a login instruction for a first application, obtain a first browser fingerprint corresponding to the first application after successful login in the first application, generate a login Token identification corresponding to the login instruction according to the first browser fingerprint, and send the login Token identification to a server; the first browser fingerprint is used to generate a first heartbeat packet corresponding to the first browser fingerprint; the login Token identification includes the first browser fingerprint, and the login Token identification is a superset of the first heartbeat packet; A heartbeat packet generation module, configured to obtain a second browser fingerprint corresponding to the second application in response to an access instruction to the second application in the same browser, and generate a second heartbeat packet corresponding to the second browser fingerprint; the first browser fingerprint and the second browser fingerprint both include a Canvas fingerprint; the Canvas fingerprint is used to generate a dynamic image; the contents of the dynamic images corresponding to the Canvas fingerprints of browsers with different operating systems, different device platforms, different browser kernels, and different browser shells are different; A login instruction receiving module, used for sending the second heartbeat packet to the server, and receiving the login instruction for the second heartbeat packet returned by the server; the server is used for comparing the first heartbeat packet with the second heartbeat packet, and if the comparison result of the two indicates that the first browser fingerprint and the second browser fingerprint are the same browser fingerprint, and the login Token identification is still within the validity period, then generating a login instruction for the second heartbeat packet; The application login module is used to automatically log in to the second application based on the login Token identifier if the login instruction is an automatic login instruction.

15. A login processing device for an application in a browser, characterized in that: Applied to a server, the device comprises: The identification receiving module is used to receive the login Token identification sent by the browser; A heartbeat packet generation module, configured to parse the login Token identifier to obtain a first browser fingerprint corresponding to the first application, and generate a first heartbeat packet corresponding to the first browser fingerprint; the login Token identifier is a superset of the first heartbeat packet; A second validity period setting module is used to set a validity period for the login Token identifier for detecting whether the identifier is valid, and detect whether the login Token identifier is within the validity period by performing a heartbeat detection on the first heartbeat packet corresponding to the login Token identifier; A heartbeat packet comparison module is used to receive a second heartbeat packet corresponding to a second application sent by the browser, and compare the first heartbeat packet with the second heartbeat packet. If the comparison result of the two indicates that the first browser fingerprint and the second browser fingerprint are the same browser fingerprint, and the login Token identifier is still within the validity period, then an automatic login instruction for the second heartbeat packet is generated, wherein the first application and the second application are different applications belonging to the same system and running in the same browser; the first browser fingerprint and the second browser fingerprint both include Canvas fingerprints; the Canvas fingerprints are used to generate dynamic images; the contents of the dynamic images corresponding to the Canvas fingerprints of browsers with different operating systems, different device platforms, different browser kernels and different browser shells are different; An instruction sending module is used to return the automatic login instruction to the browser to log in to the second application.

16. An electronic device, characterized in that: It includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus; The memory is used to store computer programs; The processor is used to implement the method according to any one of claims 1 to 12 when executing the program stored in the memory.

17. A computer-readable storage medium having instructions stored thereon, which, when executed by one or more processors, cause the processors to perform the method according to any one of claims 1 to 12.

Images