CN114172716A - Login method, login device, electronic equipment and storage medium - Google Patents
Login method, login device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN114172716A CN114172716A CN202111463180.3A CN202111463180A CN114172716A CN 114172716 A CN114172716 A CN 114172716A CN 202111463180 A CN202111463180 A CN 202111463180A CN 114172716 A CN114172716 A CN 114172716A
- Authority
- CN
- China
- Prior art keywords
- login
- verified
- verification code
- login account
- authorization
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 53
- 238000013475 authorization Methods 0.000 claims abstract description 216
- 238000012795 verification Methods 0.000 claims abstract description 165
- 238000004891 communication Methods 0.000 claims description 19
- 238000004590 computer program Methods 0.000 claims description 8
- 238000013507 mapping Methods 0.000 claims description 4
- 230000001960 triggered effect Effects 0.000 claims description 4
- 230000008569 process Effects 0.000 abstract description 7
- 238000010586 diagram Methods 0.000 description 8
- 230000002159 abnormal effect Effects 0.000 description 7
- 230000009471 action Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000005856 abnormality Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/20—Network architectures or network communication protocols for network security for managing network security; network security policies in general
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/321—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving a third party or a trusted authority
- H04L9/3213—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving a third party or a trusted authority using tickets or tokens, e.g. Kerberos
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3226—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using a predetermined code, e.g. password, passphrase or PIN
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2133—Verifying human interaction, e.g., Captcha
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computing Systems (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The embodiment of the invention provides a login method, a login device, electronic equipment and a storage medium, wherein the method comprises the following steps: receiving a login request sent by a client, wherein the login request carries a login account to be verified and a verification code to be verified; determining a verification code corresponding to the login account to be verified, and if the verification code is not consistent with the verification code to be verified, determining a preset authorization token identification list; determining an authorization verification code which is not corresponding to the login account to be verified according to the preset authorization token identification list; and if the authorization verification code is consistent with the verification code to be verified, determining that the login is successful, and returning a message of successful login to the client. Therefore, in the account sharing process, only the login account is shared, the private information of the user can be protected from being leaked, the operation is simplified, the user is prevented from changing the login password, and the potential safety hazard is avoided.
Description
Technical Field
The present invention relates to the field of internet technologies, and in particular, to a login method, a login device, an electronic device, and a storage medium.
Background
With the rapid development of internet technology, users use electronic devices more and more frequently, especially various applications installed on the electronic devices, including common software, games, entertainment software, and the like. In the process of using various applications, a user usually needs to register his/her login account and login password.
In view of the needs of special service scenarios, one user needs to log in the login account of another user for a certain period of time to perform corresponding operations. For example, during the game, the game player may have to interrupt the game due to network interruption or other transaction needs, and at this time, the friend is invited to continue the game instead.
In the related art, in order to meet the needs of a special service scenario, a user may notify another user of his/her login account and login password. For example, a gamer may send a login account and login password for a game to a friend, inviting the friend to continue the game instead. By adopting the method, the private information of the user is easy to be revealed, the user may need to change the login password, the operation is complicated, and potential safety hazards exist.
Disclosure of Invention
Embodiments of the present invention provide a login method, a login device, an electronic device, and a storage medium, so as to achieve the beneficial effects of protecting private information of a user from being leaked, simplifying operations, avoiding a user from changing a login password, and avoiding potential safety hazards. The specific technical scheme is as follows:
in a first aspect of the embodiments of the present invention, a login method is first provided, where the method includes:
receiving a login request sent by a client, wherein the login request carries a login account to be verified and a verification code to be verified;
determining a verification code corresponding to the login account to be verified, and if the verification code is not consistent with the verification code to be verified, determining a preset authorization token identification list;
determining an authorization verification code which is not corresponding to the login account to be verified according to the preset authorization token identification list;
and if the authorization verification code is consistent with the verification code to be verified, determining that the login is successful, and returning a message of successful login to the client.
In an optional embodiment, the determining the verification code corresponding to the login account to be verified includes:
acquiring a preset account list, and judging whether the preset account list contains the login account to be verified;
if the preset account list contains the login account to be verified, determining a verification code corresponding to the login account to be verified;
or,
analyzing a source IP address carried in the login request, determining a login area according to the source IP address, and judging whether the login area is a daily login area or not;
and if the login area is a daily login area, determining a verification code corresponding to the login account to be verified.
In an optional embodiment, the determining the verification code corresponding to the login account to be verified includes:
and inquiring a token identification corresponding to the login account to be verified, and generating a verification code corresponding to the login account to be verified by using the token identification.
In an optional embodiment, the determining the preset authorization token identification list includes:
and determining a preset authorization token identification list corresponding to the login account to be verified according to the mapping relation between the preset login account and the preset authorization token identification list.
In an optional implementation manner, the determining, according to the preset authorization token identification list, an authorization verification code that is not corresponding to the login account to be verified includes:
inquiring an authorization token identifier in the preset authorization token identifier list;
and generating an authorization verification code which is not corresponding to the login account to be verified by using the authorization token identifier.
In an optional embodiment, before executing the login method, the method further includes:
obtaining a token identifier to be added and a preset authorization token identifier list corresponding to a login account to be verified;
adding the token identification to be added to the preset authorization token identification list so as to increase the token identification to be added as an authorization token identification;
or,
obtaining a token identifier to be bound and a preset authorization token identifier list corresponding to a login account to be verified;
binding the token identification to be bound with the login account number to be verified, and adding the token identification to be bound in the preset authorization token identification list as an authorization token identification;
or,
receiving a token authorization instruction sent by a client, wherein the token authorization instruction is triggered in a preset login authorization interface of the client;
analyzing the token authorization instruction to obtain a token identifier of a login account to be authorized and a preset authorization token identifier list corresponding to the login account to be verified;
and authorizing the login account to be verified to the login account to be authorized to determine that the token identification is an authorization token identification, and recording the authorization token identification in the preset authorization token identification list.
In an optional implementation manner, the number of the authorization token identifications includes a plurality of numbers, and the generating, by using the authorization token identification, an authorization verification code that is not corresponding to the login account to be verified includes:
and generating an authorization verification code which is not corresponding to the login account to be verified by using any authorization token identifier.
In a second aspect of the embodiments of the present invention, there is also provided a login apparatus, including:
the system comprises a request receiving module, a login request sending module and a verification module, wherein the login request carries a login account to be verified and a verification code to be verified;
the first determining module is used for determining a verification code corresponding to the login account to be verified;
the list determining module is used for determining a preset authorization token identification list if the verification code is not consistent with the verification code to be verified;
the second determining module is used for determining an authorization verification code which is not corresponding to the login account to be verified according to the preset authorization token identification list;
and the login module is used for determining that the login is successful if the authorization verification code is consistent with the verification code to be verified, and returning a message of successful login to the client.
In a third aspect of the embodiments of the present invention, there is further provided an electronic device, including a processor, a communication interface, a memory, and a communication bus, where the processor, the communication interface, and the memory complete communication with each other through the communication bus;
a memory for storing a computer program;
a processor configured to implement the login method according to any one of the first aspect described above when executing a program stored in a memory.
In a fourth aspect of the embodiments of the present invention, there is also provided a storage medium, in which instructions are stored, and when the storage medium is run on a computer, the storage medium causes the computer to execute the login method according to any one of the first aspect.
In a fifth aspect of embodiments of the present invention, there is also provided a computer program product containing instructions which, when run on a computer, cause the computer to perform the login method of any one of the above-mentioned first aspects.
According to the technical scheme provided by the embodiment of the invention, a login request sent by a client is received, wherein the login request carries a login account to be verified and a verification code to be verified, a verification code corresponding to the login account to be verified is determined, a preset authorization token identification list is determined if the verification code is not consistent with the verification code to be verified, an authorization verification code corresponding to a login account not to be verified is determined according to the preset authorization token identification list, if the authorization verification code is consistent with the verification code to be verified, the login success is determined, and a login success message is returned to the client. The method comprises the steps of receiving a login request sent by a client, wherein the login request carries a login account to be verified and a verification code to be verified, determining a preset authorization token identification list if the verification code to be verified is not consistent with the verification code corresponding to the login account to be verified, further determining an authorization verification code corresponding to a login account not to be verified according to the determined preset authorization token identification list, and determining that login is successful if the authorization verification code is consistent with the verification code to be verified.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without inventive exercise.
Fig. 1 is a schematic flow chart illustrating an implementation of a login method in an embodiment of the present invention;
fig. 2 is a schematic flow chart of an implementation of a preset authorization token identifier list setting method shown in an embodiment of the present invention;
fig. 3 is a schematic flow chart of another implementation of a preset authorization token identification list setting method shown in the embodiment of the present invention;
fig. 4 is a schematic implementation flow diagram of another preset authorization token identification list setting method shown in the embodiment of the present invention;
fig. 5 is a schematic diagram illustrating an authorized Token ID recorded in a preset authorized Token ID list according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of a login device shown in an embodiment of the present invention;
fig. 7 is a schematic structural diagram of an electronic device shown in the embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be obtained by a person skilled in the art without any inventive step based on the embodiments of the present invention, are within the scope of the present invention.
As shown in fig. 1, an implementation flow diagram of a login method provided in an embodiment of the present invention is executed by a server, and specifically includes the following steps:
s101, a login request sent by a client is received, wherein the login request carries a login account to be verified and a verification code to be verified.
In the embodiment of the invention, a user can trigger a login request in a button triggering mode at a client, wherein the login request carries a login account to be verified and a verification code to be verified, which means that the user selects to log in through a Token (namely Token). Here, the login account to be verified may belong to the user, or the login account to be verified belongs to another user, which is not limited in the embodiment of the present invention.
For example, in the embodiment of the present invention, the user a may trigger a login request by a button trigger manner (e.g., clicking a "login" button) at the client, where the login request carries the login account (aaa) to be authenticated and the authentication code (385184) to be authenticated of the user a. Here the login account number (aaa) to be authenticated belongs to this user a.
Or,
in the embodiment of the present invention, the user a may trigger a login request by a button trigger manner (for example, clicking a "login" button) at the client, where the login request carries a login account (bbb) to be authenticated and an authentication code (385184) to be authenticated of the user B. Here the login account (bbb) to be authenticated belongs to another user, namely user B.
It should be noted that the verification code to be verified may be generated by using a Token identifier (for example, a Token ID, that is, a Token ID) corresponding to an account frequently logged in on the client, for example, if the account frequently logged in on the client is a login account of the user a, the verification code to be verified may be generated by using the Token ID corresponding to the login account of the user a, which is not limited in the embodiment of the present invention.
Specifically, for the generation of the verification code to be verified, a token (for generating the verification code) on the client may be based on a token identifier corresponding to an account number frequently logged in on the client and a current time (which is precise to a minute, and means only time of year, month, day, and no second is considered, for example, 52 minutes and 2 seconds at 13 times of 8 months and 9 days of 2021 year, 52 minutes and 51 seconds are considered to be the same time, and a part of the second may be ignored).
Based on this, in the embodiment of the present invention, for the server, the login request sent by the client may be received, and the login account to be verified and the verification code to be verified carried in the login request may be analyzed when the login request sent by the client is received.
For example, for the server, the login request sent by the client may be received, and in a case that the login request sent by the client is received, the to-be-authenticated login account (aaa) and the to-be-authenticated authentication code (385184) of the user a carried in the login request may be analyzed.
Or,
for the server, the login request sent by the client may be received, and the login account number to be authenticated (bbb) and the authentication code to be authenticated (385184) of the user B carried in the login request are analyzed when the login request sent by the client is received.
Based on this, the login account to be authenticated carried in the login request may belong to the user who triggered the login request, and is used to deal with a normal use scenario of the account, for example, the login account to be authenticated (aaa) of the user a carried in the login request.
Or,
the login account to be authenticated, which is carried in the login request, may belong to another user (i.e., a user that does not trigger the login request), and is used to deal with an account sharing scenario, in which only the login account is shared, for example, the login account to be authenticated (bbb) of the user B, which is carried in the login request.
For example, in an account sharing scenario, a user a may trigger a login request in a manner of button triggering at a client, where the login request carries a login account to be authenticated (i.e., a login account (bbb) of a user B) and an authentication code to be authenticated (385184).
For the client, the account number which is frequently logged in, i.e. the login account number (aaa) of the user a, the authentication code to be authenticated (385184) may be generated by using the Token identifier (i.e. Token ID: t1) corresponding to the login account number (aaa) of the user a.
S102, determining a verification code corresponding to the login account to be verified, and if the verification code is not consistent with the verification code to be verified, determining a preset authorization token identification list.
In the embodiment of the invention, for the server, the verification code corresponding to the login account to be verified can be determined. The authentication code corresponding to the login account to be authenticated can be determined by querying a token identifier corresponding to the login account to be authenticated and generating the authentication code corresponding to the login account to be authenticated by using the token identifier.
For example, for the login account to be authenticated (i.e. the login account (bbb) of the user B), the server queries a Token identifier (i.e. Token ID: t2) corresponding to the login account to be authenticated, and generates an authentication code corresponding to the login account to be authenticated by using the Token identifier, thereby determining the authentication code corresponding to the login account to be authenticated.
Specifically, for the generation of the verification code, based on the token identification corresponding to the login account to be verified and the current time (which is precise to minutes, meaning only time of year, month and day is considered, and no second is considered, for example, 52 minutes and 2 seconds at 13 hours of 8 months and 9 days of 2021 and 52 minutes and 51 seconds at 13 hours of 9 days of 8 months and 9 days of 2021 are considered to be the same time, and a part of the second is ignored), a set of verification codes generated by a certain verification code generation rule, which is generally composed of 6 numbers, may be changed every one minute, and the verification code generation rule on the server is consistent with the verification code generation rule on the client, which is not limited in the embodiment of the present invention.
Before determining the verification code corresponding to the login account to be verified, the server may obtain a preset account list, determine whether the preset account list includes the login account to be verified, and determine whether the verification code corresponding to the login account to be verified is determined according to a determination result.
Specifically, if the preset account list includes a login account to be verified, it indicates that the login is normal, at this time, a verification code corresponding to the login account to be verified may be determined, and if the preset account list does not include the login account to be verified, it indicates that the login is abnormal, at this time, a message of abnormal login may be returned to the client.
For example, if the preset account list includes a login account (bbb) to be verified, which indicates that the login is normal, the login account to be verified is a registered account, and at this time, the verification code corresponding to the login account to be verified is determined.
If the login account (bbb) to be verified is not included in the preset account list, the login is abnormal, the login account to be verified is an unregistered account, and at this time, a message of the login abnormality can be returned to the client, namely, the user is informed that the account is unregistered or does not exist.
In addition, before the verification code corresponding to the login account to be verified is determined, the server can also analyze a source IP address carried in the login request, determine a login area according to the source IP address, judge whether the login area is a daily login area, and determine whether the verification code corresponding to the login account to be verified is determined according to a judgment result.
Specifically, if the login area is a daily login area (corresponding to the login account to be verified), which indicates that the login is normal, the verification code corresponding to the login account to be verified is determined, and if the login area is not the daily login area, which indicates that the login is abnormal, a message of abnormal login can be returned to the channel bound to the login account to be verified.
For example, if the login area is a daily login area (corresponding to the login account to be authenticated), which indicates that the login is normal, the authentication code corresponding to the login account to be authenticated may be determined, if the login area is not the daily login area, which indicates that the login is abnormal, the login account to be authenticated logs in a different place, and at this time, a message of abnormal login is returned to a mailbox or a mobile phone number bound to the login account to be authenticated, which informs the user of the login in a different place.
It should be noted that the daily login area refers to a daily login area corresponding to a login account to be authenticated, and the channel generally refers to a channel such as a mailbox or a mobile phone number, which is not limited in the embodiment of the present invention.
In addition, after determining the verification code corresponding to the login account to be verified, the server may compare the verification code corresponding to the login account to be verified with the verification code to be verified, and perform different processing according to the comparison result.
Specifically, if the verification code corresponding to the login account to be verified is consistent with the verification code to be verified, it is indicated that the current scene is a normal account usage scene, that is, the user logs in the account of the user, at this time, it may be determined that the login is successful, and a message of successful login is returned to the client.
For example, if the verification code corresponding to the login account (aaa) to be verified is consistent with the verification code (385184) to be verified, it indicates that the current scenario is a normal usage scenario of the account, that is, the user a logs in his/her account, and at this time, it is determined that the login is successful, and a message of successful login is returned to the client.
In addition, if the verification code corresponding to the login account to be verified is not consistent with the verification code to be verified, it is indicated that the current scene may be an account sharing scene, that is, the user logs in an account of another person, and at this time, the preset authorization token identification list may be determined.
For example, if the verification code corresponding to the login account (bbb) to be verified is not consistent with the verification code (385184) to be verified, which indicates that the current scenario may be an account sharing scenario, that is, the user a logs in the account of the user B, at this time, the preset authorization token identification list may be determined.
In the embodiment of the present invention, different authorization token identification lists are preset for different login accounts, that is, each login account has a corresponding preset authorization token identification list, as shown in table 1 below, where the preset authorization token identification list includes an authorization token identification.
| Login account | Preset authorization token identification list |
| aaa | Preset authorization token identification list 1 |
| bbb | Preset authorization token identification list 2 |
| …… | …… |
TABLE 1
Based on this, in the embodiment of the present invention, the preset authorization token identification list may be specifically determined in the following manner: and determining a preset authorization token identification list corresponding to the login account to be verified according to the mapping relation between the preset login account and the preset authorization token identification list.
For example, based on the mapping relationship between the login account and the preset authorization token identification list shown in table 1, for the login account to be authenticated (bbb), the preset authorization token identification list (i.e. preset authorization token identification list 2) corresponding to the login account to be authenticated may be determined.
S103, determining an authorization verification code which is not corresponding to the login account number to be verified according to the preset authorization token identification list.
In the embodiment of the present invention, for the preset authorization token identification list, that is, the preset authorization token identification list corresponding to the login account to be verified, the authorization verification code corresponding to the login account not to be verified can be determined according to the preset authorization token identification list.
For example, for a preset authorization token identification list corresponding to a login account to be authenticated (i.e. the login account (bbb) of the user B), an authorization authentication code corresponding to a login account not to be authenticated, that is, an authorization authentication code corresponding to the login account (aaa) of the user a, is determined according to the preset authorization token identification list.
Before determining the authorization verification code corresponding to the login account not to be verified according to the preset authorization token identification list, judging whether the preset authorization token identification list is empty, if not, determining the authorization verification code corresponding to the login account not to be verified according to the preset authorization token identification list, otherwise, determining that the login is failed, and returning a login failure message to the client.
In the embodiment of the present invention, the authorization verification code corresponding to the login account not to be verified may be specifically determined in the following manner: and inquiring an authorization token identifier in a preset authorization token identifier list, and generating an authorization verification code corresponding to the login account not to be verified by using the authorization token identifier. Here, the authorization token identification corresponds to the login account number to be verified one by one.
For example, an authorized Token ID (i.e., Token ID: t1) in the preset authorized Token ID list is queried, and an authorized verification code corresponding to the login account not to be verified is generated by using the authorized Token ID (i.e., Token ID: t1), where the authorized Token ID (i.e., Token ID: t1) corresponds to the login account of the user A, i.e., an authorized verification code corresponding to the login account of the user A is generated.
Specifically, for the generation of the authorization verification code, a set of verification codes generated by a certain verification code generation rule may be composed of 6 numbers and may be changed every one minute, and the verification code generation rule on the server is consistent with the verification code generation rule on the client, which is not limited in the embodiment of the present invention, based on the authorization token identifier in the preset authorization token identifier list and the current time (which is precise to minutes, meaning only time of year, month, day, and no consideration of seconds, for example, it is considered that 52 minutes and 2 seconds at 13/8/9/13/2021/8/9/52 minutes and 51 seconds are the same time, and the second part is ignored).
In addition, in the embodiment of the present invention, the number of the authorization token identifications may include a plurality of authorization token identifications, that is, one or more authorization token identifications in the preset authorization token identification list may be included, and then an authorization verification code corresponding to the login account number not to be verified may be correspondingly generated by using any authorization token identification.
It should be noted that, for the identifier, in the embodiment of the present invention, specifically, the identifier may be an ID, a name, a storage address identified by the authorization token, and the like, which is not limited in the embodiment of the present invention.
And S104, if the authorization verification code is consistent with the verification code to be verified, determining that the login is successful, and returning a message of successful login to the client.
In the embodiment of the invention, for the server, the authorization verification code corresponding to the login account number not to be verified can be compared with the verification code to be verified, and whether the login is successful or not can be determined according to the comparison result.
Specifically, if the authorization verification code corresponding to the login account number not to be verified is consistent with the verification code to be verified, the login success can be determined, a login success message is returned to the client, and if the authorization verification code corresponding to the login account number not to be verified is inconsistent with the verification code to be verified, the login failure can be determined, and a login failure message is returned to the client.
For example, for an authorization verification code corresponding to a login account not to be verified, that is, an authorization verification code corresponding to the login account of the user a, if the authorization verification code is consistent with the verification code to be verified (385184), at this time, a login success may be determined, and a login success message is returned to the client, otherwise, a login failure message may be determined, and a login failure message is returned to the client.
In the embodiment of the present invention, the number of the authorization token identifiers includes a plurality of identifiers, and the number of the corresponding authorization verification codes includes a plurality of identifiers, and accordingly, if the authorization verification code corresponding to any non-to-be-verified login account number is consistent with the to-be-verified verification code, a login success may be determined at this time, and a login success message is returned to the client, and if the authorization verification code corresponding to any non-to-be-verified login account number is inconsistent with the to-be-verified verification code, a login failure may be determined at this time, and a login failure message is returned to the client.
For example, the authorization Token ID in the preset authorization Token ID list corresponding to the login account to be authenticated (the login account (bbb) of the user B): t1, t3, … …, where the number of the corresponding authorization verification codes includes a plurality of codes, and correspondingly, if the authorization verification code corresponding to any non-to-be-verified login account number is consistent with the to-be-verified verification code (385184), it may be determined that the login is successful at this time, and a login success message is returned to the client, and if the authorization verification code corresponding to any non-to-be-verified login account number is inconsistent with the to-be-verified verification code (385184), it may be determined that the login is failed at this time, and a login failure message is returned to the client.
In an account sharing scenario, a user B only needs to share (i.e. tell) a login account (bbb) to the user A, the user A triggers a login request at a client, the login request carries a login account to be verified, namely the login account (bbb) of the user B, and the user B can successfully log in according to the login request subsequently. Therefore, in the account sharing process, only the login account is shared, the private information of the user can be protected from being leaked, the operation is simplified, the user is prevented from changing the login password, and the potential safety hazard is avoided.
According to the technical scheme provided by the embodiment of the invention, the login request sent by the client is received, wherein the login request carries the login account number to be verified and the verification code to be verified, the verification code corresponding to the login account number to be verified is determined, if the verification code is not consistent with the verification code to be verified, a preset authorization token identification list is determined, the authorization verification code corresponding to the login account number not to be verified is determined according to the preset authorization token identification list, if the authorization verification code is consistent with the verification code to be verified, the login success is determined, and a login success message is returned to the client.
The method comprises the steps of receiving a login request sent by a client, wherein the login request carries a login account to be verified and a verification code to be verified, determining a preset authorization token identification list if the verification code to be verified is not consistent with the verification code corresponding to the login account to be verified, further determining an authorization verification code corresponding to a login account not to be verified according to the determined preset authorization token identification list, and determining that login is successful if the authorization verification code is consistent with the verification code to be verified.
As shown in fig. 2, an implementation flow diagram of a method for setting an identifier list of a preset authorization token provided in an embodiment of the present invention is executed by a server, and specifically includes the following steps:
s201, obtaining a token identifier to be added, and obtaining a preset authorization token identifier list corresponding to a login account to be verified.
In the embodiment of the invention, for the server, the token identifier to be added can be obtained, and the preset authorization token identifier list corresponding to the login account to be verified can be obtained. The number of token identifications to be added here may be one or more, and is not limited by the embodiment of the present invention.
For example, in the embodiment of the present invention, for the server, the token identifier to be added may be obtained: the authentication method comprises the steps of obtaining a token identification (t1) corresponding to a login account (aaa) of a user A, obtaining a token identification (t2) corresponding to a login account (ccc) of a user C, and correspondingly obtaining a preset authorization token identification list corresponding to a login account to be authenticated (namely, a login account (bbb) of a user B).
S202, adding the token identification to be added to the preset authorization token identification list so as to add the token identification to be added as an authorization token identification.
In the embodiment of the present invention, for the server, the token identifier to be added may be added to the preset authorization token identifier list corresponding to the login account to be verified, so as to add the token identifier to be added as the authorization token identifier.
For example, in the embodiment of the present invention, for the server, the token identifications to be added, i.e., t1 and t3, are added to the preset authorization token identification list corresponding to the login account to be verified (i.e., the login account (bbb) of the user B), so as to add the token identifications to be added (i.e., t1 and t3) as authorization token identifications.
In addition, if the authorization token identifier can be deleted from the preset authorization token identifier list according to actual needs, which is not limited in the embodiment of the present invention.
As shown in fig. 3, an implementation flow diagram of another method for setting a preset authorization token identifier list provided in the embodiment of the present invention is executed by a server, and specifically includes the following steps:
s301, obtaining a token identifier to be bound, and obtaining a preset authorization token identifier list corresponding to a login account to be verified.
In the embodiment of the invention, for the server, the token identifier to be bound can be acquired, and the preset authorization token identifier list corresponding to the login account to be verified can be acquired. The number of token identifications to be bound here may be one or more, and the embodiment of the present invention does not limit this.
For example, in the embodiment of the present invention, for the server, the token identifier to be bound may be obtained: the authentication method comprises the steps of obtaining a token identification (t1) corresponding to a login account (aaa) of a user A, obtaining a token identification (t2) corresponding to a login account (ccc) of a user C, and correspondingly obtaining a preset authorization token identification list corresponding to a login account to be authenticated (namely, a login account (bbb) of a user B).
S302, the token identification to be bound and the login account number to be verified are bound, and the token identification to be bound is added to the preset authorization token identification list to be used as an authorization token identification.
In the embodiment of the invention, for the server, the token identifier to be bound and the login account to be verified can be bound, so that the token identifier to be bound is added to a preset authorization token identifier list corresponding to the login account to be verified as the authorization token identifier.
For example, in the embodiment of the present invention, for the server, the token identifiers to be bound, i.e., t1 and t3, are bound with the login account to be authenticated (i.e., the login account (bbb) of the user B), so as to add the token identifiers to be bound (i.e., t1 and t3) in the preset authorization token identifier list corresponding to the login account to be authenticated as authorization token identifiers.
In addition, if the authorization token identifier can be deleted from the preset authorization token identifier list according to actual needs, which is not limited in the embodiment of the present invention.
As shown in fig. 4, an implementation flow diagram of another method for setting a preset authorization token identifier list provided in the embodiment of the present invention is executed by a server, and specifically includes the following steps:
s401, receiving a token authorization instruction sent by a client, wherein the token authorization instruction is triggered in a preset login authorization interface of the client.
In the embodiment of the invention, a user can start a corresponding login authorization interface, trigger a token authorization instruction in the login authorization interface and send the token authorization instruction to the server. Thus, for the server, a token authorization instruction sent by the client can be received.
It should be noted that, for the token authorization instruction, the token identifier of the login account to be authorized and the preset authorization token identifier list corresponding to the login account to be verified are carried in the token authorization instruction, which is not limited in the embodiment of the present invention.
S402, analyzing the token authorization instruction to obtain a token identifier of the login account to be authorized and a preset authorization token identifier list corresponding to the login account to be verified.
In the embodiment of the present invention, for the server, the token authorization instruction may be analyzed to obtain a token identifier to be authorized and obtain a preset authorization token identifier list corresponding to the login account to be verified. The number of token identifications to be authorized may be one or more, and the embodiment of the present invention does not limit this.
For example, in the embodiment of the present invention, for the server, the token authorization instruction may be parsed to obtain the token identifier to be authorized: the authentication method comprises the steps of obtaining a token identification (t1) corresponding to a login account (aaa) of a user A, obtaining a token identification (t3) corresponding to a login account (ccc) of a user C, and correspondingly obtaining a preset authorization token identification list corresponding to a login account to be authenticated (namely, a login account (bbb) of a user B).
And S403, authorizing the login account to be verified to the login account to be authorized to determine that the token identifier is an authorization token identifier, and recording the authorization token identifier in the preset authorization token identifier list.
In the embodiment of the invention, for the server, the login account to be verified is authorized to the login account to be authorized, so that the token identifier of the login account to be authorized is determined to be the authorization token identifier, and the authorization token identifier is recorded in the preset authorization token identifier list.
For example, in the embodiment of the present invention, for the server, the login account to be authenticated (i.e., the login account (bbb) of the user B) is authorized to the login account to be authorized (i.e., the login account (aaa) of the user a), so as to determine that the Token ID of the login account to be authorized (i.e., the login account (aaa) of the user a) is the authorized Token ID, and the authorized Token ID, i.e., t1, is recorded in the preset authorized Token ID list, as shown in fig. 5.
In addition, if the authorization token identifier can be deleted from the preset authorization token identifier list according to actual needs, which is not limited in the embodiment of the present invention.
Corresponding to the foregoing method embodiment, an embodiment of the present invention further provides a login apparatus, as shown in fig. 6, where the apparatus may include: a request receiving module 610, a first determining module 620, a list determining module 630, a second determining module 640, a login module 650.
A request receiving module 610, configured to receive a login request sent by a client, where the login request carries a login account to be verified and a verification code to be verified;
a first determining module 620, configured to determine a verification code corresponding to the login account to be verified;
a list determining module 630, configured to determine a preset authorization token identifier list if the verification code is inconsistent with the verification code to be verified;
a second determining module 640, configured to determine, according to the preset authorization token identifier list, an authorization verification code that is not corresponding to the login account to be verified;
and the login module 650 is configured to determine that the login is successful if the authorization verification code is consistent with the verification code to be verified, and return a message that the login is successful to the client.
The embodiment of the present invention further provides an electronic device, as shown in fig. 7, which includes a processor 71, a communication interface 72, a memory 73 and a communication bus 74, where the processor 71, the communication interface 72, and the memory 73 complete mutual communication through the communication bus 74,
a memory 73 for storing a computer program;
the processor 71, when executing the program stored in the memory 73, implements the following steps:
receiving a login request sent by a client, wherein the login request carries a login account to be verified and a verification code to be verified; determining a verification code corresponding to the login account to be verified, and if the verification code is not consistent with the verification code to be verified, determining a preset authorization token identification list; determining an authorization verification code which is not corresponding to the login account to be verified according to the preset authorization token identification list; and if the authorization verification code is consistent with the verification code to be verified, determining that the login is successful, and returning a message of successful login to the client.
The communication bus mentioned in the electronic device may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The communication 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, but this does not mean that there is only one bus or one type of bus.
The communication interface is used for communication between the electronic equipment and other equipment.
The Memory may include a Random Access Memory (RAM) or a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. Optionally, the memory may also be at least one memory device located remotely from the processor.
The Processor may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the Integrated Circuit may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a discrete Gate or transistor logic device, or a discrete hardware component.
In another embodiment of the present invention, a storage medium is further provided, where instructions are stored, and when the instructions are executed on a computer, the instructions cause the computer to execute the login method in any one of the above embodiments.
In a further embodiment of the present invention, there is also provided a computer program product containing instructions which, when run on a computer, cause the computer to perform the login method as described in any of the above embodiments.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the invention to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a storage medium or transmitted from one storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The storage medium may be any available medium that can be accessed by a computer or a data storage device including one or more available media integrated servers, data centers, and the like. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
All the embodiments in the present specification are described in a related manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The above description is only for the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention shall fall within the protection scope of the present invention.
Claims (10)
1. A method of logging in, the method comprising:
receiving a login request sent by a client, wherein the login request carries a login account to be verified and a verification code to be verified;
determining a verification code corresponding to the login account to be verified, and if the verification code is not consistent with the verification code to be verified, determining a preset authorization token identification list;
determining an authorization verification code which is not corresponding to the login account to be verified according to the preset authorization token identification list;
and if the authorization verification code is consistent with the verification code to be verified, determining that the login is successful, and returning a message of successful login to the client.
2. The method according to claim 1, wherein the determining the verification code corresponding to the login account to be verified comprises:
acquiring a preset account list, and judging whether the preset account list contains the login account to be verified;
if the preset account list contains the login account to be verified, determining a verification code corresponding to the login account to be verified;
or,
analyzing a source IP address carried in the login request, determining a login area according to the source IP address, and judging whether the login area is a daily login area or not;
and if the login area is a daily login area, determining a verification code corresponding to the login account to be verified.
3. The method according to claim 1, wherein the determining the verification code corresponding to the login account to be verified comprises:
and inquiring a token identification corresponding to the login account to be verified, and generating a verification code corresponding to the login account to be verified by using the token identification.
4. The method of claim 1, wherein determining the list of preset authorization token identifications comprises:
and determining a preset authorization token identification list corresponding to the login account to be verified according to the mapping relation between the preset login account and the preset authorization token identification list.
5. The method according to claim 1, wherein the determining, according to the preset authorization token identification list, an authorization verification code that is not corresponding to the login account to be verified includes:
inquiring an authorization token identifier in the preset authorization token identifier list;
and generating an authorization verification code which is not corresponding to the login account to be verified by using the authorization token identifier.
6. The method of claim 5, further comprising, prior to performing the login method:
obtaining a token identifier to be added and a preset authorization token identifier list corresponding to a login account to be verified;
adding the token identification to be added to the preset authorization token identification list so as to increase the token identification to be added as an authorization token identification;
or,
obtaining a token identifier to be bound and a preset authorization token identifier list corresponding to a login account to be verified;
binding the token identification to be bound with the login account number to be verified, and adding the token identification to be bound in the preset authorization token identification list as an authorization token identification;
or,
receiving a token authorization instruction sent by a client, wherein the token authorization instruction is triggered in a preset login authorization interface of the client;
analyzing the token authorization instruction to obtain a token identifier of a login account to be authorized and a preset authorization token identifier list corresponding to the login account to be verified;
and authorizing the login account to be verified to the login account to be authorized to determine that the token identification is an authorization token identification, and recording the authorization token identification in the preset authorization token identification list.
7. The method according to claim 5, wherein the number of the authorization token identifications includes a plurality of numbers, and the generating, by using the authorization token identifications, the authorization verification code that is not corresponding to the login account to be verified includes:
and generating an authorization verification code which is not corresponding to the login account to be verified by using any authorization token identifier.
8. A login apparatus, the apparatus comprising:
the system comprises a request receiving module, a login request sending module and a verification module, wherein the login request carries a login account to be verified and a verification code to be verified;
the first determining module is used for determining a verification code corresponding to the login account to be verified;
the list determining module is used for determining a preset authorization token identification list if the verification code is not consistent with the verification code to be verified;
the second determining module is used for determining an authorization verification code which is not corresponding to the login account to be verified according to the preset authorization token identification list;
and the login module is used for determining that the login is successful if the authorization verification code is consistent with the verification code to be verified, and returning a message of successful login to the client.
9. An electronic device is characterized by comprising a processor, a communication interface, a memory and a communication bus, wherein the processor and the communication interface are used for realizing mutual communication by the memory through the communication bus;
a memory for storing a computer program;
a processor for implementing the method steps of any one of claims 1 to 7 when executing a program stored in the memory.
10. A storage medium on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111463180.3A CN114172716A (en) | 2021-12-02 | 2021-12-02 | Login method, login device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111463180.3A CN114172716A (en) | 2021-12-02 | 2021-12-02 | Login method, login device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114172716A true CN114172716A (en) | 2022-03-11 |
Family
ID=80482656
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111463180.3A Pending CN114172716A (en) | 2021-12-02 | 2021-12-02 | Login method, login device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114172716A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115086040A (en) * | 2022-06-16 | 2022-09-20 | 北京金山云网络技术有限公司 | Login authentication method, device, storage medium and electronic equipment |
Citations (28)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CA2673316A1 (en) * | 2004-11-04 | 2006-05-11 | Topeer Corporation | System and method for creating a secure trusted social network |
| CN104104507A (en) * | 2013-04-10 | 2014-10-15 | 比亚迪股份有限公司 | Method and system for logging in to user service network |
| WO2015101332A1 (en) * | 2013-12-31 | 2015-07-09 | 腾讯科技（深圳）有限公司 | Password classification management method and system |
| CN104852903A (en) * | 2015-04-13 | 2015-08-19 | 苏州天趣信息科技有限公司 | Method and system for temporarily sharing game account |
| US20150312236A1 (en) * | 2014-04-29 | 2015-10-29 | Twitter, Inc. | Authentication mechanism |
| US20160034990A1 (en) * | 2014-07-31 | 2016-02-04 | Robert J. Kannair | System and method for securely retrieving private data from customer mobile device |
| CN105407070A (en) * | 2014-07-28 | 2016-03-16 | 小米科技有限责任公司 | Logging-in authorization method and device |
| CN105656948A (en) * | 2016-03-30 | 2016-06-08 | 北京小米移动软件有限公司 | Account login method and device |
| CN105812398A (en) * | 2016-06-06 | 2016-07-27 | 百度在线网络技术（北京）有限公司 | Remote login authorization method and remote login authorization device |
| CN105935495A (en) * | 2016-04-12 | 2016-09-14 | 网易（杭州）网络有限公司 | Game role log-in control method, apparatus and system, and game system |
| CN106656978A (en) * | 2016-10-19 | 2017-05-10 | 广东欧珀移动通信有限公司 | Account login method and server |
| CN106656958A (en) * | 2016-09-27 | 2017-05-10 | 乐视控股（北京）有限公司 | Mobile-terminal-based account login method, login apparatus and login system |
| CN107733864A (en) * | 2017-09-08 | 2018-02-23 | 咪咕互动娱乐有限公司 | A kind of account sharing method, device and computer-readable recording medium |
| CN107885985A (en) * | 2017-11-23 | 2018-04-06 | 维沃移动通信有限公司 | A kind of application program account sharing method and terminal |
| CN108289074A (en) * | 2017-01-09 | 2018-07-17 | 腾讯科技（深圳）有限公司 | User account login method and device |
| CN108712435A (en) * | 2018-05-25 | 2018-10-26 | 四川斐讯信息技术有限公司 | A kind of verification system and method for login application program |
| CN108769083A (en) * | 2018-08-01 | 2018-11-06 | 北京奇虎科技有限公司 | Login method, apparatus and system based on distributed server |
| CN109286633A (en) * | 2018-10-26 | 2019-01-29 | 深圳市华云中盛科技有限公司 | Single sign-on method, device, computer equipment and storage medium |
| CN109309683A (en) * | 2018-10-30 | 2019-02-05 | 泰华智慧产业集团股份有限公司 | The method and system of client identity verifying based on token |
| KR20190011595A (en) * | 2017-07-25 | 2019-02-07 | (주)헤리트 | Authentication method and apparatus for sharing login ID |
| CN109802941A (en) * | 2018-12-14 | 2019-05-24 | 平安科技（深圳）有限公司 | A kind of login validation method, device, storage medium and server |
| CN110602216A (en) * | 2019-09-16 | 2019-12-20 | 宁波奥克斯电气股份有限公司 | Method and device for using single account by multiple terminals, cloud server and storage medium |
| CN110598385A (en) * | 2019-09-16 | 2019-12-20 | 宁波奥克斯电气股份有限公司 | Air conditioner user account sharing authorization method and system |
| CN110661788A (en) * | 2019-09-05 | 2020-01-07 | 深圳龙图腾创新设计有限公司 | Login authentication management system, login method, login device, equipment and storage medium |
| CN111181977A (en) * | 2019-12-31 | 2020-05-19 | 瑞庭网络技术（上海）有限公司 | Login method, device, electronic equipment and medium |
| CN111241555A (en) * | 2019-12-30 | 2020-06-05 | 北京顺达同行科技有限公司 | Access method and device for simulating user login, computer equipment and storage medium |
| CN112883366A (en) * | 2021-03-29 | 2021-06-01 | 口碑(上海)信息技术有限公司 | Account sharing login method, device, system, electronic equipment and storage medium |
| CN113111341A (en) * | 2021-04-12 | 2021-07-13 | 北京沃东天骏信息技术有限公司 | Account sharing and login method and device |
-
2021
- 2021-12-02 CN CN202111463180.3A patent/CN114172716A/en active Pending
Patent Citations (28)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CA2673316A1 (en) * | 2004-11-04 | 2006-05-11 | Topeer Corporation | System and method for creating a secure trusted social network |
| CN104104507A (en) * | 2013-04-10 | 2014-10-15 | 比亚迪股份有限公司 | Method and system for logging in to user service network |
| WO2015101332A1 (en) * | 2013-12-31 | 2015-07-09 | 腾讯科技（深圳）有限公司 | Password classification management method and system |
| US20150312236A1 (en) * | 2014-04-29 | 2015-10-29 | Twitter, Inc. | Authentication mechanism |
| CN105407070A (en) * | 2014-07-28 | 2016-03-16 | 小米科技有限责任公司 | Logging-in authorization method and device |
| US20160034990A1 (en) * | 2014-07-31 | 2016-02-04 | Robert J. Kannair | System and method for securely retrieving private data from customer mobile device |
| CN104852903A (en) * | 2015-04-13 | 2015-08-19 | 苏州天趣信息科技有限公司 | Method and system for temporarily sharing game account |
| CN105656948A (en) * | 2016-03-30 | 2016-06-08 | 北京小米移动软件有限公司 | Account login method and device |
| CN105935495A (en) * | 2016-04-12 | 2016-09-14 | 网易（杭州）网络有限公司 | Game role log-in control method, apparatus and system, and game system |
| CN105812398A (en) * | 2016-06-06 | 2016-07-27 | 百度在线网络技术（北京）有限公司 | Remote login authorization method and remote login authorization device |
| CN106656958A (en) * | 2016-09-27 | 2017-05-10 | 乐视控股（北京）有限公司 | Mobile-terminal-based account login method, login apparatus and login system |
| CN106656978A (en) * | 2016-10-19 | 2017-05-10 | 广东欧珀移动通信有限公司 | Account login method and server |
| CN108289074A (en) * | 2017-01-09 | 2018-07-17 | 腾讯科技（深圳）有限公司 | User account login method and device |
| KR20190011595A (en) * | 2017-07-25 | 2019-02-07 | (주)헤리트 | Authentication method and apparatus for sharing login ID |
| CN107733864A (en) * | 2017-09-08 | 2018-02-23 | 咪咕互动娱乐有限公司 | A kind of account sharing method, device and computer-readable recording medium |
| CN107885985A (en) * | 2017-11-23 | 2018-04-06 | 维沃移动通信有限公司 | A kind of application program account sharing method and terminal |
| CN108712435A (en) * | 2018-05-25 | 2018-10-26 | 四川斐讯信息技术有限公司 | A kind of verification system and method for login application program |
| CN108769083A (en) * | 2018-08-01 | 2018-11-06 | 北京奇虎科技有限公司 | Login method, apparatus and system based on distributed server |
| CN109286633A (en) * | 2018-10-26 | 2019-01-29 | 深圳市华云中盛科技有限公司 | Single sign-on method, device, computer equipment and storage medium |
| CN109309683A (en) * | 2018-10-30 | 2019-02-05 | 泰华智慧产业集团股份有限公司 | The method and system of client identity verifying based on token |
| CN109802941A (en) * | 2018-12-14 | 2019-05-24 | 平安科技（深圳）有限公司 | A kind of login validation method, device, storage medium and server |
| CN110661788A (en) * | 2019-09-05 | 2020-01-07 | 深圳龙图腾创新设计有限公司 | Login authentication management system, login method, login device, equipment and storage medium |
| CN110602216A (en) * | 2019-09-16 | 2019-12-20 | 宁波奥克斯电气股份有限公司 | Method and device for using single account by multiple terminals, cloud server and storage medium |
| CN110598385A (en) * | 2019-09-16 | 2019-12-20 | 宁波奥克斯电气股份有限公司 | Air conditioner user account sharing authorization method and system |
| CN111241555A (en) * | 2019-12-30 | 2020-06-05 | 北京顺达同行科技有限公司 | Access method and device for simulating user login, computer equipment and storage medium |
| CN111181977A (en) * | 2019-12-31 | 2020-05-19 | 瑞庭网络技术（上海）有限公司 | Login method, device, electronic equipment and medium |
| CN112883366A (en) * | 2021-03-29 | 2021-06-01 | 口碑(上海)信息技术有限公司 | Account sharing login method, device, system, electronic equipment and storage medium |
| CN113111341A (en) * | 2021-04-12 | 2021-07-13 | 北京沃东天骏信息技术有限公司 | Account sharing and login method and device |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115086040A (en) * | 2022-06-16 | 2022-09-20 | 北京金山云网络技术有限公司 | Login authentication method, device, storage medium and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108183924A (en) | A kind of login validation method and terminal device | |
| CN106878250B (en) | Cross-application single-state login method and device | |
| CN107196909B (en) | Invitation registration method and device | |
| CN105591743B (en) | Method and device for identity authentication through equipment operation characteristics of user terminal | |
| CN111030812A (en) | Token verification method, device, storage medium and server | |
| CN111355713B (en) | Proxy access method, device, proxy gateway and readable storage medium | |
| CN110691085B (en) | Login method, login device, password management system and computer readable medium | |
| CN115065512B (en) | Account login method, system, device, electronic equipment and storage medium | |
| US10277579B2 (en) | Information processing system that provides a resource to an application of a terminal through a network | |
| CN113179282A (en) | Method and device for merging account numbers and server | |
| CN114172716A (en) | Login method, login device, electronic equipment and storage medium | |
| CN111259368A (en) | Method and equipment for logging in system | |
| CN108650123B (en) | Fault information recording method, device, equipment and storage medium | |
| CN112272093B (en) | Token management method, electronic equipment and readable storage medium | |
| CN113761498A (en) | Third party login information hosting method, system, equipment and storage medium | |
| CN114172713A (en) | Login method, login device, electronic equipment and storage medium | |
| CN110336840B (en) | Third party account registration method and system for voice conversation platform | |
| CN116389140A (en) | Identity authentication method and device, electronic equipment and storage medium | |
| CN114157483B (en) | Login method, login device, electronic equipment and storage medium | |
| CN111680279B (en) | Login verification method, device and system | |
| CN113285915A (en) | Registration management method and device and private cloud control server | |
| CN114971632A (en) | Social platform binding system, method and device, electronic equipment and storage medium | |
| CN108449367B (en) | Method and device for managing user login security, electronic equipment and readable medium | |
| CN107172106B (en) | Security information interaction method and system | |
| JP2001175600A (en) | Method and device for reporting illegal access |
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 |