Authority authentication method for uncontrolled right form data and related device

Abstract

The embodiment of the invention provides an authentication method for non-control right form data permission and a related device, which are used for avoiding the problem that service codes strongly invade non-control right form data. The method provided by the embodiment of the invention comprises the following steps: receiving an operation request for an uncontrolled right form; according to the operation request, calling an authentication model to obtain a non-control right form and an operation for the non-control right form; obtaining a pre-configured operation authority configuration item of the non-control authority form; if it is determined that the non-control right form is provided with operation permission configuration according to the non-control right form, the operation for the non-control right form and a pre-configured operation permission configuration item, obtaining an authentication data identifier of the non-control right form; according to the operation authority configuration item, the authentication data identifier, the non-control authority form and the operation aiming at the non-control authority form, executing preposed function authority authentication on the operation aiming at the non-control authority form; and if all the data in the non-control right form pass the authentication, receiving an operation executed on the non-control right form, and triggering the operated business logic.

Description

Technical Field

[0001] The present invention relates to the technical field of data management, and in particular to a method and a related device for authenticating authority of non-control form data. Background Art

[0002] In actual application scenarios, in order to achieve sharing of the same basic table data among different business applications (such as personnel management applications and foreign affairs management applications), the basic table data is generally published to different applications to achieve sharing of the same basic table data in different business application scenarios.

[0003] In the same business application, in order to display the basic table data in different business scenarios, the basic table data is generally divided into different control forms. For example, in the foreign affairs management application, the total basic table data can be divided into two control forms (certificate management form and personnel attendance form). For each control form, a non-control form can be set up at its subordinate level. The control form here will correspond to a real table data in the database, while the non-control form has no corresponding table data in the database, but shares a real table data with the control form to which it belongs.

[0004] In the prior art, in order to implement the authority management of non-control form data, an authentication scheme is generally written for each non-control form, which will cause problems such as strong business code intrusion and complex development. Summary of the invention

[0005] The embodiments of the present invention provide a method and related device for authenticating data permissions of non-control forms, which are used to configure verification information for non-control forms in a customized manner, rather than configuring verification information for non-control forms by writing code as in the prior art. This avoids the problem of strong intrusion of business codes into non-control forms in the prior art, and correspondingly achieves flexibility and convenience in configuring verification information for non-control forms.

[0006] A first aspect of an embodiment of the present application provides a method for authenticating non-control form data permissions, including:

[0007] Receiving an operation request for the non-control form;

[0008] According to the operation request, calling the authentication model to obtain the non-control authority form and the operation for the non-control authority form from the context information of the non-control authority form;

[0009] Obtaining operation permission configuration items pre-configured for the non-control form, wherein the operation permission configuration items at least include: business operations, associated authentication entities, first associated permission items, and functional permission checks, wherein the associated authentication entity is used to indicate the control form to which the non-control form belongs, the first associated permission item is used to indicate the non-control form, and the functional permission check is used to indicate the execution of business operation authentication on the non-control form;

[0010] Match the non-control form and the operation on the non-control form with the pre-configured operation permission configuration item; if it is determined according to the matching result that the non-control form is set with a matching operation permission configuration, obtain the authentication data identifier set for the non-control form, wherein the authentication data identifier is used to indicate the control form to which the non-control form belongs;

[0011] According to the operation permission configuration item, the non-control right form and the operation on the non-control right form, a pre-function permission authentication is performed on the operation on the non-control right form, wherein the pre-function permission authentication is used to indicate the authentication of the operation on the non-control right form;

[0012] If all the data in the non-control form are authenticated, the operation performed on the non-control form is received, and the business logic after the operation is triggered.

[0013] A second aspect of an embodiment of the present application provides an authentication device for non-control form data permissions, including:

[0014] A receiving unit, configured to receive an operation request for the non-control form;

[0015] An acquisition unit, configured to call an authentication model to acquire the non-control authority form and an operation on the non-control authority form from context information of the non-control authority form according to the operation request;

[0016] The acquisition unit is further used to acquire the operation permission configuration items pre-configured for the non-control right form, wherein the operation permission configuration items at least include: business operations, associated verification entities, first associated permission items and functional permission checks, the associated verification entity is used to indicate the control right form to which the non-control right form belongs, the first associated permission item is used to indicate the non-control right form, and the functional permission check is used to indicate the execution of business operation authentication for the non-control right form;

[0017] A determination unit, for obtaining an authentication data identifier set for the non-control form if it is determined that the non-control form is set with a matching operation permission configuration based on the non-control form, the operation on the non-control form and the pre-configured operation permission configuration item, wherein the authentication data identifier is used to indicate the control form to which the non-control form belongs;

[0018] A pre-authentication unit, used for performing a pre-functional authority authentication on the operation of the non-control right form according to the operation authority configuration item, the non-control right form and the operation on the non-control right form, wherein the pre-functional authority authentication is used to indicate the authentication of the operation on the non-control right form;

[0019] The receiving unit is further configured to receive an operation performed on the non-control authority form and trigger the business logic after the operation if all the data in the non-control authority form are authenticated.

[0020] A third aspect of an embodiment of the present application provides a computer device, including a processor and a memory, which, when executing a computer program stored in the memory, is used to implement the authentication method for non-control form data permissions provided in the first aspect of the embodiment of the present application.

[0021] A fourth aspect of an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the computer program is used to implement the authentication method for non-control form data permissions provided in the first aspect of an embodiment of the present application.

[0022] A fifth aspect of an embodiment of the present application provides a computer program product on which a computer program is stored. When the computer program is executed by a processor, it is used to implement the authentication method for non-control form data permissions provided in the first aspect of an embodiment of the present application.

[0023] It can be seen from the above technical solutions that the embodiments of the present invention have the following advantages:

[0024] When an operation request for a non-control form is received, the embodiment of the present application calls the authentication model to obtain the non-control form and the operation for the non-control form from the context information of the non-control form, obtains the operation permission configuration item of the non-control form, and matches the non-control form and the operation for the non-control form with the operation permission configuration item of the non-control form. If it is determined according to the matching result that the non-control form is set with a matching operation permission configuration, the authentication data identifier set by the non-control form is obtained, and according to the operation permission configuration item, the non-control form and the operation for the non-control form, the pre-function permission authentication is performed on the operation of the non-control form. If all data in the non-control form are authenticated, the operation performed on the non-control form is received, and the business logic after the operation is triggered.

[0025] Because the embodiment of the present application configures the authentication configuration information for non-control forms by pre-custom configuration, compared with the prior art method of writing an authentication scheme for each non-control form through code, it avoids the problem of strong intrusion of business codes into non-control forms in the prior art, and correspondingly realizes the flexibility and convenience of configuring authentication information for non-control forms. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] Figure 1 This is a schematic diagram of the architecture of the authentication system for non-control form data permissions in an embodiment of the present application;

[0027] Figure 2 A schematic diagram of an embodiment of a method for authenticating non-control form data permissions in an embodiment of the present application;

[0028] Figure 3 A schematic diagram of an interface for authentication configuration information of a non-control form in an embodiment of the present application;

[0029] Figure 4 A schematic diagram of another embodiment of a method for authenticating non-control form data permissions in an embodiment of the present application;

[0030] Figure 5 Another interface diagram of the authentication configuration information of the non-control form in the embodiment of the present application;

[0031] Figure 6 Another interface diagram of the authentication configuration information of the non-control form in the embodiment of the present application;

[0032] Figure 7 A schematic diagram of another embodiment of a method for authenticating non-control form data permissions in an embodiment of the present application;

[0033] Figure 8 A schematic diagram of an embodiment of an authentication device for non-control form data permissions in an application embodiment. DETAILED DESCRIPTION

[0034] An embodiment of the present invention provides an authentication method and related device for non-control form data permissions, which is used to configure verification information for non-control forms in a customized manner, rather than configuring verification information for non-control forms by code writing as in the prior art. This avoids the problem of strong intrusion of business codes into non-control forms in the prior art, and correspondingly achieves the flexibility of configuring verification information for non-control forms.

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

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

[0037] An embodiment of the present application provides an authentication method for non-control form data permissions. The general principle of the authentication method for non-control form data permissions is: when it is necessary to verify the authorization of an operation request for a non-control form, the authentication model is called according to the operation request to obtain the non-control form and the operation for the non-control form from the context information of the non-control form; the operation permission configuration items pre-configured for the non-control form are obtained, wherein the operation permission configuration items at least include: business operations, associated verification entities, first associated permission items and functional permission verification, the associated verification entity is used to indicate the control form to which the non-control form belongs, the first associated permission item is used to indicate the non-control form, and the functional permission verification is used to indicate the execution of business operation authentication for the non-control form; the non-control form and the operation for the non-control form are matched with the pre-configured operation permission configuration items, and if it is determined according to the matching result that the non-control form is set with If the operation permission configuration matches, the authentication data identifier set for the non-control form is obtained, wherein the authentication data identifier is used to indicate the control form to which the non-control form belongs; according to the operation permission configuration item, the non-control form and the operation on the non-control form, the pre-function permission authentication is performed on the operation of the non-control form, wherein the pre-function permission authentication is used to indicate the authentication of the operation on the non-control form; if all the data in the non-control form are authenticated, the operation performed on the non-control form is received, and the business logic after the operation is triggered, that is, the embodiment of the present application configures the operation verification information for the non-control form by custom configuration, thereby avoiding the problem of strong code intrusion into the non-control form caused by configuring the operation verification information for the non-control form by code writing in the prior art, and correspondingly realizes the flexibility and convenience of configuring the operation verification information for the non-control form.

[0038] In order to better implement the above-mentioned non-control form data permission authentication method, the present application embodiment provides a non-control form data permission authentication system, please refer to Figure 1 , Figure 1A schematic diagram of the architecture of an authentication system for non-control form data permissions provided for an embodiment of the present application. The authentication system for non-control form data permissions may include at least one terminal device 101 and a server 102; different types of applications may be installed on the terminal device 101, for example, WPS, Excel, instant messaging applications, live broadcast applications, conference communication applications, etc. may be installed on the terminal device 101; the terminal device 101 may be a smart phone, tablet computer, laptop computer, desktop computer, smart car, etc. The server 102 may authenticate the non-control form data in each application installed in the terminal device. The server 102 may be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDN), and basic cloud computing services such as big data and artificial intelligence platforms, etc.

[0039] Among them, the authentication method for non-control form data permissions is executed by the terminal device 101 or the server 102. When the authentication method for non-control form data permissions is executed by the terminal device 101, the terminal device 101 can, when receiving an operation request for a non-control form, call the authentication model from the server 102 to obtain the non-control form and the operation for the non-control form from the context information of the non-control form; obtain the pre-configured operation permission configuration item of the non-control form, match the non-control form and the operation for the non-control form with the pre-configured operation permission configuration item, if it is determined according to the matching result that the non-control form is set with a matching operation permission configuration, then obtain the authentication data identifier set for the non-control form, and perform pre-function permission authentication on the operation for the non-control form according to the operation permission configuration item, the non-control form and the operation for the non-control form; if all data in the non-control form are authenticated, then receive the operation performed on the non-control form and trigger the business logic after the operation.

[0040] For ease of understanding, the following describes the authentication method for non-control form data permissions in the embodiment of the present application. Figure 2 , an embodiment of the authentication method of non-control form data permissions in the embodiment of the present application includes:

[0041] 201. Receive an operation request for a non-control form;

[0042] For ease of understanding, a brief description is first given of the non-control form in the embodiment of the present application: In order to facilitate the management of data, data is generally managed and stored in the form of a table to facilitate the management and operation of the data.

[0043] If the data is personnel basic information data, and this type of personnel basic information data can be applied in different scenarios, such as applying personnel basic information in the attendance scenario, or applying personnel basic information in the document management scenario, and in order to realize the application of the same personnel basic information data in different scenarios, multiple subordinate non-control forms can be set for the same personnel basic information form data, and the non-control form here actually has no actual form data in the database, but only when displaying, the corresponding data is filtered out from the above-mentioned personnel basic information form. For example, in the attendance scenario, the information form of the personnel who need attendance can be filtered out from the above-mentioned personnel basic information form for display, and in the document management scenario, the information form that needs to execute document management is filtered out from the listed personnel basic information form for display.

[0044] That is to say: the non-control form in the embodiment of the present application is actually subordinate to the control form (that is, the personnel basic information form in the above embodiment), and the non-control form has no corresponding data entity in the database, because the data entity behind the non-control form is actually the data in the control form.

[0045] In the prior art, when setting data permissions for non-control forms, fixed verification codes are generally written into the non-control forms through code writing, thereby implementing data verification of the non-control forms through the verification code. This will lead to strong intrusion into the business code of the non-control form data and complex development.

[0046] To address this problem, the embodiment of the present application configures the operation authentication information for the non-control right form by means of a custom configuration, thereby achieving flexibility and convenience in configuring the operation authentication information for the non-control right form.

[0047] Specifically, when a user needs to operate a non-control form, a non-control form operation request may be sent to the client. The operation request may be an add, delete or modify request for the non-control form. There is no specific restriction on the type of operation.

[0048] 202. According to the operation request, the authentication model is called to obtain the non-control form and the operation on the non-control form from the context information of the non-control form;

[0049] When an operation request for a non-control form is received, the authentication model is called to obtain the non-control form and the operation for the non-control form from the context information of the non-control form. For example, when step 201 is an add operation for the non-control form, the operation for the non-control form here is an add operation for the non-control form, and when step 201 is a delete operation for the non-control form, the operation for the non-control form here is a delete operation.

[0050] 203. Obtain operation permission configuration items pre-configured for the non-control form, wherein the operation permission configuration items at least include: business operation, associated verification entity, first associated permission item and functional permission check, wherein the business operation is used to indicate the operation that needs to be authenticated for the non-control form, the associated verification entity is used to indicate the controlling form to which the non-control form belongs, the first associated permission item is used to indicate the non-control form, and the functional permission check is used to indicate the authentication of the business operation for the non-control form;

[0051] When the authentication model is called to obtain the non-control form and the operation on the non-control form from the context information of the non-control form, the operation permission configuration items pre-set for the non-control form are obtained, wherein the operation permission configuration items include at least: business operations, associated verification entities, associated permission items and functional permission verification, wherein the business operations are used to indicate the operations allowed for the non-control form, the associated verification entity is used to indicate the controlling form to which the non-control form belongs, the first associated permission item is used to indicate the non-control form, and the functional permission verification is used to indicate the operation authentication for the non-control form.

[0052] For ease of understanding, Figure 3 A graphical interface diagram of a non-control form controlling form operation permissions is given. Figure 3 In the context of business operations, business operations refer to operations allowed on non-control forms, such as Figure 3 If the business operation in is OK, then clicking "OK" for the non-controlling form requires operation verification, and the associated verification entity is used to indicate the controlling form to which the non-controlling form belongs, such as Figure 3 The associated verification entity in is "Certificate Management", that is, the control form to which the non-control form "Borrowing Registration" belongs is the "Certificate Management" form, and the associated permission item is used to indicate the non-control form, such as Figure 3 The first associated permission item in the "Lending Registration" form is to perform operation verification on the non-control form data of "Lending Registration", and the functional permission verification is used to indicate that the operation verification needs to be performed on the non-control form, such as Figure 3 In the case of a non-control form, authentication is required when performing a confirmation operation on the non-control form.

[0053] 204. Match the non-control form and the operation on the non-control form with the pre-configured operation permission items. If it is determined according to the matching result that the non-control form has no matching operation permission configuration, receive the permission operation performed on the non-control form and trigger the business logic after the permission operation.

[0054] When it is determined that the non-control form has no matching operation permission configuration according to the non-control form and the operation on the non-control form, the permission operation performed on the non-control form is received, and the business logic after the permission operation is triggered.

[0055] Specifically, the non-control form here has no matching operation permission configuration, that is, no corresponding operation permission is set for the non-control form. Then, the permission operation performed on the non-control form is received, and the business logic after the permission operation is triggered. If it is a deletion operation for the non-control form data, the deletion of the corresponding non-control form data is triggered.

[0056] It should be noted here that step 204 is only an optional execution step in the embodiment of the present application, and is not a required step.

[0057] 205. Match the non-control form and the operation on the non-control form with the pre-configured operation permission items. If it is determined according to the matching result that the non-control form is set with a matching operation permission configuration, then obtain the authentication data identifier set for the non-control form, or obtain the authentication data identifier and the authentication failure control policy set for the non-control form, wherein the authentication data identifier is used to indicate the control form to which the non-control form belongs, and the authentication failure control policy includes the control policy for the authentication failure of all data in the non-control form, and / or the control policy for the authentication failure of part of the data in the non-control form;

[0058] If it is determined based on the non-control form and the operations on the non-control form that the non-control form is set with a matching operation permission configuration, that is, operation permissions are set for the non-control form, then the authentication data identifier set for the non-control form is obtained, wherein the authentication data identifier here is used to indicate the control form to which the non-control form belongs. For example, when a non-control form belongs to multiple control forms, the authentication data identifier here is used to indicate the multiple control forms to which the non-control form belongs, such as in Figure 3 In the schematic diagram, if the borrowing registration belongs not only to the certificate management but also to the book management, then the authentication data identifier here includes not only the certificate management but also the book management.

[0059] Further, as an optional embodiment, because in a business scenario, when authentication fails (all authentication fails or partial authentication), the system default logic is to terminate execution, and in an actual business scenario, such as in the "loan registration" business scenario, when partial authentication fails, we can also set the non-control form data that has been successfully authenticated to execute the corresponding business logic. Therefore, the embodiment of the present application can also obtain the authentication failure control policy set for the non-control form when the non-control form is set with a matching operation permission configuration, and control the non-control form data to execute the corresponding business logic according to the authentication failure control policy.

[0060] Specifically, the control strategy for authentication failure here includes a control strategy for authentication failure of all non-control form data and / or a control strategy for authentication failure of part of the data in the non-control form.

[0061] 206. According to the operation authority configuration item, the non-control authority form, the authentication data identifier, and the operation on the non-control authority form, a pre-function authority authentication is performed on the operation on the non-control authority form, wherein the pre-function authentication is used to indicate the authentication of the operation on the non-control authority form;

[0062] After obtaining the operation permission configuration item for the non-control form, the pre-function permission authentication is performed for the operation of the non-control form. The pre-function authentication here is used to indicate the authentication of the operation of the non-control form. The pre-function authentication here includes: determining whether the above-mentioned associated verification entity belongs to the authentication data identifier, determining whether the operation for the non-control form is the above-mentioned business operation, if the operation for the non-control form is the above-mentioned business operation, then performing function permission authentication for the operation.

[0063] As in Figure 3 In the example, if the associated authentication entity is "certificate management", it is first determined whether "certificate management" belongs to the authentication data identifier. If "certificate management" belongs to the authentication data identifier, the operation for the non-control form is further obtained. If the operation for the non-control form is "OK", the pre-function authentication is performed for the "OK" operation. If the operation for the non-control form is "Add", the pre-function authentication is not performed for the "Add" operation. The pre-function authentication here is to verify whether the operation behavior obtained in the context information is allowed to be performed on the non-control form. For example, if the operation behavior for the non-control form is "OK" obtained in the context information, the confirmation behavior is authenticated. If the operation behavior for the non-control form obtained from the context information is "Add", the addition behavior is not authenticated.

[0064] 207. If all data in the non-control form are authenticated, the operation performed on the non-control form is received and the business logic after the operation is triggered.

[0065] When all the data in the non-control form are authenticated, the operation performed on the non-control form is received and the business logic after the operation is triggered.

[0066] As in Figure 3 In the process, if the data in the "borrowing registration" form are authenticated, the "OK" operation clicked on the non-control form is received, and the business logic after the "OK" operation is triggered, that is, the certificate in the non-control form data is triggered to be borrowed and registered.

[0067] 208. If some of the data in the non-control form passes the authentication, the data in the non-control form is controlled to execute corresponding business logic according to the authentication failure control strategy.

[0068] Optionally, because the authentication failure control policy set for the non-control form is also obtained in step 205, when some data in the non-control form are authenticated, the embodiment of the present application controls the data in the non-control form to execute corresponding business logic according to the authentication failure control policy.

[0069] Because the embodiment of the present application configures the authentication configuration information for non-control forms by pre-custom configuration, compared with the prior art method of writing an authentication scheme for each non-control form through code, it avoids the problem of strong intrusion of business codes into non-control forms in the prior art, and correspondingly realizes the flexibility and convenience of configuring authentication information for non-control forms.

[0070] Furthermore, the embodiments of the present application can also control the business access policy in the scenario where data authentication fails in the non-control form, thereby improving the flexibility and convenience of controlling the non-control form data in the business scenario.

[0071] based on Figure 2 The embodiment described above, the control strategy for failure of authentication of some data in the non-control form is described in detail below:

[0072] As an optional embodiment, if the control strategy for authentication failure of some data in the non-control form includes: continuing to execute the business logic for some data that passed the authentication, and terminating the business logic for some data that did not pass the authentication, then when controlling the data in the non-control form to execute the corresponding business logic according to the authentication failure control strategy, the following operations can be specifically performed:

[0073] The business logic is executed for the partial data that passes the authentication to obtain the corresponding business operation result, and the mark deletion is performed for the partial data that fails the authentication to cache the partial data that fails the authentication and the corresponding authentication result.

[0074] Specifically, when some data in a non-control form fails to be authenticated, in order to avoid the influence of some failed data on the business logic executed by the data that passed authentication, the embodiment of the present application can perform mark deletion (false deletion) on the part of the data that failed authentication, and cache the part of the data that failed authentication and the corresponding authentication results, so as to facilitate post-authentication of the business logic executed by the data that failed authentication and the data that passed authentication, and prompt the user with the post-authentication data.

[0075] Specifically, when performing post-authentication, the embodiment of the present application specifically performs the following operations:

[0076] Obtain partial data that failed authentication and the corresponding authentication results from the cache, obtain the business operation results of the data that passed authentication, integrate the partial data that failed authentication and the corresponding authentication results, and the business operation results to obtain an integrated result set, and display a prompt message of authentication failure based on the integrated result set, that is, the result set after post-authentication.

[0077] Because the embodiment of the present application caches the data that failed to be authenticated and the authentication results when partial authentication of the data in the non-control form fails, it makes it possible to perform data integration based on the data that failed to be authenticated and the business operation results of the data that succeeded in authentication, and display a prompt message of the authentication failure based on the integrated result set, thereby improving the convenience of displaying the detailed information of the total authentication data in the authentication failure scenario to the user.

[0078] Specifically, as an optional embodiment, in order to improve the convenience of the authentication process and improve the authentication efficiency, Figure 2 Step 206 in the embodiment, that is, when executing the step of "performing pre-function permission authentication for operations on non-control form according to the operation permission configuration item", the embodiment of the present application can also operate according to the following steps:

[0079] For example, when performing pre-functional permission authentication for operations of non-control forms according to the operation permission configuration items, the pre-functional permission authentication for operations of non-control forms can be performed by calling the authentication model. Specifically, when using the authentication model to perform pre-functional authentication for non-control forms, a base class method can be set in the authentication model, wherein the method base class in the authentication model includes: a pre-authentication method base class, a pre-authentication result processing method base class, and a method base class for processing authentication failure data. Because after the method base class is set in the authentication model, when the authentication model is applied to different business scenarios, the base class method can also be inherited by the business side plug-ins in different business scenarios to implement the method base class in different scenarios, thereby avoiding the step of compiling a corresponding authentication method for each business scenario, and improving the versatility of the authentication model in different business scenarios.

[0080] based on Figure 2 In the embodiment described above, in addition to configuring the operation authentication configuration information of the non-control form by means of pre-customized configuration, the authentication configuration information of the non-control form can also be configured by means of pre-customized configuration, wherein the authentication configuration information here is the authentication configuration for the access operation of the non-control form. The following describes the process of authenticating the access request of the non-control form, please refer to Figure 4 :

[0081] 401, receiving access request to non-control form;

[0082] Specifically, before receiving an operation request for a data form, an access request for the data form needs to be received, wherein the access request is used to perform a viewing operation on the data form.

[0083] Specifically, when receiving an access request for non-controlling data expression, the user may be provided with an access request for a non-controlling data form through a data link or through client login. There is no specific restriction on the form in which the user accesses the non-controlling data form.

[0084] 402. According to the access request, the form authentication service is called to obtain the authentication configuration information of the non-control form, wherein the authentication configuration information of the non-control form records whether the non-control form needs authentication and the authentication configuration items required when authentication is needed;

[0085] When receiving a request to access non-control form data, the embodiment of the present application can call the form authentication service to obtain the configuration information of the non-control form, wherein the authentication configuration information of the non-control form records whether the non-control form requires authentication, and the authentication configuration items required when authentication is required.

[0086] Specifically, the form authentication service in the embodiment of the present application may be a service stored in a separate server, or a service integrated in a data control center. No specific limitation is imposed on the storage address of the form authentication service.

[0087] In addition, when calling the form authentication service, it can be called through an API interface, or through a microservice, etc. There is no specific restriction on the form of calling the form authentication service.

[0088] Furthermore, the authentication configuration information of the non-control form records whether the non-control form needs authentication, and detailed information of the authentication configuration items required when authentication is required. As a specific embodiment, it can be recorded in the form of an interface for easy understanding. Figure 5A schematic diagram of the specific information interface is given to show whether verification is required for non-control forms and the verification configuration items required when verification is required.

[0089] 403. If it is determined that the non-control form needs to verify the authority based on the authority verification configuration information of the non-control form, then obtain the associated authority verification entity and the second associated authority item pre-customized and configured for the non-control form, as well as the context information of the non-control form, wherein the second associated authority verification entity is used to characterize the control form to which the non-control form belongs, the associated authority item is used to characterize the operation type of the access object on the non-control form, and the context information of the non-control form at least includes the non-control form, the control form to which the non-control form belongs, and the access object identifier;

[0090] When it is determined that the non-control form needs to verify permissions based on the verification configuration information of the non-control form, the associated verification entity and associated permission items that are pre-customized for the non-control form, as well as the context information of the non-control form are obtained, wherein the pre-configured associated verification entity is used to characterize the controlling form to which the non-control form belongs, and the associated permission items are used to characterize the operation type of the access object on the non-control form, and the context information of the non-control form includes at least the non-control form, the controlling form to which the non-control form belongs, and the access object identifier.

[0091] Specifically in Figure 5 In the schematic diagram, the basic information is lending registration, that is, the non-control form accessed is the lending registration form data, and the form verification permission is turned on, that is, the form verification permission is set for the non-control form data (lending registration form data). The associated verification entity in the form permission configuration is used to represent the control form data to which the lending registration form data belongs. Figure 5 The data in the middle is the certificate management form data, that is, the controlling form data to which the lending registration form data belongs is the certificate management form data, that is, in the database, only the certificate management form data corresponds to a real data form, and the lending registration form data is just displayed by filtering out the corresponding data from the certificate management form data, and there is no real form data corresponding to the lending registration form data in the database.

[0092] The second associated permission item is used to represent the type of operation that the access object performs on the non-control form. Figure 3 In the middle, it means to view, that is, when viewing the lending registration form data, it is necessary to perform form permission verification. Only after the verification is passed, can it be viewed, otherwise it will be prompted that there is no permission to view. The context information of the non-controlling form at least includes the non-controlling form, the controlling form to which the non-controlling form belongs, and the access object identifier, so as to judge whether the access object can access the non-controlling form through the context information of the non-controlling form and the verification configuration information of the non-controlling form.

[0093] 404. If it is determined that the access object has the right to access the non-control form according to the associated authentication entity and the associated permission item pre-customized and configured for the non-control form and the context information of the non-control form, the access object is allowed to access the non-control form.

[0094] After obtaining the access object identifier and the non-control form, as well as the controlling form to which the non-control form belongs based on the context information of the non-control form, it is further determined whether the access object has the authority to view the non-control form. If so, the access object is allowed to access the non-control form, otherwise it is prompted that the access object cannot view the non-control form.

[0095] Specifically, the judgment process is as follows:

[0096] Because the context information of the non-control form records the non-control form, the control form to which the non-control form belongs, and the access object identifier, specifically in the authentication process, the non-control form in the context information is compared with the non-control form in the access request, the control form in the context information is compared with the pre-custom configured associated authentication entity, and the access request in the context is compared with the pre-custom configured second associated permission item. If the comparison is successful and it is determined in the terminal authentication that the access object identifier has access rights, it is determined that the access object has the right to access the non-control form, and the access object is allowed to access the non-control form.

[0097] As an optional embodiment, in order to facilitate users to customize the authentication configuration information of non-control forms, the embodiment of the present application can receive the user's configuration of the basic information of the non-control form and the authentication configuration items through a graphical interface, thereby improving the flexibility and convenience of the user's configuration of the basic information of the non-control form and the authentication configuration items.

[0098] In an embodiment of the present application, when a user's access request to a non-control form is received, the form authentication service is called to obtain the verification configuration information of the non-control form, and when it is determined that the non-control form requires verification authority, the associated verification entity and associated verification items that are pre-customized and configured for the non-control form, as well as the context information of the non-control form are further obtained, so as to determine whether the access object has the authority to access the non-control form based on the context information of the non-control form and the verification configuration items of the non-control form. Because the embodiment of the present application configures the verification configuration information of the non-control form by pre-customization, the flexibility and convenience of configuring the verification configuration items of the non-control form are improved.

[0099] Furthermore, before calling the authentication configuration information of the non-control form, it is also necessary to configure the authentication information of the non-control form. As an optional embodiment, in order to improve the convenience of the configuration process, the configuration information of the non-control form can be configured through a graphical interface. Specifically, the schematic diagram of the configuration interface is as follows: Figure 5 As shown, Figure 5 The basic information in is used to configure non-control form and form verification permissions. For example, if the non-control form is "borrowing registration", the form verification permission is used to open or close it through a button. When the button is turned on, the "form verification" permission needs to be set for the non-control form. When the button is turned off, the "form verification" permission does not need to be set for the non-control form. The form permission configuration is used to show that when performing the operation in the second associated permission item operation on the non-control form, it is necessary to perform the verification operation on the control form (that is, the associated verification entity) to which the non-control form belongs, such as Figure 5 The non-control form of "borrowing registration" belongs to the control form "certificate management". When performing the "view" operation on the form data of "borrowing registration", it is necessary to perform the authorization operation on "certificate management". The form operation permission configuration is used to configure which operations on the form require authorization operations on the non-control form. Among them, the form operation permission configuration includes business operations, associated authorization entities, the first associated authorization item and functional authorization verification. For example, in Figure 5 In the case of performing the "Confirm" operation on the "Loan Registration" form data, it is necessary to verify the functional permissions of the "Certificate Management" in the same way as the microservice verification or system verification, and after the verification is passed, the "Confirm" operation is allowed on the "Loan Registration" form data.

[0100] Furthermore, as an optional embodiment, when non-control form data belongs to different applications, you can also set "authorization verification application" in the form permission configuration. For example, when "borrowing registration" belongs not only to the foreign affairs management application but also to the personnel management application, when verifying the form permissions, you can also verify the application to which the non-control form belongs. The form operation permission configuration can further include "operation scenario coding", "authorization verification application" and "data permission verification". For ease of understanding, Figure 6 Another schematic diagram of the authentication information configuration interface is given, in which the authentication application is used to indicate the application to which the non-control form belongs, and the operation scenario code is used to indicate the scenario of the business operation, mainly to facilitate the identification of the business scenario, such as Figure 6The business scenario code "SSC-OP-001" indicates that the "OK" operation is clicked in the form data of "Lending Registration", and the authentication application "Foreign Affairs Management of Central State-owned Enterprises" is used to indicate that the application to which "Lending Registration" belongs is "Foreign Affairs Management of Central State-owned Enterprises", and the authentication method is the authentication method used when authenticating business operations, which can be specifically authenticated by microservice authentication or system authentication. When calling the microservice for authentication, the microservice is called to verify whether the operation of the access object on the non-control form is allowed, while the system authentication not only verifies whether the operation of the access object on the non-control form is allowed, but also verifies the system status of the non-control form data. For example, when clicking on a certain "Lending Registration" data to perform the "OK" operation authentication, a mutual exclusion check is also performed on the "Lending Registration" data, such as whether the non-control data to be lent out has been lent out, etc. That is, in addition to performing the operation authentication, the business status verification also needs to be performed to ensure that the status of the non-control form data is normal.

[0101] The embodiment of the present application can not only configure the form permissions and form operation permissions of non-control form data, but also verify the permissions of the application to which the non-control form belongs, thereby suggesting the convenience of authenticating different non-control form data in different applications.

[0102] For ease of understanding, the following describes the process of performing pre-authentication and post-authentication on non-control form data when form authentication and form operation authentication are required. Please refer to Figure 7 :

[0103] 701. Receive an authentication request for a non-control form;

[0104] 702. Call the pre-authentication component to execute the non-control form Figure 2 Form authentication and Figure 4 Pre-authentication of form operation in the embodiment;

[0105] 703. If all data in the non-control form are authenticated successfully, the business logic is triggered;

[0106] 704. If authentication of some data in the non-authorization form fails, the post-authentication component is called to obtain the authentication failure data and the corresponding authentication results, as well as the business operation results of the authentication passed data from the cache, and the authentication failure data and the corresponding authentication results, as well as the business operation results are integrated, and the authentication failure prompt information is displayed according to the result set after data integration.

[0107] It should be noted that the above steps are similar to those described in the previous method embodiments and can be referenced to each other, and will not be repeated here.

[0108] It is understandable that, in various embodiments of the present invention, the sequence numbers of the above steps do not mean the order of execution. The order of execution of the steps should be determined by their functions and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0109] The above describes in detail the authentication method of the non-control form data permission in the embodiment of the present application. Next, the authentication device of the non-control form data permission in the embodiment of the present application is described. Figure 8 , an embodiment of the authentication device for non-control form data permissions in the embodiment of the present application includes:

[0110] The receiving unit 801 is used to receive an operation request for the non-control form;

[0111] The acquisition unit 802 is used to call the authentication model to acquire the non-control authority form and the operation for the non-control authority form from the context information of the non-control authority form according to the operation request;

[0112] The acquisition unit 802 is further used to acquire the operation permission configuration items pre-configured for the non-control form, wherein the operation permission configuration items at least include: business operations, associated verification entities, first associated permission items and functional permission checks, the associated verification entity is used to indicate the control form to which the non-control form belongs, the first associated permission item is used to indicate the non-control form, and the functional permission check is used to indicate the execution of business operation authentication on the non-control form;

[0113] The determination unit 803 is used to obtain the authentication data identifier set for the non-control form if it is determined that the non-control form is set with a matching operation permission configuration based on the non-control form, the operation on the non-control form and the pre-configured operation permission configuration item, wherein the authentication data identifier is used to indicate the control form to which the non-control form belongs;

[0114] The pre-authentication unit 804 is used to perform pre-functional authority authentication on the operation of the non-control right form according to the operation authority configuration item, the non-control right form, the authentication data identifier and the operation on the non-control right form, wherein the pre-functional authority authentication is used to indicate the authentication of the operation on the non-control right form;

[0115] The receiving unit 801 is further configured to receive an operation performed on the non-control authority form if all data in the non-control authority form has passed the authentication, and trigger the business logic after the operation.

[0116] Preferably, the acquisition unit 802 is further configured to:

[0117] Obtaining an authentication failure control policy set for the non-control authority form, wherein the authentication failure control policy includes a control policy for authentication failure of all data in the non-control authority form and / or a control policy for authentication failure of part of the data in the non-control authority form;

[0118] The authentication device also includes:

[0119] The control unit 805 is used to control the data in the non-control authority form to execute corresponding business logic according to the authentication failure control strategy if some of the data in the non-control authority form passes the authentication.

[0120] Preferably, the control unit 805 is specifically used for:

[0121] Execute business logic for some of the data that has passed authentication to obtain the corresponding business operation results;

[0122] Mark and delete some data that fails authentication;

[0123] The partial data that failed the authentication and the corresponding authentication results are cached.

[0124] Preferably, the authentication device further comprises:

[0125] A post-authentication unit 806, configured to obtain the partial data that failed the authentication and the corresponding authentication result from the cache;

[0126] Obtaining the business operation result;

[0127] Post-authentication is performed on the partial data that failed the authentication and the corresponding authentication results, as well as the business operation results, to obtain a result set after post-authentication, wherein the post-authentication is used to perform data integration on the partial data that failed the authentication and the corresponding authentication results, as well as the business operation results;

[0128] According to the result set after the post-authentication, a prompt message of authentication failure is displayed.

[0129] Preferably, the pre-authentication unit 804 is specifically used for:

[0130] Calling the authentication model to perform pre-function permission authentication on the operation of the non-control form, wherein the authentication model is provided with a base class method;

[0131] Preferably, the authentication device further comprises:

[0132] The setting unit 807 is used to inherit the base class method through the service side plug-in, and set the authentication data identifier and the authentication failure control strategy by implementing the base class pre-method.

[0133] Preferably, the receiving unit 801 is further used for:

[0134] Receive access requests to non-control forms;

[0135] The acquisition unit 802 is further configured to:

[0136] According to the access request, the form authentication service is called to obtain the authentication configuration information of the non-control form;

[0137] If it is determined that the non-control form requires verification of permissions based on the verification configuration information of the non-control form, then the associated verification entity and the second associated permission item pre-configured for the non-control form, as well as the context information of the non-control form, are obtained, wherein the second associated permission item is used to indicate the viewing operation performed on the non-control form;

[0138] The determining unit 803 is further configured to:

[0139] If it is determined that the access object has the right to access the non-control form based on the associated authentication entity and the second associated permission item pre-configured for the non-control form and the context information of the non-control form, the access object is allowed to access the non-control form.

[0140] Preferably, the receiving unit 801 is further used for:

[0141] The basic information of the custom configuration, form permission configuration and form operation permission configuration are received through a graphical interface, wherein the basic information includes the non-control form and form verification form permission, the form permission configuration includes the associated verification entity and the associated permission item, and the form operation permission configuration includes business operations, associated verification entities, associated permission items and functional permission verification.

[0142] Preferably, the form permission configuration also includes an authorization application, and the form operation permission configuration also includes an operation scenario code, the authorization application, an authorization method and data permission verification, wherein the operation scenario code is used to indicate the scenario of the business operation, and the authorization application is used to indicate the application to which the non-control form belongs.

[0143] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0144] Because the embodiment of the present application configures the authentication configuration information of the non-control form by pre-customizing the configuration, the flexibility and convenience of configuring the authentication configuration items of the non-control form are improved.

[0145] The above describes the authentication device for non-control form data permissions in the embodiment of the present invention from the perspective of modular functional entities. The following describes the computer device in the embodiment of the present invention from the perspective of hardware processing:

[0146] The computer device is used to implement the function of an authentication device for non-control form data permissions. In an embodiment of the present invention, an embodiment of the computer device includes:

[0147] Processor and memory;

[0148] When the memory is used to store a computer program and the processor is used to execute the computer program stored in the memory, the steps in the above method embodiment can be implemented.

[0149] It can be understood that when the processor in the computer device described above executes the computer program, it can also implement the functions of the various units in the above-mentioned corresponding device embodiments, which will not be repeated here. Exemplarily, the computer program can be divided into one or more modules / units, and the one or more modules / units are stored in the memory and executed by the processor to complete the present invention. The one or more modules / units can be a series of computer program instruction segments that can perform specific functions, and the instruction segments are used to describe the execution process of the computer program in the authentication device of the non-control form data authority. For example, the computer program can be divided into the various units in the above-mentioned authentication device of non-control form data authority, and each unit can implement the specific functions described in the above-mentioned authentication device of the corresponding non-control form data authority.

[0150] The computer device may be a computing device such as a desktop computer, a notebook, a PDA, and a cloud server. The computer device may include, but is not limited to, a processor and a memory. Those skilled in the art will appreciate that a processor and a memory are merely examples of computer devices and do not constitute a limitation of the computer device. The computer device may include more or fewer components, or a combination of certain components, or different components. For example, the computer device may also include input and output devices, network access devices, buses, and the like.

[0151] The processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc. The processor is the control center of the computer device, and uses various interfaces and lines to connect various parts of the entire computer device.

[0152] The memory can be used to store the computer program and / or module, and the processor realizes various functions of the computer device by running or executing the computer program and / or module stored in the memory, and calling the data stored in the memory. The memory can mainly include a program storage area and a data storage area, wherein the program storage area can store an operating system, at least one application required for a function, etc.; the data storage area can store data created according to the use of the terminal, etc. In addition, the memory can include a high-speed random access memory, and can also include a non-volatile memory, such as a hard disk, a memory, a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (SecureDigital, SD) card, a flash card (Flash Card), at least one disk storage device, a flash memory device, or other volatile solid-state storage devices.

[0153] The present invention also provides a computer-readable storage medium, which is used to implement the function of an authentication device for non-control form data permissions, and a computer program is stored thereon. When the computer program is executed by a processor, the processor can be used to execute the steps in the above method embodiment.

[0154] It is understandable that if the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a corresponding computer-readable storage medium. Based on such an understanding, the present invention implements all or part of the processes in the above-mentioned corresponding embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, U disk, mobile hard disk, disk, optical disk, computer memory, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), electric carrier signal, telecommunication signal and software distribution medium. It should be noted that the content contained in the computer-readable medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media do not include electric carrier signals and telecommunication signals.

