CN112333248B - Login failure verification method and related device - Google Patents
Login failure verification method and related device Download PDFInfo
- Publication number
- CN112333248B CN112333248B CN202011156898.3A CN202011156898A CN112333248B CN 112333248 B CN112333248 B CN 112333248B CN 202011156898 A CN202011156898 A CN 202011156898A CN 112333248 B CN112333248 B CN 112333248B
- Authority
- CN
- China
- Prior art keywords
- client device
- active
- cloud platform
- user
- inactive state
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/535—Tracking the activity of the user
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- General Engineering & Computer Science (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The embodiment of the application discloses an account login state verification method which can verify whether the login state of client equipment is valid or not. The method comprises the following steps: the method comprises the steps that a client device monitors operation records of a user; the client device generates an active proof according to the operation record of the user; the client device sends the active evidence to the cloud platform; the method comprises the steps that a user device sends an active certificate to a cloud platform, and the cloud platform determines whether the client device is in an inactive state according to the active certificate; setting the cloud platform account to an offline state; the cloud platform sends offline information to an application server, wherein the offline information is used for notifying the application server that the client device is in an inactive state; and stopping providing the application service of the cloud platform account number to the client device by the application server.
Description
Technical Field
The embodiment of the application relates to the field of information processing, in particular to a login failure verification method.
Background
Most websites have an automatic offline function at present, and when a user does not operate in a login state for a long time, the website can automatically log off an account of the user, so that the account safety of the user is protected.
To achieve the above-mentioned functions, the present application server needs to query from the cloud platform whether the client device is online every time it provides a service to the client user. The method requires frequent communication of the application server with the cloud platform to inquire the account login state of the client, and increases the burden of the cloud platform.
Disclosure of Invention
Aiming at the problems, the application provides a login failure verification method which can reduce the communication frequency between a cloud platform and an application server.
The first aspect of the present application provides a login failure verification method, which is applied to a cloud platform, wherein the cloud platform is provided with a plurality of service applications, and the service applications correspond to client devices and application servers, and the method comprises the following steps:
receiving an active certificate sent by a client device, wherein the client device logs in a cloud platform account;
determining whether the client device is in an inactive state according to the active proof;
and if the client device is in an inactive state, setting the cloud platform account to an offline state.
And sending offline information to an application server, wherein the offline information is used for notifying the application server that the client device is in an inactive state.
Optionally, the determining whether the client device is in an inactive state according to the active proof includes:
and detecting whether the active certification sent by the client device is received within a preset time interval.
Optionally, the determining whether the client device is in an inactive state according to the active proof includes:
detecting whether an active certificate sent by the client device is received within a preset detection interval;
detecting whether a count of the active proof is incremented;
and if the cloud platform does not receive the active evidence sent by the client device in the predicted time interval or the count of the active evidence is not increased, otherwise, confirming that the client device is in an inactive state.
The second aspect of the present application provides a login failure verification method, which is applied to a client device, wherein a service application provided by a cloud platform is running on the client device, and the method comprises:
monitoring an operation record of a user;
generating an active proof according to the operation record of the user;
and sending the active evidence to the cloud platform.
Optionally, the generating the liveness proof according to the operation record of the user includes:
and monitoring operation instructions sent by the user on the client device, and generating an active certification every time the operation instructions are sent by the user.
Optionally, the generating the liveness proof according to the operation record of the user includes:
establishing an active counter; monitoring an operation instruction sent by the user on a client device, and increasing the value of the active counter every time the operation instruction is sent by the user;
and generating an active evidence according to the value of the active counter according to a preset generation interval.
The third aspect of the present application provides a login failure verification method, applied to an application server, the method comprising:
receiving offline information sent by a cloud platform, wherein the offline information is used for notifying the application server that client equipment is in an inactive state;
and the application server stops providing the application service of the cloud platform account to the client device.
The fourth aspect of the present application also provides a cloud platform corresponding to the method of the first aspect, the cloud platform comprising:
the receiving unit is used for receiving the active certificate sent by the client device, and the client device logs in with the cloud platform account;
a confirmation unit, configured to determine whether the client device is in an inactive state according to the active proof;
and the offline unit is used for setting the cloud platform account to an offline state when the client device is in an inactive state.
And the sending unit is used for sending offline information to the application server, wherein the offline information is used for informing the application server that the client equipment is in an inactive state.
The fifth aspect of the present application also provides a client device, corresponding to the method of the second aspect, comprising:
the detection unit is used for monitoring the operation record of the user;
a generation unit, configured to generate an active proof according to the operation record of the user;
and the sending unit is used for sending the active evidence to the cloud platform.
The sixth aspect of the present application also provides a client device corresponding to the method of the third aspect, the client device comprising:
the receiving unit is used for receiving offline information sent by the cloud platform, and the offline information is used for notifying the application server that the client device is in an inactive state;
and the stopping unit is used for stopping providing the application service of the cloud platform for the client device when the receiving unit receives the offline information.
The seventh aspect of the present application also provides a computer apparatus comprising:
a processor, a memory;
the processor is connected with the memory;
the processor is configured to perform the login failure verification method of any one of the first aspect to the third aspect stored in the memory.
From the above technical solutions, the embodiment of the present application has the following advantages: according to the login failure verification method provided by the application, the application server does not need to frequently inquire the state of the client from the cloud platform, and the cloud platform actively informs the application server of the change of the account login state of the client when the client is off line, so that the application server is prevented from frequently verifying the online state of the user inquired from the cloud platform, and resources occupying the cloud platform are saved.
Drawings
FIG. 1 is a flow chart of a prior login failure verification method;
FIG. 2 is a schematic diagram of an embodiment of a login failure verification method according to the present application;
FIG. 3 is a schematic diagram of an embodiment of a login failure verification method according to the present application;
FIG. 4 is a schematic diagram of an embodiment of a login failure verification method according to the present application;
FIG. 5 is a schematic diagram of an embodiment of a login failure verification method according to the present application;
FIG. 6 is a schematic diagram of an embodiment of a cloud platform provided by the present application;
FIG. 7 is a schematic diagram of one embodiment of a client device provided by the present application;
FIG. 8 is a schematic diagram of an embodiment of an application server provided by the present application;
FIG. 9 is a schematic diagram of an embodiment of a computer device provided by the present application.
Detailed Description
The embodiment of the application provides a login failure verification method which is suitable for a cloud platform, an application server for providing application service and client equipment for using service. The login failure verification method is used for off-line of the logged account in the webpage when the webpage is not operated for a long time. The login time-effect verification method provided by the application can be used for completing verification of the activity degree of the user on the client device, and when the user does not operate the client device for a long time, the cloud platform can be used for off-line the account number of the user and informing the application server. The method and the system avoid the process that the application server repeatedly inquires the cloud platform about the online state of the user account, and reduce the burden of the cloud platform.
The current flow chart of webpage login verification is shown in fig. 1, and when a user accesses a cloud platform on a client device, various sub-applications integrated on the cloud platform can be used. These sub-applications run specifically on some application servers, serving users using client devices through integration of cloud platforms. For example, playing audio, uploading pictures, or viewing PDF documents online may all be a sub-application on the cloud platform. When a user operates on a webpage of the cloud platform, the client terminal application receives a corresponding operation instruction of the user so as to provide corresponding application service for the user. When the application server provides services for users, different application services can be provided according to different online states of the users. For example, only when a user's cloud platform account is online, the user may view a picture stored in the album application from the album application of the cloud platform. In order to grasp the online state of a user in real time, the current application server needs to frequently inquire whether the user is online from the cloud platform, and resources of the cloud platform are excessively occupied.
In order to solve the problems, the application provides a login failure verification method, which avoids excessive occupation of resources of a cloud platform due to frequent verification of the online state of a user by an application server.
Fig. 2 shows a general flow of the login time-effect verification method provided by the application. The login failure verification method mainly relies on the user equipment to automatically send the liveness certificate, so that whether the user equipment is online or not is verified. The cloud platform account number in the application refers to an account number registered by a user on a cloud platform, and the user logs in one cloud platform account number, so that various application services on the cloud platform can be used.
301. The method comprises the steps that a client device monitors operation records of a user;
and under the condition that the user logs in the cloud platform account, the client device detects operation records of the user on the client device. These operational records may be operations such as clicking, inputting by the user on the cloud platform, or may include operations such as moving a mouse, pressing keys, or other types of inputs by the user on the client device. As a detailed example, an interceptor may be provided in the client device, and records the operation performed by the user in the form of postMessage when the user's operation instruction passes the request.
302. The client device generates an active proof according to the operation record of the user;
the client device generates a corresponding active proof for verifying whether the user is still operating the client device according to the operation instruction in step 301.
303. The client device sends the active evidence to the cloud platform;
the client device sends the liveness certificate to the cloud platform so that the cloud platform verifies the liveness certificate, and the liveness certificate is used for the cloud platform to confirm whether the corresponding client device is still used by a user.
Those skilled in the art will appreciate that the active state referred to herein refers to a state in which the customer has operated during the last period of time. The user is in an active state, so that the user is more likely to perform other operations on the client in the next time, and therefore the account of the client is not suitable to be offline. In contrast, the inactive state refers to a state that the user has not operated from the client for a period of time before, which means that the user may leave the server device, or the user performs other operations on the server device, and no operation on the website is required, and the cloud platform should offline the account number logged in by the user.
304. The cloud platform determines whether the client device is in an inactive state according to the active proof;
and the cloud platform confirms whether the client device of the user is in an active state according to the active certification of the user. The manner in which the active state and the inactive state are specifically determined depends on the form of the active proof.
305. Setting the cloud platform account to an offline state;
and if the cloud platform confirms that the client device is in the inactive state, setting the account number state of the cloud platform logged in the client device from the login state to the offline state. Optionally, after the cloud platform logs off the account number of the client device, the cloud platform may send corresponding reminding information to the client device and force the client device to leave the cloud platform page.
306. And the cloud platform sends offline information to the application server, wherein the offline information is used for informing the application server that the client device is in an inactive state.
And the cloud platform sends the offline information to the application server so as to inform the application server to set the cloud platform account number logged on the corresponding client device from a login state to an offline state.
307. And stopping providing the application service of the cloud platform account number to the client device by the application server.
After the cloud platform account number logged in by the client device is switched from the login state to the offline state, the corresponding client device does not have the authority to use the application service any more, and the application server stops providing the application service for the corresponding client device.
It can be seen that, in the above solution, if the client device is not operated for a long time, the active proof of the client device cannot pass the authentication of the cloud platform, and then the cloud platform will offline the account on the client device, so as to prevent the user from stealing the account by other people using the client device after leaving the client device for a long time.
The embodiment of fig. 4 illustrates a preferred manner of generation and verification of the liveness evidence of the present application, including:
401. the method comprises the steps that a client device monitors operation records of a user;
and under the condition that the user logs in the cloud platform account, the client device detects operation records of the user on the client device. These operational records may be operations such as clicking, inputting by the user on the cloud platform, or may include operations such as moving a mouse, pressing keys, or other types of inputs by the user on the client device.
402. The client device generates an active proof according to the operation record of the user;
the client device generates a corresponding active proof for verifying whether the user is still operating the client device according to the operation instruction in step 301. In particular, the operation record of the user may include the operation type of the user, the operation time, but for the sake of reliability in reducing the data amount, the operation record may be used only to indicate that the user has performed an operation, not necessarily to indicate what operation the user has performed specifically.
403. And the client device sends the active evidence to the cloud platform.
The client device sends the liveness proof to the cloud platform so that the cloud platform verifies the liveness proof of the client device. The active proof may be sent in a timed manner, e.g. every 1 minute, the client device detects if the user has an operation record within 1 minute, and if so, sends an active proof once. Or each time the user performs an input operation, such as clicking, moving a cursor, etc., using the client device, an active proof is sent to the cloud platform.
404. The cloud platform detects whether an active proof sent by the client device is received within a preset time interval, if not, step 405 is executed
The cloud platform detects whether the active proof of the client device is received within a preset time interval, and if the active proof of the client device is not received, the cloud platform indicates that the user is not using the client device. After the user has not used the client device for a long period of time, the client device is in an inactive state. Those skilled in the art will appreciate that the active state referred to herein refers to a state in which the customer has operated during the last period of time. The user is in an active state, so that the user is more likely to perform other operations on the client in the next time, and therefore the account of the client is not suitable to be offline. In contrast, the inactive state refers to a state that the user has not operated from the client for a period of time before, which means that the user may leave the server device, or the user performs other operations on the server device, and no operation on the website is required, and the cloud platform should offline the account number logged in by the user.
It should be noted that, even if the transmission rule of the client device is to transmit the liveness certificate once every 1 minute, the cloud platform does not have to set the preset time interval to 1 minute. The cloud platform may set a preset time interval longer than a transmission period of the active proof, so as to prevent the client device from being erroneously determined to enter the inactive state when the client device fails to transmit the active proof due to occasional network connection failure.
405. And setting the cloud platform account to an offline state.
And if the cloud platform confirms that the client device is in the inactive state, setting the account number state of the cloud platform logged in the client device from the login state to the offline state. Optionally, after the cloud platform logs off the account number of the client device, the cloud platform may send corresponding reminding information to the client device and force the client device to leave the cloud platform page.
407. And the cloud platform sends offline information to the application server, wherein the offline information is used for informing the application server that the client device is in an inactive state.
And if the cloud platform confirms that the client device is in the inactive state, setting the account number state of the cloud platform logged in the client device from the login state to the offline state. Optionally, after the cloud platform logs off the account number of the client device, the cloud platform may send corresponding reminding information to the client device and force the client device to leave the cloud platform page.
408. And stopping providing the application service of the cloud platform account number to the client device by the application server.
After the cloud platform account number logged in by the client device is switched from the login state to the offline state, the corresponding client device does not have the authority to use the application service any more, and the application server stops providing the application service for the corresponding client device.
Referring to fig. 5, in another embodiment of the present application, an liveness proof for a client device may be generated by means of a count increment, the embodiment comprising:
501. the method comprises the steps that a client device monitors operation records of a user;
and under the condition that the user logs in the cloud platform account, the client device detects operation records of the user on the client device. These operational records may be operations such as clicking, inputting by the user on the cloud platform, or may include operations such as moving a mouse, pressing keys, or other types of inputs by the user on the client device.
502. Establishing an active counter, and increasing the value of the active counter every time the user sends out an operation instruction;
an active counter is established on the client device, the initial value of which suggests that it be set to zero. According to the detection of the user operation record, the value in the active counter is increased by 1 every time the user gives an operation instruction. It should be noted that, in a predefined manner, the computer device may be designated to monitor only a few specific operation instructions. For example, the active counter increases the value of the active counter by 1 only each time the mouse left click behavior is monitored. Of course, the person skilled in the art may make changes in this solution, for example, modifying the size of the count value increment each time, for example, when the operation record corresponds to decreasing the volume of the web page media, the count value is incremented by 2, and when the operation record is uploading the picture file, the count value is incremented by 3, which is easily conceivable by the person skilled in the art.
503. Generating an active evidence according to the value of the active counter according to a preset generation interval;
the client device generates the active proof according to the value of the active counter every time the preset generation interval passes, and it is simpler to directly use the value of the active counter as the active proof generated at this time.
504. And the client device sends the active evidence to the cloud platform.
And the user terminal equipment sends the active certification to the cloud platform according to a preset generation interval so that the cloud platform verifies the active certification of the client terminal equipment.
505. The cloud platform detects whether an active proof sent by the client device is received within a preset time interval, if yes, the step 506 is continuously executed, and if no, the step 507 is executed;
the cloud platform detects whether the active proof of the client device is received within a preset time interval, and if the active proof of the client device is not received, the cloud platform indicates that the user is not using the client device. After the user has not used the client device for a long period of time, the client device is in an inactive state. It should be noted that, even if the transmission rule of the client device is to transmit the liveness certificate once every 1 minute, the cloud platform does not have to set the preset time interval to 1 minute. The cloud platform may set a preset time interval longer than a transmission period of the active proof, so as to prevent the client device from being erroneously determined to enter the inactive state when the client device fails to transmit the active proof due to occasional network connection failure.
506. The cloud platform detects whether the count of the active proof is increased; if not, executing step 507;
the cloud platform detects whether the active proof of the client device is received within a preset time interval, and if the active proof of the client device is not received, the cloud platform indicates that the user is not using the client device. If the user does not use the client device for a long period of time, it is interpreted that the client device is in an inactive state. Those skilled in the art will appreciate that the active state referred to herein refers to a state in which the customer has operated during the last period of time. The user is in an active state, so that the user is more likely to perform other operations on the client in the next time, and therefore the account of the client is not suitable to be offline. In contrast, the inactive state refers to a state that the user has not operated from the client for a period of time before, which means that the user may leave the device of the server, or the user performs other operations on the server, which is no longer needed to operate on the website, and the server should take the account number logged in by the user off line.
If the user is using the client device, the client device generates an operation record according to various operations of the user, so that the count value of the active proof transmitted each time is increased. The cloud platform compares the current received active proof with the last active proof, and if the value of the current active proof increases, the cloud platform indicates that the user is using the client device in the period. Otherwise, if the count of active credentials is not incremented, indicating that the user is not using the client device, step 507 is performed.
507. And the cloud platform sets the cloud platform account number to be in an offline state.
And if the cloud platform confirms that the client device is in the inactive state, setting the account number state of the cloud platform logged in the client device from the login state to the offline state. Optionally, after the cloud platform logs off the account number of the client device, the cloud platform may send corresponding reminding information to the client device and force the client device to leave the cloud platform page.
508. And the cloud platform sends offline information to the application server, wherein the offline information is used for informing the application server that the client device is in an inactive state.
And the cloud platform sends the offline information to the application server so as to inform the application server to switch the cloud platform account number logged on the corresponding client device from a login state to an offline state.
509. And stopping providing the application service of the cloud platform account number to the client device by the application server.
After the cloud platform account number logged in by the client device is switched from the login state to the offline state, the corresponding client device does not have the authority to use the application service any more, and the application server stops providing the application service for the corresponding client device.
It will be appreciated that the reason why the client device is inactive for a long time may be that the client device itself disconnects the network, the client crashes or the client is turned off by the user, so that the offline notification sent by the cloud platform may not be received by the client device, and the offline notification is mainly sent for the case that the client device is operating normally but the user is not operating for a long time.
Fig. 6 illustrates a cloud platform, comprising:
a receiving unit 601, configured to receive an active certificate sent by a client device, where the client device logs in to a cloud platform account;
a confirmation unit 602, configured to determine whether the client device is in an inactive state according to the active proof;
and the offline unit 603 is configured to set the cloud platform account to an offline state when the client device is in an inactive state.
And the sending unit 604 is configured to send offline information to an application server, where the offline information is used to notify the application server that the client device is in an inactive state.
Fig. 7 illustrates a client device having a service application provided by a cloud platform running thereon, the client device comprising:
a detection unit 701 for monitoring an operation record of a user;
a generating unit 702, configured to generate an active proof according to the operation record of the user;
and the sending unit 703 is configured to send the active certificate to the cloud platform.
Fig. 8 illustrates an application server on which a service application with a cloud platform is running, the application server comprising:
a receiving unit 801, configured to receive offline information sent by a cloud platform, where the offline information is used to notify the application server that the client device is in an inactive state;
and the stopping unit 802 is configured to stop providing the application service of the cloud platform to the client device when the receiving unit receives offline information. One embodiment of a computer device is described below, with reference to FIG. 9, including
Referring to fig. 9, a computer device 900 may include one or more central processing units (central processing units, CPU) 901 and memory 905, where one or more applications or data are stored in memory 905. Wherein the memory 905 may be volatile storage or persistent storage. The program stored in memory 905 may comprise one or more modules, each of which may comprise a series of instruction operations in a service server. Still further, the central processor 901 may be arranged to communicate with the memory 905 to execute a series of instruction operations in the memory 905 on the computer device 900. The computer device 900 may also include one or more power supplies 902, one or more wired or wireless network interfaces 903, one or more input output interfaces 904, and/or one or more operating systems, such as Windows ServerTM, mac OS XTM, unixTM, linuxTM, freeBSDTM, etc. The cpu 901 may perform the corresponding operations of any of the embodiments shown in fig. 1 to 5, and will not be described herein.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, which are not repeated herein.
In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in part or all of the technical solution or in part in the form of a software product stored in a storage medium, including instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a read-only memory (ROM), a random access memory (RAM, random access memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
Claims (9)
1. A login failure verification method is applied to a cloud platform and is characterized in that the cloud platform is provided with a plurality of service applications, and the service applications correspond to client equipment and an application server, and the method comprises the following steps:
receiving an active certificate sent by a client device, wherein the client device logs in a cloud platform account;
determining whether the client device is in an inactive state according to the active proof; the determining whether the client device is in an inactive state according to the active proof comprises: detecting whether a count of the active proof is incremented; if the count of the active certificates is not increased, confirming that the client device is in an inactive state;
if the client device is in an inactive state, setting the cloud platform account to an offline state;
and sending offline information to an application server, wherein the offline information is used for notifying the application server that the client device is in an inactive state.
2. The login failure verification method according to claim 1, wherein said determining whether the client device is in an inactive state according to the liveness proof comprises:
and detecting whether the active certification sent by the client device is received within a preset time interval.
3. The login failure verification method according to claim 1, wherein said determining whether the client device is in an inactive state according to the liveness proof comprises:
detecting whether an active certificate sent by the client device is received within a preset time interval;
and if the cloud platform does not receive the active evidence sent by the client device within the preset time interval, confirming that the client device is in an inactive state.
4. A login failure verification method applied to a client device, wherein a service application provided by a cloud platform is operated on the client device, and the method is characterized by comprising the following steps:
monitoring an operation record of a user;
generating an active proof according to the operation record of the user; the generating the liveness certificate according to the operation record of the user comprises the following steps: establishing an active counter, and increasing the value of the active counter every time the user sends out an operation instruction; generating an active evidence according to the value of the active counter according to a preset generation interval;
and sending the active evidence to the cloud platform.
5. The login failure verification method according to claim 4, wherein the generating an liveness certificate according to the operation record of the user comprises:
and monitoring operation instructions sent by the user on the client device, and generating an active certification every time the operation instructions are sent by the user.
6. A login failure verification method applied to an application server, the method comprising:
receiving offline information sent by a cloud platform, wherein the offline information is used for notifying the application server that client equipment is in an inactive state; the determining process of the inactive state comprises the following steps: the cloud platform receives an active certificate sent by a client device; detecting whether a count of the active proof is incremented; if the count of the active certificates is not increased, confirming that the client device is in an inactive state;
and the application server stops providing the application service of the cloud platform account to the client device.
7. A cloud platform, comprising:
the receiving unit is used for receiving the active certificate sent by the client device, and the client device logs in with the cloud platform account;
a confirmation unit, configured to determine whether the client device is in an inactive state according to the active proof; the confirmation unit is specifically configured to: detecting whether a count of the active proof is incremented; if the count of the active certificates is not increased, confirming that the client device is in an inactive state;
the offline unit is used for setting the cloud platform account to an offline state when the client device is in an inactive state;
and the sending unit is used for sending offline information to the application server, wherein the offline information is used for informing the application server that the client equipment is in an inactive state.
8. A device for a client, wherein a service application provided by a cloud platform runs on the client, the device comprising:
the detection unit is used for monitoring the operation record of the user;
a generation unit, configured to generate an active proof according to the operation record of the user; the generating unit is specifically configured to: establishing an active counter, and increasing the value of the active counter every time the user sends out an operation instruction; generating an active evidence according to the value of the active counter according to a preset generation interval;
and the sending unit is used for sending the active evidence to the cloud platform.
9. A computer device, comprising:
a processor, a memory;
the processor is connected with the memory;
the processor is configured to perform the login failure checking method according to any one of claims 1 to 6 stored in the memory.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011156898.3A CN112333248B (en) | 2020-10-26 | 2020-10-26 | Login failure verification method and related device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011156898.3A CN112333248B (en) | 2020-10-26 | 2020-10-26 | Login failure verification method and related device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112333248A CN112333248A (en) | 2021-02-05 |
| CN112333248B true CN112333248B (en) | 2023-09-01 |
Family
ID=74310846
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011156898.3A Active CN112333248B (en) | 2020-10-26 | 2020-10-26 | Login failure verification method and related device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112333248B (en) |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101674669A (en) * | 2009-10-12 | 2010-03-17 | 中兴通讯股份有限公司 | Method, service node equipment and access node equipment for keep-alive processing |
| WO2011026358A1 (en) * | 2009-09-04 | 2011-03-10 | 中兴通讯股份有限公司 | Method and system for processing abnormal off-line for web authentication user |
| CN103313216A (en) * | 2013-06-24 | 2013-09-18 | 腾讯科技（深圳）有限公司 | Message prompt method, system and device for communication account |
| CN103441883A (en) * | 2013-09-04 | 2013-12-11 | 上海辰锐信息科技公司 | System-user management method |
| CN103947270A (en) * | 2011-11-22 | 2014-07-23 | Sca艾普拉控股有限公司 | System and method for paging off-line state terminals |
| CN105095055A (en) * | 2015-07-22 | 2015-11-25 | 北京奇虎科技有限公司 | User activity statistical approach and system |
| CN105227660A (en) * | 2015-09-30 | 2016-01-06 | 小米科技有限责任公司 | A kind of based reminding method and device |
| CN106412965A (en) * | 2016-11-17 | 2017-02-15 | 上海斐讯数据通信技术有限公司 | Method, network-surfing terminal, and system for automatic off-line realization |
| CN107508917A (en) * | 2017-09-29 | 2017-12-22 | 济南浚达信息技术有限公司 | A kind of web site user activity statistical method and system based on bitmap |
| CN107704997A (en) * | 2017-09-12 | 2018-02-16 | 广东万丈金数信息技术股份有限公司 | Assess the method, apparatus and storage medium of client liveness |
| CN108040344A (en) * | 2017-12-07 | 2018-05-15 | 上海斐讯数据通信技术有限公司 | A kind of online user management method of radio reception device, radio reception device |
| CN108206777A (en) * | 2017-11-28 | 2018-06-26 | 维沃移动通信有限公司 | A kind of information push method and server |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9942134B2 (en) * | 2015-09-30 | 2018-04-10 | International Business Machines Corporation | Holding of a link in an optical interface by a lower level processor until authorization is received from an upper level processor |
-
2020
- 2020-10-26 CN CN202011156898.3A patent/CN112333248B/en active Active
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2011026358A1 (en) * | 2009-09-04 | 2011-03-10 | 中兴通讯股份有限公司 | Method and system for processing abnormal off-line for web authentication user |
| CN101674669A (en) * | 2009-10-12 | 2010-03-17 | 中兴通讯股份有限公司 | Method, service node equipment and access node equipment for keep-alive processing |
| CN103947270A (en) * | 2011-11-22 | 2014-07-23 | Sca艾普拉控股有限公司 | System and method for paging off-line state terminals |
| CN103313216A (en) * | 2013-06-24 | 2013-09-18 | 腾讯科技（深圳）有限公司 | Message prompt method, system and device for communication account |
| CN103441883A (en) * | 2013-09-04 | 2013-12-11 | 上海辰锐信息科技公司 | System-user management method |
| CN105095055A (en) * | 2015-07-22 | 2015-11-25 | 北京奇虎科技有限公司 | User activity statistical approach and system |
| CN105227660A (en) * | 2015-09-30 | 2016-01-06 | 小米科技有限责任公司 | A kind of based reminding method and device |
| CN106412965A (en) * | 2016-11-17 | 2017-02-15 | 上海斐讯数据通信技术有限公司 | Method, network-surfing terminal, and system for automatic off-line realization |
| CN107704997A (en) * | 2017-09-12 | 2018-02-16 | 广东万丈金数信息技术股份有限公司 | Assess the method, apparatus and storage medium of client liveness |
| CN107508917A (en) * | 2017-09-29 | 2017-12-22 | 济南浚达信息技术有限公司 | A kind of web site user activity statistical method and system based on bitmap |
| CN108206777A (en) * | 2017-11-28 | 2018-06-26 | 维沃移动通信有限公司 | A kind of information push method and server |
| CN108040344A (en) * | 2017-12-07 | 2018-05-15 | 上海斐讯数据通信技术有限公司 | A kind of online user management method of radio reception device, radio reception device |
Non-Patent Citations (1)
| Title |
|---|
| 基于Linux名字空间的Web服务器动态防御方法;陈刚等;《计算机应用》;20171210(第12期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112333248A (en) | 2021-02-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP2454679B1 (en) | Management of an instant message session | |
| US8701199B1 (en) | Establishing a trusted session from a non-web client using adaptive authentication | |
| US8910254B2 (en) | System and methods for profiling client devices | |
| US20090007250A1 (en) | Client authentication distributor | |
| CN109257321B (en) | Secure login method and device | |
| CN108259618B (en) | Synchronous data interaction processing method and device | |
| JP2008152471A (en) | Server, information processing method, server program and server system | |
| CN113672897A (en) | Data communication method, device, electronic equipment and storage medium | |
| CN111885080B (en) | Login service architecture, server and client | |
| EP2107493A1 (en) | Business management system | |
| CN116827601A (en) | Data transmission method, device, electronic equipment and storage medium | |
| CN112333248B (en) | Login failure verification method and related device | |
| CN110912676A (en) | Key management method and system | |
| CN112953951B (en) | User login verification and security detection method and system based on domestic CPU | |
| CN105959147A (en) | Command storage method, client and center server | |
| JP5918297B2 (en) | Terminal log management system, terminal log management apparatus, terminal log management method, and terminal log management program | |
| CN115514531B (en) | Data hijacking alarm method, system, electronic equipment and storage medium | |
| TWI502375B (en) | Instant messaging method, system and device | |
| CN113765766B (en) | Session control method, device and equipment of virtual private network | |
| CN111541719B (en) | Authentication method and device and information processing equipment | |
| CN113806825B (en) | Verification method and device, storage medium and electronic equipment | |
| CN117763582A (en) | Page resource access method and device, client device and storage medium | |
| KR20060031949A (en) | Remote client terminal management system | |
| CN112399414B (en) | Network connection method, device, electronic equipment and storage medium | |
| CN109639509B (en) | Network equipment configuration method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |