WO2019052170A1

WO2019052170A1 - Method, apparatus and device for implementing user login avoidance, and computer storage medium

Info

Publication number: WO2019052170A1
Application number: PCT/CN2018/083817
Authority: WO
Inventors: 曾靖嵩; 曹慧玲; 洪隆樟
Original assignee: 平安科技（深圳）有限公司
Priority date: 2017-09-13
Filing date: 2018-04-20
Publication date: 2019-03-21
Also published as: CN108259456B; CN108259456A

Abstract

Disclosed are a method, apparatus and device for implementing user login avoidance, and a computer storage medium. The method comprises: acquiring account information input when a user logs into an application program; executing a login operation according to a login prompt of the application program; acquiring an URL address after executing the login operation; storing the URL address in a Cookie; and if an external plugin needs to carry out user login, acquiring the URL address from the Cookie, and opening the URL address so as to implement user login avoidance. According to the present application, repeated program development can be avoided, and the usage experience of the user is improved.

Description

Method, device, device and computer storage medium for realizing user login free

This application claims the priority of the Chinese patent application filed on September 13, 2017, the Chinese Patent Office, the application number is CN 201710822494.5, and the application is entitled "Method, device, device, computer readable storage medium for realizing user-free login". The entire contents of this application are incorporated herein by reference.

Technical field

The present application relates to the field of computer technologies, and in particular, to a method, an apparatus, a device, and a computer storage medium for implementing user login-free.

Background technique

With the proliferation of users of smart client APPs and the increasing demand for multi-channels in business scenarios, external plug-ins developed in the APP by the hypertext markup language HTML5 are plug-and-play, and the need for seamless access is increasingly urgent; For the user login, it faces complicated operations that require multiple logins, which seriously affects the user experience. For developers, it is necessary to develop a repeated login program, which seriously affects development efficiency and program optimization rate.

Summary of the invention

The embodiment of the present invention provides a method, an apparatus, a device, and a computer storage medium for implementing user login-free, which can implement user login, avoid repeated program development, and improve user experience.

In one aspect, the embodiment of the present application provides a method for implementing user login-free, the method includes: acquiring account information input by a user when logging in to an application; performing a login operation according to a login prompt of the application; and obtaining a login operation after performing the login operation The URL address is stored in the cookie; if the external plug-in needs to perform the user login, the URL address is obtained from the cookie and the URL address is opened to implement the user-free login.

On the other hand, the embodiment of the present application further provides an apparatus for implementing user login-free, the apparatus comprising: a first obtaining unit, configured to acquire account information input when a user logs in to an application; and a first execution unit, configured to: Performing a login operation according to the login prompt of the application; a second obtaining unit, configured to obtain a URL address after performing the login operation; a storage unit, configured to store the URL address into a cookie; and opening a unit for externally The plug-in needs to perform a user login, obtain the URL address from the cookie, and open the URL address to implement user-free login.

In another aspect, the embodiment of the present application further provides a device for implementing user login-free, including: a memory for storing a program for implementing user-free login; and a processor for running the user-free stored in the memory. The logged-in program performs the following operations: obtaining account information input when the user logs in to the application; performing a login operation according to the login prompt of the application; obtaining a URL address after performing the login operation; storing the URL address in the cookie If the external plug-in needs to perform user login, obtain the URL address from the cookie and open the URL address to implement user-free login.

In still another aspect, an embodiment of the present application further provides a computer storage medium, where the computer storage medium stores one or more computer programs, and the one or more computer programs can be executed by one or more processors to implement The following steps: obtaining account information input when the user logs in to the application; performing a login operation according to the login prompt of the application; obtaining a URL address after performing the login operation; storing the URL address in a cookie; if an external plug-in needs to be performed The user logs in, obtains the URL address from the cookie, and opens the URL address to implement user-free login.

The embodiment of the present application can implement user-free login, can avoid repeated program development, and improve the user experience.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings used in the description of the embodiments will be briefly described below. It is obvious that the drawings in the following description are some embodiments of the present application. For the ordinary technicians, other drawings can be obtained based on these drawings without paying creative labor.

FIG. 1 is a schematic flowchart of a method for implementing user login-free according to an embodiment of the present application;

2 is another schematic flowchart of a method for implementing user login-free according to an embodiment of the present application;

FIG. 3 is another schematic flowchart of a method for implementing user login-free according to an embodiment of the present disclosure;

FIG. 4 is a schematic flowchart of a method for implementing user login-free according to another embodiment of the present application; FIG.

FIG. 5 is a schematic flowchart of a method for implementing user login-free according to another embodiment of the present application; FIG.

FIG. 6 is a schematic diagram of a method for implementing a user-free login method according to an embodiment of the present application; FIG.

FIG. 7 is a schematic block diagram of an apparatus for implementing user login-free according to an embodiment of the present application; FIG.

FIG. 8 is another schematic block diagram of an apparatus for implementing user login-free according to an embodiment of the present application; FIG.

FIG. 9 is another schematic block diagram of an apparatus for implementing user login-free according to an embodiment of the present disclosure;

FIG. 10 is another schematic block diagram of an apparatus for implementing user login-free according to an embodiment of the present application; FIG.

FIG. 11 is another schematic block diagram of an apparatus for implementing user login-free according to an embodiment of the present disclosure;

FIG. 12 is a schematic structural diagram of a device for implementing a user-free login according to an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application are clearly and completely described in the following with reference to the drawings in the embodiments of the present application. It is obvious that the described embodiments are a part of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present application without departing from the inventive scope are the scope of the present application.

Please refer to FIG. 1. FIG. 1 is a schematic flowchart of a method for implementing user login-free according to an embodiment of the present application. The method includes steps S101 to S105.

S101. Acquire account information input when the user logs in to the application.

In the embodiment of the present application, the account information refers to personal information used by the user to log in to an application. For example, when the user logs in to the application 1, the account information that needs to be input includes the user's account name, account password, and the like.

S102. Perform a login operation according to the login prompt of the application.

In the embodiment of the present application, for the application 1, after the user inputs the account information, the login operation is performed according to the login prompt of the application 1. Specifically, the login operation performed by the user is the login logic preset by the application, and the preset is preset. The login logic specifies the operation steps that should be performed after the user inputs the account information, and gives the corresponding login prompt for the relevant operation steps, or displays the corresponding login interface. The default login logic can be developed and defined by the application developer. The specific login logic is not limited herein.

S103. Acquire a URL address after performing the login operation.

In the embodiment of the present application, the URL address refers to the network address of the page. If the default login logic is successfully executed, the URL address after the login operation is performed, for example, after the user successfully logs in to the application 1, The login page will complete the update and jump to the page where the user has logged in. Since each page (including the login page and the non-login page) has its own different page address, ie URL address, it is in the page where the user has logged in. The URL address is also present, and the URL address is obtained, such as http://www.yidenglu.com/.

S104. Store the URL address into a cookie.

In the embodiment of the present application, a cookie is provided for storing the URL address, and the cookie refers to a small piece of text information, which is transmitted between the web server and the browser along with the user request and the page, for example, when the user requests to access the URL. When the address is a page on http://www.yidenglu.com/, the application sends more than one page to the user. If the page is a logged in page, the cookie stores the page in the logged in state. URL address. The cookie is stored in a folder on the user's hard disk. Later, if the user accesses the page on the site again, when the user enters the URL address as http://www.yidenglu.com/, the browser will Look up the cookie associated with the URL on the local hard drive. If the cookie exists, the browser sends it along with the page request to the site, and the application can open the requested page.

S105. If the external plug-in needs to perform user login, obtain the URL address from the cookie and open the URL address to implement user-free login.

In the embodiment of the present application, the external plug-in refers to an application plug-in written by a hypertext markup language HTML5 or other programming language, and the application plug-in exists by being attached to an application, and the external plug-in may be required to perform a user. The plugin that is logged in can also be a plugin that does not require user login. If the external plug-in is a plug-in that requires user login, the stored application login page can be obtained from the cookie and the page can be opened to implement the user-free login.

Further, as shown in FIG. 2, the step of acquiring the URL address from the cookie and opening the URL address includes steps S201 to S202.

S201. Acquire a stored URL address from the cookie.

S202. Open a historical login page according to the URL address and through a browser to implement user login-free.

Further, as shown in FIG. 3, steps S301 to S303 are included before the opening of the URL address.

S301. Verify that the URL address obtained from the cookie matches the external plugin.

In the embodiment of the present application, before receiving the request to open the URL address, the terminal is triggered to display a verification interface, where the user is required to input a verification identifier to verify whether the external plug-in is related to the URL address. match. The terminal obtains the verification identifier input in the verification interface, and verifies whether the verification identifier input by the user matches the preset identifier by using the preset identifier. The verification identifier input by the user may be a character identifier, which may be a fingerprint identifier, or may be The voice identifier is obtained when the verification identifier input by the user is a character identifier, and the character information input by the user on the verification interface is acquired; when the verification identifier input by the user is a fingerprint identifier, the fingerprint information input by the user on the verification interface is acquired; when the user inputs When the verification identifier is a voice identifier, the voice information input by the user on the verification interface is obtained.

S302. If no, the URL address is rejected by the browser.

S303. If yes, perform the step of opening the URL address.

It can be seen from the above that the embodiment of the present application obtains the account information input when the user logs in to the application; performs a login operation according to the login prompt of the application; obtains the URL address after the login operation is performed; and stores the URL address into the cookie. If the external plug-in needs to perform user login, the URL address is obtained from the cookie and the URL address is opened to implement user-free login, which can avoid repeated program development and improve the user experience.

Please refer to FIG. 4. FIG. 4 is a schematic flowchart of a method for implementing user-free login according to an embodiment of the present application. The method includes steps S401 to S407.

S401. Acquire account information input when the user logs in to the application.

S402. Perform a login operation according to the login prompt of the application.

S403. Obtain a URL address after performing the login operation.

S404. Encrypt the obtained URL address based on a preset encryption mechanism.

In the embodiment of the present application, since the personal account information of the user is stored in the URL address, the user may use personal privacy information such as an account password in the application, and if not encrypted, directly stored in the cookie. It can be easily stolen or viewed directly by other applications from cookies, resulting in the disclosure of personal privacy information that users need to protect. Therefore, in this embodiment, the encryption process is performed according to a preset encryption mechanism, so that various URL addresses in the application are first encrypted and then stored on the cookie, even if the URL address in the cookie is directly called in other applications. , all need to be decrypted before they can be viewed or opened. Otherwise, if there is no encrypted password for decryption, the view will only be displayed as garbled, and the valid content of the data cannot be obtained, which avoids the various URLs generated in the application being easily stolen. , effectively ensuring the security of the user's personal privacy information contained in the data generated by the application running.

It should be noted that when the URL address in the application needs to be encrypted, a virtual block device (Hard Disk Image) is first established, and the created virtual block device is used as a device mapper mechanism. The logical volume required for encryption is loaded to ensure continuous availability, consistency, and accuracy of the URL address. The URL address in the application is placed under the loaded logical volume, and the URL address in the application is encrypted by using a preset encryption algorithm. In this embodiment, the preset encryption algorithm may be advanced encryption. The Advanced Encryption Standard (AES) algorithm, of course, does not limit the default encryption algorithm to other encryption algorithms. When the URL address in the application is encrypted by using the AES algorithm, the encryption key is the set encryption password corresponding to the application, so that the URL address in the application is encrypted and stored in the cookie, and then passed. When the computer or other terminal checks the encrypted URL address stored under the cookie, it needs to decrypt it according to the encrypted password to view the valid content. Otherwise, it will be displayed as garbled, which improves various applications generated by the application. The security of the data file.

S405. Send the encrypted URL address to the cookie.

In the embodiment of the present application, a cookie is provided for storing the encrypted URL address, and the cookie refers to a small piece of text information, which is transmitted between the web server and the browser along with the user request and the page, for example, in the user. When requesting access to a page with a URL address of http://www.yidenglu.com/, the application sends more than one page to the user. If the page is a logged in page, the cookie is stored in the logged in state. The URL of the page. The cookie is stored in a folder on the user's hard disk. Later, if the user accesses the page on the site again, when the user enters the URL address as http://www.yidenglu.com/, the browser will Look up the cookie associated with the URL on the local hard drive. If the cookie exists, the browser sends it along with the page request to the site, and the application can open the requested page.

S406. If the external plug-in needs to perform user login, obtain the URL address from the cookie and open the URL address to implement user-free login.

It can be seen from the above that the encryption process according to the preset encryption mechanism in this embodiment prevents various URL addresses generated in the application from being easily stolen, and effectively ensures the user's personal privacy information included in the data generated by the application running. Security.

Referring to FIG. 5, FIG. 5 is a schematic flowchart of a method for implementing user-free login according to an embodiment of the present application. The method includes steps S501 to S507.

S501. Determine whether a request instruction for acquiring user account information is received.

In the embodiment of the present application, the user registers a user account in the corresponding background server by using the user's mobile phone in advance. The user account includes at least a login account and a login password for logging in to the server. After the registration is completed, the server logs the login. The account number and the login password are stored in the server local storage. In this way, when the user needs to log in to the server, the user needs to input the login account and the login password on the terminal; that is, the server needs to obtain the login account and login password of the user, and verify the login account and login password of the user, and the user needs to log in to the server. The preset button may be clicked on the display interface of the terminal to submit a request for obtaining the login interface to the terminal, and the terminal receives the acquisition request.

S502. If the request instruction is received, displaying a login interface on the current display interface, where the login interface includes at least an account input box and a password input box.

In the embodiment of the present application, the terminal may display a login interface as shown in FIG. 6 on its display interface, and the login interface includes an account input box, a password input box, a “confirm” button, and a “cancel” button.

S503. Acquire account information input when the user logs in to the application.

S504. Perform a login operation according to the login prompt of the application.

S505. Obtain a URL address after performing the login operation.

S506. Store the URL address into a cookie.

S507. If the external plug-in needs to perform user login, obtain the URL address from the cookie and open the URL address to implement user-free login.

Referring to FIG. 7 , corresponding to the foregoing method for implementing user-free login, the embodiment of the present application further provides an apparatus for implementing user-free login, and the apparatus 100 includes: a first acquiring unit 101, a first executing unit 102, and a first The second obtaining unit 103, the storage unit 104, and the opening unit 105.

The first obtaining unit 101 is configured to acquire account information input when the user logs in to the application. The first execution unit 102 is configured to perform a login operation according to the login prompt of the application. The second obtaining unit 103 is configured to obtain a URL address after the login operation is performed. The storage unit 104 is configured to store the URL address into a cookie. The opening unit 105 is configured to: if the external plug-in needs to perform user login, obtain the URL address from the cookie and open the URL address to implement user-free login.

Referring to FIG. 8, the opening unit 105 includes: a third obtaining unit 1051, configured to obtain the stored URL address from the cookie. The sub-unit 1052 is opened for opening the historical login page according to the URL address and by using a browser to implement user-free login.

Referring to FIG. 9, the apparatus further includes: a verification unit 106, configured to verify whether a URL address obtained from the cookie matches the external plug-in. The second execution unit 107 is configured to, if not, reject the URL address to be opened by the browser. The third executing unit 108 is configured to, if yes, perform the step of opening the URL address.

Referring to FIG. 10, corresponding to the foregoing method for implementing user-free login, the embodiment of the present application further provides an apparatus for implementing user-free login, and the apparatus 200 includes: a first acquiring unit 201, a first executing unit 202, and a first The second obtaining unit 203, the encrypting unit 204, the transmitting unit 205, and the opening unit 206.

The first obtaining unit 201 is configured to acquire account information input when the user logs in to the application. The first execution unit 202 is configured to perform a login operation according to the login prompt of the application. The second obtaining unit 203 is configured to obtain a URL address after performing the login operation. The encryption unit 204 is configured to encrypt the acquired URL address based on a preset encryption mechanism. The sending unit 205 is configured to send the encrypted URL address to the cookie. The opening unit 206 is configured to: if the external plug-in needs to perform user login, obtain the URL address from the cookie and open the URL address to implement user-free login.

Referring to FIG. 11 , corresponding to the foregoing method for implementing user-free login, the embodiment of the present application further provides a device for implementing user-free login, and the device 300 includes: a determining unit 301, a display unit 302, and a first acquiring unit 303. The first execution unit 304, the second acquisition unit 305, the storage unit 306, and the open unit 307.

The determining unit 301 is configured to determine whether a request instruction for acquiring user account information is received. The display unit 302 is configured to display a login interface on the current display interface if the request command is received, where the login interface includes at least an account input box and a password input box. The first obtaining unit 303 is configured to acquire account information input when the user logs in to the application. The first execution unit 304 is configured to perform a login operation according to the login prompt of the application. The second obtaining unit 305 is configured to obtain a URL address after the login operation is performed. The storage unit 306 is configured to store the URL address into a cookie. The opening unit 307 is configured to: if the external plug-in needs to perform user login, obtain the URL address from the cookie and open the URL address to implement user-free login.

