TWI680658B - Single-user login system with allows network address changes and method thereof - Google Patents

Abstract

A stand-alone login system and method allowing network address changes. When a client logs in to a server, the server generates corresponding token information and provides it to the client, so that the client can embed it when transmitting the client request. This token information is used for user identification of single sign-on, and the client continuously sends echo information containing token information to the server at a fixed sending cycle, so that when the token information is invalid, the client can get the server immediately The feedback from the client and when the server receives an echo request in advance, the token information is updated to ensure a single login, which is used to achieve the technical effect of improving the applicability of the single login.

Description

Single machine login system and method for allowing network address change

The invention relates to a stand-alone login system and a method thereof, in particular to a stand-alone login system and a method thereof that allow a network address to be changed.

In recent years, with the popularity and vigorous development of the Internet, various systems or websites have sprung up. In order to solve the problem of multiple users operating an account at the same time, causing security, authorization, or consumption of hardware resources, a single machine Login becomes one of the most watched solutions.

Generally speaking, the traditional single sign-on method usually records the IP address of the account when the login is successful, and checks whether the network addresses are consistent when receiving subsequent requests. Out. However, this method of single sign-on is only applicable to a simple network environment. When the network address drift often occurs in the network environment where the client is located, it will cause a misjudgment situation, so that the client still needs to frequently restart Sign in, that is, it cannot be applied to more complicated network environments, so it has the problem of poor applicability of single sign-on.

In view of this, some manufacturers have proposed using a hardware key as a single sign-on technology, which uses the key set in the chip as a verification certificate, and does not need to use a traditional account password to log in. However, this method does not need to enter the account password, so the login mechanism on the server side needs to be adjusted accordingly. It cannot be directly applied to the unadjusted network environment, and the hardware key may be lost or damaged, so it is still There is a problem that the applicability of single sign-on is not good.

In summary, it can be seen that the applicability of single sign-on has been poor in the prior art for a long time, so it is necessary to propose improved technical means to solve this problem.

The invention discloses a stand-alone login system and method for allowing network address changes.

First, the present invention discloses a stand-alone login system that allows a network address to change. The system includes a client and a server. On the client side, it includes: a transmission module and an execution module. The transmission module is used for receiving token information for storage, and transmitting multiple client requests, wherein each client request embeds the stored token information when transmitting; the execution module is used for successful After logging in, an echo request is continuously sent at a fixed sending cycle, and the echo request includes token information.

On the server side, it includes: a login module and an update module. The login module is used to allow the client to log in, and after the client successfully logs in, the corresponding token information is generated to be transmitted to the corresponding client; the update module is used to receive the echo request in advance during the non-sending period. , Update the token information, and send the updated token information to the client that sent the echo request, so that this client stores the updated token information.

In addition, the present invention discloses a stand-alone login method that allows a network address to be changed. The method is applied to a network environment with a client and a server. The steps include: the server provides the client to log in, and after the client successfully logs in, generates The corresponding token information is transmitted to the corresponding client; the client receives the corresponding token information from the server for storage, and embeds the token information into each client when sending multiple client requests to the server In the request; the client continuously sends an echo request to the server with a fixed sending cycle, wherein the echo request includes token information; when the server receives the echo request in advance in a non-sending period, the server updates the token information, And the updated token information is transmitted to the client that sent the echo request, so that this client embeds the updated token information into the client request to be transmitted.

The system and method disclosed in the present invention are as above. The difference from the prior art is that the present invention generates corresponding token information from the server and provides it to the client when the client logs in to the server, so that the client transmits the client. When requested, the token information is embedded for user identification of single sign-on, and the client continuously sends echo messages containing token information to the server at a fixed sending cycle, so that when the token information becomes invalid, the client It can get feedback from the server in real time, and update the token information to ensure a single machine login when the server receives an echo request in advance.

Through the above technical means, the present invention can achieve the technical effect of improving the applicability of single sign-on.

In the following, the embodiments of the present invention will be described in detail with reference to the drawings and examples, so as to fully understand and implement the implementation process of how the present invention applies technical means to solve technical problems and achieve technical effects.

