CN111817999A - User login method and device - Google Patents
User login method and device Download PDFInfo
- Publication number
- CN111817999A CN111817999A CN201910288984.0A CN201910288984A CN111817999A CN 111817999 A CN111817999 A CN 111817999A CN 201910288984 A CN201910288984 A CN 201910288984A CN 111817999 A CN111817999 A CN 111817999A
- Authority
- CN
- China
- Prior art keywords
- account
- server
- user
- binding
- party
- 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 55
- 238000004891 communication Methods 0.000 claims description 38
- 238000012795 verification Methods 0.000 claims description 24
- 230000004044 response Effects 0.000 claims description 15
- 238000012790 confirmation Methods 0.000 claims description 5
- 238000004883 computer application Methods 0.000 abstract description 2
- 238000012545 processing Methods 0.000 description 20
- 238000010586 diagram Methods 0.000 description 6
- 238000004590 computer program Methods 0.000 description 4
- 238000013475 authorization Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000003491 array Methods 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000002349 favourable effect Effects 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000003672 processing method Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001960 triggered effect Effects 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/0815—Network architectures or network communication protocols for network security for authentication of entities providing single-sign-on or federations
-
- 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/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
-
- 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/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
Landscapes
- Engineering & Computer Science (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Power Engineering (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The embodiment of the application provides a user login method and device, and relates to the technical field of computer application. Receiving a third party account login request sent by a client; judging whether the third party account has a binding relationship; if yes, logging in a server by using the third-party account; if not, sending binding prompt information to the client; receiving an account binding request sent by the client; determining a user account and establishing a binding relationship between the user account and the third party account; and the user account is used for logging in the server. The technical scheme provided by the embodiment of the application ensures the login safety of the user.
Description
Technical Field
The embodiment of the application relates to the technical field of computer application, in particular to a user login method and device.
Background
In the use of application programs (APP), in order to better obtain the services provided by an application server, a user is often required to log in the application server.
In the prior art, in order to facilitate the user login, the user can log in through the third-party account authorization. However, the method of logging in by using the third party account has the problem of poor security. If the information of the subsequent third-party account is wrong or the password is lost, the third-party account cannot be continuously used for logging in, so that inconvenience is brought to the user.
Disclosure of Invention
The embodiment of the application provides a user login method and device, which are used for solving the technical problem that the third party account login security is poor in the prior art.
In a first aspect, an embodiment of the present application provides a method for a user to log in, where the method includes:
receiving a third party account login request sent by a client;
judging whether the third party account has a binding relationship;
if yes, logging in a server by using the third-party account;
if not, sending binding prompt information to the client;
receiving an account binding request sent by the client;
determining a user account and establishing a binding relationship between the user account and the third party account; and the user account is used for logging in the server.
In a second aspect, an embodiment of the present application provides a method for a user to log in, including:
responding to a third party account login operation, sending a third party account login request to a server so that the server can conveniently judge whether the third party account has a binding relationship, if so, logging in the server by using the third party account, and if not, generating binding prompt information;
receiving the binding prompt information sent by the server;
outputting the binding prompt information;
responding to account binding operation, sending an account binding request to the server so that the server can determine a user account and establish a binding relationship between the user account and the third party account; and the user account is used for logging in the server.
In a third aspect, an embodiment of the present application provides an apparatus for a user to log in, including:
the first message receiving module is used for receiving a third-party account login request sent by a client;
the first judgment module is used for judging whether the third party account has a binding relationship;
the first account login module is used for logging in a server by using the third party account if the first judgment module has a positive result;
the first message sending module is used for sending binding prompt information to the client if the first judgment module has no result;
the second message receiving module is used for receiving the account binding request sent by the client;
the binding module is used for determining a user account and establishing a binding relationship between the user account and the third party account; and the user account is used for logging in the server.
In a fourth aspect, an embodiment of the present application provides an apparatus for a user to log in, including:
the first message response module is used for responding to the login operation of the third-party account;
a sixth message sending module, configured to send a third party account login request to the server, so that the server can determine whether the third party account has a binding relationship;
a fifth message receiving module, configured to receive the binding prompt message sent by the server;
the first output module is used for outputting the binding prompt message;
the second message response module is used for responding to the account binding operation;
a seventh message sending module, configured to send an account binding request to the server, so that the server determines a user account and establishes a binding relationship between the user account and the third party account; and the user account is used for logging in the server.
In a fifth aspect, an embodiment of the present application provides a server, including a processing component and a storage component;
the storage component stores one or more computer instructions, wherein the one or more computer instructions are for the processing component to invoke execution;
the processing component is to:
receiving a third party account login request sent by a client;
judging whether the third party account has a binding relationship;
if yes, logging in a server by using the third-party account;
if not, sending binding prompt information to the client;
receiving an account binding request sent by the client;
determining a user account and establishing a binding relationship between the user account and the third party account; and the user account is used for logging in the server.
In a sixth aspect, an embodiment of the present application provides a terminal, including a processing component and a storage component;
the storage component stores one or more computer instructions, wherein the one or more computer instructions are for the processing component to invoke execution;
the processing component is to:
responding to a third party account login operation, sending a third party account login request to a server so that the server can conveniently judge whether the third party account has a binding relationship, if so, logging in the server by using the third party account, and if not, generating binding prompt information;
receiving the binding prompt information sent by the server;
outputting the binding prompt information;
responding to account binding operation, sending an account binding request to the server so that the server can determine a user account and establish a binding relationship between the user account and the third party account; and the user account is used for logging in the server.
In the embodiment of the application, a third party account login request sent by a client is received; judging whether the third party account has a binding relationship; if yes, logging in the server by using the third party account; if not, sending binding prompt information to the client; receiving an account binding request sent by the client; determining a user account and establishing a binding relationship between the user account and the third party account; and the user account is used for logging in the server. Whether the third party account can be directly used for logging in the server side is determined by judging whether the third party account and the user account have a binding relationship. Under the condition that the binding relationship does not exist between the user account and the third party account, the user account is determined and the binding relationship is established, so that the third party account can be used for logging in a server side by using the user account with the binding relationship when the third party account is wrong, or the correct third party account information is helped to be retrieved, the condition that the third party account cannot log in due to information error or password error when the third party account logs in the server side is effectively avoided, and the logging safety of the third party account is improved.
These and other aspects of the present application will be more readily apparent from the following description of the embodiments.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative efforts.
FIG. 1 is a flowchart illustrating an embodiment of a user login method provided in the present application;
FIG. 2 is a flowchart illustrating a user login method according to another embodiment of the present application;
FIG. 3 is a schematic structural diagram illustrating an embodiment of a device for user login provided by the present application;
FIG. 4 is a schematic structural diagram of another embodiment of a device for user login provided by the present application;
FIG. 5 is a schematic diagram illustrating an embodiment of a server provided by the present application;
fig. 6 is a schematic structural diagram illustrating an embodiment of a terminal provided in the present application.
Detailed Description
In order to make the technical solutions better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application.
In some of the flows described in the specification and claims of this application and in the above-described figures, a number of operations are included that occur in a particular order, but it should be clearly understood that these operations may be performed out of order or in parallel with the order in which they occur herein, the order of the operations being indicated as 101, 102, etc. merely to distinguish between the various operations, and the order of the operations by themselves is not intended to represent any order of performance. Additionally, the flows may include more or fewer operations, and the operations may be performed sequentially or in parallel. It should be noted that, the descriptions of "first", "second", etc. in this document are used for distinguishing different messages, devices, modules, etc., and do not represent a sequential order, nor limit the types of "first" and "second" to be different.
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Fig. 1 is a flowchart of an embodiment of a user login method provided in an embodiment of the present application, where the method may include the following steps:
101: and receiving a third party account login request sent by the client.
The technical scheme of the embodiment can be executed by the server.
The client side responds to the third party account login operation of the user, and then can send a third party account login request to the server side.
The third-party account may refer to a login account obtained by a user through registration in a third-party system, and the third-party system may refer to any other business system different from the business system formed by the client and the server in the embodiment of the present application.
102: and judging whether the third party account has a binding relationship.
In the embodiment of the application, the judgment process can be realized by calling the check interface by the server, and the check interface of the server receives the third party account and compares the third party account with the account data in the database. If the database has account data which is completely the same as the received third party account, the server side judges that the third party account has a binding relationship; and if the database does not have account data which is completely the same as the received third party account, the server side judges that the third party account does not have the binding relationship.
The account data is third party account data of the bound user account in the database.
The user account may refer to a login account obtained by the server for registering the user.
103: and logging in a server by using the third party account.
And if the server side judges that the third party account has the binding relationship, directly logging in the server side by using the third party account.
104: and sending binding prompt information to the client.
And if the server side judges that the third party account does not have the binding relationship, sending binding prompt information to the client side.
The binding prompt information can prompt the user that the third-party account does not have a binding relationship and login can be realized only by providing the user account.
105: and receiving an account binding request sent by the client.
106: determining a user account and establishing a binding relationship between the user account and the third party account; and the user account is used for logging in the server.
The determination of the user account may have multiple implementation manners:
as an optional manner, the account binding request may be an account registration request, and the determining of the user account may refer to allocating the user account, that is, allocating, by the server, the user account for the user based on the account binding request, and establishing a binding relationship between the user account and a third party account provided by the user.
Optionally, the server may further send the allocated user account to the client, so that the client outputs the user account, and the user can conveniently know the user account, and then, the purpose of logging in the server can be achieved by using the user account. The user account can comprise an account ID, an account password and the like, the server can specifically distribute the account ID for the user, and the password setting prompt information is output through the client, so that the account password is obtained based on a password setting request sent by the user through the client, and the user account is obtained.
As another alternative, the account binding request may include the user account, that is, the user account may be provided by the user, and thus, the determining the user account may include:
and determining the user account included in the account binding request.
Optionally, the user account may include an account ID, an account password, and the like.
The binding relationship between the user account and the third party account is established, that is, the binding relationship can be stored in a database, so that whether the third party account has the binding relationship or not is judged, and the third party account can be known by searching the database.
In this embodiment, the establishment of the binding relationship between the user account and the third party account is implemented by calling a binding interface through a server. And a binding interface of the server receives the user account and the third party account, and integrates data information corresponding to the user account and the third party account, so that the server can determine that the same user logs in and is matched with the same data information no matter the user account or the third party account passes through. The establishment of the binding relationship further improves the security of the third party account login server, and if the third party account is lost carelessly, the third party account can be logged in the server by virtue of the user account which has the binding relationship with the third party account, so that the loss of data information is avoided, or the third party account can be found back by virtue of the user account.
In certain embodiments, the method may further comprise:
and sending third party account login prompt information to the client.
The login prompt information may include a login account selection interface, a user account input box, a third party account input box, and the like.
Optionally, the login account selection interface may include a user account login button, a third party account login button. The user can conveniently and directly click the third-party account login button to select the third-party account login server.
In some embodiments, the user account may refer to a communication account of the user, when the account binding request includes the user account.
The determining a user account and establishing a binding relationship between the user account and the third party account may include:
based on the communication account, sending verification information carrying a verification identifier to the communication account;
receiving user input information sent by the client;
judging whether the user input information is the same as the verification identification;
and if so, taking the communication account as a user account, and establishing a binding relationship between the communication account and the third party account.
The verification information carrying the verification identifier may be digital, alphabetic, or character information.
Optionally, the server may compare the two pieces of information by determining whether the user input information is the same as the verification identifier, and if the numbers, letters, or character information of the two pieces of information are completely the same, the two pieces of information may be determined to be the same.
The communication account may refer to a mobile phone number, for example.
In some embodiments, after determining the user account, the method may further include:
judging whether the user account has a binding relationship;
if so, sending login failure prompt information to the client;
and otherwise, establishing the binding relationship between the user account and the third party account.
The determination of whether the user account has the binding relationship may be implemented by the server invoking another check interface, and the determination of whether the user account has the binding relationship may specifically be a determination of whether the user account has bound to any third party account.
And the other check interface of the server receives the user account and compares the user account with the account in the database. If an account identical to the user account exists in the database and a binding relationship exists between the account and another account, judging that the binding relationship exists between the user account; if the database does not have an account number which is completely the same as the user account number, or the account number does not have a binding relationship with other account numbers, judging that the user account number does not have the binding relationship.
Wherein the account is a user account in the database.
In the process that a user logs in a server, data information corresponding to different user accounts is different, each third-party account can be bound with one user account, whether the user accounts have a binding relationship or not is judged, so that the binding with the user accounts can be realized when different third-party accounts are used for logging in the server, and the situations that a plurality of third-party accounts are bound with the same user account, so that the information is disordered and the data is wrong are avoided.
Alternatively, the login failure prompt message may include a text description message and a pattern message. The descriptive information may be suggestive information indicating that the user account is bound.
In some embodiments, if it is determined that the user account has a binding relationship, the method may further include:
sending account login prompt information to the client;
receiving a user account login request sent by the client;
and logging in the server by using the user account.
The account login prompt information can be a user account input box, a password input box and a user account login button.
In some embodiments, if it is determined that the user account has a binding relationship, the method may further include:
sending unbinding prompt information to the client;
and receiving a unbinding prompt request sent by the client, canceling the binding relationship of the user account, and reestablishing the binding relationship between the user account and the third party account.
Wherein, the unbinding prompt message can comprise a word description message and an unbinding button. The descriptive information may be suggestive information for releasing the binding of the third party account.
In the embodiment of the application, the unbinding process is realized by calling an unbinding interface by a server. And a binding-removing interface of the server receives the user account, calls account data which is completely the same as the user account from the database, and cancels the binding relationship between the account data and other account data in the database.
The binding relationship is released, so that the third party account and the user account are in one-to-one correspondence, and the inconvenience to the user caused by disordered and dispersed data information is avoided.
And the server calls a binding interface to reestablish the binding relationship between the user account and the third party account.
As another embodiment, as illustrated in fig. 2, the present application further provides an information processing method, which may include the following steps:
201: and responding to the third party account login operation, and sending a third party account login request to the server.
The technical scheme of the embodiment can be executed by the client.
The third party account login request may include third party account authorization information. The authorization information can refer to the information of the head portrait of the third-party account user and the information of the communication name of the third-party account user, which can be displayed in a public way.
In this embodiment, the sending of the third party account login request to the server is convenient for the server to determine whether the third party account has a binding relationship.
The specific manner of determining whether the third party account has the binding relationship by the server may be as described in the embodiment shown in fig. 1, and is not described herein again.
If the third party account is judged to have the binding relationship by the server, logging in the server by using the third party account, otherwise, generating binding prompt information.
202: and receiving the binding prompt information sent by the server.
The binding prompt information is generated after the server judges that the third-party account has the binding relationship.
203: and outputting the binding prompt information.
204: and responding to the account binding operation, and sending an account binding request to the server.
The account binding operation is triggered after the user receives the binding prompt message.
In this embodiment, the sending of the account binding request to the server is convenient for the server to determine a user account and establish a binding relationship between the user account and the third party account; and the user account is used for logging in the server. The establishment of the binding relationship between the third party and the third party promotes the security of third party login.
The specific manner of determining the user account and establishing the binding relationship between the user account and the third party account by the server may be as described in the embodiment shown in fig. 1, and is not described herein again.
In certain embodiments, the method may further comprise:
receiving third party account login prompt information sent by the server;
and outputting the third party account login prompt information.
The third-party account login prompt information is output, so that the user can independently select a login mode when logging in the server, and the problems of complex operation and single mode when logging in the server by using the user account are solved.
In some embodiments, in the case of the user account included in the account binding request, the user account may refer to a communication account of the user;
the sending an account binding request to the server in response to the account binding operation may further include:
responding to the account binding operation, and determining a communication account input by a user;
and sending an account binding request comprising the communication account to the server.
And determining a communication account input by a user, namely determining the user account included in the account binding request.
In certain embodiments, the method may further comprise:
outputting verification prompt information;
determining user input information in response to a user input operation;
sending the user input information to the server so that the server can verify whether the user input information is the same as a verification identifier, if so, taking the communication account as a user account and establishing a binding relationship between the communication account and the third party account; the verification identification is contained in a verification message sent by the server to the communication account.
The verification prompt message may be a message prompting the user to input verification information.
Wherein, the user input operation is the operation performed by the user input information; the user input information may refer to authentication information which is received by the user based on the communication account and is sent by the server and carries an authentication identifier.
In certain embodiments, the method may further comprise:
receiving login failure prompt information sent by the server; the login failure prompt message is sent when the server judges that the user account has a binding relationship;
and outputting the login failure prompt information.
The output of the login failure prompt message is beneficial to helping a user to determine that the user account has a binding relationship and cannot directly log in the server by using the third party account.
In some embodiments, if the server determines that the user account has a binding relationship, the method may further include:
receiving account login prompt information sent by the server;
outputting the account login prompt information;
and responding to the user account login operation, and sending a user account login request to the server so as to conveniently login the server by using the user account.
And outputting the account login prompt information to prompt the user to log in the server by using the user account.
The user account login operation may refer to an operation in which the user inputs a user account and a password based on the account login prompt information.
In some embodiments, if the server determines that the user account has a binding relationship, the method may further include:
receiving unbinding prompt information sent by the server;
outputting the unbinding prompt information;
and responding to a user unbinding operation request, and sending unbinding confirmation information to the server so as to facilitate the server to release the binding relationship of the user account and reestablish the binding relationship between the user account and the third party account.
And outputting the unbinding prompt message, which is favorable for prompting the user to release the binding relationship of the user account.
The user unbinding operation request may refer to an operation performed by the user to request to release the binding relationship of the user account based on the unbinding prompt information.
The specific manner of releasing the binding relationship of the user account by the server may be as described in the embodiment shown in fig. 1, and is not described herein again.
Fig. 3 is a schematic structural diagram of an embodiment of an apparatus for user login provided in the present application, where the apparatus may include:
a first message receiving module 301, configured to receive a third party account login request sent by a client;
a first determining module 302, configured to determine whether the third party account is bound to a user account;
a first account login module 303, configured to log in a server by using the third party account if the result of the first determination module is yes;
a first message sending module 304, configured to send a binding prompt message to the client if the first determining module result is negative;
a second message receiving module 305, configured to receive an account binding request sent by the client;
a binding module 306, configured to determine a user account, and establish a binding relationship between the user account and the third party account; and the user account is used for logging in the server.
In some embodiments, the apparatus may further comprise:
and the second message sending module is used for sending third party account login prompt information to the client.
In some embodiments, the binding module is specifically configured to determine the user account included in the account binding request, and establish a binding relationship between the user account and the third party account.
In some embodiments, the user account is a communication account; the binding module comprises:
a first message sending unit, configured to send verification information carrying a verification identifier to the communication account;
the first message receiving unit is used for receiving user input information sent by the client;
a first judgment unit configured to judge whether the user input information is the same as the verification identifier;
a binding unit; and the third-party account is used for establishing a binding relationship between the communication account and the third-party account if the first judgment unit judges that the communication account is the user account.
In some embodiments, the apparatus may further comprise:
the second judgment module is used for judging whether the user account has a binding relationship;
and the third message sending module is used for sending login failure prompt information to the client if the result of the second judging module is positive.
In some embodiments, the apparatus may further comprise:
the fourth message sending module is used for sending account login prompt information to the client;
the third message receiving module is used for receiving a user account login request sent by the client;
and the second account login module is used for logging in the server by using the user account.
In some embodiments, the apparatus may further comprise:
a fifth message sending module, configured to send unbinding prompt information to the client;
the fourth message receiving module is used for receiving unbinding confirmation information sent by the client;
and the unbinding module is used for canceling the binding relationship of the user account.
The user login apparatus shown in fig. 3 may execute the user login method shown in the embodiment shown in fig. 1, and the implementation principle and the technical effect are not described again. The specific manner in which each module and unit of the user login device in the above embodiments perform operations has been described in detail in the embodiments related to the method, and will not be described in detail here.
Fig. 4 is a schematic structural diagram of another embodiment of an apparatus for user login provided in the present application, where the apparatus may include:
a first message response module 401, configured to respond to a third party account login operation;
a sixth message sending module 402, configured to send a third party account login request to the server, so that the server can determine whether the third party account has a binding relationship;
a fifth message receiving module 403, configured to receive the binding prompt message sent by the server;
a first output module 404, configured to output the binding prompt message;
a second message response module 405, configured to respond to the account binding operation;
a seventh message sending module 406, configured to send an account binding request to the server, so that the server determines a user account and establishes a binding relationship between the user account and the third party account; and the user account is used for logging in the server.
In some embodiments, the apparatus may further comprise:
the sixth message receiving module is used for receiving third party account login prompt information sent by the server;
and the second output module is used for outputting the third party account login prompt information.
In some embodiments, the account binding request includes the user account, the user account is a communication account, and the second message response module includes:
the first message response unit is used for responding to the account binding operation;
the first determination unit is used for determining the communication account input by the user.
In some embodiments, the apparatus may further comprise:
the third output module is used for outputting verification prompt information;
the third message response module is used for responding to the input operation of the user and determining the input information of the user;
an eighth message sending module, configured to send the user input information to the server, so that the server verifies whether the user input information is the same as the verification identifier.
In some embodiments, the apparatus may further comprise:
a seventh message receiving module, configured to receive a login failure prompt message sent by the server;
and the fourth output module is used for outputting the login failure prompt message.
In some embodiments, the apparatus may further comprise:
the eighth message receiving module is used for receiving account login prompt information sent by the server;
the fifth output module is used for outputting the account login prompt information;
the fourth message response module is used for responding to the login operation of the user account;
and the ninth message sending module is used for sending a user account login request to the server so as to conveniently login the server by using the user account.
In some embodiments, the apparatus may further comprise:
a ninth message receiving module, configured to receive unbinding prompt information sent by the server;
the sixth output module is used for outputting the unbinding prompt message;
the fifth message response module is used for responding to the user unbinding operation request;
and the tenth message sending module is used for sending unbinding confirmation information to the server so that the server can conveniently release the binding relationship of the user account.
The user login apparatus shown in fig. 4 may execute the user login method shown in the embodiment shown in fig. 2, and the implementation principle and the technical effect are not described again. The specific manner in which each module and unit of the user login device in the above embodiments perform operations has been described in detail in the embodiments related to the method, and will not be described in detail here.
In one possible design, the apparatus for user login of the embodiment shown in fig. 3 may be implemented as a server, which may include a storage component 501 and a processing component 502 as shown in fig. 5;
the storage component stores one or more computer instructions, wherein the one or more computer instructions are for execution invoked by the processing component.
The processing component is to:
receiving a third party account login request sent by a client;
judging whether the third party account has a binding relationship;
if yes, logging in a server by using the third-party account;
if not, sending binding prompt information to the client;
receiving an account binding request sent by the client;
determining a user account and establishing a binding relationship between the user account and the third party account; and the user account is used for logging in the server.
Wherein the processing components may include one or more processors executing computer instructions to perform all or part of the steps of the above-described method. Of course, the processing elements may also be implemented as one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, micro-controllers, microprocessors or other electronic components configured to perform the above-described methods.
The storage component is configured to store various types of data to support operations in the server. The memory components may be implemented by any type or combination of volatile or non-volatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.
Of course, the server may of course also comprise other components, such as input/output interfaces, communication components, etc.
The input/output interface provides an interface between the processing components and peripheral interface modules, which may be output devices, input devices, etc.
The communication component is configured to facilitate wired or wireless communication between the server and other devices, and the like.
An embodiment of the present application further provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a computer, the method for user login in the embodiment shown in fig. 1 may be implemented.
In one possible design, the apparatus for user login of the embodiment shown in fig. 4 may be implemented as a terminal, which may include a storage component 601 and a processing component 602 as shown in fig. 6;
the storage component stores one or more computer instructions, wherein the one or more computer instructions are for execution invoked by the processing component.
The processing component is to:
responding to a third party account login operation, sending a third party account login request to a server so that the server can conveniently judge whether the third party account has a binding relationship, if so, logging in the server by using the third party account, and if not, generating binding prompt information;
receiving the binding prompt information sent by the server;
outputting the binding prompt information;
responding to account binding operation, sending an account binding request to the server so that the server can determine a user account and establish a binding relationship between the user account and the third party account; and the user account is used for logging in the server.
Wherein the processing components may include one or more processors executing computer instructions to perform all or part of the steps of the above-described method. Of course, the processing elements may also be implemented as one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, micro-controllers, microprocessors or other electronic components configured to perform the above-described methods.
The storage component is configured to store various types of data to support operations in the server. The memory components may be implemented by any type or combination of volatile or non-volatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.
Of course, the terminal may of course also comprise other components, such as input/output interfaces, communication components, etc.
The input/output interface provides an interface between the processing components and peripheral interface modules, which may be output devices, input devices, etc.
The communication component is configured to facilitate wired or wireless communication between the terminal and other devices, and the like.
An embodiment of the present application further provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a computer, the method for user login in the embodiment shown in fig. 2 may be implemented.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware. With this understanding in mind, the above-described technical solutions may be embodied in the form of a software product, which can be stored in a computer-readable storage medium such as ROM/RAM, magnetic disk, optical disk, etc., and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the embodiments or some parts of the embodiments.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.
Claims (16)
1. A method for logging in a user is characterized by comprising the following steps:
receiving a third party account login request sent by a client;
judging whether the third party account has a binding relationship;
if yes, logging in a server by using the third-party account;
if not, sending binding prompt information to the client;
receiving an account binding request sent by the client;
determining a user account and establishing a binding relationship between the user account and the third party account; and the user account is used for logging in the server.
2. The method according to claim 1, wherein before receiving the third party account login request sent by the client, the method further comprises:
and sending third party account login prompt information to the client.
3. The method of claim 1, wherein determining the user account comprises:
and determining the user account included in the account binding request.
4. The method of claim 3, wherein the user account is a communication account;
the determining the user account and establishing the binding relationship between the user account and the third party account includes:
based on the communication account, sending verification information carrying a verification identifier to the communication account;
receiving user input information sent by the client;
judging whether the user input information is the same as the verification identification;
and if so, taking the communication account as a user account, and establishing a binding relationship between the communication account and the third party account.
5. The method of claim 3, further comprising:
judging whether the user account has a binding relationship;
and if so, sending login failure prompt information to the client.
6. The method of claim 5, further comprising:
sending user account login prompt information to the client;
receiving a user account login request sent by the client;
and logging in the server by using the user account.
7. The method of claim 6, further comprising:
sending unbinding prompt information to the client;
and receiving unbinding confirmation information sent by the client, canceling the binding relationship of the user account, and reestablishing the binding relationship between the user account and the third party account.
8. A method for logging in a user is characterized by comprising the following steps:
responding to a third party account login operation, sending a third party account login request to a server so that the server can conveniently judge whether the third party account has a binding relationship, if so, logging in the server by using the third party account, and if not, generating binding prompt information;
receiving the binding prompt information sent by the server;
outputting the binding prompt information;
responding to account binding operation, sending an account binding request to the server so that the server can determine a user account and establish a binding relationship between the user account and the third party account; and the user account is used for logging in the server.
9. The method of claim 8, wherein prior to responding to the third party account login operation, the method further comprises:
receiving third party account login prompt information sent by the server;
and outputting the third party account login prompt information.
10. The method of claim 8, wherein the account binding request includes the user account, and wherein the user account is a communication account;
the sending an account binding request to the server in response to the account binding operation includes:
responding to the account binding operation, and determining a communication account input by a user;
and sending an account binding request comprising the communication account to the server.
11. The method of claim 10, further comprising:
outputting verification prompt information;
determining user input information in response to a user input operation;
sending the user input information to the server so that the server can verify whether the user input information is the same as a verification identifier, if so, taking the communication account as a user account and establishing a binding relationship between the communication account and the third party account; the verification identification is contained in a verification message sent by the server to the communication account.
12. The method of claim 8, further comprising:
receiving login failure prompt information sent by the server; the login failure prompt message is sent when the server judges that the user account has a binding relationship;
and outputting the login failure prompt information.
13. The method of claim 12, further comprising:
receiving account login prompt information sent by the server;
outputting the account login prompt information;
and responding to the user account login operation, and sending a user account login request to the server so as to conveniently login the server by using the user account.
14. The method of claim 13, further comprising:
receiving unbinding prompt information sent by the server;
outputting the unbinding prompt information;
and responding to a user unbinding operation request, and sending unbinding confirmation information to the server so as to facilitate the server to release the binding relationship of the user account and reestablish the binding relationship between the user account and the third party account.
15. An apparatus for a user to log in, comprising:
the first message receiving module is used for receiving a third-party account login request sent by a client;
the first judgment module is used for judging whether the third party account has a binding relationship;
the first account login module is used for logging in a server by using the third party account if the first judgment module has a positive result;
the first message sending module is used for sending binding prompt information to the client if the first judgment module has no result;
the second message receiving module is used for receiving the account binding request sent by the client;
the binding module is used for determining a user account and establishing a binding relationship between the user account and the third party account; and the user account is used for logging in the server.
16. An apparatus for a user to log in, comprising:
the first message response module is used for responding to the login operation of the third-party account;
a sixth message sending module, configured to send a third party account login request to the server, so that the server can determine whether the third party account has a binding relationship;
a fifth message receiving module, configured to receive the binding prompt message sent by the server;
the first output module is used for outputting the binding prompt message;
the second message response module is used for responding to the account binding operation;
a seventh message sending module, configured to send an account binding request to the server, so that the server determines a user account and establishes a binding relationship between the user account and the third party account; and the user account is used for logging in the server.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910288984.0A CN111817999A (en) | 2019-04-11 | 2019-04-11 | User login method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910288984.0A CN111817999A (en) | 2019-04-11 | 2019-04-11 | User login method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111817999A true CN111817999A (en) | 2020-10-23 |
Family
ID=72844349
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910288984.0A Pending CN111817999A (en) | 2019-04-11 | 2019-04-11 | User login method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111817999A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112948804A (en) * | 2021-03-05 | 2021-06-11 | 腾讯科技（深圳）有限公司 | Program control method, device and computer readable storage medium |
| CN113378221A (en) * | 2021-06-11 | 2021-09-10 | 上海妙一生物科技有限公司 | Account information processing method and device |
| CN114172713A (en) * | 2021-12-02 | 2022-03-11 | 北京金山云网络技术有限公司 | Login method, login device, electronic equipment and storage medium |
| US11736479B2 (en) | 2020-09-28 | 2023-08-22 | Alipay Labs (singapore) Pte. Ltd. | Binding server accounts |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104753943A (en) * | 2015-03-30 | 2015-07-01 | 努比亚技术有限公司 | Method and device for log-in control of third-party account |
| CN105306733A (en) * | 2015-11-13 | 2016-02-03 | 深圳正品创想科技有限公司 | Third-party login mobile phone number binding method based on mobile phone APP |
| US20160112419A1 (en) * | 2013-06-25 | 2016-04-21 | Huawei Technologies Co., Ltd. | Account Login Method, Device, and System |
-
2019
- 2019-04-11 CN CN201910288984.0A patent/CN111817999A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160112419A1 (en) * | 2013-06-25 | 2016-04-21 | Huawei Technologies Co., Ltd. | Account Login Method, Device, and System |
| CN104753943A (en) * | 2015-03-30 | 2015-07-01 | 努比亚技术有限公司 | Method and device for log-in control of third-party account |
| CN105306733A (en) * | 2015-11-13 | 2016-02-03 | 深圳正品创想科技有限公司 | Third-party login mobile phone number binding method based on mobile phone APP |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11736479B2 (en) | 2020-09-28 | 2023-08-22 | Alipay Labs (singapore) Pte. Ltd. | Binding server accounts |
| CN112948804A (en) * | 2021-03-05 | 2021-06-11 | 腾讯科技（深圳）有限公司 | Program control method, device and computer readable storage medium |
| CN113378221A (en) * | 2021-06-11 | 2021-09-10 | 上海妙一生物科技有限公司 | Account information processing method and device |
| CN113378221B (en) * | 2021-06-11 | 2022-09-23 | 上海妙一生物科技有限公司 | Account information processing method and device |
| CN114172713A (en) * | 2021-12-02 | 2022-03-11 | 北京金山云网络技术有限公司 | Login method, login device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111817999A (en) | User login method and device | |
| CN105592065B (en) | A kind of Website logging method and its login system based on SMS | |
| JP5536082B2 (en) | Managing user authentication | |
| CN109787976B (en) | Information updating method and device, computer equipment and storage medium | |
| CN107249004B (en) | Identity authentication method, device and client | |
| US9009793B2 (en) | Dynamic pin dual factor authentication using mobile device | |
| CN105337997B (en) | Login method of application client and related equipment | |
| CN102594817A (en) | Password agent method, user terminal equipment and password agent server | |
| CN105989485B (en) | Service management method and device | |
| CN111064749B (en) | Network connection method, device and storage medium | |
| CN110247897B (en) | System login method, device, gateway and computer readable storage medium | |
| WO2015196817A1 (en) | Account number login method, apparatus and system | |
| CN113824628B (en) | User identity authentication method, device, server and storage medium based on IM | |
| CN113179282A (en) | Method and device for merging account numbers and server | |
| CN106209569B (en) | Authentication method and device for enterprise instant messaging | |
| CN104462934B (en) | A kind of information processing method and electronic equipment | |
| CN106203021A (en) | The application login method of a kind of many certification modes integration and system | |
| CN107872446B (en) | Communication account management method and device and server | |
| CN108900525B (en) | Processing method and device for verification code request | |
| CN108769059B (en) | Verification method, device, medium and computing equipment | |
| CN110351296B (en) | Application login method and device and related equipment thereof | |
| CN112165473A (en) | Method, device and medium for detecting random account password reset logic loophole | |
| CN111859320A (en) | Cross-system login-free method, device, equipment and readable storage medium | |
| CN109040056B (en) | User verification method based on server | |
| CN105577621B (en) | Business operation verification method, device and system |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20201023 |