[0155] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0156] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0157] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0158] As described above, the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit the same. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features thereof may be replaced by equivalents. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for authenticating non-control form data permissions, characterized in that: include: Receiving an operation request for the non-control form; According to the operation request, calling the authentication model to obtain the non-control authority form and the operation for the non-control authority form from the context information of the non-control authority form; Obtaining operation permission configuration items pre-configured for the non-control form, wherein the operation permission configuration items at least include: business operations, associated authentication entities, first associated permission items, and functional permission checks, wherein the associated authentication entity is used to indicate the control form to which the non-control form belongs, the first associated permission item is used to indicate the non-control form, and the functional permission check is used to indicate the execution of business operation authentication on the non-control form; If it is determined that the non-control form is provided with a matching operation permission configuration according to the non-control form, the operation on the non-control form and the pre-configured operation permission configuration item, then the authentication data identifier set for the non-control form is obtained, wherein the authentication data identifier is used to indicate the control form to which the non-control form belongs; According to the operation authority configuration item, the non-control authority form, the authentication data identifier and the operation on the non-control authority form, a pre-function authority authentication is performed on the operation on the non-control authority form; If all the data in the non-control form are authenticated, the operation performed on the non-control form is received, and the business logic after the operation is triggered.

2. The method according to claim 1, characterized in that The method further comprises: Obtaining an authentication failure control policy set for the non-control authority form, wherein the authentication failure control policy includes a control policy for authentication failure of all data in the non-control authority form and / or a control policy for authentication failure of part of the data in the non-control authority form; If some of the data in the non-control authority form passes the authentication, then according to the authentication failure control strategy, the data in the non-control authority form is controlled to execute the corresponding business logic.

3. The method according to claim 2, characterized in that If authentication of some data in the non-control form fails, the control strategy includes: continuing to execute the business logic for the part of the data that passed the authentication, and terminating the business logic for the part of the data that failed the authentication; According to the authentication failure control strategy, controlling the data in the non-control form to execute corresponding business logic includes: Execute business logic for some of the data that has passed authentication to obtain the corresponding business operation results; Mark and delete some data that fails authentication; The partial data that failed the authentication and the corresponding authentication results are cached.

4. The method according to claim 3, characterized in that The method further comprises: Obtaining the partial data that failed the authentication and the corresponding authentication result from the cache; Obtaining the business operation result; Post-authentication is performed on the partial data that failed the authentication and the corresponding authentication results, as well as the business operation results, to obtain a result set after post-authentication, wherein the post-authentication is used to perform data integration on the partial data that failed the authentication and the corresponding authentication results, as well as the business operation results; According to the result set after the post-authentication, a prompt message of authentication failure is displayed.

5. The method according to claim 1, characterized in that The process of performing pre-function permission authentication on the operation of the non-control form includes: Calling the authentication model to perform pre-function permission authentication on the operation of the non-control form, wherein the authentication model is provided with a base class method; Before obtaining the authentication data identifier set for the non-control form, the method further includes: The base class method is inherited through a service side plug-in, and the authentication data identifier and authentication failure control strategy are set by implementing the base class front method.

6. The method according to claim 1, characterized in that Before receiving an operation request for the non-control form, the method further includes: Receive access requests to non-control forms; According to the access request, the form authentication service is called to obtain the authentication configuration information of the non-control form; If it is determined that the non-control form requires verification of permissions based on the verification configuration information of the non-control form, then the associated verification entity and the second associated permission item pre-configured for the non-control form, as well as the context information of the non-control form, are obtained, wherein the second associated permission item is used to indicate the viewing operation performed on the non-control form; If it is determined that the access object has the right to access the non-control form based on the associated authentication entity and the second associated permission item pre-configured for the non-control form and the context information of the non-control form, the access object is allowed to access the non-control form.

7. The method according to any one of claims 1 to 6, characterized in that: Before receiving the access request to the non-control form, the method further includes: The basic information of the custom configuration, form permission configuration and form operation permission configuration are received through a graphical interface, wherein the basic information includes the non-control form and form verification form permission, the form permission configuration includes the associated verification entity and the associated permission item, and the form operation permission configuration includes business operations, associated verification entities, associated permission items and functional permission verification.

8. The method according to claim 7, characterized in that The form permission configuration also includes an authorization application, and the form operation permission configuration also includes an operation scenario code, the authorization application, an authorization method and data permission verification, wherein the operation scenario code is used to indicate the scenario of the business operation, the authorization method includes microservice authorization or system authorization, and the authorization application is used to indicate the application to which the non-control form belongs.

9. A non-control form data authority authentication device, characterized in that: include: A receiving unit, configured to receive an operation request for the non-control form; An acquisition unit, configured to call an authentication model to acquire the non-control authority form and an operation on the non-control authority form from context information of the non-control authority form according to the operation request; The acquisition unit is further used to acquire the operation permission configuration items pre-configured for the non-control right form, wherein the operation permission configuration items at least include: business operations, associated verification entities, first associated permission items and functional permission checks, the associated verification entity is used to indicate the control right form to which the non-control right form belongs, the first associated permission item is used to indicate the non-control right form, and the functional permission check is used to indicate the execution of business operation authentication for the non-control right form; A determination unit, for obtaining an authentication data identifier set for the non-control form if it is determined that the non-control form is set with a matching operation permission configuration based on the non-control form, the operation on the non-control form and the pre-configured operation permission configuration item, wherein the authentication data identifier is used to indicate the control form to which the non-control form belongs; A pre-authentication unit, used for performing a pre-functional authority authentication on the operation of the non-control right form according to the operation authority configuration item, the non-control right form and the operation on the non-control right form, wherein the pre-functional authority authentication is used to indicate the authentication of the operation on the non-control right form; The receiving unit is further configured to receive an operation performed on the non-control authority form and trigger the business logic after the operation if all the data in the non-control authority form are authenticated.

10. A computer device comprising a processor and a memory, characterized in that: The memory is used to implement the non-control form data authority authentication method according to any one of claims 1 to 8 when executing the computer program stored in the memory.

11. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, it is used to implement the authentication method for non-control form data permissions as described in any one of claims 1 to 8.

12. A computer program product having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, it is used to implement the authentication method for non-control form data permissions as described in any one of claims 1 to 8.

Images