A website login state sharing method and system

Abstract

The application discloses a website login state sharing method and system, and belongs to the technical field of website application. The method comprises the following steps: for the cloud, a cookie pool is established on the cloud, and a service interface is established for the cookie pool; binding information is generated, and the binding information is stored in the cookie pool; the cookie pool is inquired according to a specified login account; the same specified login account is allowed to log in a target website of a business system, and a keep-alive interface of the target website is called to keep alive the login state of the specified login account and the same specified login account. The method can realize one-party login and multi-party sharing, avoid forced offline caused by repeated login, ensure business continuity, keep alive the login state, prolong the effective duration of the login state, and improve the user experience.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of website application, and more particularly, to a website login state sharing method and system. BACKGROUND

[0002] For internet products in the form of a website, it is sometimes necessary to integrate the website into other business systems to form an integrated whole and improve user experience. There are two main integration methods. One is to directly embed a website page, and users can operate directly in the business system intranet webpage without the need to open the website separately. The other is to analyze and imitate the calling of a website interface to realize business operation, and a different display interface from the original website can be made to achieve better consistency with the business system.

[0003] However, a website usually contains a login function. When multiple logins occur, the user who logs in later can operate, and the user who logs in first will be forced to log out and enter an unlogged-in state. Since there are many business systems, it is easy to have simultaneous use of website functions after integrating the website into the business systems, thereby causing frequent logout and inability to normally use the business. SUMMARY

[0004] To solve the above problems, the present application provides a website login state sharing method, which comprises the following steps:

[0005] For the cloud, a cookie pool is established on the cloud, and a service interface is established for the cookie pool;

[0006] After a specified login account logs in a target website of a business system, the service interface is called to bind the cookie information generated after the specified login account logs in the target website of the business system to the specified login account, generate binding information, and store the binding information in the cookie pool;

[0007] When the specified login account has logged in the target website of the business system and the same specified login account logs in the target website of the business system, the integration mode of the target website is determined, the service interface is called with different processing logic according to different integration modes, and the specified login account is queried in the cookie pool;

[0008] If the binding information is queried through the specified login account, the cookie information is obtained based on the binding information, the same specified login account is allowed to log in the target website of the business system based on the obtained cookie information, and the login state of the specified login account and the same specified login account is kept alive by calling the keep-alive interface of the target website.

[0009] Optionally, the service interface comprises a write-in interface, a query interface, and a deletion interface.

[0010] Optionally, after the specified login account logs in the target website of the business system, the write interface is called to bind the cookie information generated after the specified login account logs in the target website of the business system with the specified login account, generate binding information, and store the binding information in the cookie pool.

[0011] Optionally, the query interface is called to query the specified login account in the cookie pool according to different processing logics.

[0012] Optionally, the website login state sharing method further comprises: calling a delete interface to delete the cookie information corresponding to the expired or specified account.

[0013] Optionally, the integration mode of the target website comprises: an embedded website page integration mode and a website interface calling integration mode.

[0014] In another aspect, the application further provides a website login state sharing system, characterized in that comprising:

[0015] An initial unit is configured to establish a cookie pool on the cloud and establish a service interface for the cookie pool.

[0016] An information storage unit is configured to call the service interface to bind the cookie information generated after the specified login account logs in the target website of the business system with the specified login account, generate binding information, and store the binding information in the cookie pool after the specified login account logs in the target website of the business system.

[0017] A query unit is configured to determine the integration mode of the target website when the specified login account has logged in the target website of the business system and the same specified login account logs in the target website of the business system, call the service interface according to different processing logics to query the specified login account in the cookie pool according to different processing logics.

[0018] A state sharing unit is configured to obtain the cookie information based on the binding information when the specified login account queries the binding information, allow the same specified login account to log in the target website of the business system based on the obtained cookie information, and call the keep-alive interface of the target website to keep alive the login state of the specified login account and the same specified login account.

[0019] Optionally, the service interface comprises: a write interface, a query interface, and a delete interface.

[0020] Optionally, after the specified login account logs in the target website of the business system, the write interface is called to bind the cookie information generated after the specified login account logs in the target website of the business system with the specified login account, generate binding information, and store the binding information in the cookie pool.

[0021] Optionally, the query interface is called to query the specified login account in the cookie pool according to different processing logics.

[0022] Optionally, the website login state sharing method further comprises: calling a delete interface to delete the cookie information corresponding to the expired or specified account.

[0023] Optionally, the integration mode of the target website comprises: an embedded website page integration mode and a website interface calling integration mode.

[0024] In another aspect, the application further provides a computing device, comprising: one or more processors;

[0025] the processor is configured to execute one or more programs;

[0026] when the one or more programs are executed by the one or more processors, the method as described above is implemented.

[0027] In another aspect, the application further provides a computer readable storage medium, which has a computer program stored thereon, and the computer program is executed to implement the method as described above.

[0028] Compared with the prior art, the application has the following beneficial effects:

[0029] The application provides a website login state sharing method, comprising: for a cloud, establishing a Cookie pool on the cloud, and establishing a service interface for the Cookie pool; after a specified login account logs in a target website of a business system, calling the service interface, binding Cookie information generated after the specified login account logs in the target website of the business system with the specified login account, generating binding information, and storing the binding information in the Cookie pool; when the specified login account has logged in the target website of the business system and the same specified login account logs in the target website of the business system, determining an integration mode of the target website, calling the service interface with different processing logics according to different integration modes, and querying the Cookie pool according to the specified login account; if the binding information is queried through the specified login account, obtaining Cookie information based on the binding information, allowing the same specified login account to log in the target website of the business system based on the obtained Cookie information, and calling a keep-alive interface of the target website to keep alive the login states of the specified login account and the same specified login account. The method can realize one-party login and multi-party sharing, avoid forced offline caused by repeated login, ensure business continuity, keep alive the login state, improve the effective duration of the login state, and improve user experience. BRIEF DESCRIPTION OF DRAWINGS

[0030] Figure 1 A flowchart of the method of the application;

[0031] Figure 2 A logic flowchart of the method of the application for embedded website page mode login state sharing;

[0032] Figure 3 A logic flowchart of the method of the application for calling website interface mode login state sharing;

[0033] Figure 4 A structure diagram of the system of the application. DETAILED DESCRIPTION

[0034] Reference will now be made to the drawings to describe the exemplary embodiments of the present application in detail. The application can be implemented in many different forms and is not limited to the embodiments described herein, which are provided to fully and completely disclose the application and to fully convey the scope of the application to those skilled in the art. The terms used in the exemplary embodiments shown in the drawings are not limitations of the application. In the drawings, the same elements / elements are denoted by the same reference numerals.

[0035] The terms used herein, including technical terms, have meanings commonly understood by those skilled in the art, unless otherwise specified. In addition, it is to be understood that the terms defined by commonly used dictionaries are to be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art, and are not to be interpreted in an idealized or overly formal sense unless otherwise specifically so indicated.

[0036] Embodiment 1:

[0037] The present application provides a website login state sharing method, as shown in Figure 1 The method comprises the following steps:

[0038] Step 1, for the cloud, establishing a Cookie pool on the cloud, and establishing a service interface for the Cookie pool;

[0039] Step 2, after a specified login account logs in a target website of a business system, calling the service interface to bind the Cookie information generated after the specified login account logs in the target website of the business system with the specified login account, generating binding information, and storing the binding information in the Cookie pool;

[0040] Step 3, when the specified login account has logged in the target website of the business system and the same specified login account logs in the target website of the business system, determining the integration mode of the target website, calling the service interface with different processing logics according to different integration modes, and querying the Cookie pool according to the specified login account;

