Front-end dynamic data permission binding and verification method, system and readable storage medium

Abstract

The application discloses a front-end dynamic data permission binding and verification method and system and a readable storage medium. The method comprises the following steps: obtaining target data, wherein the target data is derived from front-end dynamic data; extracting a permission factor based on the target data to obtain a permission characteristic value; performing matching verification based on the permission characteristic value and a dynamic matching table to obtain a matching result; and outputting a verification result based on the matching result, wherein the verification result comprises unsuccessful verification, successful verification, illegal verification, code calling, calling error and illegal calling. The application reduces single-path network overhead through multiple dynamic judgments, reduces the problem of exceeding authority at the front-end level, avoids the shortcomings of complex code structure and difficult maintenance through code calling, optimizes the coupling problem of front-end permission and business logic code, improves the timeliness of permission binding and verification and the operability of dynamic management, and facilitates real-time management of users.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data processing, and more particularly, to a front-end dynamic data permission binding and verification method, system and readable storage medium. BACKGROUND

[0002] With the diversification of Internet applications, the types of applications provided to users or developers are also becoming more and more diverse. In actual application, it will involve the use of permission binding and verification functions. Currently, the permission binding has problems such as performance consumption and code maintenance difficulty. For example, front-end permission binding usually needs to perform permission verification every time a user requests, which may increase additional computing and network overhead, thereby affecting the performance of the application.

[0003] In addition, front-end permission binding usually needs to tightly couple permission logic with business logic, which may lead to complex code structure and difficulty in maintenance. When it is necessary to modify or extend the permission function, a large amount of code may need to be modified, which increases the risk of errors and maintenance costs. SUMMARY

[0004] The purpose of the present application is to provide a front-end dynamic data permission binding and verification method, system and readable storage medium, which reduces single-path network overhead through multiple dynamic judgments, reduces the problem of unauthorized access at the front-end level, avoids the disadvantage of complex and difficult-to-maintain code structure through code calling, optimizes the problem of coupling of front-end permission and business logic code, improves the timeliness of permission binding and verification and the operability of dynamic management, and facilitates real-time management by users.

[0005] The first aspect of the present application provides a front-end dynamic data permission binding and verification method, comprising the following steps:

[0006] obtaining target data, wherein the target data is derived from front-end dynamic data;

[0007] extracting permission factors based on the target data to obtain permission feature values;

[0008] based on the permission feature values, performing matching verification combined with a dynamic matching table to obtain a matching result;

[0009] outputting a verification result based on the matching result, wherein the verification result includes unsuccessful verification, successful verification, illegal verification, code calling, calling error and illegal calling.

[0010] In the present application, the target data is obtained, specifically including:

[0011] obtaining a dynamic data stream;

[0012] First-level data distinction is performed based on the dynamic data flow to distinguish the front-end dynamic data;

[0013] Second-level data distinction is performed based on the front-end dynamic data, and specifically, feature parameter identification is performed to extract data with the permission factor to obtain the target data.

[0014] In this solution, the permission factor extraction based on the target data is performed to obtain a permission feature value, specifically including:

[0015] After the target data is obtained, the identified feature parameters are extracted synchronously, wherein the feature parameters include a binding permission feature, a forwarding transition feature, and a storage feature.

[0016] The permission factor extraction is performed based on the feature parameters to obtain the permission feature value from the binding permission feature, wherein the permission feature value includes at least a first feature, a second feature, and a third feature, the first feature includes a known permission factor, the second feature includes an unknown permission factor, and the third feature includes a code call factor.

[0017] In this solution, the matching verification based on the permission feature value and a dynamic matching table is performed to obtain a matching result, specifically including:

[0018] The dynamic matching table is obtained, wherein the dynamic matching table is dynamically updated based on user input.

[0019] The matching verification based on the permission feature value and the dynamic matching table is performed to obtain a matching result, wherein,

[0020] The first feature matching result is outputted by matching the first feature with the dynamic matching table, wherein the first feature matching result includes successful matching and unsuccessful matching.

[0021] The second feature matching result is outputted by matching the second feature with the dynamic matching table, wherein the second feature matching result includes successful matching and unsuccessful matching.

[0022] The third feature matching result is outputted by matching the third feature with the dynamic matching table, wherein the third feature matching result includes successful matching and unsuccessful matching.

[0023] In this solution, the verification result is outputted based on the matching result, specifically including:

[0024] The verification success verification result is obtained based on the successful matching in the first feature matching result and the successful matching in the second feature matching result.

[0025] obtaining a verification result of verification unsuccessful based on the unsuccessful matching in the first feature matching result;

[0026] obtaining a verification result of illegal verification based on the unsuccessful matching in the second feature matching result;

[0027] obtaining a verification result of code calling based on the successful matching in the third feature matching result on the basis of the verification successful;

[0028] obtaining a verification result of verification successful based on the unsuccessful matching in the third feature matching result on the basis of the verification successful;

[0029] obtaining a verification result of calling error based on the successful matching in the third feature matching result on the basis of the verification unsuccessful;

[0030] obtaining a verification result of verification unsuccessful based on the unsuccessful matching in the third feature matching result on the basis of the verification unsuccessful;

[0031] obtaining a verification result of illegal calling based on the successful matching in the third feature matching result on the basis of the illegal verification;

[0032] obtaining a verification result of illegal verification based on the unsuccessful matching in the third feature matching result on the basis of the illegal verification.

[0033] In the scheme, after obtaining the verification result of code calling, the method further comprises:

[0034] identifying target code and a target position based on the code calling factor, wherein the target position comprises a replacement position and an expansion position;

[0035] calling the target code for replacement based on the replacement position;

[0036] calling the target code for expansion based on the expansion position.

[0037] The second aspect of the application further provides a front-end dynamic data permission binding and verification system, comprising a memory and a processor, the memory comprising a front-end dynamic data permission binding and verification method program, the front-end dynamic data permission binding and verification method program being executed by the processor to realize the following steps:

[0038] obtaining target data, wherein the target data is derived from front-end dynamic data;

[0039] extracting a permission factor based on the target data to obtain a permission feature value;

[0040] The permission feature value is matched based on the dynamic matching table to obtain a matching result.

[0041] A verification result is output based on the matching result, wherein the verification result includes unsuccessful verification, successful verification, illegal verification, code calling, calling error, and illegal calling.

[0042] In the scheme, the target data is obtained, specifically including:

[0043] A dynamic data stream is obtained.

[0044] A first-level data is distinguished based on the dynamic data stream to obtain the front-end dynamic data.

[0045] A second-level data is distinguished based on the front-end dynamic data, specifically based on a feature parameter to extract data with the permission factor to obtain the target data.

[0046] In the scheme, the permission factor is extracted based on the target data to obtain a permission feature value, specifically including:

[0047] After the target data is obtained, the identified feature parameters are extracted synchronously, wherein the feature parameters include a binding permission feature, a forwarding transition feature, and a storage feature.

[0048] The permission factor is extracted based on the feature parameters to obtain the permission feature value from the binding permission feature, wherein the permission feature value includes at least a first feature, a second feature, and a third feature, the first feature includes a known permission factor, the second feature includes an unknown permission factor, and the third feature includes a code calling factor.

[0049] In the scheme, the permission feature value is matched based on the dynamic matching table to obtain a matching result, specifically including:

[0050] A dynamic matching table is obtained, wherein the dynamic matching table is dynamically updated based on user input.

[0051] The permission feature value is matched based on the dynamic matching table to obtain a matching result, wherein,

[0052] The dynamic matching table is matched based on the first feature to judge and output a first feature matching result, wherein the first feature matching result includes successful matching and unsuccessful matching.

[0053] The dynamic matching table is matched based on the second feature to judge and output a second feature matching result, wherein the second feature matching result includes successful matching and unsuccessful matching.

[0054] match the third feature based on the third feature to output a third feature matching result, wherein the third feature matching result comprises successful matching and unsuccessful matching.

[0055] In the scheme, the verification result is output based on the matching result, and specifically comprises:

[0056] a verification success verification result is obtained based on the successful matching in the first feature matching result and the successful matching in the second feature matching result;

[0057] a verification unsuccessful verification result is obtained based on the unsuccessful matching in the first feature matching result;

[0058] an illegal verification verification result is obtained based on the unsuccessful matching in the second feature matching result;

[0059] a code calling verification result is obtained based on the successful matching in the third feature matching result on the basis of the verification success;

[0060] a verification success verification result is obtained based on the unsuccessful matching in the third feature matching result on the basis of the verification success;

[0061] a calling error verification result is obtained based on the successful matching in the third feature matching result on the basis of the verification unsuccessful;

[0062] a verification unsuccessful verification result is obtained based on the unsuccessful matching in the third feature matching result on the basis of the verification unsuccessful;

[0063] an illegal calling verification result is obtained based on the successful matching in the third feature matching result on the basis of the illegal verification;

[0064] an illegal verification verification result is obtained based on the unsuccessful matching in the third feature matching result on the basis of the illegal verification.

[0065] In the scheme, after obtaining the code calling verification result, the method further comprises:

[0066] identifying target code and a target position based on the code calling factor, wherein the target position comprises a replacement position and an expansion position;

[0067] calling the target code for replacement based on the replacement position;

[0068] calling the target code for expansion based on the expansion position.

[0069] The third aspect of the present application provides a computer readable storage medium, wherein a front-end dynamic data permission binding and verification method program of a machine is included in the computer readable storage medium, and the front-end dynamic data permission binding and verification method program is executed by a processor to implement the steps of the front-end dynamic data permission binding and verification method according to any one of the above.

[0070] The front-end dynamic data permission binding and verification method, system and readable storage medium disclosed by the present application reduce single-path network overhead through multiple dynamic judgments, reduce the problem of overreach at the front-end level, avoid the shortcomings of complex code structure and difficult maintenance through code calling, optimize the coupling problem of front-end permissions and business logic code, improve the timeliness of permission binding and verification and the operability of dynamic management, and facilitate real-time management by users. BRIEF DESCRIPTION OF DRAWINGS

[0071] Figure 1 A flowchart of the front-end dynamic data permission binding and verification method of the present application is shown.

[0072] Figure 2 A block diagram of the front-end dynamic data permission binding and verification system of the present application is shown. DETAILED DESCRIPTION

[0073] In order to more clearly understand the above-mentioned purposes, features and advantages of the present application, the present application will be further described in detail below with reference to the drawings and specific embodiments. It should be noted that the embodiments of the present application and the features in the embodiments can be combined with each other without conflict.

[0074] In the following description, many specific details are set forth in order to provide a thorough understanding of the present application, however, the present application can also be implemented in other ways different from those described herein, therefore, the protection scope of the present application is not limited by the specific embodiments disclosed below.

[0075] Figure 1 A flowchart of the front-end dynamic data permission binding and verification method of the present application is shown.

[0076] As Figure 1 shown, the present application discloses a front-end dynamic data permission binding and verification method, comprising the following steps:

[0077] S102, obtaining target data, wherein the target data is derived from front-end dynamic data;

[0078] S104, extracting a permission factor based on the target data to obtain a permission feature value;

[0079] S106, performing matching verification based on the permission feature value in combination with a dynamic matching table to obtain a matching result;

[0080] S108, output a verification result based on the matching result, wherein the verification result includes verification unsuccessful, verification successful, illegal verification, code calling, calling error and illegal calling.

[0081] It should be noted that in the embodiment, the dynamic data flow is captured for feature data, the permission can be verified, and the required code can be replaced or modified in time based on different verification results, thereby reducing the error risk and maintenance cost of the code. Specifically, the target data needs to be obtained first, and the target data is obtained from the front-end dynamic data. Then, the permission factor is extracted based on the target data to obtain the permission feature value. Different data corresponds to different permission features, and different processing means are adopted, so as to match the permission feature value with the dynamic matching table to obtain the matching result. Since the dynamic matching table can be updated in real time by the user, the matching result obtained by verification includes multiple results, such as verification unsuccessful, verification successful, illegal verification, code calling, calling error and illegal calling. The dynamic table matching reduces the over-authorization problem of the front-end layer, and the real-time dynamic updating optimizes the coupling problem of the front-end permission and the business logic code. The code calling can avoid the disadvantage of complex code structure and difficult maintenance, and facilitates the user to manage the code.

[0082] According to the embodiment of the application, the target data is obtained, specifically including:

[0083] Obtaining a dynamic data flow;

[0084] Based on the dynamic data flow, a first-level data is distinguished to distinguish the front-end dynamic data;

[0085] Based on the front-end dynamic data, a second-level data is distinguished, specifically based on a feature parameter to distinguish the data with the permission factor to obtain the target data.

[0086] It should be noted that in the embodiment, the dynamic data flow is captured for multiple-level data to obtain the target data. Specifically, based on the dynamic data flow, a first-level data is distinguished to distinguish the front-end dynamic data, so that based on the front-end dynamic data, a second-level data is distinguished, specifically based on a feature parameter to distinguish the data with the permission factor to obtain the target data. Correspondingly, the feature parameter includes a binding permission feature, a forwarding transition feature and a storage feature.

[0087] According to the embodiment of the application, the permission factor is extracted based on the target data to obtain the permission feature value, specifically including:

[0088] After the target data is acquired, the identified feature parameters are synchronously extracted, wherein the feature parameters include a binding permission feature, a forwarding transition feature, and a storage feature;

[0089] Permission factor extraction is performed based on the feature parameters to obtain the permission feature value from the binding permission feature, wherein the permission feature value includes at least a first feature, a second feature, and a third feature, the first feature includes a known permission factor, the second feature includes an unknown permission factor, and the third feature includes a code call factor.

[0090] It should be noted that in the present embodiment, different feature parameters are processed differently, and the present embodiment mainly illustrates the binding permission feature. Specifically, the permission feature value is obtained from the binding permission feature, wherein the permission feature value includes at least a first feature, a second feature, and a third feature, the first feature includes a known permission factor, the second feature includes an unknown permission factor, and the third feature includes a code call factor.

[0091] According to an embodiment of the present application, the matching verification based on the permission feature value in combination with the dynamic matching table is performed to obtain a matching result, specifically including:

[0092] The dynamic matching table is acquired, wherein the dynamic matching table is dynamically updated based on user input;

[0093] The matching verification based on the permission feature value in combination with the dynamic matching table is performed to obtain a matching result, wherein,

[0094] The first feature is matched with the dynamic matching table to output a first feature matching result, wherein the first feature matching result includes successful matching and unsuccessful matching;

[0095] The second feature is matched with the dynamic matching table to output a second feature matching result, wherein the second feature matching result includes successful matching and unsuccessful matching;

[0096] The third feature is matched with the dynamic matching table to output a third feature matching result, wherein the third feature matching result includes successful matching and unsuccessful matching.

[0097] It should be noted that in the present embodiment, the dynamic matching table dynamically stores different matching features, including different permission factors and different code calling factors. Therefore, in actual application, the dynamic matching table needs to be obtained first, and then the matching verification is performed based on the permission feature value and the corresponding dynamic matching table. Correspondingly, the first feature matching result is output based on the matching of the first feature and the dynamic matching table, wherein the first feature matching result includes successful matching and unsuccessful matching; the second feature matching result is output based on the matching of the second feature and the dynamic matching table, wherein the second feature matching result includes successful matching and unsuccessful matching; the third feature matching result is output based on the matching of the third feature and the dynamic matching table, wherein the third feature matching result includes successful matching and unsuccessful matching, wherein different matching results are combined to obtain different verification results, which will be described later.

[0098] According to the embodiment of the present application, the verification result is output based on the matching result, specifically including:

[0099] The verification success verification result is obtained based on the successful matching in the first feature matching result and the successful matching in the second feature matching result;

[0100] The verification unsuccessful verification result is obtained based on the unsuccessful matching in the first feature matching result;

[0101] The illegal verification verification result is obtained based on the unsuccessful matching in the second feature matching result;

[0102] On the basis of the verification success, the code calling verification result is obtained based on the successful matching in the third feature matching result;

[0103] On the basis of the verification success, the verification success verification result is continued to be obtained based on the unsuccessful matching in the third feature matching result;

[0104] On the basis of the verification unsuccessful, the calling error verification result is obtained based on the successful matching in the third feature matching result;

[0105] On the basis of the verification unsuccessful, the verification unsuccessful verification result is continued to be obtained based on the unsuccessful matching in the third feature matching result;

[0106] On the basis of the illegal verification, the illegal calling verification result is obtained based on the successful matching in the third feature matching result;

[0107] On the basis of the illegal verification, the illegal verification verification result is continued to be obtained based on the unsuccessful matching in the third feature matching result.

[0108] It should be noted that in the embodiment, the verification result includes verification unsuccessful, verification successful, illegal verification, code calling, calling error and illegal calling, which are obtained according to different feature matching results. Specifically, the verification successful verification result is obtained based on the successful matching in the first feature matching result and the successful matching in the second feature matching result; the verification unsuccessful verification result is obtained based on the unsuccessful matching in the first feature matching result; the illegal verification verification result is obtained based on the unsuccessful matching in the second feature matching result; the code calling verification result is obtained based on the successful matching in the third feature matching result on the basis of the verification successful; the verification successful verification result is continuously obtained based on the unsuccessful matching in the third feature matching result on the basis of the verification successful; the calling error verification result is obtained based on the successful matching in the third feature matching result on the basis of the verification unsuccessful; the verification unsuccessful verification result is continuously obtained based on the unsuccessful matching in the third feature matching result on the basis of the verification unsuccessful; the illegal calling verification result is obtained based on the successful matching in the third feature matching result on the basis of the illegal verification; and the illegal verification verification result is continuously obtained based on the unsuccessful matching in the third feature matching result on the basis of the illegal verification.

[0109] According to the embodiment of the application, after the verification result of the code calling is obtained, the method further comprises:

[0110] The target code and the target position are identified based on the code calling factor, wherein the target position includes a replacement position and an expansion position;

[0111] The target code is called for replacement based on the replacement position;

[0112] The target code is called for expansion based on the expansion position.

[0113] It should be noted that in the embodiment, after the verification result of the code calling is obtained, the target code and the target position are identified based on the code calling factor, wherein the target code is extracted from the code database, and the target position is the position in the existing code. Further, the target code is called for replacement based on the replacement position, and the target code is called for expansion based on the expansion position.

[0114] Figure 2 A block diagram of a front-end dynamic data authority binding and verification system is shown.

[0115] As Figure 2As shown, the application discloses a front-end dynamic data permission binding and verification system, which comprises a memory and a processor, the memory comprises a front-end dynamic data permission binding and verification method program, and the front-end dynamic data permission binding and verification method program realizes the following steps when executed by the processor:

[0116] Obtain target data, wherein the target data is derived from front-end dynamic data;

[0117] Extract a permission factor based on the target data to obtain a permission feature value;

[0118] Based on the permission feature value, perform matching verification based on a dynamic matching table to obtain a matching result;

[0119] Output a verification result based on the matching result, wherein the verification result comprises unsuccessful verification, successful verification, illegal verification, code calling, calling error and illegal calling.

[0120] It should be noted that in the embodiment, by capturing feature data of the dynamic data stream, the permission can be verified specifically, and based on different verification results, the required code can be called in time for replacement or modification, thereby reducing the error risk and maintenance cost of the code. Specifically, first, the target data needs to be obtained, and correspondingly, the target data is derived from the front-end dynamic data. Then, after obtaining the target data, the permission factor is extracted to obtain the permission feature value. Different data corresponds to different permission features, and different processing means are adopted, so that the permission feature value is combined with the dynamic matching table to perform matching to obtain the matching result. Since the dynamic matching table can be updated in real time by the user, the matching result obtained by verification includes multiple results, such as unsuccessful verification, successful verification, illegal verification, code calling, calling error and illegal calling. The dynamic table matching reduces the problem of exceeding the power of the front-end layer, and real-time dynamic updating optimizes the coupling problem of the front-end permission and the business logic code. In addition, the code calling can avoid the disadvantage of complex code structure difficult to maintain, and facilitates the user to manage the code.

[0121] According to the embodiment of the application, the target data is obtained, specifically comprising:

[0122] Obtain a dynamic data stream;

[0123] Based on the dynamic data stream, perform first-level data division to divide the front-end dynamic data;

[0124] Based on the front-end dynamic data, perform second-level data division, specifically based on feature parameters to distinguish and extract data with the permission factor to obtain the target data.

[0125] It should be noted that in the embodiment, the multi-level data is distinguished based on the dynamic data flow to obtain the target data, specifically, the first-level data is distinguished based on the dynamic data flow to obtain the front-end dynamic data, and the second-level data is distinguished based on the front-end dynamic data, specifically, the feature parameters are identified to extract the data with the permission factor from the target data, and correspondingly, the feature parameters include the binding permission feature, the forwarding transition feature, and the storage feature.

[0126] According to the embodiment of the application, the permission factor is extracted based on the target data to obtain the permission feature value, specifically including:

