CN109697342B - Login equipment management method and device - Google Patents
Login equipment management method and device Download PDFInfo
- Publication number
- CN109697342B CN109697342B CN201811578912.1A CN201811578912A CN109697342B CN 109697342 B CN109697342 B CN 109697342B CN 201811578912 A CN201811578912 A CN 201811578912A CN 109697342 B CN109697342 B CN 109697342B
- Authority
- CN
- China
- Prior art keywords
- login
- verification
- user
- deleted
- equipment
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/45—Structures or tools for the administration of authentication
Abstract
The present disclosure provides a login device management method and apparatus, wherein the method includes: deleting operation of a user for the login equipment to be deleted in the login equipment list is responded; if the login equipment to be deleted is not the login equipment currently logged in by the user, prompting the user to perform first verification; and when the verification is successful, deleting the login equipment to be deleted from the login equipment list according to the deletion operation. Therefore, when the login device to be deleted is not the login device currently logged in by the user, safety verification is required to confirm that the deletion operation is triggered by the user, and the login device to be deleted is allowed to be deleted after the safety verification is passed, so that the safety of the account is protected.
Description
Technical Field
The present disclosure relates to the field of device management technologies, and in particular, to a login device management method and apparatus.
Background
With the development of terminal device technology, the variety of terminal devices is increasing, and the terminal devices are computers, smart phones, tablet computers, wearable devices, vehicle-mounted intelligent terminals and the like. And allowing the user who has successfully registered a certain application program or content provider to log in different terminal equipment by using a corresponding account number and account password, and providing corresponding services for the user based on the certain application program or content provider called by the terminal equipment.
In the related art, when a user logs in a terminal device, login information is recorded in a login device management list. The user can know which terminal devices are logged in by checking the login device management list; at the same time, the user is allowed to delete the login device stored in the login device management list.
However, whether the login device management list is checked or the login device stored in the login device management list is deleted, security verification is not performed, and a certain security risk exists. Therefore, how to better manage the login device becomes a technical problem to be solved urgently.
Disclosure of Invention
The present disclosure is directed to solving, at least to some extent, one of the technical problems in the related art.
A first object of the present disclosure is to provide a login device management method.
A second object of the present disclosure is to provide a login device management apparatus.
A third object of the present disclosure is to provide yet another login device management apparatus.
A fourth object of the present disclosure is to provide a computer-readable storage medium.
To achieve the above object, an embodiment of a first aspect of the present disclosure provides a login device management method, including:
responding to the deletion operation of the user for the login equipment to be deleted in the login equipment list;
if the login equipment to be deleted is not the login equipment currently logged in by the user, prompting the user to perform first verification;
and when the verification is successful, deleting the login equipment to be deleted from the login equipment list according to the deletion operation.
Further, the method further comprises:
when the verification fails, prompting the user to perform the first verification again;
and if the continuous verification failure times exceed the target times, refusing to respond to the deletion operation of the user aiming at the login equipment to be deleted in the login equipment list.
Further, the method further comprises: and if the login equipment to be deleted is the login equipment currently logged in by the user, deleting the login equipment to be deleted from the login equipment list according to the deleting operation.
Further, before the responding user performs a deletion operation on the login device to be deleted in the login device list, the method further includes:
responding to the trigger operation of displaying the login equipment list, and prompting the user to perform second verification;
when the verification is successful, requesting the login equipment list from a server;
and receiving and displaying the login equipment list returned by the server.
Further, the first verification and the second verification are any one of the following verification methods:
the method comprises the steps of verification based on a login password, verification based on an information verification code, USB Key verification, face verification, fingerprint verification and voiceprint verification.
Further, the login device list comprises at least one login device, wherein the at least one login device is sorted according to the activity of the user.
Further, the login information of the login device comprises at least one of the following information:
the identification of the login equipment, the login starting time, the login ending time, the login duration, the historical login duration closest to the current time, the login times and the login state.
According to the login equipment management method provided by the embodiment of the disclosure, the deletion operation of a user for the login equipment to be deleted in the login equipment list is responded; if the login equipment to be deleted is not the login equipment currently logged in by the user, prompting the user to perform first verification; and when the verification is successful, deleting the login equipment to be deleted from the login equipment list according to the deletion operation. Therefore, when the login device to be deleted is not the login device currently logged in by the user, safety verification is required to confirm that the deletion operation is triggered by the user, and the login device to be deleted is allowed to be deleted after the safety verification is passed, so that the safety of the account is protected.
To achieve the above object, an embodiment of a second aspect of the present disclosure provides a login device management apparatus, including:
the response module is used for responding to the deletion operation of the user aiming at the login equipment to be deleted in the login equipment list;
the processing module is used for prompting the user to perform first verification if the login equipment to be deleted is not the login equipment currently logged in by the user;
and the processing module is further configured to delete the login device to be deleted from the login device list according to the deletion operation when the verification is successful.
Further, the processing module is further configured to prompt the user to perform the first verification again when the verification fails;
the processing module is further configured to refuse to respond to a deletion operation of the user for the login device to be deleted in the login device list if the number of continuous authentication failures exceeds the target number.
Further, the processing module is further configured to: and if the login equipment to be deleted is the login equipment currently logged in by the user, deleting the login equipment to be deleted from the login equipment list according to the deleting operation.
Further, the response module is further configured to respond to a trigger operation of displaying the login device list before responding to a deletion operation of a user for a login device to be deleted in the login device list;
the processing module is further used for prompting the user to perform second verification;
the processing module is further used for requesting the login equipment list from the server when the verification is successful;
the processing module is further used for receiving and displaying the login equipment list returned by the server.
The login equipment management device provided by the embodiment of the disclosure responds to the deletion operation of a user on the login equipment to be deleted in the login equipment list; if the login equipment to be deleted is not the login equipment currently logged in by the user, prompting the user to perform first verification; and when the verification is successful, deleting the login equipment to be deleted from the login equipment list according to the deletion operation. Therefore, when the login device to be deleted is not the login device currently logged in by the user, safety verification is required to confirm that the deletion operation is triggered by the user, and the login device to be deleted is allowed to be deleted after the safety verification is passed, so that the safety of the account is protected.
To achieve the above object, an embodiment of a third aspect of the present disclosure provides a login device management apparatus, including: memory, processor and computer program stored on the memory and executable on the processor, characterized in that the processor implements the login device management method as described above when executing the program.
In order to achieve the above object, a fourth aspect of the present disclosure provides a computer-readable storage medium, on which a computer program is stored, which when executed by a processor implements the login device management method as described above.
Additional aspects and advantages of the disclosure will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the disclosure.
Drawings
The foregoing and/or additional aspects and advantages of the present disclosure will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings of which:
fig. 1 is a schematic flowchart of a login device management method according to an embodiment of the present disclosure;
fig. 2 is a schematic flowchart of another login device management method according to an embodiment of the present disclosure;
FIG. 3 is an exemplary account and security interface;
FIG. 4 is an exemplary login device management interface;
fig. 5 is a schematic structural diagram of a login device management apparatus according to an embodiment of the present disclosure;
fig. 6 is a schematic structural diagram of another login device management apparatus according to an embodiment of the present disclosure.
Detailed Description
Reference will now be made in detail to the embodiments of the present disclosure, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the drawings are exemplary and intended to be illustrative of the present disclosure, and should not be construed as limiting the present disclosure.
A login device management method and apparatus according to an embodiment of the present disclosure are described below with reference to the drawings.
Fig. 1 is a schematic flowchart of a login device management method according to an embodiment of the present disclosure. The embodiment provides a login device management method, wherein an execution main body of the login device management method is a login device management method device, and the execution main body is composed of hardware and/or software.
As shown in fig. 1, the login device management method includes the following steps:
and S101, responding to the deletion operation of the user on the login equipment to be deleted in the login equipment list, and executing the step S102 or executing the step S106.
The embodiment of the present disclosure may be applied to a mobile terminal, wherein the mobile terminal may include but is not limited to: smart mobile phone, panel computer, wearable equipment, on-vehicle intelligent terminal, certainly, can also include other equipment, and this embodiment of this disclosure does not do the restriction to this.
In this embodiment, the login device list may display the login device that the user has logged in, the login information of the login device, and the like. The login device may be understood as a terminal device that the user has logged in, for example, a mobile phone of a certain model. Specifically, for a user who has successfully registered a certain application or content provider, when the user logs in a certain terminal device using a corresponding account and account password, login information for logging in the terminal device is added to a login device list.
Furthermore, in order to facilitate the user to quickly know the activity of the user logging in the terminal device, the login devices in the login device list are sorted according to the activity of the user. The user activity may be understood as a login duration of the user logging in the terminal device or a login number of times of logging in the terminal device, but is not limited thereto.
Further, in order to facilitate the user to view the detailed information of the login device, the login information of the login device added to the login device list includes, but is not limited to, the following information: the identification of the login equipment, the login starting time, the login ending time, the login duration, the historical login duration closest to the current time, the login times and the login state. The identifier of the login device may be a name of the login device, and the login state includes an online state or an offline state.
In this embodiment, the login device list is displayed on the human-computer interaction interface of the mobile terminal, and the user can input the deletion operation of the login device to be deleted through the human-computer interaction interface. And if the login equipment to be deleted is the login equipment currently logged in by the user, directly deleting the login equipment without performing security verification. If the login device to be deleted is not the login device currently logged in by the user, security verification is required to confirm that the deletion operation is triggered by the user himself, and the login device to be deleted is allowed to be deleted after the security verification.
S102, if the login device to be deleted is not the login device currently logged in by the user, prompting the user to perform first verification, and executing the step S103 or S104.
In this embodiment, the specific form of the verification manner of the first verification is not limited. The first verification may be any one of the following verification manners: the authentication is performed based on the login password, the authentication is performed based on the information authentication code, the USB Key authentication, the face authentication, the fingerprint authentication, and the voiceprint authentication, but not limited thereto.
The authentication is performed based on the login password, the login password is set in advance, and subsequently, the authentication is performed by judging whether the input login password is consistent with the login password set in advance. In this embodiment, the login password is set by the user, which may further protect the security of the user using an application program or an account of a content provider.
For the verification based on the information verification code, the information verification code may be a short message verification code or an information verification code received from a bound mailbox, but is not limited thereto. For example, a mobile phone number or a personal mailbox for receiving the information verification code and an account are bound in advance, so that the short message verification code can be sent to the mobile phone number of the user or the information verification code can be sent to the mailbox of the user subsequently, and the user performs verification based on the obtained information verification code. In this embodiment, the information verification code is received by the bound mobile phone number or the personal mailbox, which may further protect the security of the user using an application program or an account of a content provider.
Aiming at the USB Key verification, the first verification is carried out by judging the validity of the USB Key.
The face verification method comprises the steps of recognizing the face of a user in advance and storing the face into a mobile terminal, and subsequently verifying by judging whether input face information is matched with stored face information.
The fingerprint verification method includes the steps that a fingerprint of a user is identified in advance and stored in the mobile terminal, and verification is conducted subsequently by judging whether input fingerprint information is matched with stored fingerprint information or not.
Aiming at voiceprint verification, voice of a user is identified in advance and stored in the mobile terminal, and verification is performed by judging whether input voiceprint information is matched with the stored voiceprint information.
It should be noted that compared with the verification modes such as verification based on the login password or verification based on the information verification code, the verification modes such as USB Key verification, face verification, fingerprint verification, voiceprint verification and the like, the operation of inputting the login password or the information verification code by the user can be omitted, convenience is brought to the user, and the risk brought by leakage of the login password or the information verification code is effectively avoided.
S103, when the verification is successful, deleting the login equipment to be deleted from the login equipment list according to the deletion operation.
In this embodiment, when the user passes the first authentication, it is described that the user has the authority to delete the login device in the login device list, and the authorized user is allowed to log in the login device in the device list.
And S104, prompting the user to perform the first verification again when the verification fails.
And S105, if the continuous verification failure times exceed the target times, refusing to respond to the deletion operation of the user for the login equipment to be deleted in the login equipment list.
In this embodiment, the target number of times is set according to an actual situation, and the target number of times is, for example, 5 times.
In practical applications, the reason why the user fails the first authentication may be that the user fails the first authentication due to an incorrect operation while performing the first authentication. For example, when the first authentication is authentication based on the login password, it may be that the login password is mistaken. When the first verification is verification based on the information verification code, it may be that the information verification code is mistaken. When the first verification is a USB Key verification, it may be that the USB Key has expired. When the first verification is face verification, it may be that the camera is not aligned, and the camera does not capture all faces. When the first verification is a fingerprint verification, it may be that the correct fingerprint is not used. When the first verification is a voiceprint verification, it may be that the user's voice is muted so that the pronunciation is deviated from the normal pronunciation.
In the embodiment, a fault tolerance mechanism is established, the user is allowed to perform multiple times of first verification after the verification fails, and the user is considered not to have the authority to delete the login equipment in the login equipment list only after the user is confirmed to continuously perform multiple times of verification failures, so that the user requirement for safely managing the login equipment list is met.
And S106, if the login equipment to be deleted is the login equipment currently logged in by the user, deleting the login equipment to be deleted from the login equipment list according to the deleting operation.
In this embodiment, if the login device to be deleted is the login device currently logged in by the user, the login device is directly deleted, and the login is exited.
According to the login equipment management method provided by the embodiment of the invention, the deletion operation of a user for the login equipment to be deleted in the login equipment list is responded; if the login equipment to be deleted is not the login equipment currently logged in by the user, prompting the user to perform first verification; and when the verification is successful, deleting the login equipment to be deleted from the login equipment list according to the deletion operation. Therefore, when the login device to be deleted is not the login device currently logged in by the user, safety verification is required to confirm that the deletion operation is triggered by the user, and the login device to be deleted is allowed to be deleted after the safety verification is passed, so that the safety of the account is protected.
Further, with reference to fig. 2 in combination, on the basis of the embodiment shown in fig. 1, before step S101, the login device management method further includes:
s107, responding to the trigger operation of displaying the login equipment list, and prompting the user to perform second verification.
In this embodiment, the specific form of the verification manner of the second verification is not limited. The second verification may be any one of the following verification manners: the authentication is performed based on the login password, the authentication is performed based on the information authentication code, the USB Key authentication, the face authentication, the fingerprint authentication, and the voiceprint authentication, but not limited thereto.
Furthermore, the first verification mode and the second verification mode are different, so that the user can be subjected to double verification, and the security of the protected account is further enhanced.
And S108, when the verification is successful, requesting the login equipment list from the server.
In this embodiment, when the user passes the second authentication, it is described that the user has the right to view the login device list.
In this embodiment, when the user fails the second verification, the user is prompted to perform the second verification again. And if the continuous verification failure times exceed the set times, refusing to respond to the trigger operation of displaying the login equipment list. Wherein the setting is set according to the actual situation, and the setting number is, for example, 3.
In practical applications, the reason why the user fails the second authentication may be that the user fails the second authentication due to an incorrect operation while performing the second authentication. For example, when the second authentication is authentication based on the login password, it may be that the login password is mistaken. When the second verification is verification based on the information verification code, it may be that the information verification code is mistaken. When the second verification is the USB Key verification, it may be that the USB Key has expired. When the second verification is face verification, the camera may be misaligned, and the camera does not acquire all faces. When the second verification is a fingerprint verification, it may be that the correct fingerprint is not used. When the second verification is the voiceprint verification, it may be that the user's voice is muted so that the pronunciation is deviated from the normal pronunciation.
In the embodiment, a fault tolerance mechanism is established, the user is allowed to perform secondary verification for multiple times after the verification fails, and the user is considered not to have the authority to view the login equipment list only after the user is confirmed to continuously have multiple times of verification failures, so that the user requirement for safely managing the login equipment list is met.
And S109, receiving and displaying the login equipment list returned by the server.
For example, an application or a content provider generally configures an account and a security interface, and a user may input a trigger operation for displaying a login device list in the account and the security interface. For example, the user clicks a "login device management" button on the account and security interface shown in fig. 3, pops up the login device management interface shown in fig. 4, and displays a login device list in the login device management interface. The clicking operation of the user on the login equipment management button is the triggering operation of displaying the login equipment list input by the user.
According to the login equipment management method provided by the embodiment of the disclosure, the user is prompted to perform second verification by responding to the trigger operation of displaying the login equipment list; when the verification is successful, requesting the login equipment list from a server; and receiving and displaying the login equipment list returned by the server. Therefore, only the user passing the second verification has the authority to check the login equipment list, and the user without the authority is prohibited from checking the login equipment list, so that the safety of the account is ensured.
The embodiment of the disclosure also provides a login device management device. Fig. 5 is a schematic structural diagram of a login device management apparatus according to an embodiment of the present disclosure. As shown in fig. 5, the login device management apparatus includes: response module 11, processing module 12.
The response module 11 is configured to respond to a deletion operation of a user on a login device to be deleted in the login device list;
the processing module 12 is configured to prompt the user to perform a first authentication if the login device to be deleted is not the login device currently logged in by the user;
the processing module 12 is further configured to delete the login device to be deleted from the login device list according to the deletion operation when the verification is successful.
Further, the processing module 12 is further configured to prompt the user to perform the first authentication again when the authentication fails;
the processing module 12 is further configured to refuse to respond to a deletion operation of the user for the login device to be deleted in the login device list if the number of consecutive authentication failures exceeds the target number.
Further, the processing module 12 is further configured to: and if the login equipment to be deleted is the login equipment currently logged in by the user, deleting the login equipment to be deleted from the login equipment list according to the deleting operation.
Further, the response module 12 is further configured to respond to a trigger operation of displaying the login device list before responding to a deletion operation of the user for the login device to be deleted in the login device list;
the processing module 12 is further configured to prompt the user to perform a second authentication;
the processing module 12 is further configured to, when the verification is successful, request the login device list from the server;
the processing module 12 is further configured to receive and display the login device list returned by the server.
It should be noted that the foregoing explanation on the embodiment of the login device management method is also applicable to the login device management apparatus in this embodiment, and details are not described here.
The login equipment management device provided by the embodiment of the disclosure responds to the deletion operation of a user on the login equipment to be deleted in the login equipment list; if the login equipment to be deleted is not the login equipment currently logged in by the user, prompting the user to perform first verification; and when the verification is successful, deleting the login equipment to be deleted from the login equipment list according to the deletion operation. Therefore, when the login device to be deleted is not the login device currently logged in by the user, safety verification is required to confirm that the deletion operation is triggered by the user, and the login device to be deleted is allowed to be deleted after the safety verification is passed, so that the safety of the account is protected.
Fig. 6 is a schematic structural diagram of a login device management apparatus according to an embodiment of the present disclosure. The electronic device includes:
The login device management method provided in the above-described embodiment is implemented when the processor 1002 executes the program.
Further, the electronic device further includes:
a communication interface 1003 for communicating between the memory 1001 and the processor 1002.
A memory 1001 for storing computer programs that may be run on the processor 1002.
The processor 1002 is configured to implement the login device management method according to the foregoing embodiment when executing the program.
If the memory 1001, the processor 1002, and the communication interface 1003 are implemented independently, the communication interface 1003, the memory 1001, and the processor 1002 may be connected to each other through a bus and perform communication with each other. The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended ISA (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 6, but this is not intended to represent only one bus or type of bus.
Optionally, in a specific implementation, if the memory 1001, the processor 1002, and the communication interface 1003 are integrated on one chip, the memory 1001, the processor 1002, and the communication interface 1003 may complete communication with each other through an internal interface.
The processor 1002 may be a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits configured to implement embodiments of the present disclosure.
The present disclosure also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the login device management method as described above.
In the description herein, references to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present disclosure. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.
Furthermore, the terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In the description of the present disclosure, "a plurality" means at least two, e.g., two, three, etc., unless explicitly specifically limited otherwise.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing steps of a custom logic function or process, and alternate implementations are included within the scope of the preferred embodiment of the present disclosure in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the embodiments of the present disclosure.
The logic and/or steps represented in the flowcharts or otherwise described herein, e.g., an ordered listing of executable instructions that can be considered to implement logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For the purposes of this description, a "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic device) having one or more wires, a portable computer diskette (magnetic device), a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). Additionally, the computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.
It should be understood that portions of the present disclosure may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. If implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.
It will be understood by those skilled in the art that all or part of the steps carried by the method for implementing the above embodiments may be implemented by hardware related to instructions of a program, which may be stored in a computer readable storage medium, and when the program is executed, the program includes one or a combination of the steps of the method embodiments.
In addition, functional units in the embodiments of the present disclosure may be integrated into one processing module, or each unit may exist alone physically, or two or more units are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module, if implemented in the form of a software functional module and sold or used as a stand-alone product, may also be stored in a computer readable storage medium.
The storage medium mentioned above may be a read-only memory, a magnetic or optical disk, etc. Although embodiments of the present disclosure have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present disclosure, and that changes, modifications, substitutions and alterations may be made to the above embodiments by those of ordinary skill in the art within the scope of the present disclosure.
Claims (10)
1. A login device management method is characterized by comprising the following steps:
receiving a login equipment list; the login equipment list comprises at least one login equipment, wherein the at least one login equipment is sorted according to the activity of the user;
responding to the deletion operation of the user for the login equipment to be deleted in the login equipment list;
if the login equipment to be deleted is not the login equipment currently logged in by the user, prompting the user to perform first verification;
when the verification is successful, deleting the login equipment to be deleted from the login equipment list according to the deletion operation;
and if the login equipment to be deleted is the login equipment currently logged in by the user, deleting the login equipment to be deleted from the login equipment list according to the deleting operation.
2. The method of claim 1, further comprising:
when the verification fails, prompting the user to perform the first verification again;
and if the continuous verification failure times exceed the target times, refusing to respond to the deletion operation of the user aiming at the login equipment to be deleted in the login equipment list.
3. The method according to claim 1, further comprising, before the deletion operation of the responding user for the login device to be deleted in the login device list:
responding to the trigger operation of displaying the login equipment list, and prompting the user to perform second verification;
when the verification is successful, requesting the login equipment list from a server;
and receiving and displaying the login equipment list returned by the server.
4. The method according to claim 3, wherein the first authentication and the second authentication are any one of the following authentication methods:
the method comprises the steps of verification based on a login password, verification based on an information verification code, USB Key verification, face verification, fingerprint verification and voiceprint verification.
5. The method of claim 1, wherein the login information of the login device comprises at least one of:
the identification of the login equipment, the login starting time, the login ending time, the login duration, the historical login duration closest to the current time, the login times and the login state.
6. A login device management apparatus, comprising:
the processing module is used for receiving a login equipment list; the login equipment list comprises at least one login equipment, wherein the at least one login equipment is sorted according to the activity of the user;
the response module is used for responding to the deletion operation of the user for the login equipment to be deleted in the login equipment list;
the processing module is used for prompting the user to perform first verification if the login equipment to be deleted is not the login equipment currently logged in by the user;
the processing module is further configured to delete the login device to be deleted from the login device list according to the deletion operation when the verification is successful;
the processing module is further configured to: and if the login equipment to be deleted is the login equipment currently logged in by the user, deleting the login equipment to be deleted from the login equipment list according to the deleting operation.
7. The apparatus of claim 6,
the processing module is further used for prompting the user to perform the first verification again when the verification fails;
the processing module is further configured to refuse to respond to a deletion operation of the user for the login device to be deleted in the login device list if the number of continuous authentication failures exceeds the target number.
8. The apparatus of claim 6,
the response module is further used for responding to and displaying the trigger operation of the login equipment list before responding to the deletion operation of the user on the login equipment to be deleted in the login equipment list;
the processing module is further used for prompting the user to perform second verification;
the processing module is further used for requesting the login equipment list from the server when the verification is successful;
the processing module is further used for receiving and displaying the login equipment list returned by the server.
9. A login device management apparatus, comprising:
memory, processor and computer program stored on the memory and executable on the processor, characterized in that the processor implements the login device management method according to any of claims 1-5 when executing the program.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out a login device management method according to any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811578912.1A CN109697342B (en) | 2018-12-24 | 2018-12-24 | Login equipment management method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811578912.1A CN109697342B (en) | 2018-12-24 | 2018-12-24 | Login equipment management method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109697342A CN109697342A (en) | 2019-04-30 |
| CN109697342B true CN109697342B (en) | 2022-04-08 |
Family
ID=66232088
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811578912.1A Active CN109697342B (en) | 2018-12-24 | 2018-12-24 | Login equipment management method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109697342B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110931015B (en) * | 2019-12-04 | 2022-10-28 | 奇瑞新能源汽车股份有限公司 | Safety verification system and method for remotely controlling vehicle |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1536821A (en) * | 2003-04-09 | 2004-10-13 | 华为技术有限公司 | Equipment capable of making equipment logging interface implement hynamic arrangement and its method |
| CN102801728A (en) * | 2012-08-13 | 2012-11-28 | 汉柏科技有限公司 | Management method and system for automatic login of client side |
| CN106888149A (en) * | 2015-12-16 | 2017-06-23 | 北京奇虎科技有限公司 | Subscribe to mail unsubscription method and device |
| CN108848113A (en) * | 2018-08-15 | 2018-11-20 | 广州视源电子科技股份有限公司 | Client device log-in control method, device, storage medium and server |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CA2524849A1 (en) * | 2005-10-28 | 2007-04-28 | Overcow Corporation | Method of providing secure access to computer resources |
| CN101087262A (en) * | 2006-06-07 | 2007-12-12 | 阿里巴巴公司 | An instant communication processing method and system |
| CN101079903B (en) * | 2007-06-21 | 2011-01-19 | 中国工商银行股份有限公司 | Method and system based on remote login of user terminal |
| CN105592065B (en) * | 2015-11-05 | 2019-03-15 | 中国银联股份有限公司 | A kind of Website logging method and its login system based on SMS |
| CN107920164B (en) * | 2017-11-15 | 2020-10-27 | 中国联合网络通信集团有限公司 | Application sequencing method and system and server |
-
2018
- 2018-12-24 CN CN201811578912.1A patent/CN109697342B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1536821A (en) * | 2003-04-09 | 2004-10-13 | 华为技术有限公司 | Equipment capable of making equipment logging interface implement hynamic arrangement and its method |
| CN102801728A (en) * | 2012-08-13 | 2012-11-28 | 汉柏科技有限公司 | Management method and system for automatic login of client side |
| CN106888149A (en) * | 2015-12-16 | 2017-06-23 | 北京奇虎科技有限公司 | Subscribe to mail unsubscription method and device |
| CN108848113A (en) * | 2018-08-15 | 2018-11-20 | 广州视源电子科技股份有限公司 | Client device log-in control method, device, storage medium and server |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109697342A (en) | 2019-04-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104917749B (en) | account registration method and device | |
| CN111835689B (en) | Identity authentication method of digital key, terminal device and medium | |
| CN108183924A (en) | A kind of login validation method and terminal device | |
| CN107729727B (en) | Real-name authentication method and device for account | |
| CN105117630A (en) | Fingerprint authentication method, fingerprint authentication apparatus, and terminal | |
| CN104850771A (en) | Identity verification method and related equipment | |
| CN104077689A (en) | Information verification method, relevant device and system | |
| CN105530356A (en) | Mobile communication terminal and data protection method and apparatus thereof | |
| CN110298936B (en) | Vehicle key configuration method, system and equipment thereof | |
| CN109639724B (en) | Password retrieving method, password retrieving device, computer device and storage medium | |
| CN105046135A (en) | Information display method, information display apparatus and terminal | |
| CN106845181A (en) | The acquisition methods and electronic equipment of a kind of password | |
| CN113132404B (en) | Identity authentication method, terminal and storage medium | |
| CN105050061A (en) | Method and device for sending messages on the basis of user voiceprint information | |
| CN111414605B (en) | Unlocking method and device of embedded security unit, electronic equipment and storage medium | |
| CN109697342B (en) | Login equipment management method and device | |
| CN112560815B (en) | File calling method, device, medium and electronic equipment | |
| CN108900525B (en) | Processing method and device for verification code request | |
| CN112887922B (en) | Message sending method and electronic equipment | |
| CN109876451A (en) | The login method and equipment of game APP | |
| CN112966249A (en) | Multi-user account switching method and device, computer equipment and medium | |
| CN105653918A (en) | Safe operation method, safe operation device and terminal | |
| CN111340635A (en) | Data checking method, equipment, server and readable storage medium | |
| CN109710692B (en) | User information processing method and device in block chain network and storage medium | |
| CN111859320A (en) | Cross-system login-free method, device, equipment and readable storage medium |
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 |