[0041] Step 4, if the binding information is queried through the specified login account, obtaining the Cookie information based on the binding information, allowing the same specified login account to log in the target website of the business system based on the obtained Cookie information, and calling the keep-alive interface of the target website to keep alive the login state of the specified login account and the same specified login account.

[0042] The service interface comprises a write interface, a query interface and a delete interface.

[0043] The write interface is called after the specified login account logs in the target website of the business system to bind the Cookie information generated after the specified login account logs in the target website of the business system with the specified login account, generate binding information, and store the binding information in the Cookie pool.

[0044] The query interface is called with different processing logics to query the Cookie pool according to the specified login account.

[0045] The website login state sharing method further comprises: calling a deletion interface to delete Cookie information corresponding to an expired or specified account.

[0046] The integration mode of the target website comprises: an embedded website page integration mode and a website interface calling integration mode.

[0047] The application will be further described in combination with embodiments:

[0048] The implementation process of the specific case mainly comprises implementation in a Cookie pool and a business system, and the specific implementation process is as follows:

[0049] In the Cookie pool:

[0050] The Cookie pool is a cloud service, comprising three service interfaces, namely, a query interface, a write interface and a deletion interface.

[0051] (1) The query interface: querying Cookie information of a specified login account of a specified website. The Cookie information is used to share the previous login state of the website to a new login behavior.

[0052] (2) The write interface: writing Cookie information of a specified login account of a specified website. The Cookie information is added when the Cookie information does not exist in the Cookie pool, and is overwritten when the Cookie information exists. The Cookie information is used to save the login state of the website for sharing by a new login behavior.

[0053] (3) The deletion interface: deleting Cookie information of a specified login account of a specified website. The Cookie information is used to delete expired Cookie information of the website, so as to avoid the situation that the Cookie information is repeatedly used but invalid.

[0054] In the business system:

[0055] When the business system is used, a user must log in to the business system, and then can select a supported website address and fill in website information such as a login account and a login password. Only one piece of website information can be maintained for each website address, but website information of multiple website addresses can be maintained simultaneously. The business system automatically records the correspondence between the business system user and the website information.

[0056] When the user uses these websites in the business system again, the previous login state of the website is used preferentially, and the website information is used to log in automatically when the login is invalid, and the login state is shared. Meanwhile, in order to ensure that the login state is as long as possible, the login state is kept alive by the login party.

[0057] According to different integration modes of the business system, the processing logic is different.

[0058] The embedded website page logic is as follows: Figure 2As shown, in the client software of the business system, a browser component can be embedded and loaded, and the website can be opened in the browser component, so as to realize the client-embedded website page. The processing logic of this integration mode is as follows:

[0059] Step 1: According to the user of the business system, open the website address, and query the corresponding website login account and login password.

[0060] Step 2: Call the Cookie pool query interface to query the Cookie information of the specified login account of the specified website. If it exists, continue to step 3, otherwise jump to step 5.

[0061] Step 3: Write the Cookie information into the client-embedded browser component, and then open the website in the browser component. Continue to detect until the website page is loaded. According to the website characteristics, determine whether the current login state is, if so, end the process, otherwise continue to step 4.

[0062] Step 4: Call the Cookie pool deletion interface to delete the Cookie information of the specified login account of the specified website.

[0063] Step 5: Automatically fill in the login account and login password on the website login page, simulate clicking the login button, and continue to detect until the login is completed. According to the website characteristics, determine whether the current login state is, if so, continue to step 6, otherwise report an error "account password error" and close the embedded browser component, and the process ends.

[0064] Step 6: Call the Cookie pool write interface to write the Cookie information of the specified login account of the specified website.

[0065] Step 7: After the user completes the website operation, hide the embedded browser component, and refresh the website page in the background at a fixed time, to realize the login state keep-alive.

[0066] In the above steps, the behaviors of detecting website loading completion, detecting website login completion, determining login state according to website characteristics, automatically filling in account password, simulating clicking login button, etc. are similar but not exactly the same for different websites, so the website needs to be adapted before it can be supported.

[0067] The website interface calling logic is as shown in Figure 3 In the client software and cloud services of the business system, the business operation can be realized by simulating the calling of the website interface, and then cooperating with the display interface of the business system itself to interact with the user. The processing logic of this integration mode is as follows:

[0068] Step 1: According to the user of the business system, open the website address, and query the corresponding website login account and login password.

[0069] Step 2: Call the Cookie pool query interface to query the Cookie information of the specified website and the specified login account, if the Cookie information exists, continue step 3, otherwise jump to step 5.

[0070] Step 3: Use the Cookie information to call a website service interface, judge whether the interface returns successfully, if yes, end the process, otherwise continue step 4.

[0071] Step 4: Call the Cookie pool deletion interface to delete the Cookie information of the specified website and the specified login account.

[0072] Step 5: Use the login account and the login password to call the website login interface, judge whether the interface returns successfully, if yes, continue step 6, otherwise report an error "account password error" and end the process.

[0073] Step 6: Call the Cookie pool writing interface to write the Cookie information of the specified website and the specified login account.

[0074] Step 7: Use the Cookie information to call the website keep-alive interface at a fixed time to realize the login state keep-alive.

[0075] In the above steps, the login interface, the service interface, the keep-alive interface of different websites, the calling mode and the parameters are different, and need to be determined after analyzing the website.

[0076] The application supports website login state sharing, one login and multiple sharing, avoids forced logout caused by repeated login, and ensures business continuity without interruption.

[0077] The application supports login state sharing and automatic login in two ways of embedded website page and calling website interface, has high flexibility and wide coverage scenarios.

[0078] The application realizes login state keep-alive by the login side, improves the effective duration of the login state, and improves the user experience.

[0079] The application establishes a Cookie pool in the cloud to store the Cookie information generated after website login, and the business system uses the Cookie information in the Cookie pool when using the website function, if the Cookie information does not exist or is expired, the login is performed again, so as to realize website login state sharing, avoid forced logout caused by repeated login, ensure business continuity without interruption. Support login state sharing in two ways of embedded website page and calling website interface, have high flexibility and wide coverage scenarios. Realize login state keep-alive by the login side, improve the effective duration of the login state, and improve the user experience.

[0080] Embodiment 2:

[0081] The application also provides a website login state sharing system 200, as shown inFigure 4 As shown, comprising:

[0082] The initial unit 201 is used for establishing a Cookie pool at the cloud and establishing a service interface for the Cookie pool;

[0083] The information storage unit 202 is used for calling the service interface after the specified login account logs in the target website of the business system, binding the Cookie information generated after the specified login account logs in the target website of the business system with the specified login account, generating binding information, and storing the binding information into the Cookie pool;

[0084] The query unit 203 is used for determining the integration mode of the target website when the specified login account has logged in the target website of the business system and the same specified login account logs in the target website of the business system, calling the service interface with different processing logics, and querying the Cookie pool according to the specified login account.

[0085] The state sharing unit 204 is used for obtaining the Cookie information based on the binding information when the binding information is queried by the specified login account, allowing the same specified login account to log in the target website of the business system based on the obtained Cookie information, and calling the keep-alive interface of the target website to keep the login state of the specified login account and the same specified login account.

[0086] The service interface comprises a write interface, a query interface and a delete interface.

[0087] The write interface is called after the specified login account logs in the target website of the business system, the Cookie information generated after the specified login account logs in the target website of the business system is bound with the specified login account, binding information is generated, and the binding information is stored into the Cookie pool.

[0088] The query interface is called to query the Cookie pool according to the specified login account with different processing logics.

[0089] The website login state sharing method further comprises calling the delete interface to delete the Cookie information corresponding to the expired or specified account.

[0090] The integration mode of the target website comprises an embedded website page integration mode and a website interface calling integration mode.

[0091] The application can realize one-party login and multi-party sharing, avoids forced offline caused by repeated login, ensures business continuity, realizes login state keep-alive, improves effective duration of login state, and improves user experience.

[0092] Embodiment 3:

[0093] Based on the same inventive concept, the application further provides a computer device including a processor and a memory, the memory being used to store a computer program, the computer program including program instructions, and the processor being used to execute the program instructions stored in the computer storage medium. The processor can be a central processing unit (CPU), and can also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc., which are the computing core and control core of the terminal, and are suitable for implementing one or more instructions, and are specifically suitable for loading and executing one or more instructions in the computer storage medium to implement a corresponding method flow or a corresponding function, so as to implement the steps of the method in the above embodiments.

[0094] Embodiment 4:

[0095] Based on the same inventive concept, the application further provides a storage medium, specifically a computer readable storage medium (Memory), which is a memory device in the computer device, and is used to store programs and data. It can be understood that the computer readable storage medium herein can include an internal storage medium in the computer device, and of course can also include an expansion storage medium supported by the computer device. The computer readable storage medium provides a storage space, and the storage space stores an operating system of the terminal. In addition, one or more instructions suitable for being loaded and executed by the processor are also stored in the storage space, and the instructions can be one or more computer programs (including program codes). It should be noted that the computer readable storage medium herein can be a high-speed RAM memory, or a non-volatile memory such as at least one disk memory. One or more instructions stored in the computer readable storage medium can be loaded and executed by the processor to implement the steps of the method in the above embodiments.

[0096] Those skilled in the art will appreciate that embodiments of the present application can be readily used as software, hardware, or a combination of software and hardware. In a software embodiment, the methods can be tangibly embodied in a machine-readable storage medium having stored thereon instructions that can be used to program a computer to perform any of the methods. The software implementation can be initialized by loading and executing a set of instructions arranged to perform one of the methods into the computer's memory. Alternatively, hard-wired circuitry can be used in place of, or in combination with, software instructions. Thus, the

[0097] The present application is described in reference to the flowchart illustrations and / or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart illustrations and / or block diagrams. Figure 1 one or more functions specified in one or more of the flowchart illustrations and / or block diagrams. Figure 1 means for performing each of the functions specified in the flowchart illustrations and / or block diagrams.

[0098] These computer program instructions can also be stored in a computer- readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instructions which implement the flowchart illustrations and / or block diagrams. Figure 1 one or more functions specified in one or more of the flowchart illustrations and / or block diagrams. Figure 1 means for performing each of the functions specified in the flowchart illustrations and / or block diagrams.

[0099] These computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the flowchart illustrations and / or block diagrams. Figure 1 one or more functions specified in one or more of the flowchart illustrations and / or block diagrams. Figure 1 means for performing each of the functions specified in the flowchart illustrations and / or block diagrams.

[0100] While preferred embodiments of the application have been described, modifications and variations can be apparent to those skilled in the art once aware of the general underlying concepts. Accordingly, the appended claims are intended to embrace all such modifications and variations as fall within the scope of the application.

[0101] It will be apparent to those skilled in the art that various modifications and variations can be made to the present application without departing from the spirit or scope of the application. Thus, it is intended that the present application cover modifications and variations of this application provided they come within the scope of the appended claims and their equivalents.

Claims

1. A website login state sharing method, characterized by, The website login state sharing method comprises the following steps: For the cloud, a cookie pool is established on the cloud, and a service interface is established for the cookie pool; After a specified login account logs in a target website of a business system, the service interface is called to bind cookie information generated after the specified login account logs in the target website of the business system to the specified login account, generate binding information, and store the binding information in the cookie pool; When the specified login account has logged in the target website of the business system and the same specified login account logs in the target website of the business system, the integration mode of the target website is determined, the service interface is called according to different processing logics, and the specified login account is queried in the cookie pool according to the different processing logics; If the binding information is queried through the specified login account, the cookie information is obtained based on the binding information, the same specified login account is allowed to log in the target website of the business system based on the obtained cookie information, and a keep-alive interface of the target website is called to keep alive the login state of the specified login account and the same specified login account; The different processing logics comprise an embedded website page logic and a website interface calling logic. The embedded website page logic comprises the following steps: The cookie information is written into a client embedded browser component, the website is opened in the browser component, and the website page is continuously detected until the website page is loaded; After the user completes the website operation, the embedded browser component is hidden, the website page is refreshed in the background at a regular time, and the login state is kept alive. The website interface calling logic comprises the following steps: The website business interface is called using the cookie information, and it is judged whether the interface returns successfully; The website keep-alive interface is called at a regular time using the cookie information, and the login state is kept alive.

2. The website login state sharing method of claim 1, wherein, The service interface comprises a write-in interface, a query interface, and a deletion interface.

3. The website login state sharing method according to claim 2, characterized in that, After the specified login account logs in the target website of the business system, the write-in interface is called to bind the cookie information generated after the specified login account logs in the target website of the business system to the specified login account, generate binding information, and store the binding information in the cookie pool.

4. The website login state sharing method of claim 2, wherein, The query interface is called according to different processing logics, and the specified login account is queried in the cookie pool according to the different processing logics.

5. The website login state sharing method of claim 2, wherein, The website login state sharing method further comprises calling the deletion interface to delete the cookie information corresponding to an expired or specified account.

6. The website login state sharing method of claim 1, wherein, The integration mode of the target website comprises an embedded website page integration mode and a website interface calling integration mode.

7. A website login state sharing system characterized by comprising: The website login state sharing method comprises the following steps: An initial unit is configured to establish a cookie pool on the cloud and establish a service interface for the cookie pool; The information storage unit is configured to, after the specified login account logs in the target website of the business system, call the service interface, bind the cookie information generated after the specified login account logs in the target website of the business system with the specified login account, generate binding information, and store the binding information in a cookie pool. The query unit is configured to, when the specified login account has logged in the target website of the business system and the same specified login account logs in the target website of the business system, determine the integration mode of the target website, call the service interface according to different processing logics, and query the cookie pool according to the specified login account. The state sharing unit is configured to, when the binding information is queried by the specified login account, obtain the cookie information based on the binding information, allow the same specified login account to log in the target website of the business system based on the obtained cookie information, and call a keep-alive interface of the target website to keep alive the login states of the specified login account and the same specified login account. The different processing logics include an embedded website page logic and a website interface calling logic. The embedded website page logic includes: writing the cookie information into a client embedded browser component, opening the website in the browser component, and continuously detecting until the website page is loaded; hiding the embedded browser component after the user completes the website operation, and refreshing the website page in the background to keep alive the login state. The website interface calling logic includes: calling the website business interface using the cookie information, and judging whether the interface returns successfully; calling the website keep-alive interface using the cookie information to keep alive the login state.

8. The website login state sharing system according to claim 7, characterized in that, The service interface includes a write-in interface, a query interface, and a delete interface.

9. The website login state sharing system according to claim 8, characterized in that, After the specified login account logs in the target website of the business system, the write-in interface is called to bind the cookie information generated after the specified login account logs in the target website of the business system with the specified login account, generate binding information, and store the binding information in a cookie pool.

10. The website login state sharing system according to claim 8, characterized in that, The query interface is called to query the cookie pool according to the specified login account according to different processing logics.

11. The website login state sharing system according to claim 8, characterized in that, The website login state sharing method further includes calling the delete interface to delete the cookie information corresponding to the expired or specified account.

12. The website login state sharing system according to claim 7, characterized in that, The integration mode of the target website includes an embedded website page integration mode and a website interface calling integration mode.

13. A computer device, comprising: The computer program is stored on the computer readable medium and is executed to implement the method according to any one of claims 1-6. The computer program is stored on the computer readable medium and is executed to implement the method according to any one of claims 1-6. ​ ​ ​ 14. A computer-readable storage medium, characterized in that, ​

Images