Visualization implementation method and device for identity authentication, equipment, medium and program product
By using a visual identity authentication process tool to generate authentication forms and configuration interfaces, the problem of low development efficiency in traditional identity authentication is solved, and efficient and low-cost identity authentication process configuration is achieved.
Patent Information
- Application Number
- CN202511787375.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-11-28
- Publication Date
- 2026-02-27
AI Technical Summary
Traditional identity authentication processes require coding, resulting in low development efficiency and high maintenance costs. Developers also need to be familiar with the relevant protocols and code.
This paper provides a visual implementation method for identity authentication. By generating authentication forms and configuration interfaces, developers can select the authentication type and configure relevant information to generate the authentication process.
It improves the development efficiency of the identity authentication process, reduces operation and maintenance costs, and eliminates the need for developers to read and be familiar with the code.
Smart Images
Figure CN121580375A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of software development technology, specifically to a visual implementation method, apparatus, device, medium, and program product for identity authentication. Background Technology
[0002] In application development, the authentication process is a crucial step. Authentication is the process of verifying the identity of the user accessing the interface, ensuring the legitimacy of the entity initiating the request (user, application, or service, etc.), and that only legitimate entities can access protected data and functions.
[0003] Traditionally, the authentication and authorization process requires writing code according to an authentication protocol. However, this approach requires developers to be familiar with the relevant protocols and the code writing process, making the development of authentication processes inefficient. Summary of the Invention
[0004] In view of this, embodiments of this application provide a visual implementation method, apparatus, device, medium, and program product for identity authentication to improve the efficiency of developing identity authentication processes.
[0005] To address the above problems, the technical solutions provided in this application are as follows:
[0006] In a first aspect, embodiments of this application provide a visual implementation method for identity authentication, the method comprising:
[0007] Get the selected authentication type;
[0008] An authentication form is generated based on the identity authentication type, and the authentication form includes target fields associated with the identity.
[0009] The authentication step module corresponding to the authentication type is displayed, and the authentication step module has a corresponding configuration interface; the authentication step module corresponds to the process steps of the authentication process of the authentication type.
[0010] Obtain the configuration information from the configuration interface;
[0011] In response to a trigger operation indicating that the configuration information has been configured, an identity authentication process corresponding to the identity authentication type is generated based on the field value of the target field passed through the authentication form and the configuration information.
[0012] In one possible implementation, the identity authentication type is an authorization code identity authentication type, and the authentication step module includes an authorization request module, an access token acquisition module, an authorized user acquisition module, and a token addition and signature module.
[0013] The step of obtaining the configuration information of the configuration interface includes:
[0014] Obtain the authorization code from the callback address configured through the configuration interface corresponding to the authorization request module;
[0015] Obtain the correspondence between the authorization code and the token configured through the configuration interface corresponding to the access token acquisition module;
[0016] Obtain the user identity information configured through the configuration interface corresponding to the authorized user module;
[0017] Retrieve the position of the token in the authentication request as configured in the configuration interface corresponding to the token addition and signature module.
[0018] In one possible implementation, the authentication type is a client credential authentication type, and the authentication step module includes an access token acquisition module and a token addition and signature module.
[0019] The step of obtaining the configuration information of the configuration interface includes:
[0020] Obtain the correspondence between the target field and the token configured through the configuration interface corresponding to the access token acquisition module;
[0021] Retrieve the position of the token in the authentication request as configured in the configuration interface corresponding to the token addition and signature module.
[0022] In one possible implementation, the authentication step module further includes an access token refresh module;
[0023] The step of obtaining the configuration information of the configuration interface also includes:
[0024] Retrieve the token refresh mode information configured in the configuration interface corresponding to the refresh access token module.
[0025] In one possible implementation, the authentication type is either a basic authentication type or an application programming interface key authentication type, and the authentication step module includes a token addition and signature module.
[0026] The step of obtaining the configuration information of the configuration interface includes:
[0027] Obtain the correspondence between the target field and the token configured in the configuration interface corresponding to the token addition and signature module, as well as the position of the token addition in the authentication request.
[0028] In one possible implementation, the authentication step module further includes a module for dynamically obtaining the basic path;
[0029] The step of obtaining the configuration information of the configuration interface also includes:
[0030] Retrieve the base path or the base path acquisition path information configured in the configuration interface corresponding to the dynamically acquired base path module.
[0031] In one possible implementation, the target field includes a base path field; the base path field is used to set the base path used by the identity authentication process.
[0032] In one possible implementation, the method further includes:
[0033] In response to modification and / or addition of the target field, update the target fields included in the authentication form.
[0034] In one possible implementation, the method further includes:
[0035] Determine the data fields that need to be transmitted between the authentication step modules;
[0036] Get the field value of the data field.
[0037] In one possible implementation, the method further includes:
[0038] Generate a test link for the identity authentication process, and / or generate a publication link for the identity authentication process.
[0039] Secondly, embodiments of this application provide a visual implementation device for identity authentication, the device comprising:
[0040] The first acquisition unit is used to acquire the selected authentication type;
[0041] The first generation unit is configured to generate an authentication form based on the identity authentication type, the authentication form including a target field associated with the identity;
[0042] The display unit is used to display the authentication step module corresponding to the identity authentication type. The authentication step module has a configuration interface. The authentication step module corresponds to the process steps of the identity authentication process of the identity authentication type.
[0043] The second acquisition unit is used to acquire the configuration information of the configuration interface;
[0044] The second generation unit is used to respond to the trigger operation of configuration completion for the configuration information and generate the identity authentication process corresponding to the identity authentication type based on the field value of the target field passed through the authentication form and the configuration information.
[0045] Thirdly, embodiments of this application provide a visual implementation device for identity authentication, including: a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the visual implementation method for identity authentication as described in any of the above claims.
[0046] Fourthly, embodiments of this application provide a computer-readable storage medium storing instructions that, when executed on a terminal device, cause the terminal device to perform the visual implementation method for identity authentication as described in any of the preceding claims.
[0047] Fifthly, embodiments of this application provide a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program including program code for performing a visual implementation of the authentication as described in any of the preceding claims.
[0048] Therefore, the embodiments of this application have the following beneficial effects:
[0049] This application provides a development tool for a visual identity authentication process. After selecting an identity authentication type, it generates an authentication form corresponding to that type, including the target fields required for that authentication type. The tool displays the authentication step modules corresponding to each authentication type, each with a configuration interface. Developers can configure the configuration information for each authentication step module visually within its corresponding configuration interface. After configuring the information, the tool generates the identity authentication process corresponding to that type based on the field values of the target fields passed through the authentication form and the configuration information. This visual configuration and generation of the identity authentication process reduces operational and maintenance costs, eliminating the need for developers to read or familiarize themselves with the code, thus improving the efficiency of identity authentication process development. Attached Figure Description
[0050] Figure 1 A flowchart illustrating a visual implementation method for identity authentication provided in an embodiment of this application;
[0051] Figure 2 This is a schematic diagram of the authentication form interface corresponding to the basic identity authentication type in the embodiments of this application;
[0052] Figure 3 This is a schematic diagram of the authentication step module corresponding to the basic identity authentication type in the embodiments of this application;
[0053] Figure 4 This is a schematic diagram of the configuration page for the add token and signature modules corresponding to the basic identity authentication types in this application embodiment;
[0054] Figure 5 This is a schematic diagram of the authentication form interface corresponding to the application programming interface key authentication type in this embodiment of the application application;
[0055] Figure 6 This is a schematic diagram of the authentication step module corresponding to the application programming interface key authentication type in the embodiments of this application;
[0056] Figure 7 This is a schematic diagram of the configuration page for the add token and sign-up modules corresponding to the application programming interface key authentication type in this embodiment of the application.
[0057] Figure 8 This is a schematic diagram of the authentication form interface corresponding to the client credential authentication type in this embodiment of the application;
[0058] Figure 9 This is a schematic diagram of the authentication step module corresponding to the client credential authentication type in the embodiments of this application;
[0059] Figure 10 This is a schematic diagram of the authentication form interface corresponding to the authorization code authentication type in the embodiments of this application;
[0060] Figure 11 This is a schematic diagram of the authentication step module corresponding to the authorization code identity authentication type in the embodiments of this application;
[0061] Figure 12 A schematic diagram of a visual implementation device for identity authentication provided in an embodiment of this application;
[0062] Figure 13 This is a schematic diagram of an electronic device provided in an embodiment of this application. Detailed Implementation
[0063] To make the above-mentioned objectives, features and advantages of the embodiments of this application more apparent and understandable, the embodiments of this application will be further described in detail below with reference to the accompanying drawings and specific implementation methods.
[0064] To facilitate understanding and explanation of the technical solutions provided in the embodiments of this application, the background technology of the embodiments of this application will be described first below.
[0065] In the traditional approach, developing an identity authentication process requires writing code to implement the authentication and authorization procedures according to the authentication protocol. However, this approach requires developers to be familiar with the relevant protocols and the code writing process, and the code needs to be modified for each application scenario, making the development of identity authentication processes inefficient.
[0066] Based on this, embodiments of this application provide a visual implementation method, apparatus, device, medium, and program product for identity authentication, and provide a development tool for a visual identity authentication process. Through visual authentication forms and parameter configurations, developers can use this tool to visually encapsulate the identity authentication and authorization processes of various identity authentication types into connector authentication. The developed identity authentication process is aggregated by the dimension of the service to be connected, supporting shared use among users within an enterprise and across enterprises. Generating the identity authentication process through visual configuration results in low operating costs and low subsequent maintenance costs, as developers do not need to read or be familiar with the code. Furthermore, developers can customize authentication forms to meet customized scenario requirements. It offers high reusability; once developed and encapsulated, the generated identity authentication process can be used in different application scenarios.
[0067] To facilitate understanding of the embodiments of this application, the following description, in conjunction with the accompanying drawings, illustrates a visual implementation method for identity authentication provided by the embodiments of this application.
[0068] See Figure 1 As shown, this figure is a flowchart of a visual implementation method for identity authentication provided in an embodiment of this application. Figure 2 As shown, the method may include S101-S105:
[0069] S101: Obtain the selected authentication type.
[0070] This application's embodiments can be applied to development tools for visual identity authentication processes. Developers can first select the authentication type; different authentication types correspond to different authentication processes. Authentication types can include authorization code authentication, client credential authentication, basic authentication, and application programming interface key authentication, etc. Specifically, the authorization code authentication type can be OAuth2Code (the authorization code mode of the OAuth 2.0 protocol), the client credential authentication type can be OAuth2ClientCredentials (the client mode of the OAuth 2.0 protocol), the basic authentication type can be Basic Auth, and the application programming interface key authentication type can be API Key, etc.
[0071] In practical applications, a list interface including authentication types can be provided, allowing developers to select an authentication type from the list. Alternatively, an input box including authentication types can be provided, allowing developers to enter their selected authentication type. This application embodiment does not limit the specific implementation method for developers to select authentication types. After obtaining the authentication type selected by the developer, the corresponding authentication form and authentication step module can be generated in subsequent steps.
[0072] S102: Generate an authentication form based on the authentication type. The authentication form includes target fields associated with the identity.
[0073] After obtaining the authentication type selected by the developer, an authentication form corresponding to that type can be generated. An authentication form can be understood as a form provided to the user who needs to authenticate during the authentication process. The authentication form includes target fields. Different authentication types include different target fields associated with the identity. For example, in the basic authentication type, target fields may include a username (userID) field, a password field, etc. In the Application Programming Interface Key (API Key) authentication type, target fields may include an API Key field, etc. During the authentication process, the values of the target fields can be passed through the authentication form. In practical applications, an authentication form interface can be provided, displaying the target fields and related information, and allowing a preview of the final authentication form provided to the user.
[0074] In this step, an authentication form and its target fields are initialized based on the authentication type. Developers can reconfigure the initialized authentication form and its target fields, or add custom fields to the authentication form, depending on their needs.
[0075] In one possible implementation, it may also include: updating the target fields included in the authentication form in response to modification and / or addition of target fields.
[0076] In this embodiment, the target fields can also be modified and / or added to update the target fields included in the authentication form. In practical applications, the target fields generated during initialization can be modified by triggering the "Edit Target Fields" function in the authentication form interface. New target fields can also be added by triggering the "Add Target Fields" function. This allows developers to customize the authentication form and its included target fields to meet customized scenarios.
[0077] S103: Displays the authentication step module corresponding to the identity authentication type. The authentication step module has a corresponding configuration interface; the authentication step module corresponds to the process steps of the identity authentication process for the identity authentication type.
[0078] After obtaining the authentication type selected by the developer, the system can also display the authentication step module corresponding to that type. The authentication step module can be understood as the key process steps required for the authentication flow corresponding to that type. Different authentication types can have different authentication step modules abstracted from them.
[0079] Each authentication step module has a corresponding configuration interface, where you can configure the information required for that module. In practice, you can trigger the authentication step module to display its configuration interface, which is a more concise approach. Alternatively, the authentication step module and its configuration interface can be displayed simultaneously.
[0080] It is understood that the execution order of S102 and S103 is not limited in the embodiments of this application. For example, in the first implementation, an authentication form can be generated first, an authentication form interface can be provided, and after the authentication form is confirmed, the authentication step module corresponding to the identity authentication type can be displayed. As another example, in the second implementation, both the authentication form interface and the authentication step module corresponding to the identity authentication type can be provided simultaneously.
[0081] S104: Obtain configuration information from the configuration interface.
[0082] Developers can configure the authentication step module in the configuration interface corresponding to the authentication step module, thereby obtaining the configuration information of the configuration interface corresponding to each authentication step module. The configuration information is used to generate the corresponding identity authentication process.
[0083] For the authentication steps, modules, and configuration information corresponding to different identity authentication types, please refer to the descriptions in the subsequent embodiments, which will not be repeated here.
[0084] S105: In response to the trigger operation that completes the configuration of the configuration information, generate the identity authentication process corresponding to the identity authentication type based on the field value of the target field passed through the authentication form and the configuration information.
[0085] After configuring the configuration information for each authentication step module, developers can trigger the configuration to complete. Then, by reading the configuration information of each authentication step module and utilizing the field values of the target fields passed through the authentication form, the system can automatically generate the authentication process corresponding to the selected authentication type.
[0086] This application provides a development tool for a visual identity authentication process. After selecting an identity authentication type, it generates an authentication form corresponding to that type, including the target fields required for that authentication type. The tool displays the authentication step modules corresponding to each authentication type, each with a configuration interface. Developers can configure the configuration information for each authentication step module visually within its corresponding configuration interface. After configuring the information, the tool generates the identity authentication process corresponding to that type based on the field values of the target fields passed through the authentication form and the configuration information. This visual configuration and generation of the identity authentication process reduces operational and maintenance costs, eliminating the need for developers to read or familiarize themselves with the code, thus improving the efficiency of identity authentication process development.
[0087] When the authentication type is Basic Auth, this application's embodiment will illustrate the visual implementation method of authentication. Basic Auth authentication involves the user inputting a username and password, which are then concatenated, encoded, and added to the request header for identity verification.
[0088] See Figure 2 The image shows a schematic diagram of the authentication form interface corresponding to the basic identity authentication type.
[0089] After the user selects the basic authentication type, an authentication form is generated and displayed. The authentication form interface includes this form. Target fields in the authentication form can include username (userID), password, base URL, proxy group, etc. Information about the target fields, such as display name, field name, and field type, can also be displayed. Additionally, a preview of the final authentication form provided to the user can be displayed. During the authentication process, the user can fill in their username (userID), password, and other information through the authentication form.
[0090] In practical applications, the authentication form interface allows users to edit target fields, modifying their display name, field name, and field type. Adding new target fields is also possible by triggering the "Add Field" button. This allows developers to customize the authentication form, adjusting the parameters required from the user (authentication user) as needed, while still meeting the authentication requirements of the encapsulated interface. After confirming the authentication form, a "Next" button can be triggered to further display the authentication steps.
[0091] In one possible implementation, the authentication type is the basic authentication type, and the authentication step module may include a token addition and signature module. Therefore, the specific implementation of S104 obtaining configuration information from the configuration interface may include:
[0092] Retrieve the correspondence between the target fields configured in the configuration interface corresponding to the add token and signature modules and the token, as well as the position of the token in the authentication request.
[0093] See Figure 3 The diagram shows a schematic of the authentication step module corresponding to the basic identity authentication type.
[0094] When the authentication type is basic authentication, the authentication process can be abstracted into two key steps: dynamically obtaining the base URL module and adding the token and signing the authentication. Each authentication step module provides a visual API request configuration interface. The dynamically obtaining the base URL module is optional, meaning it does not need to be configured.
[0095] In practical applications, the authentication step module can be triggered to further display the corresponding configuration interface. See also Figure 4 The diagram illustrates the configuration page for the "Add Token and Signature" module corresponding to the basic authentication type. For example, the dropdown button for the "Add Token and Signature" module displays this configuration page. On this page, the mapping between target fields and tokens, as well as the token's placement in the authentication request, can be entered. For instance, in Basic Auth authentication, the code entered on this page represents concatenating and encoding the values of the username (userID) and password fields to generate a token, which is then added to the authentication request header. This code constitutes configuration information, which is minimal. After developers complete the configuration as needed, the authentication process will be generated according to the Basic Auth authentication execution flow. The authentication process executes the API requests corresponding to each authentication step module as needed to complete the authentication and authorization process.
[0096] In one possible implementation, when the authentication type is a basic authentication type, the authentication steps module may also include a module for dynamically obtaining the basic path.
[0097] The specific implementation of S104 obtaining configuration information from the configuration interface may also include:
[0098] Retrieves the base path or the base path acquisition path information configured in the configuration interface corresponding to the dynamically acquired base path module.
[0099] In this embodiment, the base path (BaseURL) can also be configured through the configuration interface corresponding to the dynamically obtained base path module, or the method for dynamically obtaining the base path (BaseURL) can be configured. It is understood that since the target field can also include the base path field, which is used to set the base path used in the authentication process, the base path (BaseURL) can also be passed through the authentication form. The base path (BaseURL) is a configuration item for the base URL; after configuration, all requests in the authentication process will automatically include this base path (BaseURL).
[0100] In this embodiment, the authentication form required for the basic identity authentication type's authentication process is automatically generated. The authentication process for the basic identity authentication type is then broken down visually, allowing for rapid setting of relevant configuration parameters. This visual configuration and generation of the basic identity authentication type's authentication process improves the efficiency of developing such processes.
[0101] When the authentication type is the Application Programming Interface Key (API Key) authentication type, taking API Key authentication as an example, the visual implementation method of authentication provided in this application embodiment will be described. Authentication using the API Key authentication type uses a unique identifier issued by the business service for identity verification.
[0102] See Figure 5 The diagram shows a schematic of the authentication form interface corresponding to the application programming interface key authentication type.
[0103] After the user selects the basic authentication type, an authentication form is generated and displayed. The authentication form interface, including this form, can include target fields such as the Application Programming Interface Key (apiKey), base URL, and proxy group. It can also display relevant information about the target fields, such as display name, field name, and field type. Furthermore, a preview of the final authentication form provided to the user can be displayed. During the authentication process, the user can enter information such as the Application Programming Interface Key (apiKey) through the authentication form.
[0104] In practical applications, the authentication form interface allows users to edit target fields and add new fields. This enables developers to customize the authentication form, adjusting the parameters required from the user (authentication user) as needed, while still meeting the authentication requirements of the encapsulated interface. After confirming the authentication form, a "Next" button can be triggered to further display the authentication steps.
[0105] In one possible implementation, the authentication type is an application programming interface key authentication type, and the authentication step module includes a token addition and signature module. Therefore, the specific implementation of S104 obtaining configuration information from the configuration interface includes:
[0106] Retrieve the correspondence between the target fields configured in the configuration interface corresponding to the add token and signature modules and the token, as well as the position of the token in the authentication request.
[0107] See Figure 6 The diagram shows a schematic of the authentication step module corresponding to the application programming interface key authentication type.
[0108] When the authentication type is Application Programming Interface Key Authentication, the authentication process can be abstracted into two key steps: dynamically obtaining the base URL module and adding the token and signing the authentication. Each authentication step module provides a visual API request configuration interface. The dynamically obtaining the base URL module is optional, meaning it does not need to be configured.
[0109] In practical applications, the authentication step module can be triggered to further display the corresponding configuration interface. See also Figure 7 The diagram illustrates the configuration page for the "Add Token and Signature" module corresponding to the API Key authentication type. For example, the dropdown button for the "Add Token and Signature" module displays this configuration page. On this page, the mapping between target fields and tokens, as well as the token's placement in the authentication request, can be entered. For instance, in API Key authentication, the code on this page can represent processing the value of the API Key field and using it as a token, adding it to the authentication request header. This code constitutes configuration information, which is minimal. Developers complete the configuration as needed, generating the authentication process based on the API Key authentication execution flow. The authentication process executes the API requests corresponding to each authentication step module as required, completing the authentication and authorization process.
[0110] In one possible implementation, when the authentication type is an application programming interface key authentication type, the authentication step module also includes a module for dynamically obtaining the underlying path.
[0111] The specific implementation of S104 obtaining configuration information from the configuration interface may also include:
[0112] Retrieves the base path or the base path acquisition path information configured in the configuration interface corresponding to the dynamically acquired base path module.
[0113] In this embodiment, the base path (BaseURL) can also be configured through the configuration interface corresponding to the dynamically obtained base path module, or the dynamic acquisition method of the base path (BaseURL) can be configured. It is understood that since the target field can also include the base path field, which is used to set the base path used in the identity authentication process, the base path (BaseURL) can also be passed through the authentication form.
[0114] In this embodiment, the authentication form required for the authentication process of the API key authentication type is automatically generated. The authentication process of the API key authentication type is also broken down visually, allowing for rapid setting of relevant configuration parameters. This visual configuration and generation of the API key authentication type authentication process improves the efficiency of developing such processes.
[0115] When the authentication type is client credential authentication, taking the application programming interface key authentication type OAuth2ClientCredentials as an example, the visual implementation method of authentication provided in this application embodiment will be described. This authentication method follows the OAuth2.0 protocol. The client application uses the client identifier (Client ID) and client secret (Client Secret) to exchange for a token, and uses the token to access subsequent requests.
[0116] See Figure 8 The diagram shows a schematic of the authentication form interface corresponding to the client credential authentication type.
[0117] After the user selects client credential authentication as the authentication type, an authentication form is generated and displayed. The authentication form can include target fields such as ClientID, ClientSecret, baseURL, baseAuthURL, and proxyGroup. It can also display relevant information about the target fields, such as display name, field name, and field type. Furthermore, a preview of the final authentication form provided to the user can be displayed. During the authentication process, the user can fill in information such as ClientID and ClientSecret through the authentication form.
[0118] In practical applications, the authentication form interface allows users to edit target fields and add new fields. This enables developers to customize the authentication form, adjusting the parameters required from the user (authentication user) as needed, while still meeting the authentication requirements of the encapsulated interface. After confirming the authentication form, a "Next" button can be triggered to further display the authentication steps.
[0119] In one possible implementation, the authentication type is client credential authentication, and the authentication steps module includes an access token acquisition module and a token addition and signature module. Therefore, the specific implementation of S104 obtaining configuration information from the configuration interface may include:
[0120] A1: Obtain the correspondence between the target fields configured in the configuration interface corresponding to the access token module and the token.
[0121] A2: Retrieve the position of the token configured in the configuration interface corresponding to the token addition and signature modules in the authentication request.
[0122] See Figure 9 The diagram shows a schematic of the authentication step module corresponding to the client credential authentication type.
[0123] When the authentication type is client credential authentication, the authentication process can be abstracted into four key steps: obtaining an access token, refreshing the access token, dynamically obtaining the base URL, and adding and signing the token. Each authentication step module provides a visual API request configuration interface. The refreshing and dynamically obtaining the base URL modules are optional, meaning they do not need to be configured.
[0124] In practical applications, triggering authentication step modules can further display the corresponding configuration interfaces. For example, the dropdown button for the "Get Access Token" module can display its configuration page. On this page, the mapping between target fields and tokens can be configured. In OAuth2ClientCredentials authentication, after the user completes authorization, an authorization code can be obtained using the Client ID and Client Secret. This authorization code can then be used to obtain a token for accessing resources. The specific method for obtaining the token can be written on this configuration page. Similarly, the dropdown button for the "Add Token and Signature" module can display its configuration page. This page allows specifying the token's placement in the authentication request. For instance, in OAuth2ClientCredentials authentication, the code written on this page indicates that the token will be added to the authentication request header. This code is configuration information, consisting of only a small amount of code. After developers complete the configuration as needed, the authentication process will be generated according to the OAuth2ClientCredentials authentication execution flow. The identity authentication process is used to execute the API requests corresponding to each authentication step module as needed to complete identity authentication and authorization.
[0125] In one possible implementation, when the authentication type is client credential authentication, the authentication steps module also includes a refresh access token module.
[0126] The specific implementation of S104 obtaining configuration information from the configuration interface may also include:
[0127] Retrieve the token refresh mode information configured in the configuration interface corresponding to the refresh access token module.
[0128] After obtaining a token, you can refresh the configuration interface corresponding to the access token module to set the token refresh mode when the token expires or is about to expire, thus obtaining token refresh mode information. After setting the token refresh mode, you can initiate a request to obtain a new token when the token expires or is about to expire, ensuring continued access to resources without requiring the user to re-authorize.
[0129] In one possible implementation, when the authentication type is client credential authentication, the authentication steps module also includes a module for dynamically obtaining the base path.
[0130] The specific implementation of S104 obtaining the configuration information configured in the configuration interface corresponding to the authentication step module may also include:
[0131] Retrieves the base path or the base path acquisition path information configured in the configuration interface corresponding to the dynamically acquired base path module.
[0132] In this embodiment, the base path (BaseURL) can also be configured through the configuration interface corresponding to the dynamically obtained base path module, or the dynamic acquisition method of the base path (BaseURL) can be configured. It is understood that since the target field can also include the base path field, which is used to set the base path used in the identity authentication process, the base path (BaseURL) can also be passed through the authentication form.
[0133] In this embodiment, the authentication form required for the client credential authentication type's authentication process is automatically generated. The authentication process for this type is then visually broken down, allowing for rapid configuration parameter settings. This visually configures and generates the client credential authentication type's authentication process, improving the efficiency of developing such processes.
[0134] When the authentication type is the authorization code authentication type, taking OAuth2Code as the basic authentication type as an example, the visual implementation method of authentication provided in this application embodiment is described. This authentication method follows the OAuth2.0 protocol, requiring the user to log in and verify with the identity provider. After successful verification, the identity provider gives the authorization code to the application. The application extracts the authorization code and exchanges an access token with the identity provider to verify subsequent requests.
[0135] See Figure 10 The image shows a schematic diagram of the authentication form interface corresponding to the authorization code authentication type.
[0136] After the user selects authorization code authentication as the authentication type, an authentication form is generated and displayed. The authentication form can include target fields such as Client ID, Client Secret, and the scope of the authorization. It can also display relevant information about the target fields, such as display name, field name, and field type. Furthermore, a preview of the final authentication form provided to the user can be displayed. During the authentication process, the user can fill in information such as Client ID, Client Secret, and the scope of the authorization through the authentication form.
[0137] In practical applications, the authentication form interface allows users to edit target fields and add new fields. This enables developers to customize the authentication form, adjusting the parameters required from the user (authentication user) as needed, while still meeting the authentication requirements of the encapsulated interface. After confirming the authentication form, a "Next" button can be triggered to further display the authentication steps.
[0138] In one possible implementation, the authentication type is an authorization code authentication type, and the authentication step module includes an authorization request module, an access token acquisition module, an authorized user acquisition module, and a token addition and signature module. Therefore, the specific implementation of S104 obtaining configuration information from the configuration interface may include:
[0139] B1: Obtain the authorization code from the callback address configured through the configuration interface corresponding to the authorization request module.
[0140] B2: Obtain the mapping relationship between the authorization code and the token configured through the configuration interface of the Access Token module.
[0141] B3: Obtain the user identity information configured through the configuration interface corresponding to the authorized user module.
[0142] B4: Retrieve the position of the token configured in the authentication request within the configuration interface corresponding to the token addition and signature modules.
[0143] See Figure 11 The diagram shows a schematic of the authentication step module corresponding to the authorization code identity authentication type.
[0144] When the authentication type is authorization code authentication, the authentication process can be abstracted into six key steps: authorization request module, access token acquisition module, authorized user acquisition module, access token refresh module, dynamic base URL acquisition module, token addition and signature module. Each authentication step module provides a visual API request configuration interface. The access token refresh and base URL acquisition modules are optional, meaning they do not need to be configured.
[0145] In practical applications, the authentication process can be triggered to display the corresponding configuration interface. For example, the configuration page for the authorization request module can be displayed via a dropdown menu. The authorization request module provides a redirect callback address, which, after successful user authorization, allows the user to retrieve the authorization code and related data.
[0146] The dropdown menu for the "Get Access Token" module displays its configuration page. This page allows you to configure the mapping between authorization codes and tokens. In OAuth2Code authentication, after a user completes authorization, the authorization code is determined using the Client ID and Client Secret. The authorization code is then retrieved via a callback URL, and a token for accessing resources can be obtained from it. This configuration page allows you to specify how to obtain the token. The dropdown menu for the "Authorize User" module also displays its configuration page. This page allows you to retrieve the authorized user's identity information to ensure authentication security. The dropdown menu for the "Add Token and Signature" module displays its configuration page. This page allows you to specify where the token should be added to the authentication request. For example, in OAuth2Code authentication, the code entered on this page indicates that the token will be added to the authentication request header. This section of code contains configuration information, which is a very small amount of code. After developers complete the configuration as needed, the OAuth2Code authentication process will generate the identity authentication flow. The identity authentication flow is used to execute the API requests corresponding to each authentication step module as needed to complete identity authentication and authorization.
[0147] In one possible implementation, when the authentication type is an authorization code authentication type, the authentication steps module also includes a refresh access token module.
[0148] The specific implementation of S104 obtaining configuration information from the configuration interface may also include:
[0149] Retrieve the token refresh mode information configured in the configuration interface corresponding to the refresh access token module.
[0150] After obtaining a token, you can refresh the configuration interface corresponding to the access token module to set the token refresh mode when the token expires or is about to expire, thus obtaining token refresh mode information. After setting the token refresh mode, you can initiate a request to obtain a new token when the token expires or is about to expire, ensuring continued access to resources without requiring the user to re-authorize.
[0151] In one possible implementation, when the authentication type is an authorization code authentication type, the authentication steps module also includes a module for dynamically obtaining the basic path.
[0152] The specific implementation of S104 obtaining configuration information from the configuration interface may also include:
[0153] Retrieves the base path or the base path acquisition path information configured in the configuration interface corresponding to the dynamically acquired base path module.
[0154] In this embodiment, the base path (BaseURL) can also be configured through the configuration interface corresponding to the dynamically obtained base path module, or the dynamic acquisition method of the base path (BaseURL) can be configured. It is understood that since the target field can also include the base path field, which is used to set the base path used in the identity authentication process, the base path (BaseURL) can also be passed through the authentication form.
[0155] In this embodiment, the authentication form required for the authorization code authentication process is automatically generated. The authorization code authentication process is then visually broken down, allowing for rapid configuration parameter settings. This visually configures and generates the authorization code authentication process, improving the efficiency of developing such processes.
[0156] One possible implementation may also include:
[0157] Determine the data fields that need to be passed between the authentication step modules; obtain the field values of the data fields.
[0158] In this embodiment, data fields for data transfer between authentication step modules can also be declared. In practical applications, an interface defining the authentication process data can be displayed, showing the data fields that need to be transferred between authentication step modules. These data fields can be referenced in API requests from any authentication step module. Furthermore, data fields can be edited, and their values can be added or modified.
[0159] One possible implementation may also include:
[0160] Generate a test link for the identity authentication process, and / or generate a publish link for the identity authentication process.
[0161] After generating the authentication process, it can be tested, such as testing the token acquisition process or the token refresh process, to verify its effectiveness. Once the tests are passed, the authentication process can be encapsulated and published, allowing connectors to use it.
[0162] Based on the above-described method embodiments, this application also provides a visualization implementation device for identity authentication, which will be described below with reference to the accompanying drawings.
[0163] See Figure 12 As shown, this figure is a structural schematic diagram of a visual implementation device for identity authentication provided in an embodiment of this application. Figure 12 As shown, the visual implementation device for this identity authentication includes:
[0164] The first acquisition unit 1201 is used to acquire the selected identity authentication type;
[0165] The first generation unit 1202 is used to generate an authentication form according to the identity authentication type, the authentication form including a target field associated with the identity;
[0166] The display unit 1203 is used to display the authentication step module corresponding to the identity authentication type. The authentication step module has a configuration interface. The authentication step module corresponds to the process steps of the identity authentication process of the identity authentication type.
[0167] The second acquisition unit 1204 is used to acquire the configuration information of the configuration interface;
[0168] The second generation unit 1205 is used to generate an identity authentication process corresponding to the identity authentication type in response to a trigger operation that indicates the configuration of the configuration information is complete.
[0169] In one possible implementation, the identity authentication type is an authorization code identity authentication type, and the authentication step module includes an authorization request module, an access token acquisition module, an authorized user acquisition module, and a token addition and signature module.
[0170] The second acquisition is specifically used for:
[0171] Obtain the authorization code from the callback address configured through the configuration interface corresponding to the authorization request module;
[0172] Obtain the correspondence between the authorization code and the token configured through the configuration interface corresponding to the access token acquisition module;
[0173] Obtain the user identity information configured through the configuration interface corresponding to the authorized user module;
[0174] Retrieve the position of the token in the authentication request as configured in the configuration interface corresponding to the token addition and signature module.
[0175] In one possible implementation, the authentication type is a client credential authentication type, and the authentication step module includes an access token acquisition module and a token addition and signature module.
[0176] The second acquisition unit is specifically used for:
[0177] Obtain the correspondence between the target field and the token configured through the configuration interface corresponding to the access token acquisition module;
[0178] Retrieve the position of the token in the authentication request as configured in the configuration interface corresponding to the token addition and signature module.
[0179] In one possible implementation, the authentication step module further includes an access token refresh module;
[0180] The second acquisition unit is further configured to:
[0181] Retrieve the token refresh mode information configured in the configuration interface corresponding to the refresh access token module.
[0182] In one possible implementation, the authentication type is either a basic authentication type or an application programming interface key authentication type, and the authentication step module includes a token addition and signature module.
[0183] The second acquisition unit is specifically used for:
[0184] Obtain the correspondence between the target field and the token configured in the configuration interface corresponding to the token addition and signature module, as well as the position of the token addition in the authentication request.
[0185] In one possible implementation, the authentication step module further includes a module for dynamically obtaining the basic path;
[0186] The second acquisition unit is further configured to:
[0187] Retrieve the base path or the base path acquisition path information configured in the configuration interface corresponding to the dynamically acquired base path module.
[0188] In one possible implementation, the target field includes a base path field; the base path field is used to set the base path used by the identity authentication process.
[0189] In one possible implementation, the device further includes:
[0190] An update unit is used to update the target fields included in the authentication form in response to modification and / or addition of the target fields.
[0191] In one possible implementation, the device further includes:
[0192] A determining unit is used to determine the data fields that need to be transmitted between the authentication step modules;
[0193] The third acquisition unit is used to acquire the field value of the data field.
[0194] In one possible implementation, the device further includes:
[0195] The third generation unit is used to generate a test link for the identity authentication process and / or generate a publication link for the identity authentication process.
[0196] This application provides a development tool for a visual identity authentication process. After selecting an identity authentication type, it generates an authentication form corresponding to that type, including the target fields required for that authentication type. The tool displays the authentication step modules corresponding to each authentication type, each with a configuration interface. Developers can configure the configuration information for each authentication step module visually within its corresponding configuration interface. After configuring the information, the tool generates the identity authentication process corresponding to that type based on the field values of the target fields passed through the authentication form and the configuration information. This visual configuration and generation of the identity authentication process reduces operational and maintenance costs, eliminating the need for developers to read or familiarize themselves with the code, thus improving the efficiency of identity authentication process development.
[0197] This application also provides a computer program product, including computer program instructions, which, when executed on a computer, cause the computer to perform a visual implementation method for identity authentication as described in any of the preceding embodiments.
[0198] Based on the above-described method embodiments, this application also provides an electronic device, including: one or more processors; and a storage device storing one or more programs thereon, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the above-described method for visualizing identity authentication.
[0199] The following is for reference. Figure 13The diagram illustrates a structural schematic of an electronic device 1300 suitable for implementing embodiments of this application. The terminal devices in these embodiments may include, but are not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Android Devices), PMPs (Portable Media Players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs (televisions), desktop computers, etc. Figure 13 The electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.
[0200] like Figure 13 As shown, electronic device 1300 may include a processing device (e.g., a central processing unit, a graphics processor, etc.) 1301, which can perform various appropriate actions and processes according to a program stored in read-only memory (ROM) 1302 or a program loaded from storage device 1306 into random access memory (RAM) 1303. RAM 1303 also stores various programs and data required for the operation of electronic device 1300. Processing device 1301, ROM 1302, and RAM 1303 are interconnected via bus 1304. Input / output (I / O) interface 1305 is also connected to bus 1304.
[0201] Typically, the following devices can be connected to I / O interface 1305: input devices 1306 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 1307 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 1306 including, for example, magnetic tapes, hard disks, etc.; and communication devices 1309. Communication device 1309 allows electronic device 1300 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 13 An electronic device 1300 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively.
[0202] Specifically, according to embodiments of this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication device 1309, or installed from storage device 1306, or installed from ROM 1302. When the computer program is executed by processing device 1301, it performs the functions defined in the methods of embodiments of this application.
[0203] The electronic device provided in this application embodiment and the visual implementation method of identity authentication provided in the above embodiment belong to the same inventive concept. Technical details not described in detail in this embodiment can be found in the above embodiment, and this embodiment has the same beneficial effects as the above embodiment.
[0204] Based on the above-described method embodiments, this application provides a computer-readable medium storing a computer program thereon, wherein the program, when executed by a processor, implements the visual implementation method for identity authentication as described in any of the above embodiments.
[0205] It should be noted that the computer-readable medium described in the embodiments of this application can be a computer-readable signal medium, a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In the embodiments of this application, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In the embodiments of this application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.
[0206] In some implementations, clients and servers can communicate using any currently known or future-developed network protocol such as HTTP (Hypertext Transfer Protocol) and can interconnect with digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include local area networks (“LANs”), wide area networks (“WANs”), the Internet (e.g., the Internet of Things), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future-developed networks.
[0207] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device.
[0208] The aforementioned computer-readable medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to perform the aforementioned visual implementation method for identity authentication.
[0209] Computer program code for performing the operations of the embodiments of this application can be written in one or more programming languages or a combination thereof. These programming languages include, but are not limited to, object-oriented programming languages such as Java, Smalltalk, and C++, as well as conventional procedural programming languages such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).
[0210] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.
[0211] The units described in the embodiments of this application can be implemented in software or hardware. The names of the units / modules do not necessarily limit the specific unit itself.
[0212] The functions described above in this document can be performed at least in part by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), system-on-a-chip (SoCs), complex programmable logic devices (CPLDs), and so on.
[0213] In the context of embodiments of this application, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media can include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.
[0214] It should be noted that the various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the systems or apparatus disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the descriptions are relatively simple, and relevant parts can be referred to the method section.
[0215] It should be understood that in this application, "at least one (item)" means one or more, and "more than" means two or more. "And / or" is used to describe the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.
[0216] It should also be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.
[0217] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.
[0218] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. A visual implementation method for identity authentication, characterized in that, The method includes: Get the selected authentication type; An authentication form is generated based on the identity authentication type, and the authentication form includes target fields associated with the identity. The authentication step module corresponding to the authentication type is displayed, and the authentication step module has a corresponding configuration interface; the authentication step module corresponds to the process steps of the authentication process of the authentication type. Obtain the configuration information from the configuration interface; In response to a trigger operation indicating that the configuration information has been configured, an identity authentication process corresponding to the identity authentication type is generated based on the field value of the target field passed through the authentication form and the configuration information.
2. The method according to claim 1, characterized in that, The identity authentication type is the authorization code identity authentication type, and the authentication step module includes an authorization request module, an access token acquisition module, an authorized user acquisition module, and a token addition and signature module; The step of obtaining the configuration information of the configuration interface includes: Obtain the authorization code from the callback address configured through the configuration interface corresponding to the authorization request module; Obtain the correspondence between the authorization code and the token configured through the configuration interface corresponding to the access token acquisition module; Obtain the user identity information configured through the configuration interface corresponding to the authorized user module; Retrieve the position of the token in the authentication request as configured in the configuration interface corresponding to the token addition and signature module.
3. The method according to claim 1, characterized in that, The authentication type is a client credential authentication type, and the authentication step module includes an access token acquisition module and a token addition and signature module; The step of obtaining the configuration information of the configuration interface includes: Obtain the correspondence between the target field and the token configured through the configuration interface corresponding to the access token acquisition module; Retrieve the position of the token in the authentication request as configured in the configuration interface corresponding to the token addition and signature module.
4. The method according to claim 2 or 3, characterized in that, The authentication steps module also includes an access token refresh module; The step of obtaining the configuration information of the configuration interface also includes: Retrieve the token refresh mode information configured in the configuration interface corresponding to the refresh access token module.
5. The method according to claim 1, characterized in that, The authentication type is either a basic authentication type or an application programming interface key authentication type, and the authentication step module includes a token addition and signature module; The step of obtaining the configuration information of the configuration interface includes: Obtain the correspondence between the target field and the token configured in the configuration interface corresponding to the token addition and signature module, as well as the position of the token addition in the authentication request.
6. The method according to claim 1, characterized in that, The authentication steps module also includes a module for dynamically obtaining the basic path; The step of obtaining the configuration information of the configuration interface also includes: Retrieve the base path or the base path acquisition path information configured in the configuration interface corresponding to the dynamically acquired base path module.
7. The method according to claim 1, characterized in that, The target field includes a base path field; the base path field is used to set the base path used by the identity authentication process.
8. The method according to claim 1, characterized in that, The method further includes: In response to modification and / or addition of the target field, update the target fields included in the authentication form.
9. The method according to claim 1, characterized in that, The method further includes: Determine the data fields that need to be transmitted between the authentication step modules; Get the field value of the data field.
10. The method according to claim 1, characterized in that, The method further includes: Generate a test link for the identity authentication process, and / or generate a publication link for the identity authentication process.
11. A visual implementation device for identity authentication, characterized in that, The device includes: The first acquisition unit is used to acquire the selected authentication type; The first generation unit is configured to generate an authentication form based on the identity authentication type, the authentication form including a target field associated with the identity; The display unit is used to display the authentication step module corresponding to the identity authentication type. The authentication step module has a configuration interface. The authentication step module corresponds to the process steps of the identity authentication process of the identity authentication type. The second acquisition unit is used to acquire the configuration information of the configuration interface; The second generation unit is used to respond to the trigger operation of configuration completion for the configuration information and generate the identity authentication process corresponding to the identity authentication type based on the field value of the target field passed through the authentication form and the configuration information.
12. A visual implementation device for identity authentication, characterized in that, include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, it implements the visual implementation method of identity authentication as described in any one of claims 1-10.
13. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed on a terminal device, cause the terminal device to perform the visual implementation method of identity authentication as described in any one of claims 1-10.
14. A computer program product, characterized in that, It includes a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing a visual implementation of the authentication as described in any one of claims 1-10.