The above described means for implementing user login free can be implemented in the form of a computer program that can be run on a device as shown in FIG.

FIG. 12 is a schematic structural diagram of a computer device according to the present application. The device may be a terminal or a server, wherein the terminal may be a communication-enabled electronic device such as a smart phone, a tablet computer, a notebook computer, a desktop computer, a personal digital assistant, and a wearable device. The server can be a standalone server or a server cluster consisting of multiple servers. Referring to Figure 12, the computer device 500 includes a processor 502, a non-volatile storage medium 503, a memory 504, and a network interface 505 that are coupled by a system bus 501. The non-volatile storage medium 503 of the computer device 500 can store an operating system 5031 and a computer program 5032. When the computer program 5032 is executed, the processor 502 can be caused to perform a method for implementing user-free login. The processor 502 of the computer device 500 is used to provide computing and control capabilities to support the operation of the entire computer device 500. The internal memory 504 can store a computer program that, when executed by the processor, can cause the processor 502 to perform a method of implementing user-free login. The network interface 505 of the computer device 500 is used to perform network communications, such as sending assigned tasks and the like. It will be understood by those skilled in the art that the structure shown in FIG. 12 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation of the computer device to which the solution of the present application is applied. The specific computer device may It includes more or fewer components than those shown in the figures, or some components are combined, or have different component arrangements. The processor 502 performs the following operations: acquiring account information input when the user logs in to the application; performing a login operation according to the login prompt of the application; obtaining a URL address after performing the login operation; storing the URL address to In the cookie; if the external plug-in needs to perform user login, the URL address is obtained from the cookie and the URL address is opened to implement the user-free login.

In one embodiment, the obtaining the URL address from the cookie and opening the URL address comprises: obtaining the stored URL address from the cookie; opening a history according to the URL address and through a browser Log in to the page to enable users to log in.

In an embodiment, after the obtaining the URL address after performing the login operation, the method further comprises: encrypting the acquired URL address based on a preset encryption mechanism.

In one embodiment, the processor 505 also performs an operation of verifying whether the URL address obtained from the cookie matches the external plug-in; if not, rejecting the URL address to be opened by the browser; if so, The step of opening the URL address is performed.

In an embodiment, the processor 505 further performs: determining whether a request instruction for acquiring user account information is received; and if the request instruction is received, displaying a login interface on the current display interface, the login interface At least the account input box and password input box are included.

It can be understood by those skilled in the art that the embodiment of the device for implementing the user-free login shown in FIG. 12 does not constitute a limitation on the specific configuration of the device that implements the user-free login. In other embodiments, the device that implements the user-free login may be Includes more or fewer components than shown, or combines some components, or different component arrangements. For example, in some embodiments, the device implementing user login-free may include only the memory and the processor. In such an embodiment, the structure and function of the memory and the processor are consistent with the embodiment shown in FIG. Narration.

The application provides a computer storage medium storing one or more computer programs, the one or more computer programs being executable by one or more processors to implement the above method for implementing user login free .

The foregoing storage medium of the present application includes: a magnetic disk, an optical disk, a read-only memory (ROM), and the like, which can store various program codes.

The units in all the embodiments of the present application may be implemented by a general-purpose integrated circuit, such as a CPU (Central Processing Unit), or by an ASIC (Application Specific Integrated Circuit).

The steps in the method for implementing the user-free login in the embodiment of the present application may be sequentially adjusted, merged, and deleted according to actual needs.

The units in the apparatus for implementing user-free login in the embodiment of the present application may be combined, divided, and deleted according to actual needs.

The foregoing is only a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto, and any equivalents can be easily conceived by those skilled in the art within the technical scope disclosed in the present application. Modifications or substitutions are intended to be included within the scope of the present application. Therefore, the scope of protection of this application should be determined by the scope of protection of the claims.

Claims

A method for implementing user login-free, characterized in that the method comprises:

Obtain the account information entered when the user logs in to the application;

Perform a login operation based on the login prompt of the application;

Obtaining a URL address after performing the login operation;

Storing the URL address in a cookie;

If the external plug-in needs to perform user login, the URL address is obtained from the cookie and the URL address is opened to implement user-free login.
The method of claim 1, wherein the obtaining the URL address from the cookie and opening the URL address comprises:

Obtaining the stored URL address from the cookie;

According to the URL address and opening a historical login page through a browser, the user is free from login.
The method of claim 1, wherein after the obtaining the URL address after performing the login operation, the method further comprises:

The obtained URL address is encrypted based on a preset encryption mechanism.
The method of claim 1, wherein before the opening the URL address, the method comprises:

Verifying that the URL address obtained from the cookie matches the external plugin;

If not, the URL is rejected by the browser;

If so, the step of opening the URL address is performed.
The method of claim 1 wherein the method further comprises:

Determining whether a request instruction for obtaining user account information is received;

If the request instruction is received, the login interface is displayed on the current display interface, and the login interface includes at least an account input box and a password input box.
A device for realizing user login-free, characterized in that the device comprises:

a first obtaining unit, configured to acquire account information input when the user logs in to the application;

a first execution unit, configured to perform a login operation according to a login prompt of the application;

a second obtaining unit, configured to acquire a URL address after performing the login operation;

a storage unit, configured to store the URL address into a cookie;

Opening a unit, if the external plug-in needs to perform user login, obtain the URL address from the cookie and open the URL address to implement user-free login.
The device according to claim 6, wherein the opening unit comprises:

a third obtaining unit, configured to obtain the stored URL address from the cookie;

The sub-unit is opened for opening the historical login page according to the URL address and by using a browser to implement user-free login.
The device of claim 6 wherein said device further comprises:

An encryption unit, configured to encrypt the obtained URL address according to a preset encryption mechanism;
The device of claim 6 wherein said device further comprises:

a verification unit, configured to verify whether the URL address obtained from the cookie matches the external plug-in;

a second execution unit, if not, rejecting the URL address to be opened by a browser;

And a third execution unit, configured to perform the step of opening the URL address if yes.
The device according to claim 6, wherein the device further comprises:

a determining unit, configured to determine whether a request instruction for acquiring user account information is received;

The display unit is configured to display a login interface on the current display interface if the request instruction is received, where the login interface includes at least an account input box and a password input box.
A device for implementing user login-free, characterized in that it comprises:

a memory for storing a program that implements user-free login;

a processor, configured to execute a program implemented in the memory to implement user login-free, to perform the following operations:

Obtain the account information entered when the user logs in to the application;

Perform a login operation based on the login prompt of the application;

Obtaining a URL address after performing the login operation;

Storing the URL address in a cookie;

If the external plug-in needs to perform user login, the URL address is obtained from the cookie and the URL address is opened to implement user-free login.
The device according to claim 11, wherein the obtaining the URL address from the cookie and opening the URL address comprises:

Obtaining the stored URL address from the cookie;

According to the URL address and opening a historical login page through a browser, the user is free from login.
The device of claim 11 wherein said processor further performs the following operations:

The obtained URL address is encrypted based on a preset encryption mechanism.
The device of claim 11 wherein said processor further performs the following operations:

Verifying that the URL address obtained from the cookie matches the external plugin;

If not, the URL is rejected by the browser;

If so, the step of opening the URL address is performed.
The device of claim 11 wherein said processor further performs the following operations:

Determining whether a request instruction for obtaining user account information is received;

If the request instruction is received, the login interface is displayed on the current display interface, and the login interface includes at least an account input box and a password input box.
A computer storage medium characterized in that the computer storage medium stores one or more computer programs, the one or more computer programs being executable by one or more processors to implement the steps of:

Obtain the account information entered when the user logs in to the application;

Perform a login operation based on the login prompt of the application;

Obtaining a URL address after performing the login operation;

Storing the URL address in a cookie;

If the external plug-in needs to perform user login, the URL address is obtained from the cookie and the URL address is opened to implement user-free login.
The computer readable storage medium of claim 16, wherein the obtaining the URL address from the cookie and opening the URL address comprises:

Obtaining the stored URL address from the cookie;

According to the URL address and opening a historical login page through a browser, the user is free from login.
The computer readable storage medium of claim 16 wherein said step further comprises:

The obtained URL address is encrypted based on a preset encryption mechanism.
The computer readable storage medium of claim 16 wherein said step further comprises:

Verifying that the URL address obtained from the cookie matches the external plugin;

If not, the URL is rejected by the browser;

If so, the step of opening the URL address is performed.
The computer readable storage medium of claim 16 wherein said step further comprises:

Determining whether a request instruction for obtaining user account information is received;

If the request instruction is received, the login interface is displayed on the current display interface, and the login interface includes at least an account input box and a password input box.