[0127] After obtaining the target data, the identified feature parameters are extracted synchronously, wherein the feature parameters include the binding permission feature, the forwarding transition feature, and the storage feature.

[0128] The permission factor is extracted based on the feature parameters to obtain the permission feature value from the binding permission feature, wherein the permission feature value includes at least a first feature, a second feature, and a third feature, the first feature includes a known permission factor, the second feature includes an unknown permission factor, and the third feature includes a code call factor.

[0129] It should be noted that in the embodiment, different feature parameters have different processes, and the embodiment mainly describes the binding permission feature, specifically, the permission feature value is obtained from the binding permission feature, wherein the permission feature value includes at least a first feature, a second feature, and a third feature, the first feature includes a known permission factor, the second feature includes an unknown permission factor, and the third feature includes a code call factor.

[0130] According to the embodiment of the application, the matching verification is performed based on the permission feature value and the dynamic matching table to obtain a matching result, specifically including:

[0131] The dynamic matching table is obtained, wherein the dynamic matching table is dynamically updated based on user input.

[0132] The matching verification is performed based on the permission feature value and the dynamic matching table to obtain a matching result, wherein,

[0133] The first feature is matched with the dynamic matching table to output a first feature matching result, wherein the first feature matching result includes successful matching and unsuccessful matching.

[0134] The second feature is matched with the dynamic matching table to output a second feature matching result, wherein the second feature matching result includes successful matching and unsuccessful matching.

[0135] output a third feature matching result based on the third feature matching the dynamic matching table, wherein the third feature matching result includes successful matching and unsuccessful matching.

[0136] It should be noted that in the embodiment, different matching features are dynamically stored in the dynamic matching table, including different permission factors and different code calling factors. Therefore, in actual application, the dynamic matching table needs to be acquired first, and then matching verification is performed based on the permission feature value in combination with the corresponding dynamic matching table. Accordingly, a first feature matching result is output based on the first feature matching the dynamic matching table, wherein the first feature matching result includes successful matching and unsuccessful matching; a second feature matching result is output based on the second feature matching the dynamic matching table, wherein the second feature matching result includes successful matching and unsuccessful matching; and a third feature matching result is output based on the third feature matching the dynamic matching table, wherein the third feature matching result includes successful matching and unsuccessful matching. Different matching results are combined to obtain different verification results, as described below.

[0137] According to the embodiment of the present application, the verification result is output based on the matching result, specifically including:

[0138] a verification success verification result is obtained based on the successful matching in the first feature matching result and the successful matching in the second feature matching result;

[0139] a verification unsuccessful verification result is obtained based on the unsuccessful matching in the first feature matching result;

[0140] an illegal verification verification result is obtained based on the unsuccessful matching in the second feature matching result;

[0141] on the basis of the verification success, a code calling verification result is obtained based on the successful matching in the third feature matching result;

[0142] on the basis of the verification success, a verification success verification result is continuously obtained based on the unsuccessful matching in the third feature matching result;

[0143] on the basis of the verification unsuccessful, a calling error verification result is obtained based on the successful matching in the third feature matching result;

[0144] on the basis of the verification unsuccessful, a verification unsuccessful verification result is continuously obtained based on the unsuccessful matching in the third feature matching result;

[0145] on the basis of the illegal verification, an illegal calling verification result is obtained based on the successful matching in the third feature matching result;

[0146] On the basis of the illegal verification, the verification result of the code calling is obtained based on the successful matching in the third feature matching result.

[0147] It should be noted that in the embodiment, the verification result includes verification unsuccessful, verification successful, illegal verification, code calling, calling error and illegal calling, which are obtained according to different feature matching results. Specifically, the verification successful verification result is obtained based on the successful matching in the first feature matching result and the successful matching in the second feature matching result; the verification unsuccessful verification result is obtained based on the unsuccessful matching in the first feature matching result; the illegal verification verification result is obtained based on the unsuccessful matching in the second feature matching result; on the basis of the verification successful, the code calling verification result is obtained based on the successful matching in the third feature matching result; on the basis of the verification successful, the verification successful verification result is obtained based on the unsuccessful matching in the third feature matching result; on the basis of the verification unsuccessful, the calling error verification result is obtained based on the successful matching in the third feature matching result; on the basis of the verification unsuccessful, the verification unsuccessful verification result is obtained based on the unsuccessful matching in the third feature matching result; on the basis of the illegal verification, the illegal calling verification result is obtained based on the successful matching in the third feature matching result; on the basis of the illegal verification, the illegal verification verification result is obtained based on the unsuccessful matching in the third feature matching result.

[0148] According to the embodiment of the application, after obtaining the verification result of the code calling, the method further comprises:

[0149] identifying the target code and the target position based on the code calling factor, wherein the target position includes a replacement position and an expansion position;

[0150] calling the target code for replacement based on the replacement position;

[0151] calling the target code for expansion based on the expansion position.

[0152] It should be noted that in the embodiment, after obtaining the verification result of the code calling, the target code and the target position are identified based on the code calling factor, wherein the target code is extracted from the code database, and the target position is the position in the existing code. Further, the target code is called for replacement based on the replacement position, and the target code is called for expansion based on the expansion position.

[0153] The third aspect of the present application provides a computer readable storage medium, wherein the computer readable storage medium comprises a front-end dynamic data permission binding and verification method program, and the front-end dynamic data permission binding and verification method program, when executed by a processor, implements the steps of the front-end dynamic data permission binding and verification method according to any one of the preceding aspects.

[0154] The front-end dynamic data permission binding and verification method, system and readable storage medium disclosed by the present application can reduce single-path network overhead through multiple dynamic judgments, reduce the problem of overreach at the front-end level, avoid the shortcomings of complex code structure and difficult maintenance through code calling, optimize the coupling problem of front-end permissions and business logic code, improve the timeliness of permission binding and verification and the operability of dynamic management, and facilitate real-time management by users.

[0155] In several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other manners. The above described device embodiments are only schematic. For example, the division of the units is only a logical function division. There can be another division manner for the actual implementation, for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed coupling, or direct coupling or communication connection between the components can be indirect coupling or communication connection through some interfaces, or electrical, mechanical or other forms.

[0156] The units described as separate components can or can not be physically separate, and the components displayed as units can or can not be physical units; they can be located in one place, or distributed on multiple network units; and part or all of the units can be selected according to actual needs to achieve the purpose of the present embodiment.

[0157] In addition, each functional unit in each embodiment of the present application can be integrated into one processing unit, or each unit can be a separate unit, or two or more units can be integrated into one unit; the integrated unit can be realized in the form of hardware, or in the form of hardware plus software functional unit.

[0158] Those skilled in the art can understand that all or part of the steps of the above-mentioned method embodiments can be completed by relevant hardware of program instructions, and the foregoing program can be stored in a computer readable storage medium, and the program performs the steps of the above-mentioned method embodiments when executed; and the foregoing storage medium includes: a mobile storage device, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various media that can store program codes.

[0159] Alternatively, the integrated unit of the present application can also be stored in a computer readable storage medium if it is realized in the form of a software function module and sold or used as an independent product. Based on such understanding, the technical solutions of the embodiments of the present application can be embodied in the form of a software product, and the computer software product is stored in a storage medium, includes several instructions to make a computer device (which can be a personal computer, a server, or a network device, etc.) execute all or part of the methods described in the embodiments of the present application. The foregoing storage medium includes: a mobile storage device, a ROM, a RAM, a magnetic disk or an optical disk, and various media that can store program codes.

Claims

1. A front-end dynamic data authority binding and verification method, characterized in that: The following steps are involved: Acquire target data, wherein the target data is derived from front-end dynamic data; Performing authority factor extraction based on the target data to obtain an authority feature value; Performing matching verification based on the permission feature value in combination with a dynamic matching table to obtain a matching result; A verification result is output based on the matching result, wherein the verification result includes unsuccessful verification, successful verification, illegal verification, code call, call error, and illegal call.

2. A front-end dynamic data authority binding and verification method according to claim 1, characterized in that: The acquiring of target data specifically includes: Get dynamic data stream; Performing primary data differentiation based on the dynamic data stream to differentiate and obtain the front-end dynamic data; Secondary data differentiation is performed based on the front-end dynamic data, specifically based on feature parameter identification to extract data with the authority factor to obtain the target data.

3. A front-end dynamic data authority binding and verification method according to claim 2, characterized in that: The extracting of the authority factor based on the target data to obtain the authority characteristic value specifically includes: After acquiring the target data, synchronously extracting the identified characteristic parameters, wherein the characteristic parameters include binding authority characteristics, forwarding transition characteristics, and storage characteristics; Based on the feature parameters, permission factors are extracted to obtain the permission feature value from the bound permission feature, wherein the permission feature value includes at least a first feature, a second feature, and a third feature, the first feature includes a known permission factor, the second feature includes an unknown permission factor, and the third feature includes a code call factor.

4. A front-end dynamic data authority binding and verification method according to claim 3, characterized in that: The performing matching verification based on the permission feature value in combination with the dynamic matching table to obtain a matching result specifically includes: Obtaining a dynamic matching table, wherein the dynamic matching table is dynamically updated based on user input; Based on the permission feature value and the dynamic matching table, a matching verification is performed to obtain a matching result, wherein: Matching the first feature to the dynamic matching table to output a first feature matching result, wherein the first feature matching result includes a successful match and an unsuccessful match; Matching the dynamic matching table based on the second feature to output a second feature matching result, wherein the second feature matching result includes a successful match and an unsuccessful match; The dynamic matching table is matched based on the third feature to output a third feature matching result, wherein the third feature matching result includes a successful match and an unsuccessful match.

5. A front-end dynamic data authority binding and verification method according to claim 4, characterized in that: Outputting a verification result based on the matching result specifically includes: Obtaining a verification result of successful verification based on a successful match in the first feature matching result and a successful match in the second feature matching result; Obtaining a verification result of unsuccessful verification based on an unsuccessful match in the first feature matching result; Obtaining an illegal verification result based on an unsuccessful match in the second feature matching result; Upon successful verification, obtaining a verification result of the code call based on a successful match in the third feature matching result; On the basis of the successful verification, continuing to obtain a successful verification result based on an unsuccessful match in the third feature matching result; If the verification is unsuccessful, obtaining a verification result of a call error based on a successful match in the third feature matching result; On the basis of the unsuccessful verification, continuing to obtain a verification result of unsuccessful verification based on the unsuccessful match in the third feature matching result; On the basis of the illegal verification, obtaining a verification result of the illegal call based on a successful match in the third feature matching result; On the basis of the illegal verification, a verification result of the illegal verification is further obtained based on an unsuccessful match in the third feature matching result.

6. A front-end dynamic data authority binding and verification method according to claim 5, characterized in that: After obtaining the verification result of the code call, the method further includes: identifying a target code and a target position based on the code calling factor, wherein the target position includes a replacement position and an extended position; Calling the target code to perform replacement based on the replacement position; The target code is called based on the extension position to perform extension.

7. A front-end dynamic data authority binding and verification system, characterized in that: The system comprises a memory and a processor, wherein the memory comprises a front-end dynamic data authority binding and verification method program, and when the front-end dynamic data authority binding and verification method program is executed by the processor, the following steps are implemented: Acquire target data, wherein the target data is derived from front-end dynamic data; Performing authority factor extraction based on the target data to obtain an authority feature value; Performing matching verification based on the permission feature value in combination with a dynamic matching table to obtain a matching result; A verification result is output based on the matching result, wherein the verification result includes unsuccessful verification, successful verification, illegal verification, code call, call error, and illegal call.

8. A front-end dynamic data authority binding and verification system according to claim 7, characterized in that: The acquiring of target data specifically includes: Get dynamic data stream; Performing primary data differentiation based on the dynamic data stream to differentiate and obtain the front-end dynamic data; Secondary data differentiation is performed based on the front-end dynamic data, specifically based on feature parameter identification to extract data with the authority factor to obtain the target data.

9. A front-end dynamic data authority binding and verification system according to claim 8, characterized in that: The extracting of the authority factor based on the target data to obtain the authority characteristic value specifically includes: After acquiring the target data, synchronously extracting the identified characteristic parameters, wherein the characteristic parameters include binding authority characteristics, forwarding transition characteristics, and storage characteristics; Based on the feature parameters, permission factors are extracted to obtain the permission feature value from the bound permission feature, wherein the permission feature value includes at least a first feature, a second feature, and a third feature, the first feature includes a known permission factor, the second feature includes an unknown permission factor, and the third feature includes a code call factor.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium includes a front-end dynamic data permission binding and verification method program. When the front-end dynamic data permission binding and verification method program is executed by the processor, the steps of a front-end dynamic data permission binding and verification method as described in any one of claims 1 to 6 are implemented.

Images