CN114567446A - Login authentication method and device, electronic equipment and storage medium - Google Patents

Login authentication method and device, electronic equipment and storage medium Download PDF

Info

Publication number
CN114567446A
CN114567446A CN202210199146.8A CN202210199146A CN114567446A CN 114567446 A CN114567446 A CN 114567446A CN 202210199146 A CN202210199146 A CN 202210199146A CN 114567446 A CN114567446 A CN 114567446A
Authority
CN
China
Prior art keywords
login authentication
component
login
user
logic
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.)
Granted
Application number
CN202210199146.8A
Other languages
Chinese (zh)
Other versions
CN114567446B (en
Inventor
张敏
卫彬
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ping An International Financial Leasing Co Ltd
Original Assignee
Ping An International Financial Leasing Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Ping An International Financial Leasing Co Ltd filed Critical Ping An International Financial Leasing Co Ltd
Priority to CN202210199146.8A priority Critical patent/CN114567446B/en
Publication of CN114567446A publication Critical patent/CN114567446A/en
Application granted granted Critical
Publication of CN114567446B publication Critical patent/CN114567446B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32Cryptographic 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
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/08Network architectures or network communication protocols for network security for authentication of entities

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Storage Device Security (AREA)
  • Stored Programmes (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The embodiment of the invention discloses a login authentication method, a login authentication device, electronic equipment and a storage medium, wherein the method comprises the following steps: acquiring a preset login authentication logic of a login authentication client; analyzing the login authentication node of the preset login authentication logic to generate a login authentication component according to the login authentication node; constructing a login authentication pipeline model of the login authentication client according to the preset login authentication logic and the login authentication component; and processing the login authentication instruction of the login authentication client according to the login authentication pipeline model so as to complete the login authentication process of the login authentication client. The technical scheme of the embodiment of the invention can decouple the login authentication logic of the login authentication system, thereby reducing the coupling degree of the login authentication logic and improving the maintainability of the login logic.

Description

Login authentication method and device, electronic equipment and storage medium
Technical Field
The embodiment of the invention relates to the technical field of safe login authentication, in particular to a login authentication method, a login authentication device, electronic equipment and a storage medium.
Background
Login authentication is a standard configuration of almost any system, such as a Web (World Wide Web) system, an app (application), a PC (Personal Computer) client, and the like, and many system applications basically require registration, login, and authorization authentication. Therefore, how to configure the login authentication logic with clear structure is particularly important for realizing intelligent login.
At present, a plurality of different types of common application login authentication modes exist. For example, the user may complete login authentication by registering an account and a password, or may complete login authentication by using preset login information such as a fingerprint and a gesture. Alternatively, the authentication may be directly registered by a secret-less registration method when a predetermined condition is satisfied.
However, the login authentication logic in the existing login authentication method often needs to be implemented by matching between the gateway service and the login authentication service, i.e. two services of the gateway and the login system need to be operated alternately, and needs to be implemented across services, and the login authentication logic has high overall coupling degree and is not easy to maintain.
Disclosure of Invention
Embodiments of the present invention provide a login authentication method and apparatus, an electronic device, and a storage medium, which can decouple a login authentication logic of a login authentication system, thereby reducing a coupling degree of the login authentication logic and improving maintainability of the login logic.
In a first aspect, an embodiment of the present invention provides a login authentication method, including:
acquiring a preset login authentication logic of a login authentication client;
analyzing the login authentication node of the preset login authentication logic to generate a login authentication component according to the login authentication node;
constructing a login authentication pipeline model of the login authentication client according to the preset login authentication logic and the login authentication component;
and processing the login authentication instruction of the login authentication client according to the login authentication pipeline model so as to complete the login authentication process of the login authentication client.
In a second aspect, an embodiment of the present invention further provides a login authentication apparatus, including:
the login authentication logic module is used for acquiring the preset login authentication logic of the login authentication client;
the login authentication component generation module is used for analyzing the login authentication node of the preset login authentication logic so as to generate a login authentication component according to the login authentication node;
the login authentication pipeline model building module is used for building a login authentication pipeline model of the login authentication client according to the preset login authentication logic and the login authentication component;
and the login authentication instruction processing module is used for processing the login authentication instruction of the login authentication client according to the login authentication pipeline model so as to complete the login authentication process of the login authentication client.
In a third aspect, an embodiment of the present invention further provides an electronic device, where the electronic device includes:
one or more processors;
storage means for storing one or more programs;
when executed by the one or more processors, cause the one or more processors to implement a login authentication method as provided by any of the embodiments of the invention.
In a fourth aspect, an embodiment of the present invention further provides a computer storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the login authentication method provided in any embodiment of the present invention.
According to the embodiment of the invention, after the preset login authentication logic of the login authentication client is obtained, the login authentication node of the preset login authentication logic is analyzed, so that the login authentication component is generated according to the login authentication node obtained through analysis, and the login authentication streamline model of the login authentication client is constructed according to the preset login authentication logic and the login authentication component, so that the login authentication instruction of the login authentication client is processed according to the constructed login authentication streamline model, the login authentication process of the login authentication client is completed, the problems of high login authentication logic coupling degree, poor maintainability and the like caused by the fact that the conventional login authentication process needs multi-party service alternate operation are solved, and the login authentication logic of a login authentication system can be decoupled, so that the coupling degree of the login authentication logic is reduced, and the maintainability of the login logic is improved.
Drawings
Fig. 1 is a flowchart of a login authentication method according to an embodiment of the present invention;
FIG. 2 is a diagram of a conventional password login authentication process for an account;
FIG. 3 is a diagram illustrating a conventional secondary login authentication process;
FIG. 4 is a schematic diagram of a prior art generic login authentication flow;
fig. 5 is a flowchart of a login authentication method according to a second embodiment of the present invention;
fig. 6 is a schematic structural diagram of a login authentication pipeline model according to a second embodiment of the present invention;
fig. 7 is a schematic diagram of a login authentication device according to a third embodiment of the present invention;
fig. 8 is a schematic structural diagram of an electronic device according to a fourth embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention.
It should be further noted that, for the convenience of description, only some but not all of the relevant aspects of the present invention are shown in the drawings. Before discussing exemplary embodiments in more detail, it should be noted that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although a flowchart may describe the operations (or steps) as a sequential process, many of the operations can be performed in parallel, concurrently or simultaneously. In addition, the order of the operations may be re-arranged. The process may be terminated when its operations are completed, but may have additional steps not included in the figure. The processes may correspond to methods, functions, procedures, subroutines, and the like.
The terms "first" and "second," and the like in the description and claims of embodiments of the invention and in the drawings, are used for distinguishing between different objects and not for describing a particular order. Furthermore, the terms "include" and "have," as well as any variations thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not set forth for a listed step or element but may include steps or elements not listed.
Example one
Fig. 1 is a flowchart of a login authentication method according to an embodiment of the present invention, where this embodiment is applicable to a case where a login authentication process is independently completed according to a login authentication pipeline model constructed by a login authentication component, and the method may be executed by a login authentication apparatus, and the apparatus may be implemented by software and/or hardware, and may be generally integrated in an electronic device, where the electronic device may be a terminal device or a server device, and is used in cooperation with a login authentication client for requesting login authentication. Accordingly, as shown in fig. 1, the method comprises the following operations:
s110, acquiring a preset login authentication logic of the login authentication client.
The login authentication client is also the client with the login authentication requirement. It can be understood that any client that needs a user login authentication operation may be used as a login authentication client, as long as a certain login authentication logic exists, and the embodiment of the present invention does not limit the type of the client that logs in to the authentication client. That is, the login authentication client may be an APP client, or a web page client. The preset login authentication logic may be a login authentication logic preset by the login authentication client, and may be used to authenticate the login information of the user. The login authentication logic may be understood as a flow of login authentication. It will be appreciated that the pre-established login authentication logic may comprise a number of different types, depending on the login authentication scenario.
In the embodiment of the invention, in order to solve the problem of higher coupling degree of the login authentication process caused by the alternate operation of different services, an independent login authentication service can be adopted to process the login authentication process of the login authentication client. The independent login authentication service can be deployed in the electronic equipment, has the capability of independently processing the login authentication process of any login authentication client, and can provide a modularized and configurable login authentication processing function for the login authentication client needing login authentication processing.
Correspondingly, the login authentication service can acquire the preset login authentication logic of the login authentication client, so as to process the subsequent login authentication process of the login authentication client according to the preset login authentication logic of the login authentication client.
S120, analyzing the login authentication node of the preset login authentication logic to generate a login authentication component according to the login authentication node.
The login authentication node is also understood to be each processing node in the preset login authentication logic, and may also be each processing link in the preset login authentication logic, such as an account secret verification node or an equipment verification node. The login authentication component can be a component with the node function of the login authentication node, and each login authentication component can correspondingly complete the login authentication sub-logic which is responsible for one login authentication node. The login authentication sub-logic is also the processing logic of a single processing node or processing link in the preset login authentication logic.
It will be appreciated that a complete pre-provisioned login authentication logic may typically comprise a plurality of different processing nodes. Fig. 2 is a schematic diagram of a conventional account password login authentication process, and fig. 3 is a schematic diagram of a conventional secondary login authentication process, in a specific example, as shown in fig. 2 and fig. 3, in the conventional login authentication processes, each of the conventional login authentication processes may include a plurality of login authentication nodes, such as an account password verification node, a trusted device verification node, a token issuance node, and the like, and different login authentication nodes may complete one of processing links in a login authentication logic. Meanwhile, in the existing login authentication process, the login authentication gateway and the login authentication service need to interact to complete the complete login authentication process. For example, the node function of the login authentication node verified by the trusted device needs to be independently completed by the login authentication gateway, and the node functions of other login authentication nodes need to be realized by the login authentication gateway scheduling login authentication service function of the login authentication client. The login authentication service of the login authentication client may be a type of micro service.
Fig. 4 is a schematic diagram of a conventional general login authentication flow. In a specific example, as shown in fig. 4, in a normal login authentication process, the login authentication client needs to send a login authentication command to the login authentication gateway, and the login authentication gateway invokes the login authentication service to authenticate the login authentication command. The login authentication service needs to send a request to a login authentication system background (a system background corresponding to the login authentication client) to request to acquire an ID number, and the login authentication system background can return the request ID to the login authentication service. Furthermore, the login authentication gateway calls the login authentication service to send an authentication request to the login authentication system background, and the login authentication system background can return an authentication result. After obtaining the authorization result, the login authentication service can judge the type of a login authentication client, such as an APP client or a PC client, and further obtain login information according to the judgment result of the login authentication client and feed the login information back to the front end; the login information, that is, the user association information, may be, for example, an identifier of the user and a department to which the user belongs.
In summary, in the existing login authentication process, due to the high coupling degree between the login authentication nodes, data interaction is frequently performed between the login authentication gateway and the login authentication service of the login authentication client. If the login authentication gateway accesses a new login authentication service, a login authentication flow needs to be created again, or the login authentication gateway needs to be adaptively changed, so that the login authentication cost is high.
In order to solve the above problem, in the embodiments of the present invention, a login authentication gateway and a login authentication service of a login authentication client are integrated by an independent login authentication service, and a login authentication node of a preset login authentication logic is analyzed, so as to generate a login authentication component related to the preset login authentication logic according to an analysis result. Each login authentication node can correspondingly generate a login authentication component, and each login authentication component has a configurable function. That is, the login authentication service is a configurable and componentized service, and each login authentication node in the preset login authentication logic can be decoupled, and packaging is realized in a component form. Each login authentication component can independently complete the node function of the corresponding login authentication node without data interaction with the login authentication gateway.
As shown in fig. 2 or fig. 3, a login authentication node verified by a trusted device may correspondingly generate a trusted device verification component, where the trusted device verification component is one of components created by a login authentication service for a certain preset login authentication logic, and may independently verify the trust level of the login device where a login authentication client is located. Meanwhile, the trusted device verification component is configurable, and can be configured with rules or parameters and the like for verifying the credibility of the login device where the login authentication client is located, so as to flexibly meet verification requirements of different types of trusted devices.
S130, a login authentication pipeline model of the login authentication client is built according to the preset login authentication logic and the login authentication component.
The login authentication pipeline model may be a model obtained by logically combining the login authentication components.
And S140, processing the login authentication instruction of the login authentication client according to the login authentication pipeline model so as to complete the login authentication process of the login authentication client.
Correspondingly, after the corresponding login authentication component is generated for the login authentication node of the preset login authentication logic, the login authentication service can construct a login authentication pipeline model matched with the preset login authentication logic of the login authentication client according to the acquired preset login authentication logic and the generated login authentication components. It will be appreciated that one type of predetermined login authentication logic may correspond to a matching login authentication pipeline model being generated. The login authentication service can process a login authentication instruction initiated by the login authentication client under the preset login authentication logic according to the login authentication pipeline model, so that a login authentication process of the login authentication client is completed.
For example, the first two login authentication components of the login authentication pipeline model are an account and password verification component and a trusted device verification component, and the login authentication service may first invoke the account and password verification component to verify a user account and a password sent by the login authentication client, and invoke the trusted device verification component to verify the reliability of the login device where the login authentication client is located after the verification is passed. That is, the login authentication service may complete a login authentication procedure of the login authentication client for the preset login authentication logic according to the component processing result and the component circulation sequence of each login authentication component in the login authentication pipeline model. When the node function of a certain login authentication node of the preset login authentication logic needs to be changed or updated, a specific login authentication component in the corresponding login authentication pipeline model can be positioned, the configuration information of the login authentication component is updated, other services do not need to be changed, and the maintainability of the login logic is improved.
Therefore, the login authentication process of the login authentication client is processed through the independent login authentication service, the alternate operation process of a plurality of different services can be avoided, the login authentication process can be uniformly packaged into the independent login authentication service, the consistency of the overall login authentication logic of the login authentication client is kept through a login authentication pipeline model constructed by the modularized and configurable login authentication component, the coupling degree of the login authentication logic can be reduced, and the maintainability of the login authentication logic can be improved through the unified login authentication service and the decoupled login authentication component.
According to the embodiment of the invention, after the preset login authentication logic of the login authentication client is obtained, the login authentication node of the preset login authentication logic is analyzed, the login authentication component is generated according to the login authentication node obtained through analysis, and the login authentication streamline model of the login authentication client is constructed according to the preset login authentication logic and the login authentication component, so that the login authentication instruction of the login authentication client is processed according to the constructed login authentication streamline model, the login authentication process of the login authentication client is completed, the problems of high login authentication logic coupling degree, poor maintainability and the like caused by the fact that the conventional login authentication process needs multi-party service alternate operation are solved, the login authentication logic of the login authentication system can be decoupled, the coupling degree of the login authentication logic is reduced, and the maintainability of the login logic is improved.
Example two
Fig. 5 is a flowchart of a login authentication method according to a second embodiment of the present invention, which is embodied on the basis of the second embodiment, and in this embodiment, various specific optional implementation manners of generating a login authentication component according to the login authentication node and constructing a login authentication pipeline model of the login authentication client according to the preset login authentication logic and the login authentication component are provided. Correspondingly, as shown in fig. 5, the method of this embodiment may include:
s210, acquiring a preset login authentication logic of the login authentication client.
And S220, analyzing the node execution function of the login authentication node.
The node execution function is also the node function that the login authentication node can complete. Illustratively, the node execution function of the login authentication node may be, for example, a secret account verification function, a trusted device verification function, a short message verification code verification function, a user information acquisition function, and a token issuance sub-function of each login authentication.
S230, configuring the component configuration function of the login authentication component according to the node execution function.
The component configuration function is also a component function configured for the login authentication component. It can be understood that the component configuration function of the login authentication component matches the node execution function of the corresponding login authentication node, for example, the account density verification function of the account density verification component can be configured according to the account density verification function of the account density verification node, so that the account density verification component can implement an account density verification link for presetting login authentication logic.
S240, generating the login authentication component according to the component configuration function.
And the generation login authentication component is used for completing the node execution function.
In the embodiment of the invention, after the login authentication service analyzes and obtains each login authentication node in the preset login authentication logic, the node execution function of each login authentication node can be further analyzed so as to know the sub-logic which needs to be completed in the whole preset login authentication logic by each login authentication node. Correspondingly, the login authentication service can generate corresponding configuration information according to the node execution function of each login authentication node, and configure the component configuration function of the corresponding login authentication component according to the configuration information, so that the login authentication component matched with each login authentication node is generated according to the configured component configuration function.
For example, for the login authentication node for account and password authentication, the login authentication service analyzes the node execution function of the login authentication node to verify the account and password of the user, and then the login authentication service may generate configuration information of the account and password authentication component according to the node execution function of the login authentication node for account and password authentication, and configure the component configuration function of the account and password authentication component according to the generated configuration information. For example, an algorithm or the like used by the account number and password verification component to verify the account number and password of the user may be configured. After the account and password verification component completes the component configuration function, the account and password verification component can take effect.
S250, determining the component calling sequence of the login authentication component according to the preset login authentication logic.
The component calling sequence is also the calling sequence of the login authentication service to each login authentication component.
After the login authentication service generates each login authentication component required by the preset login authentication logic, the execution sequence of the login authentication nodes of the preset login authentication logic can be further analyzed, so that the component calling sequence of each login authentication component is determined according to the execution sequence of each login authentication node.
In an optional embodiment of the present invention, the determining, according to the preset login authentication logic, a component calling order of the login authentication component may include: determining a component execution condition of the login authentication component and a common parameter set of the component execution condition according to the preset login authentication logic; determining a combination relation between the login authentication component and component execution parameters in the public parameter set according to the preset login authentication logic to obtain a component parameter integration module; and arranging and configuring the component parameter integration module according to the component execution condition to obtain a component calling sequence of the login authentication component.
Wherein the component execution condition may be an execution condition of the login authentication component. The common parameter set may be a set for storing login authentication component execution result parameters. Alternatively, the number of common parameter sets may be at least one. When the number of the common parameter sets is one, the component execution result parameters of all the login authentication components can be uniformly stored. The component execution parameter is also a component execution result parameter, optionally, the component execution parameter may be a configurable variable parameter, that is, a value of the component execution parameter may be at least one. A common parameter set may store a plurality of component execution parameters, and each login authentication component may configure one or more component execution parameters, which is not limited by the embodiment of the present invention. The component parameter integration module can be an independent module formed by integrating the login authentication component and the component execution parameter.
Specifically, when determining the component calling order of the login authentication component, the component execution condition of each login authentication component and the common parameter set matched with the component execution condition may be determined according to a preset login authentication logic. Illustratively, the component execution condition of the trusted device verification component is to perform a trust verification on the login device where the login authentication client is located. And the component execution parameters of the trusted device verification component can be configured as deviceSuccess and deviceFail. The deviceSuccess may be a component that executes a parameter for verifying the credibility of the login device where the login authentication client is located, and represents that the parameter can be called by other components only after the credible device is successfully verified. The deviceFail may be a component execution parameter for a login device where the login authentication client is not verified by the credibility, and represents that the component execution parameter can be called by other components after the credible device is failed to be verified.
Correspondingly, after the component execution condition of the login authentication component and the common parameter set of the component execution condition are determined, the combination relationship between each login authentication component and each component execution parameter in the common parameter set can be further determined according to the preset login authentication logic, and the component parameter integration module is obtained. Optionally, the subsequent login authentication component may be combined with the component execution parameter of the preceding login authentication component to obtain an integrated component parameter integration module. After all the component parameter integration modules are completed, the login authentication service can arrange and configure each component parameter integration module according to the component execution conditions to obtain a component calling sequence matched with the login authentication component.
Fig. 6 is a schematic structural diagram of a login authentication pipeline model according to a second embodiment of the present invention. In a specific example, as shown in fig. 6, the login authentication pipeline model may be configured by "login authentication components (unchangeable components) + (component execution conditions)" being component execution parameters (that is, component execution results, results are sharable), "combining a plurality of login authentication components and component execution parameters into a plurality of component parameter integration modules," arranging and configuring each component parameter integration module by using the component execution conditions, and assembling and splicing into one processing flow.
For different preset login authentication logics, the calling sequence of the login authentication component and the login authentication component is not invariable, for example, after the verification of the trusted device fails, a short message token needs to be called in the secret login authentication logic, and the login authentication request is directly ended in secondary login authentication logics such as gestures/fingerprints. In order to solve the above problem, a common parameter set is configured in the login authentication pipeline model to store component execution parameters of the login authentication component. For example, when the verification of the trusted device fails, a deviceFail parameter may be configured on the login authentication component issuing the short message token, which represents that the deviceFail parameter is invoked only after the trusted device fails. If certain conditions do not require a pre-determination condition of the trusted device, the parameter may be removed. That is, the relationship between the login authentication component and the login authentication component may be completed through the common parameter set, and specifically, the component execution parameter of the previous login authentication component may be stored in the common parameter set for the subsequent login authentication component to invoke.
Meanwhile, a TAIL end of the login authentication pipeline model can be also configured with a TAIL component (a TAIL end node component), which is the last system public component of the login authentication pipeline model and can be configured with global attribute data to carry out the final processing on the login authentication process. It should be noted that the login authentication component is a single instance, and may be injected into spring (an open source framework) in the form of component, so that support of other instances may be more conveniently obtained.
S260, building a login authentication pipeline model of the login authentication client according to the component calling sequence and the login authentication component.
Correspondingly, after the login authentication service determines the component calling sequence of each login authentication component, the login authentication components can be assembled and spliced according to the component calling sequence of each login authentication component, and a login authentication pipeline model matched with the preset login authentication logic in the login authentication client is obtained.
And S270, processing the login authentication instruction of the login authentication client according to the login authentication pipeline model so as to complete the login authentication process of the login authentication client.
In an optional embodiment of the present invention, the preset login authentication logic may include account password login authentication logic; the login authentication pipeline model can comprise an account password login authentication pipeline model; the processing the login authentication instruction of the login authentication client according to the login authentication pipeline model may include: calling a decryption component to decrypt the account password login authentication instruction to obtain a first instruction decryption result; calling a login authentication interface component to verify the user account and the user password included in the first instruction decryption result; calling a user identity confirmation component to verify the dynamic authentication information input by the user under the condition that the login authentication interface component verifies the first instruction decryption result; under the condition that the user identity confirmation component is confirmed to pass the verification, calling a trusted device verification component to verify the credibility of the current device of the user; under the condition that the trusted equipment verification component is determined not to pass the verification, calling a short message authentication request component to generate a short message authentication instruction matched with the login authentication instruction so as to enable a user to feed back short message authentication information according to the short message authentication instruction, calling a short message verification component to verify the short message authentication information, and under the condition that the short message verification component is determined to pass the verification, calling a user information acquisition component to acquire user associated information; under the condition that the trusted equipment verification component is confirmed to pass the verification, the user information acquisition component is called to acquire the user associated information; and calling a token generation component to generate a login authentication token matched with the login authentication instruction, and sending login success feedback information to the user.
The login authentication logic of the account and the password is also logic for performing login authentication through the account and the password of the user. The account password login authentication pipeline model is also a login authentication pipeline model constructed according to the account password login authentication logic and each login authentication component of the account password login authentication logic. The decryption component may be a login authentication component that decrypts information sent by the login authentication client, and related data for decryption, such as a decryption algorithm and a decryption key, may be configured in the decryption component. The first instruction decryption result may be a result obtained by the decryption component decrypting the account password login authentication instruction of the user. The login authentication interface component can authenticate the login authentication information of the user so as to authorize and authenticate the user. The user identity confirmation component may be used to confirm whether the user is a real identity. The dynamic authentication information, that is, the authentication information dynamically input by the user, may be operation information of a certain operation object, such as drag operation of a slider, or may also be information of dynamically input characters, voice, and the like. The short message authentication request component can be used for sending a short message authentication request to the login authentication client so as to authenticate the user in a short message mode. The user information obtaining component may be configured to obtain user association information, for example, the user association information may be a contact information of a mobile phone, a mailbox, and the like of a user or other associated information, and the embodiment of the present invention does not limit the information type and the information content of the user association information. Invoking the token generation component may generate a dedicated login authentication token for the user, which may implement a single sign-on function.
Specifically, if the preset login authentication logic is an account password login authentication logic, the account password login authentication pipeline model may be constructed by login authentication components such as a decryption component, a login authentication interface component, a user identity confirmation component, a trusted device verification component, a short message authentication request component, a user information acquisition component, a token generation component, and the like, which are generated according to each login authentication node of the account password login authentication logic. In the account password login authentication pipeline model, the component execution parameters of each login authentication component can be called by the next login authentication component. It is to be understood that the component execution parameters of the login authentication component are different, as can the subsequently invoked login authentication component. Correspondingly, under the condition that each login authentication component is normally transferred, the calling sequence of each login authentication component in the account password login authentication pipeline model can be as follows: the system comprises a decryption component, a login authentication interface component, a user identity confirmation component, a trusted device verification component, a short message authentication request component, a user information acquisition component and a token generation component.
That is, the specific flow of processing the login authentication instruction of the login authentication client according to the account password login authentication pipeline model may be as follows: the method comprises the steps that firstly, an account password login authentication instruction is decrypted through a decryption component to obtain a first instruction decryption result, the first instruction decryption result is also the component execution parameter of the decryption component, and then a login authentication interface component is called to verify a user account and a user password which are included in the first instruction decryption result. If the login authentication interface component is confirmed to pass the verification of the decryption result of the first instruction, the user identity confirmation component can be called to verify the dynamic authentication information input by the user; otherwise, determining that the user of the login authentication client does not have the login authentication authority, directly refusing the login authentication request, and failing to perform the login authentication of the user. For example, the user identification confirmation component may be a slider component, and the user recognizes whether the current operation object is a user or a machine device by performing a slider alignment operation on the slider component to input dynamic authentication information. The user identity confirmation component can also be a short message authentication request component, and the user can input a corresponding verification code as dynamic authentication information to confirm the identity of the user through a short message authentication operation initiated by the short message authentication request component. Correspondingly, if the user identity confirmation component is confirmed to pass the verification, the trusted device verification component can be continuously called to verify the credibility of the current device of the user. Further, if the trusted device verification component is determined not to pass the verification, the short message authentication request component can be invoked to generate a short message authentication instruction matched with the login authentication instruction, so that the user feeds back the short message authentication information according to the short message authentication instruction, and the short message verification component is invoked to verify the short message authentication information. If the short message verification component is determined to pass the verification, the user information acquisition component can be called to acquire user associated information; if the trusted device verification component is confirmed to pass the verification, the user information acquisition component can be directly called to acquire the user associated information without a short message authentication process. Meanwhile, after the trusted device verification component verifies and acquires the user association information, the token generation component can be further called to generate a login authentication token matched with the login authentication instruction, and login success feedback information is sent to the user. It will be appreciated that the login authentication token may be used by the login authentication service to perform subsequent single-sign-on functions for the user.
It should be noted that the short message authentication information may include a post-string encrypted by a real password + a login type, and the encrypted secret key is different from a secret key required by the decryption component and needs to be replaced periodically, so as to call the login authentication interface component to log in order to obtain the real password during the secondary login.
In an optional embodiment of the present invention, the preset login authentication logic may comprise non-first-login authentication logic; the login authentication pipeline model may comprise a non-first-login authentication pipeline model; the processing the login authentication instruction of the login authentication client according to the login authentication pipeline model may include: a decryption component is called to decrypt the user characteristic login authentication instruction to obtain a second instruction decryption result; calling a trusted device verification component to verify the credibility of the current device of the user; calling a user characteristic verification component to verify the second instruction decryption result under the condition that the trusted equipment verification component is determined to pass the verification; under the condition that the user characteristic verification component is confirmed to pass the verification, a login authentication interface component is called to verify a user account and a user password which are included in the second instruction decryption result; calling a user information acquisition component to acquire user associated information under the condition that the login authentication interface component is determined to pass the verification of the second instruction decryption result; and calling a token generation component to generate a login authentication token matched with the login authentication instruction, and sending login success feedback information to the user.
The non-first-time login authentication logic can be secondary login authentication logic, in the secondary login authentication process, a user can realize login by adopting a user characteristic login authentication instruction which can uniquely reflect the user characteristic such as a fingerprint or a gesture, and the login authentication is carried out without inputting an account and a password by the user. The non-initial login authentication pipeline model is a login authentication pipeline model constructed according to the non-initial login authentication logic and each login authentication component of the non-initial login authentication logic. It can be understood that, before processing the login authentication instruction of the login authentication client according to the non-first-time login authentication pipeline model, the login authentication instruction of the login authentication client needs to be processed according to the account password login authentication pipeline model, and in the process of processing the login authentication instruction of the login authentication client by the account password login authentication pipeline model, the binding mapping relationship between the user account password and the user characteristic login authentication instruction is established. The second instruction decryption result may be a result obtained by the decryption component decrypting a user characteristic login authentication instruction (such as a gesture instruction, a voice instruction, an image instruction, or a fingerprint instruction), and the result may bind a mapping relationship between a user characteristic (such as a gesture, a voice, an image, or a fingerprint) and a user account password, so as to quickly locate user account password information according to the user characteristic. The user characteristic verification component may be configured to verify a user characteristic login authentication instruction included in the second instruction decryption result.
Specifically, if the preset login authentication logic is non-initial login authentication logic, the non-initial login authentication pipeline model may be constructed according to login authentication components such as a decryption component, a trusted device verification component, a user characteristic verification component, a login authentication interface component, a user information acquisition component, a token generation component, and the like, which are generated by each login authentication node of the non-initial login authentication logic. In the non-first-sign-on authentication pipeline model, the component execution parameters of each sign-on authentication component may be invoked by the next sign-on authentication component. It is to be understood that the component execution parameters of the login authentication component are different, as can the subsequently invoked login authentication component. Correspondingly, under the condition that each login authentication component normally transfers calls, the calling sequence of each login authentication component in the non-first-time login authentication pipeline model can be as follows: the system comprises a decryption component, a trusted device verification component, a user characteristic verification component, a login authentication interface component, a user information acquisition component and a token generation component.
That is, the specific flow of processing the login authentication instruction of the login authentication client according to the non-initial login authentication pipeline model may be: firstly, the user characteristic login authentication instruction is decrypted through the decryption component to obtain a second instruction decryption result, and the second instruction decryption result is also the component execution parameter of the decryption component. Further, a trusted device verification component may be invoked to verify the trustworthiness of the current device of the user. If the trusted device verification component is confirmed to pass the verification, the user characteristic verification component can be called to verify the second instruction decryption result, specifically, the user characteristics included in the second instruction decryption result are verified, and the login authentication interface component is called to continuously verify the user account and the user password included in the second instruction decryption result under the condition that the user characteristic verification component is confirmed to pass the verification. If the login authentication interface component is determined to pass the verification of the second instruction decryption result, the user information acquisition component can be called to acquire the user association information. If the trusted device verification component is determined not to pass the verification, and/or the user characteristic verification component is determined not to pass the verification, the login authentication request can be directly refused, and the login authentication of the user fails. After the user association information is obtained, the token generation component can be called to generate a login authentication token matched with the login authentication instruction, and login success feedback information is sent to the user. It will be appreciated that the login authentication token may be used by the login authentication service to perform subsequent single-sign-on functions for the user.
In an optional embodiment of the present invention, the preset login authentication logic may further include a secret-free login authentication logic; the login authentication pipeline model may comprise a password-free login authentication pipeline model; the processing the login authentication instruction of the login authentication client according to the login authentication pipeline model may include: calling a token verification component to obtain a login authentication token carried by a password-free login authentication instruction, and verifying the validity of the login authentication token; and under the condition that the login authentication token is confirmed to pass the validity check, confirming that the login authentication of the user is successful, and sending login success feedback information to the user.
The secret-free login authentication logic does not need to check any information of the user, and the user can directly realize the logic of login authentication. The secret-free login authentication pipeline model is a login authentication pipeline model constructed according to the secret-free login authentication logic and each login authentication component of the secret-free login authentication logic. It can be understood that, before processing the login authentication instruction of the login authentication client according to the password-free login authentication pipeline model, the user is required to complete the login authentication process through the login authentication client within a certain time limit to obtain the login authentication token, so as to directly realize the password-free login authentication mode according to the login authentication token. The token verification component may be a login authentication component that verifies the validity of the login authentication token. The password-free login authentication instruction can be a login authentication instruction type triggered by a user through a login authentication client.
Specifically, if the login authentication logic is preset to be a secret-free login authentication logic, the token verification component may be generated according to a login authentication node of the secret-free login authentication logic. Accordingly, the secure login-free authentication pipeline model may consist of only a token verification component. The specific flow of processing the login authentication instruction of the login authentication client according to the password-free login authentication pipeline model can be as follows: and directly calling a token verification component to obtain a login authentication token carried by the password-free login authentication instruction, and checking the validity of the login authentication token. Under normal conditions, the login authentication token can be provided with an expiration date, and if the accumulated use time of the login authentication token does not exceed the expiration date, the login authentication token can be considered to be valid; otherwise, the login authentication token is considered invalid. Correspondingly, if the login authentication token is confirmed to pass the validity check, the login authentication success of the user can be directly confirmed, and the login success feedback information is sent to the user.
According to the technical scheme, after the preset login authentication logic of the login authentication client is obtained, analyzing the login authentication node of the preset login authentication logic to generate a login authentication component according to the login authentication node obtained by analysis, and a login authentication pipeline model of the login authentication client is constructed according to the preset login authentication logic and the login authentication component, therefore, the login authentication instruction of the login authentication client is processed according to the constructed login authentication pipeline model, the login authentication process of the login authentication client is completed, the problems that the existing login authentication process needs multi-party service alternate operation, the login authentication logic coupling degree is high, the maintainability is poor and the like are solved, the login authentication logic of the login authentication system can be decoupled, the coupling degree of the login authentication logic is reduced, and the maintainability of the login logic is improved.
It should be noted that any permutation and combination between the technical features in the above embodiments also belong to the scope of the present invention.
EXAMPLE III
Fig. 7 is a schematic diagram of a login authentication apparatus according to a third embodiment of the present invention, and as shown in fig. 7, the apparatus includes: a login authentication logic module 310, a login authentication component generation module 320, a login authentication pipeline model construction module 330, and a login authentication instruction processing module 340, wherein:
a login authentication logic module 310, configured to obtain a preset login authentication logic of a login authentication client;
a login authentication component generation module 320, configured to parse a login authentication node of the preset login authentication logic, so as to generate a login authentication component according to the login authentication node;
a login authentication pipeline model building module 330, configured to build a login authentication pipeline model of the login authentication client according to the preset login authentication logic and the login authentication component;
and the login authentication instruction processing module 340 is configured to process a login authentication instruction of the login authentication client according to the login authentication pipeline model, so as to complete a login authentication process of the login authentication client.
According to the embodiment of the invention, after the preset login authentication logic of the login authentication client is obtained, the login authentication node of the preset login authentication logic is analyzed, the login authentication component is generated according to the login authentication node obtained through analysis, and the login authentication streamline model of the login authentication client is constructed according to the preset login authentication logic and the login authentication component, so that the login authentication instruction of the login authentication client is processed according to the constructed login authentication streamline model, the login authentication process of the login authentication client is completed, the problems of high login authentication logic coupling degree, poor maintainability and the like caused by the fact that the conventional login authentication process needs multi-party service alternate operation are solved, the login authentication logic of the login authentication system can be decoupled, the coupling degree of the login authentication logic is reduced, and the maintainability of the login logic is improved.
Optionally, the login authentication component generating module 320 is specifically configured to: analyzing the node execution function of the login authentication node; configuring a component configuration function of the login authentication component according to the node execution function; generating the login authentication component according to the component configuration function; and the generation login authentication component is used for completing the node execution function.
Optionally, the login authentication pipeline model building module 330 is specifically configured to: determining a component calling sequence of the login authentication component according to the preset login authentication logic; and constructing a login authentication pipeline model of the login authentication client according to the component calling sequence and the login authentication component.
Optionally, the login authentication pipeline model building module 330 is specifically configured to: determining a component execution condition of the login authentication component and a common parameter set of the component execution condition according to the preset login authentication logic; determining a combination relation between the login authentication component and component execution parameters in the public parameter set according to the preset login authentication logic to obtain a component parameter integration module; and arranging and configuring the component parameter integration module according to the component execution condition to obtain a component calling sequence of the login authentication component.
Optionally, the preset login authentication logic includes an account password login authentication logic; the login authentication pipeline model comprises an account password login authentication pipeline model; the login authentication instruction processing module 340 is specifically configured to: calling a decryption component to decrypt the account password login authentication instruction to obtain a first instruction decryption result; calling a login authentication interface component to verify the user account and the user password included in the first instruction decryption result; calling a user identity confirmation component to verify the dynamic authentication information input by the user under the condition that the login authentication interface component verifies the first instruction decryption result; calling a trusted device verification component to verify the credibility of the current device of the user under the condition that the user identity confirmation component is confirmed to pass the verification; under the condition that the trusted equipment verification component is determined not to pass the verification, calling a short message authentication request component to generate a short message authentication instruction matched with the login authentication instruction so as to enable a user to feed back short message authentication information according to the short message authentication instruction, calling a short message verification component to verify the short message authentication information, and under the condition that the short message verification component is determined to pass the verification, calling a user information acquisition component to acquire user associated information; under the condition that the trusted equipment verification component is confirmed to pass the verification, calling the user information acquisition component to acquire the user associated information; and calling a token generation component to generate a login authentication token matched with the login authentication instruction, and sending login success feedback information to the user.
Optionally, the preset login authentication logic includes non-first login authentication logic; the login authentication pipeline model comprises a non-first login authentication pipeline model; the login authentication instruction processing module 340 is specifically configured to: calling a decryption component to decrypt the user characteristic login authentication instruction to obtain a second instruction decryption result; calling a trusted device verification component to verify the credibility of the current device of the user; calling a user characteristic verification component to verify the second instruction decryption result under the condition that the trusted equipment verification component is determined to pass the verification; under the condition that the user characteristic verification component is confirmed to pass the verification, a login authentication interface component is called to verify a user account and a user password which are included in the second instruction decryption result; calling a user information acquisition component to acquire user associated information under the condition that the login authentication interface component is determined to pass the verification of the second instruction decryption result; and calling a token generation component to generate a login authentication token matched with the login authentication instruction, and sending login success feedback information to the user.
Optionally, the preset login authentication logic includes a secret-free login authentication logic; the login authentication pipeline model comprises a secret-free login authentication pipeline model; the login authentication instruction processing module 340 is specifically configured to: calling a token verification component to obtain a login authentication token carried by a password-free login authentication instruction, and verifying the validity of the login authentication token; and under the condition that the login authentication token is confirmed to pass the validity check, confirming that the login authentication of the user is successful, and sending login success feedback information to the user.
The login authentication device can execute the login authentication method provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method. For technical details that are not described in detail in this embodiment, reference may be made to a login authentication method provided in any embodiment of the present invention.
Since the login authentication device described above is a device capable of executing the login authentication method in the embodiment of the present invention, based on the login authentication method described in the embodiment of the present invention, a person skilled in the art can understand the specific implementation of the login authentication device in the embodiment and various variations thereof, and therefore, how the login authentication device implements the login authentication method in the embodiment of the present invention is not described in detail herein. As long as those skilled in the art implement the device used in the login authentication method in the embodiments of the present invention, the device is within the scope of the present application.
Example four
Fig. 8 is a schematic structural diagram of an electronic device according to a fourth embodiment of the present invention. FIG. 8 illustrates a block diagram of an exemplary electronic device 12 suitable for use in implementing embodiments of the present invention. The electronic device 12 shown in fig. 8 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiment of the present invention.
As shown in FIG. 8, electronic device 12 is embodied in the form of a general purpose computing device. The components of electronic device 12 may include, but are not limited to: one or more processors 16, a memory 28, and a bus 18 that connects the various system components (including the memory 28 and the processors 16).
Bus 18 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, such architectures can include, but are not limited to, an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MCA) bus, an enhanced ISA bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnect (PCI) bus.
Electronic device 12 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by electronic device 12 and includes both volatile and nonvolatile media, removable and non-removable media.
Memory 28 may include computer system readable media in the form of volatile Memory, such as Random Access Memory (RAM) 30 and/or cache Memory 32. The electronic device 12 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 34 may be used to read from and write to non-removable, nonvolatile magnetic media (not shown in FIG. 8, and commonly referred to as a "hard drive"). Although not shown in FIG. 8, a magnetic disk drive for reading from and writing to a removable, nonvolatile magnetic disk (e.g., a "floppy disk") and an optical disk drive for reading from or writing to a removable, nonvolatile optical disk (e.g., a Compact disk-Read Only Memory (CD-ROM), digital video disk (DVD-ROM), or other optical media) may be provided. In these cases, each drive may be connected to bus 18 by one or more data media interfaces. Memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.
A program/utility 40 having a set (at least one) of program modules 42 may be stored, for example, in memory 28, such program modules 42 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which examples or some combination thereof may comprise an implementation of a network environment. Program modules 42 generally carry out the functions and/or methodologies of the described embodiments of the invention.
Electronic device 12 may also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, etc.), with one or more devices that enable a user to interact with electronic device 12, and/or with any devices (e.g., network card, modem, etc.) that enable electronic device 12 to communicate with one or more other computing devices. Such communication may be through an Input/Output (I/O) interface 22. Also, the electronic device 12 may communicate with one or more networks (e.g., a Local Area Network (LAN), Wide Area Network (WAN)) and/or a public Network (e.g., the Internet) via the Network adapter 20. As shown, the network adapter 20 communicates with other modules of the electronic device 12 via the bus 18. It should be appreciated that although not shown in FIG. 8, other hardware and/or software modules may be used in conjunction with electronic device 12, including but not limited to: microcode, device drivers, Redundant processing units, external disk drive Arrays, (Redundant Arrays of Independent Disks, RAID) systems, tape drives, and data backup storage systems, to name a few.
The processor 16 executes various functional applications and data processing by running the program stored in the memory 28, thereby implementing the login authentication method provided by the embodiment of the present invention: acquiring a preset login authentication logic of a login authentication client; analyzing the login authentication node of the preset login authentication logic to generate a login authentication component according to the login authentication node; constructing a login authentication pipeline model of the login authentication client according to the preset login authentication logic and the login authentication component; and processing the login authentication instruction of the login authentication client according to the login authentication pipeline model so as to complete the login authentication process of the login authentication client.
EXAMPLE five
An embodiment of the present invention further provides a computer storage medium storing a computer program, where the computer program is used to execute the login authentication method according to any one of the above embodiments of the present invention when executed by a computer processor: acquiring a preset login authentication logic of a login authentication client; analyzing the login authentication node of the preset login authentication logic to generate a login authentication component according to the login authentication node; constructing a login authentication pipeline model of the login authentication client according to the preset login authentication logic and the login authentication component; and processing the login authentication instruction of the login authentication client according to the login authentication pipeline model so as to complete the login authentication process of the login authentication client.
Computer storage media for embodiments of the invention may employ any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a Read Only Memory (ROM), an Erasable Programmable Read Only Memory (EPROM, or flash Memory), an optical fiber, a portable compact disc Read Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, Radio Frequency (RF), etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. Those skilled in the art will appreciate that the present invention is not limited to the particular embodiments described herein, and that various obvious changes, rearrangements and substitutions will now be apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims (10)

1. A login authentication method, comprising:
acquiring a preset login authentication logic of a login authentication client;
analyzing the login authentication node of the preset login authentication logic to generate a login authentication component according to the login authentication node;
constructing a login authentication pipeline model of the login authentication client according to the preset login authentication logic and the login authentication component;
and processing the login authentication instruction of the login authentication client according to the login authentication pipeline model so as to complete the login authentication process of the login authentication client.
2. The method of claim 1, wherein parsing the login authentication node of the preset login authentication logic to generate a login authentication component according to the login authentication node comprises:
analyzing the node execution function of the login authentication node;
configuring a component configuration function of the login authentication component according to the node execution function;
generating the login authentication component according to the component configuration function;
and the generation login authentication component is used for completing the node execution function.
3. The method of claim 1, wherein building a login authentication pipeline model of the login authentication client according to the preset login authentication logic and the login authentication component comprises:
determining a component calling sequence of the login authentication component according to the preset login authentication logic;
and constructing a login authentication pipeline model of the login authentication client according to the component calling sequence and the login authentication component.
4. The method of claim 3, wherein determining the component invocation order of the login authentication components according to the preset login authentication logic comprises:
determining a component execution condition of the login authentication component and a common parameter set of the component execution condition according to the preset login authentication logic;
determining a combination relation between the login authentication component and component execution parameters in the public parameter set according to the preset login authentication logic to obtain a component parameter integration module;
and arranging and configuring the component parameter integration module according to the component execution condition to obtain a component calling sequence of the login authentication component.
5. The method of claim 1, wherein the pre-set login authentication logic comprises account password login authentication logic; the login authentication pipeline model comprises an account password login authentication pipeline model;
the processing of the login authentication instruction of the login authentication client according to the login authentication pipeline model comprises the following steps:
calling a decryption component to decrypt the account password login authentication instruction to obtain a first instruction decryption result;
calling a login authentication interface component to verify the user account and the user password included in the first instruction decryption result;
calling a user identity confirmation component to verify the dynamic authentication information input by the user under the condition that the login authentication interface component verifies the first instruction decryption result;
calling a trusted device verification component to verify the credibility of the current device of the user under the condition that the user identity confirmation component is confirmed to pass the verification;
under the condition that the trusted equipment verification component is determined not to pass the verification, calling a short message authentication request component to generate a short message authentication instruction matched with the login authentication instruction so as to enable a user to feed back short message authentication information according to the short message authentication instruction, calling a short message verification component to verify the short message authentication information, and under the condition that the short message verification component is determined to pass the verification, calling a user information acquisition component to acquire user associated information;
under the condition that the trusted equipment verification component is confirmed to pass the verification, calling the user information acquisition component to acquire the user associated information;
and calling a token generation component to generate a login authentication token matched with the login authentication instruction, and sending login success feedback information to the user.
6. The method of claim 1, wherein the pre-set login authentication logic comprises non-first-login authentication logic; the login authentication pipeline model comprises a non-first login authentication pipeline model;
the processing of the login authentication instruction of the login authentication client according to the login authentication pipeline model comprises the following steps:
a decryption component is called to decrypt the user characteristic login authentication instruction to obtain a second instruction decryption result;
calling a trusted device verification component to verify the credibility of the current device of the user;
calling a user characteristic verification component to verify the second instruction decryption result under the condition that the trusted equipment verification component is determined to pass the verification;
under the condition that the user characteristic verification component is confirmed to pass the verification, a login authentication interface component is called to verify a user account and a user password which are included in the second instruction decryption result;
under the condition that the login authentication interface component is confirmed to pass the verification of the second instruction decryption result, calling a user information acquisition component to acquire user association information;
and calling a token generation component to generate a login authentication token matched with the login authentication instruction, and sending login success feedback information to the user.
7. The method of claim 1, wherein the pre-defined login authentication logic comprises a password-free login authentication logic; the login authentication pipeline model comprises a secret-free login authentication pipeline model;
the processing of the login authentication instruction of the login authentication client according to the login authentication pipeline model comprises the following steps:
calling a token verification component to obtain a login authentication token carried by a password-free login authentication instruction, and verifying the validity of the login authentication token;
and under the condition that the login authentication token is confirmed to pass the validity check, confirming that the login authentication of the user is successful, and sending login success feedback information to the user.
8. A login authentication apparatus, comprising:
the login authentication logic module is used for acquiring the preset login authentication logic of the login authentication client;
the login authentication component generation module is used for analyzing the login authentication node of the preset login authentication logic so as to generate a login authentication component according to the login authentication node;
the login authentication pipeline model building module is used for building a login authentication pipeline model of the login authentication client according to the preset login authentication logic and the login authentication component;
and the login authentication instruction processing module is used for processing the login authentication instruction of the login authentication client according to the login authentication pipeline model so as to complete the login authentication process of the login authentication client.
9. An electronic device, characterized in that the electronic device comprises:
one or more processors;
storage means for storing one or more computer programs;
the login authentication method as claimed in any one of claims 1 to 7 when executed by the one or more computer programs to cause the one or more processors to execute the computer programs.
10. A computer storage medium having a computer program stored thereon, the computer program, when executed by a processor, implementing a login authentication method according to any one of claims 1 to 7.
CN202210199146.8A 2022-03-02 2022-03-02 Login authentication method and device, electronic equipment and storage medium Active CN114567446B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210199146.8A CN114567446B (en) 2022-03-02 2022-03-02 Login authentication method and device, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210199146.8A CN114567446B (en) 2022-03-02 2022-03-02 Login authentication method and device, electronic equipment and storage medium

Publications (2)

Publication Number Publication Date
CN114567446A true CN114567446A (en) 2022-05-31
CN114567446B CN114567446B (en) 2023-05-12

Family

ID=81714962

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210199146.8A Active CN114567446B (en) 2022-03-02 2022-03-02 Login authentication method and device, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN114567446B (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090328178A1 (en) * 2008-06-27 2009-12-31 Microsoft Corporation Techniques to perform federated authentication
CN110392065A (en) * 2018-12-27 2019-10-29 上海创蓝文化传播有限公司 Dodge the realization method and system for testing number certification SDK
US20210014227A1 (en) * 2019-07-12 2021-01-14 Bank Of America Corporation Split-tiered point-to-point inline authentication architecture
CN113901411A (en) * 2021-10-15 2022-01-07 四川新网银行股份有限公司 WEB login front-mounted security reinforcement system, reinforcement method and login method

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090328178A1 (en) * 2008-06-27 2009-12-31 Microsoft Corporation Techniques to perform federated authentication
CN110392065A (en) * 2018-12-27 2019-10-29 上海创蓝文化传播有限公司 Dodge the realization method and system for testing number certification SDK
US20210014227A1 (en) * 2019-07-12 2021-01-14 Bank Of America Corporation Split-tiered point-to-point inline authentication architecture
CN113901411A (en) * 2021-10-15 2022-01-07 四川新网银行股份有限公司 WEB login front-mounted security reinforcement system, reinforcement method and login method

Also Published As

Publication number Publication date
CN114567446B (en) 2023-05-12

Similar Documents

Publication Publication Date Title
US10880292B2 (en) Seamless transition between WEB and API resource access
EP3921991A1 (en) System and method for hardening security between web services using protected forwarded access tokens
CN112131021B (en) Access request processing method and device
CN110809011A (en) Access control method and system, and storage medium
CN112039826B (en) Login method and device applied to applet end, electronic equipment and readable medium
CN110365684B (en) Access control method and device for application cluster and electronic equipment
CN105188060A (en) Mobile terminal-oriented single sign-on (SSO) authentication method and system
CN109981680B (en) Access control implementation method and device, computer equipment and storage medium
CN111698312B (en) Service processing method, device, equipment and storage medium based on open platform
CN113742676B (en) Login management method, login management device, login management server, login management system and storage medium
CN113225351B (en) Request processing method and device, storage medium and electronic equipment
CN110069909A (en) It is a kind of to exempt from the close method and device for logging in third party system
US11777942B2 (en) Transfer of trust between authentication devices
CN113360217A (en) Rule engine SDK calling method and device and storage medium
CN111147525A (en) Authentication method, system, server and storage medium based on API gateway
CN110719590A (en) One-key login method, device, equipment and storage medium based on mobile phone number
CN113901429A (en) Access method and device of multi-tenant system
CN110149211B (en) Service authentication method, service authentication device, medium, and electronic device
US20230239288A1 (en) Integrated system and integrated method between multi-cloud applications
CN114567446B (en) Login authentication method and device, electronic equipment and storage medium
CN115766134A (en) Method and device for unified authentication of API gateway
CN113055186B (en) Cross-system service processing method, device and system
CN114238925A (en) Aggregation authentication method of non-mutual trust heterogeneous system based on JWT token
CN110493236B (en) Communication method, computer equipment and storage medium
CN112511565B (en) Request response method and device, computer readable storage medium and electronic equipment

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