CN111541546B - Multi-platform login method, device, equipment and readable medium - Google Patents
Multi-platform login method, device, equipment and readable medium Download PDFInfo
- Publication number
- CN111541546B CN111541546B CN202010332351.8A CN202010332351A CN111541546B CN 111541546 B CN111541546 B CN 111541546B CN 202010332351 A CN202010332351 A CN 202010332351A CN 111541546 B CN111541546 B CN 111541546B
- Authority
- CN
- China
- Prior art keywords
- account
- target
- party
- information
- mobile phone
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- 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
- 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/0807—Network architectures or network communication protocols for network security for authentication of entities using tickets, e.g. Kerberos
-
- 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
Abstract
The embodiment of the invention discloses a multi-platform login method, a multi-platform login device, a multi-platform login equipment and a readable medium, wherein the method comprises the following steps: acquiring a login request input by a user, and determining target third party account information according to the login request; searching a standard account matched with the target third-party account information in a preset account database to serve as a target account, acquiring an account information table corresponding to the target account to serve as a target account information table, and determining a target account identifier according to the target account information table; and determining a target token corresponding to the login request, generating corresponding prompt information according to the target account identifier and the target token, and returning the prompt information to the user. The invention improves the login efficiency and user experience of the multi-platform user.
Description
Technical Field
The invention relates to the field of computer data processing, in particular to a multi-platform login method, a multi-platform login device, multi-platform login equipment and a readable medium.
Background
With the increasing popularity of internet applications, enterprises often develop internet-based applications to address the actual needs of users. The problem of storage and management of the account identity corresponding to the user needs to be solved for each large internet application. In order to achieve a better account login experience, internet developers usually provide an entry for a third-party platform (WeChat login, QQ login, mobile phone number) to log in to achieve multi-platform-based login of users.
In the prior art, different from the current application in which account registration and login are adopted to realize account identity, a plurality of third party platforms commonly used by users are generally set for login of a third party login system, so that data structures need to be added or adjusted again when other third party platforms need to be accessed. That is, basically, a third-party platform needs to be developed again from an application layer and a data storage layer, so that maintenance and development cost for realizing multi-platform login is high, and login efficiency is low.
Disclosure of Invention
In view of the foregoing, it is desirable to provide a multi-platform login method, apparatus, computer device and readable medium.
A multi-platform login method is characterized by comprising the following steps:
acquiring a login request input by a user, and determining target third party account information according to the login request;
searching a standard account matched with the target third-party account information in a preset account database to serve as a target account, acquiring an account information table corresponding to the target account to serve as a target account information table, and determining a target account identifier according to the target account information table;
and determining a target token corresponding to the login request, generating corresponding prompt information according to the target account identifier and the target token, and returning the prompt information to the user.
Further, the target third party account information includes at least one of a third party platform class, a third party account class, and/or a third party account identification,
the account database comprises an account information table corresponding to at least one standard account,
the account information table comprises at least one item of standard account identification, associated third party account information, associated creation time, current associated state, associated state update time and/or associated third party account remark information, wherein the associated third party account information comprises an associated third party platform type, an associated third party account type and an associated third party account identification.
Further, searching a standard account matched with the target third party account in a preset account database as a target account, wherein the method comprises the following steps:
searching the account database for associated third party account information matched with the target third party account;
and under the condition that the associated third party account information is matched, determining the target account according to the account information table corresponding to the matched associated third party account information.
Further, the account information table further includes an associated mobile phone number,
after matching the associated third party account information of the target third party account in the account database, further comprising:
under the condition of failed matching, displaying a preset mobile phone verification interface through the preset device, receiving mobile phone verification information input on the mobile phone verification interface, and verifying according to the mobile phone verification information;
and under the condition that the verification is passed, determining a target mobile phone number corresponding to the mobile phone verification information, searching for an associated mobile phone number matched with the target mobile phone number in the account database, and under the condition that the searching is successful, taking a standard account identifier corresponding to the searched associated mobile phone number as the target account identifier.
Furthermore, after the standard account identifier corresponding to the found associated mobile phone number is used as the target account identifier, the method further includes:
and associating the target account identification with the target third party account information.
Further, after searching the associated mobile phone number matched with the target mobile phone number in the account database, the method further includes:
under the condition of search failure, determining an account identifier as the target account identifier, and associating the target mobile phone number with the target account identifier;
adding the target account identification to the account database.
Further, after the authentication is performed according to the mobile phone authentication information, the method further includes:
and under the condition of failure in verification, displaying a preset registration interface through a preset device, acquiring account registration information input on the registration interface, determining a target account identifier and the associated third party account information according to the account registration information, and storing the target account identifier and the associated third party account information in the preset account database.
A multi-platform login device, the device comprising:
an acquisition unit: the system comprises a server, a server and a server, wherein the server is used for acquiring a login request input by a user and determining target third party account information according to the login request;
a matching unit: the system comprises a target account database, a target account identification table and a target account identification table, wherein the target account identification table is used for identifying a target account according to the target account information;
a prompt unit: and the system is used for determining a target token corresponding to the login request, generating corresponding prompt information according to the target account identifier and the target token, and returning the prompt information to the user.
Wherein the content of the first and second substances,
a computer device comprising a memory and a processor, the memory storing a computer program that, when executed by the processor, causes the processor to perform the steps of:
acquiring a login request input by a user, and determining target third party account information according to the login request;
searching a standard account matched with the target third-party account information in a preset account database to serve as a target account, acquiring an account information table corresponding to the target account to serve as a target account information table, and determining a target account identifier according to the target account information table;
and determining a target token corresponding to the login request, generating corresponding prompt information according to the target account identifier and the target token, and returning the prompt information to the user.
Further, the target third party account information includes at least one of a third party platform class, a third party account class, and/or a third party account identification,
the account database comprises an account information table corresponding to at least one standard account,
the account information table comprises at least one item of standard account identification, associated third party account information, associated creation time, current associated state, associated state update time and/or associated third party account remark information, wherein the associated third party account information comprises an associated third party platform type, an associated third party account type and an associated third party account identification.
Further, searching a standard account matched with the target third party account in a preset account database as a target account, wherein the method comprises the following steps:
searching the account database for associated third party account information matched with the target third party account;
and under the condition that the associated third party account information is matched, determining the target account according to the account information table corresponding to the matched associated third party account information.
Further, the account information table further includes an associated mobile phone number,
after matching the associated third party account information of the target third party account in the account database, further comprising:
under the condition of failed matching, displaying a preset mobile phone verification interface through the preset device, receiving mobile phone verification information input on the mobile phone verification interface, and verifying according to the mobile phone verification information;
and under the condition that the verification is passed, determining a target mobile phone number corresponding to the mobile phone verification information, searching for an associated mobile phone number matched with the target mobile phone number in the account database, and under the condition that the searching is successful, taking a standard account identifier corresponding to the searched associated mobile phone number as the target account identifier.
Furthermore, after the standard account identifier corresponding to the found associated mobile phone number is used as the target account identifier, the method further includes:
and associating the target account identification with the target third party account information.
Further, after searching the associated mobile phone number matched with the target mobile phone number in the account database, the method further includes:
under the condition of search failure, determining an account identifier as the target account identifier, and associating the target mobile phone number with the target account identifier;
adding the target account identification to the account database.
Further, after the authentication is performed according to the mobile phone authentication information, the method further includes:
and under the condition of failure in verification, displaying a preset registration interface through a preset device, acquiring account registration information input on the registration interface, determining a target account identifier and the associated third party account information according to the account registration information, and storing the target account identifier and the associated third party account information in the preset account database.
A computer-readable storage medium storing a computer program which, when executed by a processor, causes the processor to perform the steps of:
acquiring a login request input by a user, and determining target third party account information according to the login request;
searching a standard account matched with the target third-party account information in a preset account database to serve as a target account, acquiring an account information table corresponding to the target account to serve as a target account information table, and determining a target account identifier according to the target account information table;
and determining a target token corresponding to the login request, generating corresponding prompt information according to the target account identifier and the target token, and returning the prompt information to the user.
Further, the target third party account information includes at least one of a third party platform class, a third party account class, and/or a third party account identification,
the account database comprises an account information table corresponding to at least one standard account,
the account information table comprises at least one item of standard account identification, associated third party account information, associated creation time, current associated state, associated state update time and/or associated third party account remark information, wherein the associated third party account information comprises an associated third party platform type, an associated third party account type and an associated third party account identification.
Further, searching a standard account matched with the target third party account in a preset account database as a target account, wherein the method comprises the following steps:
searching the account database for associated third party account information matched with the target third party account;
and under the condition that the associated third party account information is matched, determining the target account according to the account information table corresponding to the matched associated third party account information.
Further, the account information table further includes an associated mobile phone number,
after matching the associated third party account information of the target third party account in the account database, further comprising:
under the condition of failed matching, displaying a preset mobile phone verification interface through the preset device, receiving mobile phone verification information input on the mobile phone verification interface, and verifying according to the mobile phone verification information;
and under the condition that the verification is passed, determining a target mobile phone number corresponding to the mobile phone verification information, searching for an associated mobile phone number matched with the target mobile phone number in the account database, and under the condition that the searching is successful, taking a standard account identifier corresponding to the searched associated mobile phone number as the target account identifier.
Furthermore, after the standard account identifier corresponding to the found associated mobile phone number is used as the target account identifier, the method further includes:
and associating the target account identification with the target third party account information.
Further, after searching the associated mobile phone number matched with the target mobile phone number in the account database, the method further includes:
under the condition of search failure, determining an account identifier as the target account identifier, and associating the target mobile phone number with the target account identifier;
adding the target account identification to the account database.
Further, after the authentication is performed according to the mobile phone authentication information, the method further includes:
and under the condition of failure in verification, displaying a preset registration interface through a preset device, acquiring account registration information input on the registration interface, determining a target account identifier and the associated third party account information according to the account registration information, and storing the target account identifier and the associated third party account information in the preset account database.
In the embodiment of the invention, a login request input by a user is firstly acquired, target third party account information is determined according to the login request, a standard account matched with the target third party account information is searched in a preset account database to be used as a target account, an account information table corresponding to the target account is acquired to be used as a target account information table, a target account identifier is determined according to the target account information table, a target token corresponding to the login request is finally determined, and corresponding prompt information is generated according to the target account identifier and the target token and returned to the user.
Therefore, compared with the problems of low multi-platform login efficiency and high maintenance cost caused by the fact that a new third-party platform needs to be accessed when multi-platform login is realized in the prior art and the data structure needs to be redeveloped from an application layer and a data storage layer, the invention has the advantages that a plurality of third-party accounts corresponding to the same user correspond to one standard account in the preset account database, and an account information table is established for each standard account so as to store the related information (such as login platform type, login identity information type and the like) of the associated third-party platform, so that when each new third party is added, the related information of the corresponding third-party platform is added to the account information table of the standard account corresponding to the user, and the processing efficiency of multi-platform login is improved.
Drawings
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, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Wherein:
FIG. 1 illustrates a flow diagram of a method for multi-platform login in one embodiment;
FIG. 2 illustrates a flow diagram for determining a target account in one embodiment;
FIG. 3 illustrates a flow diagram for determining an associated phone number for a target standard account in one embodiment;
FIG. 4 illustrates a flow diagram for operation in the event of handset authentication failure in one embodiment;
FIG. 5 is a block diagram that illustrates the architecture of a multi-platform logon device in one embodiment;
FIG. 6 is a diagram illustrating an internal structure of a computer device in one embodiment.
Detailed Description
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 only a part of the embodiments of the present invention, 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 invention.
The invention provides a multi-platform login method, and in one embodiment, the invention can be based on a computer processing device, such as a mobile phone, a computer and the like.
Referring to fig. 1, an embodiment of the present invention provides a multi-platform login method.
FIG. 1 shows a flow diagram of a method for multi-platform login in one embodiment. The multi-platform login method at least comprises the steps S1022 to S1026 shown in fig. 1, which are described in detail as follows:
in step S1022, a login request input by the user is obtained, and the target third party account information is determined according to the login request.
For example, the login request here may be input by a user "lie four" by opening a video viewing application such as "english classroom" on his mobile phone, in a preset login interface included in the application. Specifically, after the user "lie four" opens the application of "english minor class", it is different from a method of performing verification login by inputting a unique account and a corresponding password acquired when registering an application account number of "english minor class", and it is possible that "lie four" does not register "english minor class" or does not want to log in a manner of inputting information one by one, "lie four" selects a preset third party login entry included in a login interface, and specifically may be an icon list showing a plurality of selectable third party applications.
Still further, the target third party account information herein may include at least one of a third party platform class, a third party account class, and/or a third party account identification.
If the third-party application QQ is selected to log in the icon list through the third-party application QQ, the system jumps to a preset authorization interface corresponding to the QQ, then obtains authorization information input by the third-party application QQ in the authorization interface, and if the authorization information meets preset conditions (such as meaning authorization), the third-party application QQ returns an authorization instruction to a target application based on the invention, namely an English lesson, and then obtains a third-party platform type (recorded as the QQ), a third-party account type (recorded as the QQ number) and/or a third-party account identifier (recorded as the QQ number) corresponding to the third-party application QQ as target third-party account information.
First, the above parameters are explained, and the third party platform category refers to unique information for recording the third party platform and distinguishing from other platforms, and may be generally the name of the third party platform, such as common "wechat", "panning", "Google account", "QQ", and the like. The third-party account type refers to a representation (distinction) manner for the User identity corresponding to the third party, for example, the third-party account type corresponding to the "Google account" is a Google mailbox address, the third-party account type corresponding to the "Wechat" is a UID (i.e., User Identification), and the third-party account type corresponding to the "Taobao" is a mobile phone number.
The function of acquiring the parameters related to the third party account is as follows: in practical applications, different third-party platforms are different in the recording and verification modes of account information, and in order to achieve quick access and process login requests from various types of third-party platforms, it is necessary to establish parameters that may need to be verified and recorded when a third-party application is called to log in (for example, from which third-party application the request comes, what form the login identity of the third-party application represents), so that login information of various platforms is uniformly stored and managed.
In step S1024, a standard account matched with the target third party account information is searched in a preset account database to serve as a target account, an account information table corresponding to the target account is obtained to serve as a target account information table, and a target account identifier is determined according to the target account information table.
It should be noted that, the account database herein includes an account information table corresponding to at least one standard account.
Each account information table may include at least one of standard account identification, associated third party account information, associated creation time, current associated status, associated status update time, and/or associated third party account remark information.
It should be noted that the standard account id is unique, that is, one account information table corresponds to only one unique standard account id, that is, the standard account id is an id index for distinguishing and recording different account information tables.
Furthermore, the information related to the third party account may further include a type related to the third party platform, a type related to the third party account, and an identifier related to the third party account.
For example, for a standard user (denoted as X) in the account database, whose corresponding standard user ID is ID8689480, the associated third-party account information may be as follows: associating third party platform categories: "Taobao", "WeChat", associated third party account category "Mobile Phone number", "WeChat UID", associated third party account identification "1380000000010", "abc 1990".
That is, each standard account may be associated with a plurality of different third party platforms, specifically, managed in an application scenario, i.e., managed by each application used by one user.
The account information table established for each standard account is a universal data structure, namely, accounts of all platforms related to a certain user are related to a standard account which is stored in the system and uniquely corresponds to the user in a many-to-one mode, so that multi-platform account fusion is realized, original application user information in each third-party application is conveniently transplanted to the system, and unified storage and management are performed.
Furthermore, when it is detected that a user corresponding to a standard user submits previously unassociated third-party platform information (for example, a new third-party application is authorized to log in), only the account related information on the third-party platform needs to be acquired as target third-party account information, and then the associated third-party account in the previous step is directly updated in the account information table according to the target third-party account information, so that the user can log in on a new multi-platform, and thus, the user information of the multi-platform account can be uniformly stored and managed without changing a data structure.
In conjunction with the above description of the contents and operation of the account information table, the specific target account determination process may further include steps S1032-S1034 shown in fig. 2. FIG. 2 illustrates a flow diagram for determining a target account in one embodiment.
In step S1032, the account database is searched for associated third party account information matching the target third party account.
Continuing with the example in the foregoing step, for a standard user (denoted as X) in the account database, whose corresponding standard user identifier is ID8689480, the associated third-party account information may be as follows: associated third party platform category 1: "Taobao", the corresponding associated third party account type being "mobile phone number", the corresponding associated third party account identification being "1380000000010"; associated third party platform category 2: the "WeChat", the corresponding associated third party account category is "WeChat UID", and the corresponding associated third party account identification is "abc 1990".
In step S1034, in the case that the associated third party account information is matched, the target account is determined according to the account information table corresponding to the matched associated third party account information.
In one particular embodiment, the target third party account information herein may be as follows: target third party platform category: "WeChat", target third party account category "WeChat UID", target third party account identification "abc 1990".
Therefore, the associated third party account information of the standard user X is matched, so that the target account is the standard user X, and then the standard account identifier in the account information table corresponding to the standard user X is further acquired.
Furthermore, in practical application, a user often logs in a mobile phone number and verification code mode, which is different from the tedious process of inputting account numbers and passwords, and a mobile phone number of the user is unique, so that one mobile phone number generally corresponds to one user, and the uniqueness of the mobile phone number corresponds to the uniqueness of each standard account in the system, so that the mobile phone number can be used as an index for internal and external association and retrieval.
Therefore, in an optional embodiment, a mobile phone verification link may be further added when logging in based on the third-party platform, so as to obtain the mobile phone number of the user, and thus bind the mobile phone number with the standard user corresponding to the user in the account database, thereby implementing the association between the system storage and the bidirectional unique identifier in the application software, and thus ensuring the consistency and security of the user information while fusing multi-platform account information.
To sum up, in a specific embodiment, there may be a case that the third party account information authorized by a certain user to request login is not associated with the user before (i.e., the associated third party account information is not matched in the account database), in order to locate the standard account of the user who currently wants to login, the third party information that the user wants to add is unified and managed, and in combination with the uniqueness of the mobile phone number corresponding to each user, after the associated third party account information of the target third party account in the account database is matched, steps S1042-S1044 shown in fig. 3 are further included. FIG. 3 shows a flow diagram for determining the associated phone number for a target standard account in one embodiment.
First, the account information table may further include associated mobile phone numbers, that is, each standard user may be associated with one mobile phone number.
In step S1042, under the condition that the matching fails, a preset mobile phone verification interface is displayed by the preset device, mobile phone verification information input on the mobile phone verification interface is received, and verification is performed according to the mobile phone verification information.
Also in connection with the above-mentioned illustration in step, in the case that the associated third party account information is not currently matched in the account database, the mobile phone verification interface may be presented in an application of "english lesson" on the mobile phone of the user.
Showing on the mobile phone verification interface, for example, "do or not need to be verified by the mobile phone? After the user inputs the 'yes' information, a verification code in a preset format is generated according to a preset verification code generating program and is sent to a mobile phone corresponding to the user.
And then receiving mobile phone verification information input by the user, matching the mobile phone verification information with the verification code, and judging that the mobile phone of the user passes the verification under the condition of matching the mobile phone verification information with the verification code.
In step S1044, in the case that the verification passes, the target mobile phone number corresponding to the mobile phone verification information is determined, the associated mobile phone number matched with the target mobile phone number is searched in the account database, and in the case that the search is successful, the standard account identifier corresponding to the searched associated mobile phone number is used as the target account identifier.
It is easy to understand that the target mobile phone number is the mobile phone number corresponding to the device that receives the verification code.
Similar to the step of searching for the associated third party account information in the foregoing steps, in the case where the associated mobile phone number is found, the standard account identifier included in the account information table for obtaining the associated mobile phone number may be stored as the target account identifier.
In this way, the target third party account which fails in matching but passes the mobile phone verification can be added as new associated third party account information to the standard user identifier. That is, after the standard account identifier corresponding to the found associated mobile phone number is used as the target account identifier, the method further includes:
and associating the target account identification with the target third party account information.
Meanwhile, there is a possibility that, in an alternative embodiment, the user may not have a mobile phone number bound (there is no matching of the associated mobile phone number) before logging in through the new third party (i.e., there is no matching of the associated third party account information), and therefore, steps S1052-S1054 shown in fig. 4 may be further included after searching the account database for the associated mobile phone number matching the target mobile phone number. Figure 4 illustrates a flow diagram of operations in the event of a handset authentication failure in one embodiment.
In step S1052, in case of a failure of the search, determining an account id as the target account id, and associating the target mobile phone number with the target account id.
In step S1054, the target account identity is added to the account database.
That is, in the case where a user does not bind a mobile phone number (there is no matching of associated mobile phone numbers) before logging in through a new third party (that is, there is no matching of associated third party account information), a preset identifier generation program may determine an account identifier such as ID37904703 to be stored in a preset account database as a target account identifier, and then associate and store the mobile phone number that failed verification with the newly determined target account identifier.
Therefore, a brand-new standard user is added to the account information base, and meanwhile, the corresponding associated mobile phone number is obtained.
In step S1026, a target token corresponding to the login request is determined, and corresponding prompt information is generated according to the target account identifier and the target token and returned to the user.
For example, after determining the standard account identifier in the account database corresponding to the user currently submitting the login request, it may be determined that the login request of the user is legal, and therefore, the target token and the target account identifier corresponding to the login request may be returned to the application for submitting the login request of the user, for example, for the application of "english lesson" in the foregoing example of steps, and the relevant program in the application is invoked to generate, for example, "authentication is successful, and you are welcomed. "etc. to feed back to the user.
After steps S1022 to S1026 are described, an example of the flow of multi-platform login in an alternative embodiment of the present invention is described below.
In a specific application scenario, in the first step, a user a opens a certain application B on a mobile phone used by the user a, enters a login interface of the application B, and selects a third-party account login mode (different from login by inputting an account and a password of the application B).
And then, in the second step, selecting a third-party application C from a preset candidate third-party account, then jumping to a preset authorization interface of the application C, and after obtaining authorization information input by the user A in the authorization interface, returning an authorization instruction to the application B by the application C.
In the third step, the application B obtains the information related to the account of the application C (i.e., the third party), such as the nickname of the account, the user name of the account (i.e., the login credential), the name of the platform of the third party, etc., corresponding to the application C, and searches for whether the information related to the account of the application C exists in a preset account information base.
In the case of searching, in the fourth step, it is determined which account information table the application C account information is stored in, i.e. which standard user identifier has uniqueness is associated with, and finally, the standard user identifier is obtained, so that the user a logs in through its associated application C account in the application B.
Finally, in an optional embodiment, in order to further improve the login interaction experience of the user, when the mobile phone authentication of the user fails for various reasons (such as card change or network failure), an opportunity of logging in by registering a new account can be provided for the user.
In an optional embodiment, when the verification fails, a preset registration interface is displayed through a preset device, account registration information input on the registration interface is acquired, a target account identifier and the associated third party account information are determined according to the account registration information, and the target account identifier and the associated third party account information are stored in the preset account database.
FIG. 5 is a block diagram that illustrates the architecture of a multi-platform login device in one embodiment.
Referring to fig. 5, a multi-platform login device 1060 according to an embodiment of the present invention includes: an acquisition unit 1062, a matching unit 1064, and a presentation unit 1066.
Wherein, the obtaining unit 1060: the system comprises a server, a server and a server, wherein the server is used for acquiring a login request input by a user and determining target third party account information according to the login request;
matching unit 1064: the system comprises a target account database, a target account identification table and a target account identification table, wherein the target account identification table is used for identifying a target account according to the target account information;
presentation unit 1066: and the system is used for determining a target token corresponding to the login request, generating corresponding prompt information according to the target account identifier and the target token, and returning the prompt information to the user.
Wherein the apparatus is further configured to: acquiring a login request input by a user, and determining target third party account information according to the login request;
searching a standard account matched with the target third-party account information in a preset account database to serve as a target account, acquiring an account information table corresponding to the target account to serve as a target account information table, and determining a target account identifier according to the target account information table;
and determining a target token corresponding to the login request, generating corresponding prompt information according to the target account identifier and the target token, and returning the prompt information to the user.
Further, the target third party account information includes at least one of a third party platform class, a third party account class, and/or a third party account identification,
the account database comprises an account information table corresponding to at least one standard account,
the account information table comprises at least one item of standard account identification, associated third party account information, associated creation time, current associated state, associated state update time and/or associated third party account remark information, wherein the associated third party account information comprises an associated third party platform type, an associated third party account type and an associated third party account identification.
Further, searching a standard account matched with the target third party account in a preset account database as a target account, wherein the method comprises the following steps:
searching the account database for associated third party account information matched with the target third party account;
and under the condition that the associated third party account information is matched, determining the target account according to the account information table corresponding to the matched associated third party account information.
Further, the account information table further includes an associated mobile phone number,
after matching the associated third party account information of the target third party account in the account database, further comprising:
under the condition of failed matching, displaying a preset mobile phone verification interface through the preset device, receiving mobile phone verification information input on the mobile phone verification interface, and verifying according to the mobile phone verification information;
and under the condition that the verification is passed, determining a target mobile phone number corresponding to the mobile phone verification information, searching for an associated mobile phone number matched with the target mobile phone number in the account database, and under the condition that the searching is successful, taking a standard account identifier corresponding to the searched associated mobile phone number as the target account identifier.
Furthermore, after the standard account identifier corresponding to the found associated mobile phone number is used as the target account identifier, the method further includes:
and associating the target account identification with the target third party account information.
Further, after searching the associated mobile phone number matched with the target mobile phone number in the account database, the method further includes:
under the condition of search failure, determining an account identifier as the target account identifier, and associating the target mobile phone number with the target account identifier;
adding the target account identification to the account database.
Further, after the authentication is performed according to the mobile phone authentication information, the method further includes:
and under the condition of failure in verification, displaying a preset registration interface through a preset device, acquiring account registration information input on the registration interface, determining a target account identifier and the associated third party account information according to the account registration information, and storing the target account identifier and the associated third party account information in the preset account database.
FIG. 6 is a diagram illustrating an internal structure of a computer device in one embodiment. The computer device may specifically be a terminal, and may also be a server. As shown in fig. 6, the computer device includes a processor, a memory, and a communication module, a processing module, a presentation module, which are connected by a system bus. Wherein the memory includes a non-volatile storage medium and an internal memory. The non-volatile storage medium of the computer device stores an operating system and also stores a computer program, and when the computer program is executed by a processor, the processor can realize the multi-platform login method. The internal memory may also store a computer program, and when the computer program is executed by the processor, the processor may execute the multi-platform login method. Those skilled in the art will appreciate that the architecture shown in fig. 6 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is proposed, comprising a memory and a processor, the memory storing a computer program which, when executed by the processor, causes the processor to perform the steps of:
acquiring a login request input by a user, and determining target third party account information according to the login request;
searching a standard account matched with the target third-party account information in a preset account database to serve as a target account, acquiring an account information table corresponding to the target account to serve as a target account information table, and determining a target account identifier according to the target account information table;
and determining a target token corresponding to the login request, generating corresponding prompt information according to the target account identifier and the target token, and returning the prompt information to the user.
Further, the target third party account information includes at least one of a third party platform class, a third party account class, and/or a third party account identification,
the account database comprises an account information table corresponding to at least one standard account,
the account information table comprises at least one item of standard account identification, associated third party account information, associated creation time, current associated state, associated state update time and/or associated third party account remark information, wherein the associated third party account information comprises an associated third party platform type, an associated third party account type and an associated third party account identification.
Further, searching a standard account matched with the target third party account in a preset account database as a target account, wherein the method comprises the following steps:
searching the account database for associated third party account information matched with the target third party account;
and under the condition that the associated third party account information is matched, determining the target account according to the account information table corresponding to the matched associated third party account information.
Further, the account information table further includes an associated mobile phone number,
after matching the associated third party account information of the target third party account in the account database, further comprising:
under the condition of failed matching, displaying a preset mobile phone verification interface through the preset device, receiving mobile phone verification information input on the mobile phone verification interface, and verifying according to the mobile phone verification information;
and under the condition that the verification is passed, determining a target mobile phone number corresponding to the mobile phone verification information, searching for an associated mobile phone number matched with the target mobile phone number in the account database, and under the condition that the searching is successful, taking a standard account identifier corresponding to the searched associated mobile phone number as the target account identifier.
Furthermore, after the standard account identifier corresponding to the found associated mobile phone number is used as the target account identifier, the method further includes:
and associating the target account identification with the target third party account information.
Further, after searching the associated mobile phone number matched with the target mobile phone number in the account database, the method further includes:
under the condition of search failure, determining an account identifier as the target account identifier, and associating the target mobile phone number with the target account identifier;
adding the target account identification to the account database.
Further, after the authentication is performed according to the mobile phone authentication information, the method further includes:
and under the condition of failure in verification, displaying a preset registration interface through a preset device, acquiring account registration information input on the registration interface, determining a target account identifier and the associated third party account information according to the account registration information, and storing the target account identifier and the associated third party account information in the preset account database.
In one embodiment, a computer-readable storage medium is proposed, in which a computer program is stored which, when executed by a processor, causes the processor to carry out the steps of:
acquiring a login request input by a user, and determining target third party account information according to the login request;
searching a standard account matched with the target third-party account information in a preset account database to serve as a target account, acquiring an account information table corresponding to the target account to serve as a target account information table, and determining a target account identifier according to the target account information table;
and determining a target token corresponding to the login request, generating corresponding prompt information according to the target account identifier and the target token, and returning the prompt information to the user.
Further, the target third party account information includes at least one of a third party platform class, a third party account class, and/or a third party account identification,
the account database comprises an account information table corresponding to at least one standard account,
the account information table comprises at least one item of standard account identification, associated third party account information, associated creation time, current associated state, associated state update time and/or associated third party account remark information, wherein the associated third party account information comprises an associated third party platform type, an associated third party account type and an associated third party account identification.
Further, searching a standard account matched with the target third party account in a preset account database as a target account, wherein the method comprises the following steps:
searching the account database for associated third party account information matched with the target third party account;
and under the condition that the associated third party account information is matched, determining the target account according to the account information table corresponding to the matched associated third party account information.
Further, the account information table further includes an associated mobile phone number,
after matching the associated third party account information of the target third party account in the account database, further comprising:
under the condition of failed matching, displaying a preset mobile phone verification interface through the preset device, receiving mobile phone verification information input on the mobile phone verification interface, and verifying according to the mobile phone verification information;
and under the condition that the verification is passed, determining a target mobile phone number corresponding to the mobile phone verification information, searching for an associated mobile phone number matched with the target mobile phone number in the account database, and under the condition that the searching is successful, taking a standard account identifier corresponding to the searched associated mobile phone number as the target account identifier.
Furthermore, after the standard account identifier corresponding to the found associated mobile phone number is used as the target account identifier, the method further includes:
and associating the target account identification with the target third party account information.
Further, after searching the associated mobile phone number matched with the target mobile phone number in the account database, the method further includes:
under the condition of search failure, determining an account identifier as the target account identifier, and associating the target mobile phone number with the target account identifier;
adding the target account identification to the account database.
Further, after the authentication is performed according to the mobile phone authentication information, the method further includes:
and under the condition of failure in verification, displaying a preset registration interface through a preset device, acquiring account registration information input on the registration interface, determining a target account identifier and the associated third party account information according to the account registration information, and storing the target account identifier and the associated third party account information in the preset account database.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a non-volatile computer-readable storage medium, and can include the processes of the embodiments of the methods described above when the program is executed. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present application. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. A multi-platform login method is characterized by comprising the following steps:
acquiring a login request input by a user, and determining target third party account information according to the login request; the login request is input in a preset login interface contained in a target application after the target application is opened by the user; the determining of the target third party account information according to the login request comprises: determining a preset third-party login inlet of a third-party application selected by a user in the login interface, jumping to a preset authorization interface corresponding to the third-party application, acquiring authorization information input by the user in the authorization interface, receiving an authorization instruction returned by the third-party application under the condition that the authorization information agrees to authorization, and acquiring target third-party account information of the third-party application;
searching a standard account matched with the target third-party account information in a preset account database to serve as a target account, acquiring an account information table corresponding to the target account to serve as a target account information table, and determining a target account identifier according to the target account information table;
logging in the target application by using the target account identifier, determining a target token corresponding to the login request, and generating corresponding prompt information according to the target account identifier and the target token and returning the prompt information to the user.
2. The multi-platform login method of claim 1, wherein the target third party account information comprises at least one of a third party platform class, a third party account class, and/or a third party account identification,
the account database comprises an account information table corresponding to at least one standard account,
the account information table comprises at least one item of standard account identification, associated third party account information, associated creation time, current associated state, associated state update time and/or associated third party account remark information, wherein the associated third party account information comprises an associated third party platform type, an associated third party account type and an associated third party account identification.
3. The multi-platform login method of claim 2, wherein searching a standard account matched with the target third party account in a preset account database as a target account comprises:
searching the account database for associated third party account information matched with the target third party account;
and under the condition that the associated third party account information is matched, determining the target account according to the account information table corresponding to the matched associated third party account information.
4. The multi-platform login method of claim 3, wherein the account information table further comprises an associated phone number,
after matching the associated third party account information of the target third party account in the account database, further comprising:
under the condition of failed matching, displaying a preset mobile phone verification interface through a preset device, receiving mobile phone verification information input on the mobile phone verification interface, and verifying according to the mobile phone verification information;
and under the condition that the verification is passed, determining a target mobile phone number corresponding to the mobile phone verification information, searching for an associated mobile phone number matched with the target mobile phone number in the account database, and under the condition that the searching is successful, taking a standard account identifier corresponding to the searched associated mobile phone number as the target account identifier.
5. The multi-platform login method according to claim 4, wherein after the standard account identifier corresponding to the found associated mobile phone number is used as the target account identifier, the method further comprises:
and associating the target account identification with the target third party account information.
6. The multi-platform login method according to claim 4, wherein after searching the account database for the associated mobile phone number matching the target mobile phone number, the method further comprises:
under the condition of search failure, determining an account identifier as the target account identifier, and associating the target mobile phone number with the target account identifier;
adding the target account identification to the account database.
7. The multi-platform login method according to claim 4, after the authentication is performed according to the mobile phone authentication information, further comprising:
and under the condition of failure in verification, displaying a preset registration interface through a preset device, acquiring account registration information input on the registration interface, determining a target account identifier and the associated third party account information according to the account registration information, and storing the target account identifier and the associated third party account information in the preset account database.
8. A multi-platform login device, the device comprising:
an acquisition unit: the system comprises a server, a server and a server, wherein the server is used for acquiring a login request input by a user and determining target third party account information according to the login request; the login request is input in a preset login interface contained in a target application after the target application is opened by a user; the determining of the target third party account information according to the login request comprises: determining a preset third-party login inlet of a third-party application selected by a user in the login interface, jumping to a preset authorization interface corresponding to the third-party application, acquiring authorization information input by the user in the authorization interface, receiving an authorization instruction returned by the third-party application under the condition that the authorization information agrees to authorization, and acquiring target third-party account information of the third-party application;
a matching unit: the system comprises a target account database, a target account identification table and a target account identification table, wherein the target account identification table is used for identifying a target account according to the target account information;
a prompt unit: the system is used for logging in the target application by using the target account identifier, determining a target token corresponding to the login request, and generating corresponding prompt information according to the target account identifier and the target token and returning the prompt information to the user.
9. A readable storage medium storing a computer program which, when executed by a processor, causes the processor to perform the steps of the method according to any one of claims 1 to 7.
10. A computer device comprising a memory and a processor, the memory storing a computer program that, when executed by the processor, causes the processor to perform the steps of the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010332351.8A CN111541546B (en) | 2020-04-24 | 2020-04-24 | Multi-platform login method, device, equipment and readable medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010332351.8A CN111541546B (en) | 2020-04-24 | 2020-04-24 | Multi-platform login method, device, equipment and readable medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111541546A CN111541546A (en) | 2020-08-14 |
| CN111541546B true CN111541546B (en) | 2020-11-27 |
Family
ID=71977195
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010332351.8A Active CN111541546B (en) | 2020-04-24 | 2020-04-24 | Multi-platform login method, device, equipment and readable medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111541546B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111970286A (en) * | 2020-08-21 | 2020-11-20 | 北京恒华伟业科技股份有限公司 | User login method and device and web server |
| CN111970551B (en) * | 2020-08-21 | 2022-04-12 | 广州欢网科技有限责任公司 | IPTV card changing method, device and system |
| CN113037741B (en) * | 2021-03-04 | 2023-08-11 | 腾讯科技（深圳）有限公司 | Authentication method, authentication device, computer equipment and storage medium |
| CN113630252A (en) * | 2021-07-13 | 2021-11-09 | 上海百胜软件股份有限公司 | Multi-platform access method, system and equipment |
| CN113709146B (en) * | 2021-08-26 | 2023-06-23 | 上海掌门科技有限公司 | Method, equipment and medium for presenting entry information |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102546770A (en) * | 2011-12-26 | 2012-07-04 | 中兴通讯股份有限公司 | Unified account management method and third-party account management system |
| CN110830463A (en) * | 2019-10-30 | 2020-02-21 | 腾讯科技（深圳）有限公司 | Third party authorized login method and device |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102571857B (en) * | 2010-12-27 | 2014-12-31 | 北京闪联云视信息技术有限公司 | Method and system for realizing logging in XMPP (Xmlbased Messaging and Presence Protocol) server |
| CN104348612A (en) * | 2013-07-23 | 2015-02-11 | 腾讯科技（深圳）有限公司 | Third-party website login method based on mobile terminal and mobile terminal |
| CN104486417B (en) * | 2014-12-16 | 2018-05-25 | 上海斐讯数据通信技术有限公司 | Account safety management system and method based on cloud service |
| CN105871838B (en) * | 2016-03-30 | 2019-03-01 | 努比亚技术有限公司 | A kind of log-in control method and customer center platform of third party's account |
-
2020
- 2020-04-24 CN CN202010332351.8A patent/CN111541546B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102546770A (en) * | 2011-12-26 | 2012-07-04 | 中兴通讯股份有限公司 | Unified account management method and third-party account management system |
| CN110830463A (en) * | 2019-10-30 | 2020-02-21 | 腾讯科技（深圳）有限公司 | Third party authorized login method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111541546A (en) | 2020-08-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111541546B (en) | Multi-platform login method, device, equipment and readable medium | |
| AU2018374912B2 (en) | Model training system and method, and storage medium | |
| TWI647583B (en) | Prompt method and prompting device for login account | |
| JP2022000757A5 (en) | ||
| CN111177734A (en) | Document operation authority setting and document operation method, device, terminal and medium | |
| US10216788B2 (en) | Determining contact related information | |
| CN109684873B (en) | Data access control method and device, computer equipment and storage medium | |
| CN107864144A (en) | Obtain method and device, computer installation and the storage medium of dynamic password | |
| CN110795174B (en) | Application program interface calling method, device, equipment and readable storage medium | |
| CN112073289B (en) | Instant messaging control method and device | |
| CN110287691A (en) | Application program login method, device, equipment and storage medium | |
| US8522323B1 (en) | System and method for obtaining identities | |
| CN108737398B (en) | Processing method and device of trust system, computer equipment and storage medium | |
| CN110135136A (en) | Account fusion method, device, computer equipment and storage medium | |
| CN113326488A (en) | Personal information protection system and method | |
| US20180039771A1 (en) | Method of and server for authorizing execution of an application on an electronic device | |
| EP2031883A1 (en) | Method, system, network device, and mobile data service management platform for down sending content | |
| CN112560815B (en) | File calling method, device, medium and electronic equipment | |
| CN109087053B (en) | Collaborative office processing method, device, equipment and medium based on association topological graph | |
| CN111277595B (en) | User and data management method suitable for multiple users and multiple terminals | |
| CN112788017B (en) | Security verification method, device, equipment and medium | |
| CN113568542A (en) | Interface display method and electronic equipment | |
| CN115993918A (en) | Menu processing method, menu processing device, electronic equipment and readable storage medium | |
| CN111767576A (en) | User matching method and system based on privacy information and readable storage medium | |
| CN114238927A (en) | Business system login method, system, device, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |