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

Abstract

The invention discloses a front-end dynamic data permission binding and verification method and system and a readable storage medium, and the method comprises the steps: obtaining target data which is from front-end dynamic data; performing permission factor extraction based on the target data to obtain a permission 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, and the verification result comprises verification failure, verification success, illegal verification, code calling, calling error and illegal calling. According to the method, the overhead of a single-path network is reduced through multiple dynamic judgments, the problem of overriding of a front-end level is reduced, the defect that a code structure is complex and difficult to maintain can be avoided through code calling, the problem of coupling of front-end permission and service logic codes is optimized, the timeliness of permission binding and verification and the operability of dynamic management are improved, and the method is suitable for popularization and application. And real-time management of the user is facilitated.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and more specifically, to a front-end dynamic data permission binding and verification method, system and readable storage medium. Background Art

[0002] With the diversification of Internet applications, the types of applications provided to users or developers are becoming more and more diverse. In actual applications, the use of functions such as permission binding and verification will be involved. Among them, the current permission binding has problems such as performance consumption and difficulty in code maintenance. For example, front-end permission binding usually requires 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 requires the permission logic to be tightly coupled with the business logic, which may lead to a complex code structure and difficult maintenance. When the permission function needs to be modified or expanded, a large amount of code may need to be modified, which increases the risk of errors and maintenance costs. Summary of the invention

[0004] The purpose of the present invention is to provide a front-end dynamic data permission binding and verification method, system and readable storage medium, which can reduce single-channel network overhead and the unauthorized access problem at the front-end level through multiple dynamic judgments, avoid the shortcomings of complex code structure and difficult maintenance through code calls, optimize the coupling problem of front-end permissions and business logic codes, improve the timeliness of permission binding and verification and the operability of dynamic management, and facilitate users to perform real-time management.

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

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

[0007] Extracting authority factors based on the target data to obtain authority characteristic values;

[0008] Performing matching verification based on the permission feature value in combination with a dynamic matching table to obtain a matching result;

[0009] 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.

[0010] In this solution, the acquisition of target data specifically includes:

[0011] Get dynamic data stream;

[0012] Performing primary data differentiation based on the dynamic data stream to differentiate and obtain the front-end dynamic data;

[0013] 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 therefrom to obtain the target data.

[0014] In this solution, the authority factor extraction based on the target data to obtain the authority characteristic value specifically includes:

[0015] 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;

[0016] 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.

[0017] In this solution, the matching verification based on the permission feature value combined with the dynamic matching table to obtain the matching result specifically includes:

[0018] Obtaining a dynamic matching table, wherein the dynamic matching table is dynamically updated based on user input;

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

[0020] Matching the dynamic matching table based on the first feature to output a first feature matching result, wherein the first feature matching result includes a successful match and an unsuccessful match;

[0021] Based on the second feature matching, the dynamic matching table is judged to output a second feature matching result, wherein the second feature matching result includes a successful match and an unsuccessful match;

[0022] The dynamic matching table is judged based on the third feature matching to output a third feature matching result, wherein the third feature matching result includes a successful match and an unsuccessful match.

[0023] In this solution, outputting the verification result based on the matching result specifically includes:

[0024] 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;

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

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

[0027] On the basis of the successful verification, obtaining a verification result of the code call based on a successful match in the third feature matching result;

[0028] 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;

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

[0030] 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;

[0031] 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;

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

[0033] In this solution, after obtaining the verification result of the code call, the method further includes:

[0034] 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;

[0035] Calling the target code to replace based on the replacement position;

[0036] The target code is called based on the extended position for extension.

[0037] The second aspect of the present invention further provides a front-end dynamic data authority binding and verification system, comprising 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:

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

[0039] Extracting authority factors based on the target data to obtain authority characteristic values;

[0040] Performing matching verification based on the permission feature value in combination with a 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 call, call error and illegal call.

[0042] In this solution, the acquisition of target data specifically includes:

[0043] Get dynamic data stream;

[0044] Performing primary data differentiation based on the dynamic data stream to differentiate and obtain the front-end dynamic data;

[0045] 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 therefrom to obtain the target data.

[0046] In this solution, the authority factor extraction based on the target data to obtain the authority characteristic value specifically includes:

[0047] 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;

[0048] 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.

[0049] In this solution, the matching verification based on the permission feature value combined with the dynamic matching table to obtain the matching result specifically includes:

[0050] Obtaining a dynamic matching table, wherein the dynamic matching table is dynamically updated based on user input;

[0051] Based on the permission feature value and the dynamic matching table, a matching verification is performed to obtain a matching result, wherein:

[0052] Matching the dynamic matching table based on the first feature to output a first feature matching result, wherein the first feature matching result includes a successful match and an unsuccessful match;

[0053] Based on the second feature matching, the dynamic matching table is judged to output a second feature matching result, wherein the second feature matching result includes a successful match and an unsuccessful match;

[0054] The dynamic matching table is judged based on the third feature matching to output a third feature matching result, wherein the third feature matching result includes a successful match and an unsuccessful match.

[0055] In this solution, outputting the verification result based on the matching result specifically includes:

[0056] 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;

[0057] Obtaining a verification result of unsuccessful verification based on an unsuccessful match in the first feature matching result;

[0058] Obtaining a verification result of illegal verification based on an unsuccessful match in the second feature matching result;

[0059] On the basis of the successful verification, obtaining a verification result of the code call based on a successful match in the third feature matching result;

[0060] 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;

[0061] On the basis of the unsuccessful verification, obtaining a verification result of a call error based on a successful match in the third feature matching result;

[0062] 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;

[0063] 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;

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

[0065] In this solution, after obtaining the verification result of the code call, the method further includes:

[0066] 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;

[0067] Calling the target code to replace based on the replacement position;

[0068] The target code is called based on the extended position for extension.

[0069] The third aspect of the present invention provides a computer-readable storage medium, which includes a front-end dynamic data permission binding and verification method program of a machine. When the front-end dynamic data permission binding and verification method program is executed by a processor, the steps of a front-end dynamic data permission binding and verification method as described in any one of the above items are implemented.

[0070] The present invention discloses a front-end dynamic data permission binding and verification method, system and readable storage medium, which reduce single-channel network overhead and the problem of unauthorized access at the front-end level through multiple dynamic judgments, and can avoid the shortcomings of complex and difficult-to-maintain code structure through code calls, optimize the problem of coupling front-end permissions with business logic codes, improve the timeliness of permission binding and verification and the operability of dynamic management, and facilitate real-time management by users. BRIEF DESCRIPTION OF THE DRAWINGS

[0071] Figure 1 A flow chart of a front-end dynamic data authority binding and verification method of the present invention is shown;

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

[0073] In order to more clearly understand the above-mentioned purpose, features and advantages of the present invention, the present invention is further described in detail below in conjunction with the accompanying 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 to facilitate a full understanding of the present invention. However, the present invention may also be implemented in other ways different from those described herein. Therefore, the protection scope of the present invention is not limited to the specific embodiments disclosed below.

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

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

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

[0078] S104, extracting authority factors based on the target data to obtain authority feature values;

[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, outputting a verification result based on the matching result, wherein the verification result includes unsuccessful verification, successful verification, illegal verification, code call, call error, and illegal call.

[0081] It should be noted that, in this embodiment, by capturing characteristic data of the dynamic data stream, the permissions can be verified in a targeted manner, and based on different verification results, the required code can be responded to and called in time to replace or modify, thereby reducing the risk of code errors and maintenance costs. Specifically, it is necessary to first obtain the target data. Accordingly, the target data comes from the front-end dynamic data, and then after the target data is obtained, the permission factor is extracted to obtain the permission characteristic value. Different data correspond to different permission characteristics, and the processing methods adopted are also different. The permission characteristic value is combined with the dynamic matching table for matching to verify 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 call, call error and illegal call. Dynamic table matching is used to reduce the problem of unauthorized access at the front-end level, and real-time dynamic update optimizes the problem of coupling between front-end permissions and business logic codes. The use of code calls can avoid the shortcomings of complex code structure and difficult maintenance, which is convenient for users to manage codes.

[0082] According to an embodiment of the present invention, acquiring target data specifically includes:

[0083] Get dynamic data stream;

[0084] Performing primary data differentiation based on the dynamic data stream to differentiate and obtain the front-end dynamic data;

[0085] 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 therefrom to obtain the target data.

[0086] It should be noted that, in this embodiment, multi-level data differentiation is performed based on the dynamic data flow to obtain the target data. Specifically, the first-level data differentiation is performed based on the dynamic data flow to differentiate the front-end dynamic data, and then the second-level data differentiation is performed based on the front-end dynamic data, specifically based on feature parameter identification to extract the data with the permission factor to obtain the target data. Accordingly, the feature parameters include binding permission features, forwarding transition features and storage features.

[0087] According to an embodiment of the present invention, extracting the authority factor based on the target data to obtain the authority characteristic value specifically includes:

[0088] 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;

[0089] 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.

[0090] It should be noted that, in this embodiment, different feature parameters have different processing processes, and this 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.

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

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

[0093] Based on the permission feature value and the dynamic matching table, a matching verification is performed to obtain a matching result, wherein:

[0094] Matching the dynamic matching table based on the first feature to output a first feature matching result, wherein the first feature matching result includes a successful match and an unsuccessful match;

[0095] Based on the second feature matching, the dynamic matching table is judged to output a second feature matching result, wherein the second feature matching result includes a successful match and an unsuccessful match;

[0096] The dynamic matching table is judged based on the third feature matching to output a third feature matching result, wherein the third feature matching result includes a successful match and an unsuccessful match.

[0097] It should be noted that, in this embodiment, different matching features are dynamically stored in the dynamic matching table, including different permission factors and different code call factors. Therefore, in actual application, it is necessary to first obtain the dynamic matching table, so as to perform matching verification based on the permission feature value in combination with the corresponding dynamic matching table. Accordingly, based on the first feature matching, the dynamic matching table is judged to output a first feature matching result, wherein the first feature matching result includes a successful match and an unsuccessful match; based on the second feature matching, the dynamic matching table is judged to output a second feature matching result, wherein the second feature matching result includes a successful match and an unsuccessful match; based on the third feature matching, the dynamic matching table is judged to output a third feature matching result, wherein the third feature matching result includes a successful match and an unsuccessful match, wherein different matching results are combined to obtain different verification results, as described in the subsequent description for details.

[0098] According to an embodiment of the present invention, outputting a verification result based on the matching result specifically includes:

[0099] 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;

[0100] Obtaining a verification result of unsuccessful verification based on an unsuccessful match in the first feature matching result;

[0101] Obtaining a verification result of illegal verification based on an unsuccessful match in the second feature matching result;

[0102] On the basis of the successful verification, obtaining a verification result of the code call based on a successful match in the third feature matching result;

[0103] 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;

[0104] On the basis of the unsuccessful verification, obtaining a verification result of a call error based on a successful match in the third feature matching result;

[0105] 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;

[0106] 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;

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

[0108] It should be noted that, in this embodiment, the verification results include unsuccessful verification, successful verification, illegal verification, code call, call error and illegal call, which need to be obtained according to different feature matching results. Specifically, a verification result of successful verification is obtained based on the successful match in the first feature matching result and the successful match in the second feature matching result; a verification result of unsuccessful verification is obtained based on the unsuccessful match in the first feature matching result; a verification result of illegal verification is obtained based on the unsuccessful match in the second feature matching result; on the basis of the successful verification, a verification result of code call is obtained based on the successful match in the third feature matching result; on the basis of the successful verification, a verification result of successful verification is continued to be obtained based on the unsuccessful match in the third feature matching result; on the basis of the unsuccessful verification, a verification result of call error is obtained based on the successful match in the third feature matching result; on the basis of the unsuccessful verification, a verification result of unsuccessful verification is continued to be obtained based on the unsuccessful match in the third feature matching result; on the basis of the unsuccessful verification, a verification result of unsuccessful verification is continued to be obtained based on the unsuccessful match in the third feature matching result; on the basis of the illegal verification, a verification result of illegal call is obtained based on the successful match in the third feature matching result; on the basis of the illegal verification, a verification result of illegal verification is continued to be obtained based on the unsuccessful match in the third feature matching result.

[0109] According to an embodiment of the present invention, after obtaining the verification result of the code call, the method further includes:

[0110] 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;

[0111] Calling the target code to replace based on the replacement position;

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

[0113] It should be noted that, in this embodiment, after obtaining the verification result of the code call, it is necessary to identify the target code and the target position based on the code call factor, wherein the target code is extracted from the code database, and the target position is the position in the existing code. Furthermore, the target code is called for replacement based on the replacement position, and the target code is called for extension based on the extension position.

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

[0115] like Figure 2As shown, the present invention discloses a front-end dynamic data authority binding and verification system, including a memory and a processor, wherein the memory includes 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:

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

[0117] Extracting authority factors based on the target data to obtain authority characteristic values;

[0118] Performing matching verification based on the permission feature value in combination with a dynamic matching table to obtain a matching result;

[0119] 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.

[0120] It should be noted that, in this embodiment, by capturing characteristic data of the dynamic data stream, the permissions can be verified in a targeted manner, and based on different verification results, the required code can be responded to and called in time to replace or modify, thereby reducing the risk of code errors and maintenance costs. Specifically, it is necessary to first obtain the target data. Accordingly, the target data comes from the front-end dynamic data, and then after the target data is obtained, the permission factor is extracted to obtain the permission characteristic value. Different data correspond to different permission characteristics, and the processing methods adopted are also different. The permission characteristic value is combined with the dynamic matching table for matching to verify 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 call, call error and illegal call. Dynamic table matching is used to reduce the problem of unauthorized access at the front-end level, and real-time dynamic update optimizes the problem of coupling between front-end permissions and business logic codes. The use of code calls can avoid the shortcomings of complex code structure and difficult maintenance, which is convenient for users to manage codes.

[0121] According to an embodiment of the present invention, acquiring target data specifically includes:

[0122] Get dynamic data stream;

[0123] Performing primary data differentiation based on the dynamic data stream to differentiate and obtain the front-end dynamic data;

[0124] 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 therefrom to obtain the target data.

[0125] It should be noted that, in this embodiment, multi-level data differentiation is performed based on the dynamic data flow to obtain the target data. Specifically, the first-level data differentiation is performed based on the dynamic data flow to differentiate the front-end dynamic data, and then the second-level data differentiation is performed based on the front-end dynamic data, specifically based on feature parameter identification to extract the data with the permission factor to obtain the target data. Accordingly, the feature parameters include binding permission features, forwarding transition features and storage features.

[0126] According to an embodiment of the present invention, extracting the authority factor based on the target data to obtain the authority characteristic value specifically includes:

[0127] 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;

[0128] 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.

[0129] It should be noted that, in this embodiment, different feature parameters have different processing processes, and this 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 an embodiment of the present invention, performing matching verification based on the permission feature value in combination with a dynamic matching table to obtain a matching result specifically includes:

[0131] Obtaining a dynamic matching table, wherein the dynamic matching table is dynamically updated based on user input;

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

[0133] Matching the dynamic matching table based on the first feature to output a first feature matching result, wherein the first feature matching result includes a successful match and an unsuccessful match;

[0134] Based on the second feature matching, the dynamic matching table is judged to output a second feature matching result, wherein the second feature matching result includes a successful match and an unsuccessful match;

[0135] The dynamic matching table is judged based on the third feature matching to output a third feature matching result, wherein the third feature matching result includes a successful match and an unsuccessful match.

[0136] It should be noted that, in this embodiment, different matching features are dynamically stored in the dynamic matching table, including different permission factors and different code call factors. Therefore, in actual application, it is necessary to first obtain the dynamic matching table, so as to perform matching verification based on the permission feature value in combination with the corresponding dynamic matching table. Accordingly, based on the first feature matching, the dynamic matching table is judged to output a first feature matching result, wherein the first feature matching result includes a successful match and an unsuccessful match; based on the second feature matching, the dynamic matching table is judged to output a second feature matching result, wherein the second feature matching result includes a successful match and an unsuccessful match; based on the third feature matching, the dynamic matching table is judged to output a third feature matching result, wherein the third feature matching result includes a successful match and an unsuccessful match, wherein different matching results are combined to obtain different verification results, as described in the subsequent description for details.

[0137] According to an embodiment of the present invention, outputting a verification result based on the matching result specifically includes:

[0138] 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;

[0139] Obtaining a verification result of unsuccessful verification based on an unsuccessful match in the first feature matching result;

[0140] Obtaining a verification result of illegal verification based on an unsuccessful match in the second feature matching result;

[0141] On the basis of the successful verification, obtaining a verification result of the code call based on a successful match in the third feature matching result;

[0142] 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;

[0143] On the basis of the unsuccessful verification, obtaining a verification result of a call error based on a successful match in the third feature matching result;

[0144] 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;

[0145] 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;

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

[0147] It should be noted that, in this embodiment, the verification results include unsuccessful verification, successful verification, illegal verification, code call, call error and illegal call, which need to be obtained according to different feature matching results. Specifically, a verification result of successful verification is obtained based on the successful match in the first feature matching result and the successful match in the second feature matching result; a verification result of unsuccessful verification is obtained based on the unsuccessful match in the first feature matching result; a verification result of illegal verification is obtained based on the unsuccessful match in the second feature matching result; on the basis of the successful verification, a verification result of code call is obtained based on the successful match in the third feature matching result; on the basis of the successful verification, a verification result of successful verification is continued to be obtained based on the unsuccessful match in the third feature matching result; on the basis of the unsuccessful verification, a verification result of call error is obtained based on the successful match in the third feature matching result; on the basis of the unsuccessful verification, a verification result of unsuccessful verification is continued to be obtained based on the unsuccessful match in the third feature matching result; on the basis of the unsuccessful verification, a verification result of unsuccessful verification is continued to be obtained based on the unsuccessful match in the third feature matching result; on the basis of the illegal verification, a verification result of illegal call is obtained based on the successful match in the third feature matching result; on the basis of the illegal verification, a verification result of illegal verification is continued to be obtained based on the unsuccessful match in the third feature matching result.

[0148] According to an embodiment of the present invention, after obtaining the verification result of the code call, the method further includes:

[0149] 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;

[0150] Calling the target code to replace based on the replacement position;

[0151] The target code is called based on the extended position for extension.

[0152] It should be noted that, in this embodiment, after obtaining the verification result of the code call, it is necessary to identify the target code and the target position based on the code call factor, wherein the target code is extracted from the code database, and the target position is the position in the existing code. Furthermore, the target code is called for replacement based on the replacement position, and the target code is called for extension based on the extension position.

[0153] The third aspect of the present invention provides a computer-readable storage medium, which 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 a processor, it implements the steps of a front-end dynamic data permission binding and verification method as described in any one of the above items.

[0154] The present invention discloses a front-end dynamic data permission binding and verification method, system and readable storage medium, which reduce single-channel network overhead and the problem of unauthorized access at the front-end level through multiple dynamic judgments, and can avoid the shortcomings of complex and difficult-to-maintain code structure through code calls, optimize the problem of coupling front-end permissions with business logic codes, improve the timeliness of permission binding and verification and the operability of dynamic management, and facilitate real-time management by users.

[0155] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. 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 can be integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the components shown or discussed can be through some interfaces, and the indirect coupling or communication connection of the devices or units can be electrical, mechanical or other forms.

[0156] The units described above as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units; 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 present embodiment.

[0157] In addition, all functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may be separately used as a unit, or two or more units may be integrated into one unit; the above-mentioned integrated units may be implemented in the form of hardware or in the form of hardware plus software functional units.

[0158] A person of ordinary skill in the art can understand that: all or part of the steps of implementing the above method embodiments can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it executes the steps of the above method embodiments; and the aforementioned storage medium includes: mobile storage devices, read-only memories (ROM, Read-Only Memory), random access memories (RAM, Random Access Memory), magnetic disks or optical disks, and other media that can store program codes.

[0159] Alternatively, if the above-mentioned integrated unit of the present invention is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present invention can be essentially or partly reflected in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the methods described in each embodiment of the present invention. The aforementioned storage medium includes: various media that can store program codes, such as mobile storage devices, ROM, RAM, magnetic disks or optical disks.

Claims

1. A front-end dynamic data permission 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; Extracting authority factors based on the target data to obtain authority characteristic values; 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 permission binding and verification method according to claim 1, characterized in that: The obtaining 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 therefrom to obtain the target data.

3. A front-end dynamic data permission binding and verification method according to claim 2, characterized in that: The extracting 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 permission 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 dynamic matching table based on the first feature to output a first feature matching result, wherein the first feature matching result includes a successful match and an unsuccessful match; Based on the second feature matching, the dynamic matching table is judged 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 judged based on the third feature matching 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 permission binding and verification method according to claim 4, characterized in that: The outputting of the 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 a verification result of illegal verification based on an unsuccessful match in the second feature matching result; On the basis of the 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; On the basis of the unsuccessful verification, 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, the verification result of the illegal verification is continued to be obtained based on the 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 replace based on the replacement position; The target code is called based on the extended position for 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 the front-end dynamic data authority binding and verification method program is executed by the processor to implement the following steps: Acquire target data, wherein the target data is derived from front-end dynamic data; Extracting authority factors based on the target data to obtain authority characteristic values; 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 obtaining 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 therefrom 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 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