Account login authentication method and device, storage medium and electronic device

Abstract

The invention discloses an account login authentication method and device, a storage medium and an electronic device, and relates to the technical field of smart home, and the account login authentication method comprises the steps: obtaining a login request, and obtaining a corresponding self-built account according to an input account in the login request; wherein the input account number is an external system account number held by a login person, and the self-built account number has an association relationship with at least one external system account number; acquiring a preset authentication strategy and authentication information adopted by authentication according to the self-established account; wherein the preset authentication strategy is configured to comprise a calling rule for a plurality of authentication services; and calling the corresponding authentication service by using the authentication information based on the calling rule of the authentication service, determining a login authentication result according to authentication feedback returned by the authentication service, and returning the login authentication result to the client.

Description

Technical Field

[0001] The present application relates to the field of smart home, and more specifically, to an account login authentication method, device, storage medium and electronic device. Background Art

[0002] With the increasing complexity of business, the division of business areas in some large group companies has become more and more fine-grained, which has led to the emergence of multiple account systems such as accounts for C-end users (user center), accounts for B-end customers (customer center), and corporate employee accounts. Some users on a business platform have one identity, while others may have multiple identities. To log in to the business platform, different account systems need to be used for login authentication.

[0003] However, currently common authentication is generally implemented based on the OAuth2 standard. Generally, when a user has multiple identities, the business system uses multiple login portals to log in to multiple account systems, and it is impossible to log in to multiple accounts with one login portal. Users need to record their login accounts for different identities and select the corresponding login portals, which requires users to spend more time and may also lead to errors. Summary of the invention

[0004] The technical solution of the present application can realize user login authentication with multiple identities at one login entrance, thereby improving the user login experience.

[0005] On the one hand, an embodiment of the present application provides an account login authentication method, including:

[0006] Obtaining a login request, and obtaining a corresponding self-created account according to an input account in the login request; wherein the input account is an external system account held by the login personnel, and the self-created account has an associated relationship with at least one of the external system accounts;

[0007] Obtaining a preset authentication policy and authentication information used for authentication according to the self-created account; wherein the preset authentication policy is configured to include calling rules for multiple authentication services;

[0008] Based on the calling rule of the authentication service, the corresponding authentication service is called using the authentication information, and the login authentication result is determined according to the authentication feedback returned by the authentication service and returned to the client.

[0009] In one implementation, before obtaining the login request and obtaining the corresponding self-created account according to the input account in the login request, the method further includes:

[0010] Obtain the external system account of the login person;

[0011] The external system account and the self-built account are mapped to each other, and the association relationship between the self-built account and at least one of the external system accounts is saved.

[0012] In one implementation, the calling rule of the authentication service, calling the corresponding authentication service using the authentication information, and determining the login authentication result according to the authentication feedback returned by the authentication service and returning it to the client include:

[0013] The authentication service includes application center authentication service, authority center authentication service and account center authentication service;

[0014] Send an application authentication request to the application center to obtain the application authentication result;

[0015] If the application authentication success information fed back by the application center is received, an account identity query request is sent to the permission center to obtain the account identity information;

[0016] If the authentication account received from the authority center is a single-identity account, obtaining the authentication policy configured by the authority center;

[0017] If the authentication policy configured by the authority center is obtained, the account authentication interface of the authority center is called to authenticate the authentication information;

[0018] If a token is obtained after successful account authentication from the authority center, a self-owned token is generated based on the token and returned to the client.

[0019] In one implementation, after receiving the application authentication success information fed back by the application center and sending an account identity query request to the permission center to obtain the account identity information, the method further includes:

[0020] If the authentication account received from the authority center is a multi-identity account, obtaining the authentication policy configured by the account center from the account center;

[0021] If the authentication policy configured by the account center is obtained, the account authentication interface of the account center is called to authenticate the authentication information;

[0022] If a token is obtained after successful account authentication from the account center, a self-owned token is generated based on the token and returned to the client.

[0023] In one implementation, if the authentication account received as feedback from the authority center is a multi-identity account, after obtaining the authentication policy configured by the account center from the account center, the method further includes:

[0024] If the authentication policy configured by the account center is not obtained, the default external system account is used as the authentication account to obtain the authentication policy configured by the authority center;

[0025] If the authentication policy configured by the authority center is obtained, the account authentication interface of the authority center is called to authenticate the authentication information;

[0026] If a token is obtained after successful account authentication from the authority center, a self-owned token is generated based on the token and returned to the client.

[0027] In one implementation, if the authentication policy configured by the authority center is not obtained, the method further includes:

[0028] Obtain the authentication policy configured by the application center, and call the account authentication interface of the application center to authenticate the authentication information;

[0029] If a token is obtained after successful account authentication from the application center, a self-owned token is generated based on the token and returned to the client.

[0030] In one implementation, after receiving the application authentication success information fed back by the application center and sending an account identity query request to the permission center to obtain the account identity information, the method further includes:

[0031] If the abnormal account status information is received from the authority center, the authentication process ends, the authentication is determined to be unsuccessful, and the login authentication failure information is returned to the client.

[0032] On the other hand, an embodiment of the present application provides an account login authentication device, including:

[0033] A self-built account acquisition module, used to acquire a login request, and acquire a corresponding self-built account according to an input account in the login request; wherein the input account is an external system account held by the login personnel, and the self-built account has an associated relationship with at least one of the external system accounts;

[0034] An authentication policy acquisition module, used to acquire a preset authentication policy and authentication information adopted for authentication according to the self-created account; wherein the preset authentication policy is configured to include calling rules for multiple authentication services;

[0035] The authentication service calling module is used to call the corresponding authentication service based on the calling rules of the authentication service and the authentication information, and determine the login authentication result according to the authentication feedback returned by the authentication service and return it to the client.

[0036] In one implementation, the account login authentication device further includes:

[0037] An external system account acquisition module, used for acquiring the external system account of the login person before acquiring the login request and acquiring the corresponding self-built account according to the input account in the login request;

[0038] The association relationship saving module is used to map the external system account with the self-built account, and save the association relationship between the self-built account and at least one of the external system accounts.

[0039] In one implementation, the authentication service calling module is specifically used to:

[0040] The authentication service includes application center authentication service, authority center authentication service and account center authentication service;

[0041] Send an application authentication request to the application center to obtain the application authentication result;

[0042] If the application authentication success information fed back by the application center is received, an account identity query request is sent to the permission center to obtain the account identity information;

[0043] If the authentication account received from the authority center is a single-identity account, obtaining the authentication policy configured by the authority center;

[0044] If the authentication policy configured by the authority center is obtained, the account authentication interface of the authority center is called to authenticate the authentication information;

[0045] If a token is obtained after successful account authentication from the authority center, a self-owned token is generated based on the token and returned to the client.

[0046] In one implementation, the authentication service calling module is specifically used to:

[0047] After receiving the application authentication success information fed back by the application center and sending an account identity query request to the permission center to obtain the account identity information, the method further includes:

[0048] If the authentication account received from the authority center is a multi-identity account, obtaining the authentication policy configured by the account center from the account center;

[0049] If the authentication policy configured by the account center is obtained, the account authentication interface of the account center is called to authenticate the authentication information;

[0050] If a token is obtained after successful account authentication from the account center, a self-owned token is generated based on the token and returned to the client.

[0051] In one implementation, the authentication service calling module is specifically used to:

[0052] After obtaining the authentication policy configured by the account center from the account center if the authentication account fed back by the authority center is a multi-identity account, the method further includes:

[0053] If the authentication policy configured by the account center is not obtained, the default external system account is used as the authentication account to obtain the authentication policy configured by the authority center;

[0054] If the authentication policy configured by the authority center is obtained, the account authentication interface of the authority center is called to authenticate the authentication information;

[0055] If a token is obtained after successful account authentication from the authority center, a self-owned token is generated based on the token and returned to the client.

[0056] In one implementation, the authentication service calling module is specifically used to:

[0057] If the authentication policy configured by the authority center is not obtained, it also includes:

[0058] Obtain the authentication policy configured by the application center, and call the account authentication interface of the application center to authenticate the authentication information;

[0059] If a token is obtained after successful account authentication from the application center, a self-owned token is generated based on the token and returned to the client.

[0060] In one implementation, the authentication service calling module is specifically used to:

[0061] After receiving the application authentication success information fed back by the application center and sending an account identity query request to the permission center to obtain the account identity information, the method further includes:

[0062] If the abnormal account status information is received from the authority center, the authentication process ends, the authentication is determined to be unsuccessful, and the login authentication failure information is returned to the client.

[0063] On the other hand, an embodiment of the present application provides a computer-readable storage medium, which includes a stored program, wherein when the program is run, the account login authentication method provided by any embodiment is executed.

[0064] On the other hand, an embodiment of the present application provides an electronic device, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the account login authentication method provided by any embodiment through the computer program.

[0065] The embodiments of the present application provide an account login authentication method, device, storage medium and electronic device. By associating an external system account with a self-built account, the corresponding authentication service is called to perform login authentication. This solves the problem that when users log in to the system, they need to select their own login entry, which makes the user login operation complicated. This allows login authentication of multiple users with one login entry, thereby improving the user login experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0066] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0067] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0068] Figure 1 It is a schematic diagram of the hardware environment of an account login authentication method according to an embodiment of the present application;

[0069] Figure 2 is a flow chart of an account login authentication method according to an embodiment of the present application;

[0070] Figure 3 is a schematic diagram of account association relationship mapping according to an embodiment of the present application;

[0071] Figure 4 is a schematic diagram of a delegated multi-level authentication service according to an embodiment of the present application;

[0072] Figure 5 It is a structural diagram of an account login authentication device according to an embodiment of the present application;

[0073] Figure 6 It is a timing diagram of unified login and delivery functions of the customized platform according to an embodiment of the present application. DETAILED DESCRIPTION

[0074] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0075] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0076] According to one aspect of the embodiment of the present application, an account login authentication method is provided. The account login authentication method is widely used in smart home (Smart Home), smart home, smart home device ecology, smart residential (Intelligence House) ecology and other whole-house intelligent digital control application scenarios. Optionally, in this embodiment, the above account login authentication method can be applied to Figure 1 In the hardware environment composed of the terminal device 102 and the server 104 shown in FIG. Figure 1 As shown, the server 104 is connected to the terminal device 102 via a network, and can be used to provide services (such as application services, etc.) for the terminal or a client installed on the terminal. A database can be set on the server or independently of the server to provide data storage services for the server 104. Cloud computing and / or edge computing services can be configured on the server or independently of the server to provide data computing services for the server 104.

[0077] The network may include but is not limited to at least one of the following: wired network, wireless network. The wired network may include but is not limited to at least one of the following: wide area network, metropolitan area network, local area network, and the wireless network may include but is not limited to at least one of the following: WIFI (Wireless Fidelity), Bluetooth. The terminal device 102 may be but is not limited to a PC, a mobile phone, a tablet computer, a smart air conditioner, a smart range hood, a smart refrigerator, a smart oven, a smart stove, a smart washing machine, a smart water heater, a smart washing device, a smart dishwasher, a smart projection device, a smart TV, a smart clothes drying rack, a smart curtain, a smart audio and video, a smart socket, a smart speaker, a smart fresh air device, a smart kitchen and bathroom device, a smart bathroom device, a smart sweeping robot, a smart window cleaning robot, a smart mopping robot, a smart air purification device, a smart steamer, a smart microwave oven, a smart kitchen treasure, a smart purifier, a smart water dispenser, a smart door lock, etc.

[0078] In one aspect of the embodiment of the present application, Figure 2 The flowchart of an account login authentication method shown in FIG. 1 is a flowchart of an account login authentication method, which can be applied to a server, including:

[0079] Step S210: Obtain a login request, and obtain a corresponding self-created account according to the input account in the login request.

[0080] Among them, the input account is an external system account held by the login personnel, and the self-built account has an association relationship with at least one of the external system accounts. Under a service platform, the same login personnel can have different identities. For example, on a smart home customization platform, the store manager of the sales store belongs to the dealer and can hold a customer account. In order to customize the home, there will also be designers, and of course there will be consumers. Designers and consumers can hold user accounts, and corporate employees of the customization platform hold employee accounts. In actual situations, a login personnel may have multiple identities and hold multiple different external system accounts. The login personnel opens the unified login page on the client, for example, through the browser on the terminal device. There is usually an account input box on the unified login page. The input account is the account entered by the login personnel on the unified login page. Of course, the login personnel usually enters a password when logging in. The client sends a login request carrying the input account and password to a server configured with a unified authentication service. The association relationship between the self-built account and at least one external system account is pre-stored. In one implementation, before obtaining the corresponding self-built account according to the input account in the login request if a login request is obtained, it also includes: obtaining the external system account of the login person; mapping the external system account with the self-built account, and saving the association relationship between the self-built account and at least one external system account. For example, Figure 3 As shown in the figure, the external system account of the login personnel can be mapped to the self-built account, so that a self-built account can be associated with multiple external accounts. In this way, the authentication policy at login time can be configured to determine which account to use for login, and the login personnel do not need to remember different accounts for their different identities. In the self-built account system, a self-built account can store information such as the self-built account ID, login account, password, and external system of the source.

[0081] Step S230: Obtain a preset authentication policy and authentication information used for authentication according to the self-created account.

[0082] Wherein, the preset authentication strategy is configured to include call rules for multiple authentication services, and the authentication account is the external system account required to call the authentication service. The authentication information required for the login personnel to log in can be pre-configured, and the authentication information includes the authentication account and password, or it can be automatically determined according to the authentication priority of the external system to which the external system account belongs, and the login personnel can log in with the account they are accustomed to using. For example, for user accounts, mobile phone numbers are often used as authentication accounts when logging in, which is a familiar account for the login personnel. Optionally, the authentication service includes the authentication service of the application center, the authentication service of the authority center, and the authentication service of the account center. For the authentication of the application end, it can be managed by the application center, such as the CRM (Customer Relationship Management, customer relationship management system) system-PC (Personal Computer, personal computer) end, CRM system-mobile end, and the application end login authentication strategy can be specified. Identity authentication, the identity can be such as designer, store manager, consumer, etc., managed by the authority center, and the identity login authentication strategy can be specified; when the user has multiple identities, it is transferred to the account center for management. Account authentication is managed by the account center, and the account login authentication strategy can be specified.

[0083] Step S250: Based on the calling rule of the authentication service, the corresponding authentication service is called using the authentication information, and according to the authentication feedback returned by the authentication service, a login authentication result is determined and returned to the client.

[0084] Among them, after configuring the call rules for each authentication service through the unified authentication service, the authentication policy configured in the authentication service is called step by step using the selected authentication account for login authentication, and each called authentication service returns the corresponding authentication feedback. If the authentication service is successfully authenticated according to the configured authentication policy and returns the authentication success information, the login authentication result is determined to be a successful login and returned to the client, and the client can display the corresponding result to the login person.

[0085] In one implementation, the calling rule of the authentication service, calling the corresponding authentication service using the authentication information, and determining the login authentication result and returning it to the client according to the authentication feedback returned by the authentication service, include:

[0086] Send an application authentication request to the application center to obtain the application authentication result;

[0087] If the application authentication success information fed back by the application center is received, an account identity query request is sent to the permission center to obtain the account identity information;

[0088] If the authentication account received from the authority center is a single-identity account, obtaining the authentication policy configured by the authority center;

[0089] If the authentication policy configured by the authority center is obtained, the account authentication interface of the authority center is called to authenticate the authentication information;

[0090] If a token is obtained after successful account authentication from the authority center, a self-owned token is generated based on the token and returned to the client.

[0091] Among them, Figure 4 As shown, according to the calling rules of the authentication service, application authentication can be used as the first-level authentication, and the authentication service of the application center can be called to authenticate the application first. If the application authentication is successful, the second-level authentication can be delegated. Identity authentication can be used as the second-level authentication, and the authentication service of the permission center can be called to query the account identity information. If it is a single-identity account, the authentication policy configured by the permission center can be obtained. If the permission center has configured the authentication policy, the account authentication interface of the permission center can be called for authentication. If the authentication is successful, the corresponding token is returned, and the server of the unified authentication service generates its own token and returns it to the client.

[0092] In one implementation, after receiving the application authentication success information fed back by the application center and sending an account identity query request to the permission center to obtain the account identity information, the method further includes:

[0093] If the authentication account received from the authority center is a multi-identity account, obtaining the authentication policy configured by the account center from the account center;

[0094] If the authentication policy configured by the account center is obtained, the account authentication interface of the account center is called to authenticate the authentication information;

[0095] If a token is obtained after successful account authentication from the account center, a self-owned token is generated based on the token and returned to the client.

[0096] Among them, Figure 4 As shown, if the calling authority center determines that the account is a multi-identity account, the third-level authentication is delegated; the account authentication is used as the third-level authentication, the authentication service of the account center is called, and the authentication policy configured by the account center is obtained. If the account center has configured the authentication policy, the account authentication interface of the account center is called for authentication; if the authentication is successful, the corresponding token is returned, and the server of the unified authentication service generates its own token and returns it to the client.

[0097] In one implementation, if the authentication account received as feedback from the authority center is a multi-identity account, after obtaining the authentication policy configured by the account center from the account center, the method further includes:

[0098] If the authentication policy configured by the account center is not obtained, the default external system account is used as the authentication account to obtain the authentication policy configured by the authority center;

[0099] If the authentication policy configured by the authority center is obtained, the account authentication interface of the authority center is called to authenticate the authentication information;

[0100] If a token is obtained after successful account authentication from the authority center, a self-owned token is generated based on the token and returned to the client.

[0101] Among them, Figure 3 As shown, for multi-identity accounts, if the account center has not configured an authentication policy, it returns to the authority center to obtain the authentication policy configured by the authority center with the default external system account. If the authority center has configured an authentication policy, it calls the account authentication interface of the account center for authentication; if the authentication is successful, it returns the corresponding token, and the server of the unified authentication service generates its own token and returns it to the client.

[0102] In one implementation, if the authentication policy configured by the authority center is not obtained, the method further includes:

[0103] Obtain the authentication policy configured by the application center, and call the account authentication interface of the application center to authenticate the authentication information;

[0104] If a token is obtained after successful account authentication from the application center, a self-owned token is generated based on the token and returned to the client.

[0105] Among them, Figure 4 As shown, if the multi-identity account fails to obtain the authentication policy in the authority center as the default external system account, or the single-identity account fails to obtain the authentication policy in the authority center, it returns to the application center, calls the authentication service of the application center, obtains the authentication policy configured by the application center, and returns the corresponding token if the authentication is successful. The server of the unified authentication service generates its own token and returns it to the client. It is understandable that after obtaining the authentication policy configured by the application center, the authority center, and the account center and performing authentication, but the authentication fails, it is considered that the login failed, and the server of the unified authentication service returns the login failure information to the client.

[0106] In one implementation, after receiving the application authentication success information fed back by the application center and sending an account identity query request to the permission center to obtain the account identity information, the method further includes:

[0107] If the abnormal account status information is received from the authority center, the authentication process ends, the authentication is determined to be unsuccessful, and the login authentication failure information is returned to the client.

[0108] Among them, Figure 4 As shown, after the application center successfully authenticates the application, it confirms whether the status of the authentication account is normal. If the authentication account status is normal, the account identity information is queried and the subsequent authentication policy is obtained, and then the authentication operation is performed; if the authentication account status is abnormal, the authentication process is terminated, the authentication is determined to be unsuccessful, and the login authentication failure information is returned to the client. The abnormal account status may be that the authentication account does not exist.

[0109] The account login authentication method provided in the embodiment of the present application can complete multi-level authentication of application, identity, and account in the same login portal, and can integrate multi-system account multi-level delegation authentication, simplifying the management cost of users when logging in to multi-system accounts and reducing the situation of errors in the use of login accounts.

[0110] As a specific example, Figure 6 As shown in the figure, taking the example of opening the customized delivery function after unified login of a certain customized platform, the login person is the user steward of the store who holds a customer account. The user steward enters the customized platform login page on the terminal device, then enters the account password on the customized platform login page and clicks to log in. The login authentication interface of the unified authentication service is called through the customized platform API gateway to request login authentication. The customized platform login policy is queried from the customer center service through the unified authentication service. The customer center service performs customer authentication and calls the customer center interface for authentication. If the authentication is successful, the corresponding token and identity information are returned. The unified authentication service generates its own token based on the token returned by the customer center and saves the session, returns the session data, which carries its own token, and the customized platform API gateway returns the successful login information to the customized platform login page and displays it to the user on the customized platform login page.

[0111] After the user manager logs in successfully, he can perform delivery operations. Click the delivery menu, bring his own token to request the delivery API, verify the legitimacy of his own token through the delivery API gateway, call the token legitimacy verification interface of the unified authentication service, and if the unified authentication service returns that the token legitimacy is successfully verified, return the current login account data to the delivery API gateway, further call the delivery business interface of the delivery project service through the delivery API gateway, return the delivery result to the delivery API gateway, and further return the result to the customized platform API gateway. The customized platform API gateway returns the result to the customized platform login page, and the delivery result is visualized and rendered to display to the user.

[0112] Another aspect of the embodiment of the present application is as follows Figure 5 The structural diagram of an account login authentication device shown in FIG. 5 includes: a self-built account acquisition module 501, an authentication strategy acquisition module 503, and an authentication service calling module 505, wherein:

[0113] A self-built account acquisition module 501 is used to acquire a login request, and acquire a corresponding self-built account according to an input account in the login request; wherein the input account is an external system account held by the login personnel, and the self-built account has an associated relationship with at least one of the external system accounts;

[0114] The authentication strategy acquisition module 503 is used to acquire the preset authentication strategy and the authentication information adopted by the authentication according to the self-created account; wherein the preset authentication strategy is configured to include calling rules for multiple authentication services;

[0115] The authentication service calling module 505 is used to call the corresponding authentication service based on the calling rule of the authentication service and the authentication information, and determine the login authentication result according to the authentication feedback returned by the authentication service and return it to the client.

[0116] In one implementation, the account login authentication device further includes:

[0117] An external system account acquisition module, used for acquiring the external system account of the login person before acquiring the login request and acquiring the corresponding self-built account according to the input account in the login request;

[0118] The association relationship saving module is used to map the external system account with the self-built account, and save the association relationship between the self-built account and at least one of the external system accounts.

[0119] In one implementation, the authentication service calling module 505 is specifically used to:

[0120] The authentication service includes application center authentication service, authority center authentication service and account center authentication service;

[0121] Send an application authentication request to the application center to obtain the application authentication result;

[0122] If the application authentication success information fed back by the application center is received, an account identity query request is sent to the permission center to obtain the account identity information;

[0123] If the authentication account received from the authority center is a single-identity account, obtaining the authentication policy configured by the authority center;

[0124] If the authentication policy configured by the authority center is obtained, the account authentication interface of the authority center is called to authenticate the authentication information;

[0125] If a token is obtained after successful account authentication from the authority center, a self-owned token is generated based on the token and returned to the client.

[0126] In one implementation, the authentication service calling module 505 is specifically used to:

[0127] After receiving the application authentication success information fed back by the application center and sending an account identity query request to the permission center to obtain the account identity information, the method further includes:

[0128] If the authentication account received from the authority center is a multi-identity account, obtaining the authentication policy configured by the account center from the account center;

[0129] If the authentication policy configured by the account center is obtained, the account authentication interface of the account center is called to authenticate the authentication information;

[0130] If a token is obtained after successful account authentication from the account center, a self-owned token is generated based on the token and returned to the client.

[0131] In one implementation, the authentication service calling module 505 is specifically used to:

[0132] After obtaining the authentication policy configured by the account center from the account center if the authentication account fed back by the authority center is a multi-identity account, the method further includes:

[0133] If the authentication policy configured by the account center is not obtained, the default external system account is used as the authentication account to obtain the authentication policy configured by the authority center;

[0134] If the authentication policy configured by the authority center is obtained, the account authentication interface of the authority center is called to authenticate the authentication information;

[0135] If a token is obtained after successful account authentication from the authority center, a self-owned token is generated based on the token and returned to the client.

[0136] In one implementation, the authentication service calling module 505 is specifically used to:

[0137] If the authentication policy configured by the authority center is not obtained, it also includes:

[0138] Obtain the authentication policy configured by the application center, and call the account authentication interface of the application center to authenticate the authentication information;

[0139] If a token is obtained after successful account authentication from the application center, a self-owned token is generated based on the token and returned to the client.

[0140] In one implementation, the authentication service calling module 505 is specifically used to:

[0141] After receiving the application authentication success information fed back by the application center and sending an account identity query request to the permission center to obtain the account identity information, the method further includes:

[0142] If the abnormal account status information is received from the authority center, the authentication process ends, the authentication is determined to be unsuccessful, and the login authentication failure information is returned to the client.

[0143] The account login authentication device provided in the embodiment of the present invention can execute the account login authentication method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0144] The embodiment of the present application further provides an electronic device, wherein the electronic device may be a computer device, including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to perform the following steps through the computer program:

[0145] Obtaining a login request, and obtaining a corresponding self-created account according to an input account in the login request; wherein the input account is an external system account held by the login personnel, and the self-created account has an associated relationship with at least one of the external system accounts;

[0146] Obtaining a preset authentication policy and authentication information used for authentication according to the self-created account; wherein the preset authentication policy is configured to include calling rules for multiple authentication services;

[0147] Based on the calling rule of the authentication service, the corresponding authentication service is called using the authentication information, and the login authentication result is determined according to the authentication feedback returned by the authentication service and returned to the client.

[0148] As a computer-readable storage medium, the memory can be used to store software programs, computer executable programs and modules, such as the program instructions / modules corresponding to the account login authentication method in the embodiment of the present application (for example, the self-built account acquisition module 501, the authentication policy acquisition module 503 and the authentication service call module 505 in the account login authentication device). The processor executes various functional applications and data processing of the electronic device by running the software programs, instructions and modules stored in the memory, that is, realizing the above-mentioned account login authentication method.

[0149] In the embodiments of the present application, the above-mentioned storage medium may include, but is not limited to: U disk, read-only memory (ROM), random access memory (RAM), mobile hard disk, magnetic disk or optical disk and other media that can store program code. Through the above description of the implementation method, the technicians in the relevant field can clearly understand that the present invention can be implemented with the help of software and necessary general hardware, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium.

[0150] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. An account login authentication method, characterized in that: include: Obtaining a login request, and obtaining a corresponding self-created account according to an input account in the login request; wherein the input account is an external system account held by the login personnel, and the self-created account has an associated relationship with at least one of the external system accounts; Obtaining a preset authentication policy and authentication information used for authentication according to the self-created account; wherein the preset authentication policy is configured to include calling rules for multiple authentication services; Based on the calling rule of the authentication service, the corresponding authentication service is called using the authentication information, and the login authentication result is determined according to the authentication feedback returned by the authentication service and returned to the client.

2. The account login authentication method according to claim 1, characterized in that: Before obtaining the login request and obtaining the corresponding self-created account according to the input account in the login request, the method further includes: Obtain the external system account of the login person; The external system account and the self-built account are mapped to each other, and the association relationship between the self-built account and at least one of the external system accounts is saved.

3. The account login authentication method according to claim 1, characterized in that: The method of calling the corresponding authentication service based on the calling rule of the authentication service using the authentication information, and determining the login authentication result according to the authentication feedback returned by the authentication service and returning it to the client includes: The authentication service includes application center authentication service, authority center authentication service and account center authentication service; Send an application authentication request to the application center to obtain the application authentication result; If the application authentication success information fed back by the application center is received, an account identity query request is sent to the permission center to obtain the account identity information; If the authentication account received from the authority center is a single-identity account, obtaining the authentication policy configured by the authority center; If the authentication policy configured by the authority center is obtained, the account authentication interface of the authority center is called to authenticate the authentication information; If a token is obtained after successful account authentication from the authority center, a self-owned token is generated based on the token and returned to the client.

4. The account login authentication method according to claim 3, characterized in that: After receiving the application authentication success information fed back by the application center and sending an account identity query request to the permission center to obtain the account identity information, the method further includes: If the authentication account received from the authority center is a multi-identity account, obtaining the authentication policy configured by the account center from the account center; If the authentication policy configured by the account center is obtained, the account authentication interface of the account center is called to authenticate the authentication information; If a token is obtained after successful account authentication from the account center, a self-owned token is generated based on the token and returned to the client.

5. The account login authentication method according to claim 4, characterized in that: After obtaining the authentication policy configured by the account center from the account center if the authentication account fed back by the authority center is a multi-identity account, the method further includes: If the authentication policy configured by the account center is not obtained, the default external system account is used as the authentication account to obtain the authentication policy configured by the authority center; If the authentication policy configured by the authority center is obtained, the account authentication interface of the authority center is called to authenticate the authentication information; If a token is obtained after successful account authentication from the authority center, a self-owned token is generated based on the token and returned to the client.

6. The account login authentication method according to claim 5, characterized in that: If the authentication policy configured by the authority center is not obtained, the method further includes: Obtain the authentication policy configured by the application center, and call the account authentication interface of the application center to authenticate the authentication information; If a token is obtained after successful account authentication from the application center, a self-owned token is generated based on the token and returned to the client.

7. The account login authentication method according to claim 3, characterized in that: After receiving the application authentication success information fed back by the application center and sending an account identity query request to the permission center to obtain the account identity information, the method further includes: If the abnormal account status information is received from the authority center, the authentication process ends, the authentication is determined to be unsuccessful, and the login authentication failure information is returned to the client.

8. An account login authentication device, characterized in that: include: A self-built account acquisition module, used to acquire a login request, and acquire a corresponding self-built account according to an input account in the login request; wherein the input account is an external system account held by the login personnel, and the self-built account has an associated relationship with at least one of the external system accounts; An authentication policy acquisition module is used to obtain a preset authentication policy and authentication information used for authentication based on the self-created account; wherein the preset authentication policy is configured to include calling rules for multiple authentication services; an authentication service calling module is used to call the corresponding authentication service based on the calling rules of the authentication service using the authentication information, determine the login authentication result based on the authentication feedback returned by the authentication service, and return it to the client.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored program, wherein the program executes the method according to any one of claims 1 to 7 when executed.

10. An electronic device comprising a memory and a processor, characterized in that: A computer program is stored in the memory, and the processor is configured to execute the method according to any one of claims 1 to 7 through the computer program.

Images