Before describing the stand-alone login system and method for allowing network address changes disclosed in the present invention, the network environment to which the present invention is applied will be described. The network environment includes a wired network, a wireless network, or both. Combination so that the client and server can communicate with each other. Among them, the wired network can be connected using telephone lines, twisted pairs, cables, optical fibers, etc .; the wireless network can be connected via Bluetooth, Wi-Fi, LoRa, ZigBee, CoAP (Constrained Application Protocol), or MQTT (Message Queuing Telemetry Transport). In actual implementation, both the client and the server can be implemented using computer devices, such as: personal computers, notebook computers, tablet computers, smart phones, servers, and so on.

The following describes the stand-alone login system and method of the present invention that allow network address changes according to the drawings. Please refer to "Figure 1". "Figure 1" shows the stand-alone login system that allows network address changes according to the present invention. System block diagram. This system includes: client 110 and server 120. The client 110 includes a transmission module 111 and an execution module 112. The transmission module 111 is used for receiving token information for storage, and transmitting client requests. Each client request embeds the stored token information when transmitting. In actual implementation, the transmission module 111 can also receive error information, and when receiving the error information, it generates a prompt block to prompt the user to log in to the server 120 again.

The execution module 112 is configured to continuously send an echo request at a fixed sending period after successfully logging in to the server 120, and the echo request includes token information. In actual implementation, the fixed sending cycle refers to sending an echo request every few seconds, for example, sending every 2 seconds, sending every 3 seconds, and so on. In particular, in order to avoid that the client 110 affects the sending cycle due to reloading the webpage, which causes the echo request to be sent to the server 120 in advance, therefore, when the client 110 reloads the same webpage, the sending cycle is To stop sending the first echo request (that is, the first echo request by turns).

The server 120 includes a login module 121 and an update module 122. The login module 121 is used to allow the client 110 to log in, and after the client 110 successfully logs in, the corresponding token information is generated and transmitted to the corresponding client 110. In actual implementation, the user needs to log in to the server 120 with his own account, and the server 120 will generate corresponding token information for each login account. In addition, the same client 110 can allow different accounts to log in to the server 120, and the same account can also log in to the server 120 through different clients 110, but if the same account is used to log in to the server through different clients 110 At 120 hours, only the client 110 who last logged in will get the token information updated by the server 120, and the client 110 who previously logged in with the same account will get the error message sent by the server 120, prompting the user to log in again. It should be particularly noted that the token information may be a random string generated by the server 120 and stored at the server 120 and the client 110 at the same time, wherein the client 110 stores the token information in a cookie. .

The update module 122 is configured to update the token information when the echo request is received in advance in a non-sending period, and transmit the updated token information to the client 110 that sends the echo request, so that the client 110 stores the updated Scepter information. For example, suppose that the sending period of the original client 110 is to send every 5 seconds. When an echo request from the same user is received in advance at an interval of 3 seconds, the user may log in at the new client 110, so the update mode is updated. The group 122 regenerates the token information and transmits it to the new client 110 sending this echo request. After that, even if the original client 110 still sends an echo request, because the token information in the echo request does not match the token information of the server 120, the server 120 will discard the echo request and send an error message to the corresponding Client 110 prompts to log in again. In other words, when the server 120 receives the client request or the echo request embedded with the non-updated token information after updating the token information, it will discard the client request or the echo embedded with the token information that has not been updated. Request and send error information to the corresponding client 110.

It should be particularly noted that, in actual implementation, the modules described in the present invention can be implemented in various ways, including software, hardware, or any combination thereof. For example, in some embodiments, the modules can be used Software or hardware or one of them can be implemented. In addition, the present invention can also be implemented partially or completely based on hardware. For example, one or more modules in a system can be implemented through integrated circuit chips, systems System on Chip (SoC), Complex Programmable Logic Device (CPLD), Field Programmable Gate Array (FPGA), and so on. The invention may be a system, a method, and / or a computer program. The computer program may include a computer-readable storage medium having computer-readable program instructions for enabling a processor to implement various aspects of the present invention. The computer-readable storage medium may be a tangible computer that can hold and store instructions used by the instruction execution device. device. The computer-readable storage medium may be, but is not limited to, an electric storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. More specific examples (non-exhaustive list) of computer-readable storage media include: hard disks, random access memory, read-only memory, flash memory, optical disks, floppy disks, and any suitable combination of the foregoing. Computer-readable storage media used herein are not to be interpreted as transient signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmission media (for example, optical signals via fiber optic cables), or via electrical wires Electrical signal transmitted. In addition, the computer-readable program instructions described herein can be downloaded from computer-readable storage media to various computing / processing devices, or downloaded via a network such as the Internet, a local area network, a wide area network, and / or a wireless network To an external computer device or external storage device. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, hubs, and / or gateways. The network card or network interface in each computing / processing device receives computer-readable program instructions from the network and forwards the computer-readable program instructions for computer-readable storage media stored in each computing / processing device in. The computer program instructions for performing the operations of the present invention may be combined language instructions, instruction set architecture instructions, machine instructions, machine-related instructions, microinstructions, firmware instructions, or source code or object code written in any combination of one or more programming languages. (Object Code), the programming language includes object-oriented programming languages, such as: Common Lisp, Python, C ++, Objective-C, Smalltalk, Delphi, Java, Swift, C #, Perl, Ruby, PHP, etc., as well as regular Procedural programming languages, such as C or similar programming languages. Computer-readable program instructions can be executed entirely on a computer, partly on a computer, as a stand-alone software, partly on a client computer, partly on a remote computer, or entirely on a remote computer or server On.

Next, please refer to "Figure 2". "Figure 2" is a flowchart of a method for a single sign-on method that allows the network address to be changed according to the present invention. The method is applied to a network environment with a client 110 and a server 120. Including: the server 120 provides the client 110 for login, and after the client 110 successfully logs in, the corresponding token information is generated for transmission to the corresponding client 110 (step 210); the client 110 receives the corresponding token from the server 120 The token information is stored, and when the client request is transmitted to the server 120, the stored token information is embedded in each client request (step 220); the client 110 continuously sends an echo request to the server at a fixed sending cycle. The server 120, wherein the echo request includes token information (step 230); and when the server 120 receives the echo request in advance in a non-sending period, the server 120 updates the token information and updates the updated token The information is transmitted to the client 110 that sends the echo request, so that the client 110 embeds the client request with the updated token information (step 240). Through the above steps, when the client 110 logs into the server 120, the server 120 generates corresponding token information and provides it to the client 110, so that the client 110 embeds the token information when transmitting the client request. As a single-user login user identification, and the client 110 continuously sends echo information containing token information to the server 120 at a fixed sending cycle, so that when the token information is invalid, the client 110 can get the server in real time 120 feedback, and when the server 120 receives the echo request in advance, the token information is updated to ensure a single machine login.

The following description will be given in an embodiment in conjunction with "Figure 3" and "Figure 4". Please refer to "Figure 3" first, and "Figure 3" is a schematic diagram of applying the present invention to a client login server. In actual implementation, when a user located on the client 110 wants to log in to the server 120, the user can enter the account in the account input block 311 of the login window 300, and the password in the password input block 312. Then, click the confirmation element 321 to submit a login request to the server 120, or click the cancel element 322 to cancel the login to the server 120. Then, after successfully logging in to the server 120, the client 110 will continue to send echo requests containing token information to the server 120 at a fixed sending cycle, so that when the token information fails, the server 120 can get immediate feedback ( (Ie: error message). When the server 120 receives the echo request transmitted by the client 110 in advance, the same account may log in through another client 110. Therefore, the server 120 updates the token information and transmits the updated token information to the sender. The client 110 of the echo request makes the client 110 and the server 120 have the same token information.

As shown in "Figure 4", "Figure 4" is a schematic diagram of the application of the present invention to prompt the user to log in to the server again. In actual implementation, after updating the token information, if the server 120 receives a client request or an echo request that embeds the token information that has not been updated, it will discard the client request that embeds the token information that has not been updated. Or echo request, and send an error message to the corresponding client 110. When the client 110 receives an error message, it will generate a prompt block 400 as shown in "Figure 4", which is used to prompt the user to click on the re-login element 410, so as to open the icon shown in "Figure 3" The login window 300 logs in again.

In summary, it can be seen that the difference between the present invention and the prior art lies in that when the client logs in to the server, the server generates corresponding token information and provides it to the client, so that when the client transmits the client request, Embed this token information for user identification of single sign-on, and the client continuously sends echo information containing token information to the server at a fixed sending cycle, so that when the token information is invalid, the client can get it instantly The feedback from the server and when the server receives an echo request in advance, the token information is updated to ensure a single sign-on. This technology can solve the problems of the previous technology, and thus achieve a technology that improves the applicability of single sign-on. efficacy.

Although the present invention is disclosed in the foregoing embodiments as above, it is not intended to limit the present invention. Any person skilled in similar arts can make some modifications and retouches without departing from the spirit and scope of the present invention. The scope of patent protection shall be determined by the scope of the patent application attached to this specification.

110‧‧‧Client

111‧‧‧Transmission Module

112‧‧‧Execution Module

120‧‧‧Server

121‧‧‧Login Module

122‧‧‧Update Module

300‧‧‧Login window

311‧‧‧Account input block

312‧‧‧password input block

321‧‧‧Confirm component

322‧‧‧ Cancel component

400‧‧‧tip block

410‧‧‧Re-login to the component

Step 210‧‧‧ The server provides a client to log in, and after the client successfully logs in, a corresponding token information is generated for transmission to the corresponding client

In step 220‧‧‧, the client receives the corresponding token information from the server for storage, and embeds the stored token information into each client when sending multiple client requests to the server. Request

In step 230‧‧‧, the client continuously sends an echo request to the server at a fixed sending cycle, wherein the echo request includes the token information.

Step 240‧‧‧ When the server receives the echo request in advance in a period other than the sending cycle, the server updates the token information and transmits the updated token information to the client that sent the echo request End, so that the client embeds the client request with the updated token information

FIG. 1 is a system block diagram of a stand-alone login system that allows network address changes according to the present invention. FIG. 2 is a flowchart of a method for a single sign-on method allowing network address changes according to the present invention. FIG. 3 is a schematic diagram of applying the present invention to a client login server. FIG. 4 is a schematic diagram of a prompt block to which the present invention is applied to prompt a user to log in to the server again.

Claims (10)

A stand-alone login system allowing network address changes. The system includes: at least one client, and each client includes: a transmission module for receiving a token information for storage, and transmitting multiple client requests In which, each client request embeds the stored token information when transmitting; and an execution module for continuously sending an echo request at a fixed sending cycle after successful login, the echo request includes The token information; and a server end, the server end includes: a login module for allowing the client to log in, and after the client successfully logs in, generating the corresponding token information for transmission to The corresponding client; and an update module for updating the token information when the echo request is received in advance other than the sending cycle, and transmitting the updated token information to the person who sent the echo request The client causes the client to store the updated token information. According to the stand-alone login system that allows a network address to change according to item 1 of the scope of the patent application, when the client reloads the same webpage, it stops sending the first echo request in the sending cycle. According to the stand-alone login system allowing network address change according to item 1 of the scope of patent application, after the server has updated the token information, it receives the client request that embeds the token information that has not been updated or In the echo request, the client request or the echo request embedded with the token information that has not been updated is discarded, and an error message is transmitted to the corresponding client. According to the stand-alone login system that allows network address changes according to item 3 of the scope of patent application, when the client receives the error message, it generates a prompt block to prompt the user to log in to the server again. According to the stand-alone login system that allows network address changes according to item 1 of the scope of patent application, the token information is a random string generated by the server, and is stored on the server and the client at the same time, where: The client stores the token information in a network cookie. A stand-alone login method allowing network address changes is applied to a network environment having at least one client and a server. The steps include: the server provides the client for login, and the client successfully logs in After that, a corresponding token information is generated for transmission to the corresponding client; the client receives the corresponding token information from the server for storage, and sends multiple client requests to the server When the token information is embedded in each client request; the client continuously sends an echo request to the server at a fixed sending cycle, wherein the echo request includes the token information; and when the server When the terminal receives the echo request in advance before the sending cycle, the server updates the token information, and transmits the updated token information to the client that sent the echo request, so that the client uses The updated token information is embedded in the client request. According to the stand-alone login method that allows the network address to change according to item 6 of the patent application scope, when the client reloads the same webpage, it stops sending the first echo request in the sending cycle. According to the stand-alone login method that allows the network address to change according to item 6 of the patent application scope, after the server end has updated the token information, it receives the client request that embeds the token information that has not been updated or In the echo request, the client request or the echo request embedded with the token information that has not been updated is discarded, and an error message is transmitted to the corresponding client. According to the stand-alone login method that allows the network address to change according to item 8 of the scope of the patent application, when the client receives the error message, a prompt block is generated to prompt the user to log in to the server again. According to the stand-alone login method of allowing a network address to change according to item 6 of the scope of patent application, wherein the token information is a random string generated by the server, and stored at the server and the client at the same time, wherein, The client stores the token information in a network cookie.