CN111064725A - Code zero intrusion interface verification method and device - Google Patents
Code zero intrusion interface verification method and device Download PDFInfo
- Publication number
- CN111064725A CN111064725A CN201911289414.XA CN201911289414A CN111064725A CN 111064725 A CN111064725 A CN 111064725A CN 201911289414 A CN201911289414 A CN 201911289414A CN 111064725 A CN111064725 A CN 111064725A
- Authority
- CN
- China
- Prior art keywords
- interface
- verification
- field
- check
- json file
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/12—Applying verification of the received information
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention belongs to the technical field of communication, in particular to a code zero intrusion interface verification method, which comprises the following steps: step 1: establishing a JSON file named by an interface class; step 2: performing section interception on the interface request by using a section-oriented programming AOP technology to obtain an interface class, a check field and request data corresponding to the check field contained in the interface request; and step 3: and 4, searching JSON files named by the same interface class according to the interface class acquired in the step 2: judging whether the request data corresponding to the check field in the interface request conforms to the field check rule of the same check field in the JSON file, and if any request data does not conform to the corresponding field check rule, returning an exception prompt; and if all the data requests accord with the corresponding field verification rule, passing the verification. The method can realize the interface verification without changing the original code and sensing. Meanwhile, the invention also provides an interface checking device.
Description
Technical Field
The invention relates to the technical field of communication, in particular to a code zero-intrusion interface checking device.
Background
The general method for interface verification comprises the following steps: and performing parameter verification in the method header adding annotation or the business method.
However, this method has problems in that: each time an interface parameter check is added or modified, the code needs to be changed.
The applicant, china banking corporation, has proposed an invention patent application CN201811338540.5 in 2018, and discloses a method and a device for checking an interface message, after receiving information of a message to be checked, according to the field information included in the message to be checked, acquiring the attribute of the check rule corresponding to the field information to acquire the name of the check function and the parameters of the check rule corresponding to the field information, according to the name of the check function, a check rule program corresponding to the name of the check function can be obtained, and the obtained check rule parameters are input into the check rule program, so as to obtain a check rule program required to be executed when checking the field corresponding to the field information, and the fields in the message to be checked are checked according to the obtained check rule program, and the check rule program does not need to be rewritten for different fields. And different messages or different fields can select corresponding check rule programs according to the self check rules to complete the check, so that the flexibility, the transportability and the reusability of the check are improved.
The method can solve the technical problems, but the method also has the following problems: for example, if the name of the check function or the parameters of the check rule related in the method are stored in the database, when a check rule of a new interface method needs to be added, at least two records need to be added, one is the interface method, the other is the check field (including the type of the input parameter, whether the input parameter needs to be transmitted, the length, the transmittable value and the like), the number of the records is increased according to the increase of the check field, an association relationship needs to be established between the records, the hierarchical relationship cannot be visually seen after the addition, the low efficiency is easy to make an error, and the database is generally shared and used once the error is changed, all developers are influenced.
For example, a general method for acquiring a conventional interface request includes: performing parameter field verification in combination with an interface verification tool class in the middle of a link requesting an interface method, wherein the original code needs to be changed in the middle of the link; the filter is also an implementation but is limited to only filtering entries for web background requests.
Therefore, the prior art cannot realize real code zero intrusion interface verification.
Disclosure of Invention
The invention aims to provide a code zero intrusion interface verification method which can realize interface verification without changing the original code and sensing.
In order to achieve the purpose, the invention provides the following technical scheme:
a code zero intrusion interface verification method is characterized in that the method specifically comprises the following steps:
step 1: establishing a JSON file named by an interface class, wherein one or more key value pairs with check fields as keys and field check rules as values are stored in the JSON file;
step 2: performing section interception on the interface request by using a section-oriented programming AOP technology to obtain an interface class, a check field and request data corresponding to the check field contained in the interface request;
and step 3: searching JSON files named by the same interface class according to the interface class acquired in the step 2, and if the JSON files named by the same interface class are found, performing a step 4;
and 4, step 4: judging whether the request data corresponding to the check field in the interface request conforms to the field check rule of the same check field in the JSON file, and if any request data does not conform to the corresponding field check rule, returning an exception prompt; and if all the data requests accord with the corresponding field verification rule, passing the verification.
In the code zero intrusion interface verification method, if the JSON file named by the same interface class is not found according to the interface class acquired in the step 2 in the step 3, a result of passing verification is returned.
In the code zero intrusion interface verification method, if in step 4, part of the verification fields in the interface request do not have corresponding field verification rules in the JSON file, and the request data of other verification fields all conform to the corresponding field verification rules, a result that the verification passes is returned.
In the code zero intrusion interface verification method, if the verification rule of the interface class needs to be added, a key value pair is added in the JSON file or a key value pair is added in any key value pair;
and if the check rules of the interface class need to be reduced or modified, deleting the corresponding key value pairs or modifying the check fields and/or the field check rules in the corresponding key value pairs in the JSON file.
Meanwhile, the invention also discloses an interface checking device, which comprises the following modules:
a JSON file creating and storing module: the JSON file is used for establishing and storing a JSON file named by an interface class, and one or more key value pairs with check fields as keys and field check rules as values are stored in the JSON file;
an interface request intercepting module: the interface processing device is used for intercepting the interface request by using an AOP technology oriented to the section programming, and acquiring the interface class and the check field contained in the interface request and request data corresponding to the check field;
JSON file searching module: the JSON file is used for searching JSON files named by the same interface class according to the interface class acquired by the interface request intercepting module;
a checking module: and the device is used for verifying the request data corresponding to the verification field acquired by the interface request intercepting module by adopting the field verification rule of the verification field in the JSON file acquired by the JSON file searching module, and returning an exception prompt or outputting a verification passing result.
In the interface checking device, the checking module is further configured to output a result of passing the checking when the JSON file searching module cannot search the JSON file named with the same interface class.
In the above interface checking device, the checking module is further configured to, if there is a part of the check fields in the interface request that do not have the corresponding field check rule in the JSON file, and the request data of the other check fields all conform to the corresponding field check rule, return a result that the check is passed.
In the above interface checking device, the JSON file creating and storing module is further configured to add a key-value pair to the JSON file or add a key-value pair to any key-value pair.
In the above interface checking device, the JSON file creating and storing module is further configured to delete the corresponding key value pair or modify the check field and/or the field check rule in the corresponding key value pair in the JSON file if the check rule of the interface class needs to be reduced or modified.
Compared with the prior art, the invention has the beneficial effects that:
and the verification of interface method parameters is realized through an AOP and JSON file mode. For an interface needing parameter verification, a JSON file named by an interface class is newly established in an appointed directory, a verification rule (the name of an interface method is used as a key, a JSON object character string of the parameter verification rule is used as a value) is added in the JSON file, the interface request is subjected to section interception (the interface class, the method name and request data are obtained) through AOP, a corresponding JSON verification rule file is found, the method entry type, the method transmission necessity, the method length, the transmittable value and the like are verified in combination with an interface verification tool class, the exception is thrown out if the method entry type, the method transmission necessity, the method length, the transmittable value and the like are not met, and the original code does not need.
Through the AOP mode, the verification of the request parameters of the interface method can be realized under the condition of not changing the original code, the JSON verification file stores all the interface method verification rules of one interface, the verification rules of one interface method can be visually seen, the verification rules are added or deleted, only the corresponding JSON verification file needs to be found according to the class name, and the corresponding interface method is positioned for corresponding modification, so that the modification is convenient, the method is more visual and efficient, the JSON format has a hierarchical relationship, the complex request data verification with a multilayer relationship can be conveniently and flexibly realized, the JSON file temporarily modifies the local joint debugging without submitting Git or SVN, other developers are not influenced, and the local debugging is convenient.
Drawings
FIG. 1 is a block flow diagram of example 1 of the present invention;
fig. 2 is a block diagram showing a system according to embodiment 2 of the present invention;
fig. 3 is a block diagram of embodiment 2 of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Example 1
A code zero intrusion interface verification method, the application background of this method lies in that the requestor sends out the interface request to the requestor, the requestor is usually the front end page or app or desktop shaping, for example there is a registration page in some company's website, after the customer fills in the registration form information, click the confirmation button, will submit the registration request; the requested person, generally referred to as a back-end service, such as a user service, an order service, a device management service, a service, and an internal check module function is added to the service, and the request check is performed before the request reaches the business method, so as to ensure that the request data reaching the business method is complete and meets the rules.
Referring to fig. 1, the method specifically includes:
step 1: establishing a JSON file named by an interface class, wherein one or more key value pairs with check fields as keys and field check rules as values are stored in the JSON file;
the JSON file is illustrated by the following code, but the following code is not meant to limit the invention:
JSON checks the file name: json, userserviceimpl
Code description:
taking the above code as an example, the format of the key is "field", which indicates that the parameter value with the parameter name "field" must be transmitted, such as "company id": String ", which must be transmitted;
the key is in the format of "(option) field" indicating that the parameter value with the parameter name "field" is not mandatory to be transmitted, e.g., "marking" (option) "indicating that the parameter remark may not be transmitted;
the format of the value is 'type', which means that the input parameter value must be of the corresponding type, such as 'Integer', and must be Integer value;
the format of the value is 'type [ ]', which means that the value must be an array of a corresponding type, such as 'String [ ]', which must be an array of character strings;
the format of the value is "type (length)", which means that the value must be a corresponding type and the length does not exceed length, if the value is a type numerical value, the value means that the size does not exceed length, such as "String (20)", and must be a character String not greater than 20 bits in length; for example, "Integer (20)", must be an Integer number not greater than 20;
the format of the value is "type { item1, item2.. itemX }", which means that the input parameter value is of a corresponding type, and the value can only be item1, item2.. itemX, such as "Integer {1,2 }", which must be a value of 1 or 2, and cannot be 3 or 4;
the format of the value is { field 1: xxx, field 2: xxx } ", which indicates that the parameter value is a JSON object, and the field verification in the JSON object follows the rules;
the format of the value is [ { field 1: xxx, field 2: xxx } ], which indicates that the parameter value is a JSON object array, and the field check in the JSON object follows the rules;
from the above description of the code we can see that it contains multiple key value pairs, such as: key company ID, value string; key userName, value string, etc.
The JSON file has the advantages that: the JSON verification file can more visually see the parameter verification rule of each interface method, is more flexible and changeable, and is convenient to realize complex multi-layer parameter verification.
In the traditional technology, a database is mostly adopted to store the verification rules, when the traditional database stores the verification rules, the use is not flexible, the realization difficulty is high, once the verification parameters of the complex rules are met, even the bottom layer structure needs to be changed, and the method is not intuitive.
As a specific example, if a check of address information is added to a user interface, the code becomes as follows:
in the adding user interface, one more address information is added for verification, and only one more layer of addressList verification rule needs to be added in the userList array object in the JSON file, so that the method is convenient, efficient and visual. If the data base is placed in a database, at least two records are required to be added, one record is an interface method, the other record is a check field (including an input parameter type, whether the input parameter is required to be transmitted or not, the length, a transmittable value and the like), the number of the records is increased according to the increase of the check field, an association relation also needs to be established between the records, the hierarchical relation cannot be visually seen after the records are added, the efficiency is low, errors are easy to occur, the database is generally shared, once the records are changed, all developers are influenced, and JSON files support local debugging, so that the data base is safe and convenient.
The modification and deletion of the check rule are also very convenient in the same way.
Step 2: performing section interception on the interface request by using a section-oriented programming AOP technology to obtain an interface class, a check field and request data corresponding to the check field contained in the interface request;
the section-oriented programming AOP technology is used for intercepting the interface request on a requested party such as a back-end service party, the section-oriented programming AOP technology is used for intercepting the interface request, and the interface class contained in the interface request is obtained, for example, the interface request is analyzed to find that the interface request belongs to the user interface class. And simultaneously analyzing the interface request to analyze a check field in the interface request and request data corresponding to the check field, wherein the request data is the request data adaptive to a check rule of the user registration interface method if the check field is the user registration interface method.
By the AOP technology, interception verification can be realized under the condition of not changing the original interface code.
In the conventional technology, the interface request is mostly intercepted by other methods, for example, parameter field verification can be performed in combination with an interface verification tool in the middle of a link from the request to the interface method, and the original code needs to be changed in the middle of the link;
the filter is also an implementation way, but is limited to only filtering the web background request entries,
the section programming AOP technology can realize filtering no matter web request or pure background service code, filters the request which does not accord with the check rule, and throws out a prompt.
Generally, an interface request needs to transmit a designated parameter field value according to a check rule of the interface, for example, a user interface is added, parameter values such as a user name, a user account and a password need to be taken on a submitted form, a user interface is deleted, and a user id needs to be taken on.
The following were used:
adding request parameter data of the user interface in batches:
and requesting fields, mandatory values, parameter types and optional values of parameter data, wherein the fields, the mandatory values, the parameter types and the optional values of the parameter data must accord with the parameter verification rules of the user method adding of the user interface class, and if the fields, the mandatory values, the parameter types and the optional values do not accord with the parameter verification rules, intercepting the request. Such as:
(1) the prompt parameter, companyId, cannot be null:
(2) the cue parameter, rolls IDs, must be of array type:
and step 3: searching JSON files named by the same interface class according to the interface class acquired in the step 2, and if the JSON files named by the same interface class are found, performing a step 4; and if the JSON files with the same interface class as the name are used, returning a result of passing the verification.
In step 2, if the interface class requested by the interface belongs to the user interface class, in this step, a JSON file with the JSON file name as the user interface needs to be found, and a user registration interface method and a corresponding verification rule are found from the JSON file.
And 4, step 4: judging whether the request data corresponding to the check field in the interface request conforms to the field check rule of the same check field in the JSON file, if any request data does not conform to the corresponding field check rule, returning an abnormal prompt to the user interface; and if all the data requests accord with the corresponding field verification rule, passing the verification.
And judging whether the request data corresponding to the check field in the interface request conforms to the field check rule of the same check field in the JSON file or not through a check tool class which can be realized by adopting a special or existing check program.
The exception prompt in step 4 is to generally return a value user interface, for example, in the interface request verification process of the interface class, if the user does not fill in the user name, the returned exception prompt is to the user interface to prompt that the user name cannot be null.
In practical applications, specific situations can also occur, and if some check fields in the interface request do not have corresponding field check rules in the JSON file, and the request data of other check fields all conform to the corresponding field check rules, a result that the check is passed is returned.
The method embodiment of the invention can realize the verification of the request parameters of the interface method under the condition of not changing the original codes through the AOP mode, the JSON verification file stores all the interface method verification rules of one interface, the verification rules of one interface method can be visually seen, the verification rules are added or deleted, only the corresponding JSON verification file needs to be found according to the class name, and the corresponding interface method is positioned for corresponding modification, the modification is convenient, the visualization and the high efficiency are realized, the JSON format has the hierarchical relationship, the complex request data verification with the multilayer relationship can be conveniently and flexibly realized, the JSON file temporarily modifies the local joint debugging without influencing other developers under the condition of submitting Git or SVN, and the local debugging is convenient.
Example 2
An interface checking device B2 for implementing the method described in embodiment 1, where the device exists in the form of hardware or software on a server B where an application or service is located, and specifically, the device is applicable to a system including a client a and a server B, where the server B has a gateway B1, and a gateway B1 is connected to user services, and the user services include an interface service B3 and the interface checking device B2, and includes the following modules:
JSON file creation and storage module 1: the JSON file is used for establishing and storing a JSON file named by an interface class, and one or more key value pairs with check fields as keys and field check rules as values are stored in the JSON file; the method is used for adding key value pairs in the JSON file or adding key value pairs in any key value pair, wherein the added key value pairs also take a check field as a key and a field check rule as a value; in addition, the method can also be used for deleting the corresponding key value pair or modifying the check field and/or the field check rule in the corresponding key value pair in the JSON file if the check rule of the interface class needs to be reduced or modified.
Interface request interception module 2: the interface processing device is used for intercepting the interface request by using an AOP technology oriented to the section programming, and acquiring the interface class and the check field contained in the interface request and request data corresponding to the check field;
JSON file searching module 3: the interface request intercepting module 2 is used for acquiring interface classes, and the JSON file creating and storing module 1 is used for searching JSON files named by the same interface class;
the checking module 4: the method is used for verifying the request data corresponding to the verification field acquired by the interface request intercepting module 2 by adopting the field verification rule of the verification field in the JSON file acquired by the JSON file searching module 3, and returning an exception prompt or outputting a result of passing the verification, and is also used for outputting the result of passing the verification when the JSON file named by the same interface class cannot be searched by the JSON file searching module 3, and also used for returning the result of passing the verification if part of the verification fields in the interface request do not have the corresponding field verification rule in the JSON file and the request data of other verification fields conform to the corresponding field verification rule.
The working process of the device is as follows: the client a sends an interface request to the server B, and the gateway B1 of the server B forwards the interface request, where the service described in this embodiment is an interface request or an order service, each service has a service interface, an interface request intercepting module 2 is adopted at a service interface to intercept an interface request, then a JSON file searching module 3 finds a JSON file with the same name as an interface class according to the interface class in the interface request through a JSON file creating and storing module 1, locates a check field and a check rule in the JSON file, the checking module 4 checks the checking field and the request data in the interface request by using checking tools, judges whether the request data conforms to the checking rule of the checking field, if so, the interface request is checked to be passed, the client A can call the interface of the service, and if the interface request is not checked to be passed, the abnormal prompt is fed back to the client A.
If the JSON file searching module 3 cannot find the corresponding JSON file, the verification is passed; and if partial verification fields in the interface request cannot be found from the JSON file and other requested data pass the verification, the verification is passed.
It will be evident to those skilled in the art that the invention is not limited to the details of the foregoing illustrative embodiments, and that the present invention may be embodied in other specific forms without departing from the spirit or essential attributes thereof. The present embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the invention being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned.
Claims (9)
1. A code zero intrusion interface verification method is characterized in that the method specifically comprises the following steps:
step 1: establishing a JSON file named by an interface class, wherein one or more key value pairs with check fields as keys and field check rules as values are stored in the JSON file;
step 2: performing section interception on the interface request by using a section-oriented programming AOP technology to obtain an interface class, a check field and request data corresponding to the check field contained in the interface request;
and step 3: searching JSON files named by the same interface class according to the interface class acquired in the step 2, and if the JSON files named by the same interface class are found, performing a step 4;
and 4, step 4: judging whether the request data corresponding to the check field in the interface request conforms to the field check rule of the same check field in the JSON file, and if any request data does not conform to the corresponding field check rule, returning an exception prompt; and if all the data requests accord with the corresponding field verification rule, passing the verification.
2. The code zero intrusion interface verification method according to claim 1, wherein if no JSON file named by the same interface class is found according to the interface class acquired in step 2 in step 3, a result of passing verification is returned.
3. The method for verifying the code zero-intrusion interface according to claim 1, wherein if in the step 4, there is a part of verification fields in the interface request that have no corresponding field verification rule in the JSON file, and the request data of other verification fields all conform to the corresponding field verification rule, a result that the verification is passed is returned.
4. The code zero intrusion interface verification method according to claim 1, wherein if a verification rule of an interface class needs to be added, a key value pair is added in a JSON file or a key value pair is added in any key value pair;
and if the check rules of the interface class need to be reduced or modified, deleting the corresponding key value pairs or modifying the check fields and/or the field check rules in the corresponding key value pairs in the JSON file.
5. An interface checking device is characterized by comprising the following modules:
a JSON file creating and storing module: the JSON file is used for establishing and storing a JSON file named by an interface class, and one or more key value pairs with check fields as keys and field check rules as values are stored in the JSON file;
an interface request intercepting module: the interface processing device is used for intercepting the interface request by using an AOP technology oriented to the section programming, and acquiring the interface class and the check field contained in the interface request and request data corresponding to the check field;
JSON file searching module: the JSON file creating and storing module is used for searching the JSON files named by the same interface class according to the interface class acquired by the interface request intercepting module;
a checking module: and the device is used for verifying the request data corresponding to the verification field acquired by the interface request intercepting module by adopting the field verification rule of the verification field in the JSON file acquired by the JSON file searching module, and returning an exception prompt or outputting a verification passing result.
6. The interface verification apparatus according to claim 5, wherein the verification module is further configured to output a result of passing the verification when the JSON file lookup module fails to find the JSON file named with the same interface class.
7. The interface verification device according to claim 5, wherein the verification module is further configured to return a result that the verification is passed if there is a part of the verification fields in the interface request that do not have corresponding field verification rules in the JSON file, and the request data of other verification fields all conform to the corresponding field verification rules.
8. The interface verifier device of claim 5, wherein the JSON file creation and storage module is further configured to add key-value pairs to the JSON file or to add key-value pairs to any key-value pair.
9. The interface checking device according to claim 5, wherein the JSON file creating and storing module is further configured to delete the corresponding key value pair or modify the check field and/or the field check rule in the corresponding key value pair in the JSON file if the check rule of the interface class needs to be reduced or modified.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911289414.XA CN111064725A (en) | 2019-12-12 | 2019-12-12 | Code zero intrusion interface verification method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911289414.XA CN111064725A (en) | 2019-12-12 | 2019-12-12 | Code zero intrusion interface verification method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111064725A true CN111064725A (en) | 2020-04-24 |
Family
ID=70301782
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911289414.XA Pending CN111064725A (en) | 2019-12-12 | 2019-12-12 | Code zero intrusion interface verification method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111064725A (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112015763A (en) * | 2020-07-14 | 2020-12-01 | 北京旷视科技有限公司 | JSON data verification method and device, electronic equipment and computer readable medium |
| CN112069292A (en) * | 2020-09-09 | 2020-12-11 | 苏州思必驰信息科技有限公司 | Data permission verification method and device |
| CN112241370A (en) * | 2020-10-21 | 2021-01-19 | 网易（杭州）网络有限公司 | Verification method, system and device for API (application program interface) interface class |
| CN113517048A (en) * | 2021-07-12 | 2021-10-19 | 挂号网（杭州）科技有限公司 | Medical record data verification method and device, electronic equipment and storage medium |
| WO2023098043A1 (en) * | 2021-12-03 | 2023-06-08 | 深圳前海微众银行股份有限公司 | Interface parameter checking method and apparatus |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108132880A (en) * | 2017-12-21 | 2018-06-08 | 武汉斑马快跑科技有限公司 | A kind of parameter verification method and device |
| CN108492195A (en) * | 2018-03-08 | 2018-09-04 | 中国平安人寿保险股份有限公司 | Extensive method, equipment and storage medium are joined by a kind of entering for regulation engine packet |
| CN109344642A (en) * | 2018-08-31 | 2019-02-15 | 平安科技（深圳）有限公司 | Interface rules method of calibration, device, computer equipment and storage medium |
| CN110147261A (en) * | 2019-04-15 | 2019-08-20 | 平安普惠企业管理有限公司 | Parameter verification method and relevant device based on calling interface |
-
2019
- 2019-12-12 CN CN201911289414.XA patent/CN111064725A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108132880A (en) * | 2017-12-21 | 2018-06-08 | 武汉斑马快跑科技有限公司 | A kind of parameter verification method and device |
| CN108492195A (en) * | 2018-03-08 | 2018-09-04 | 中国平安人寿保险股份有限公司 | Extensive method, equipment and storage medium are joined by a kind of entering for regulation engine packet |
| CN109344642A (en) * | 2018-08-31 | 2019-02-15 | 平安科技（深圳）有限公司 | Interface rules method of calibration, device, computer equipment and storage medium |
| CN110147261A (en) * | 2019-04-15 | 2019-08-20 | 平安普惠企业管理有限公司 | Parameter verification method and relevant device based on calling interface |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112015763A (en) * | 2020-07-14 | 2020-12-01 | 北京旷视科技有限公司 | JSON data verification method and device, electronic equipment and computer readable medium |
| CN112069292A (en) * | 2020-09-09 | 2020-12-11 | 苏州思必驰信息科技有限公司 | Data permission verification method and device |
| CN112069292B (en) * | 2020-09-09 | 2022-07-12 | 思必驰科技股份有限公司 | Data permission verification method and device |
| CN112241370A (en) * | 2020-10-21 | 2021-01-19 | 网易（杭州）网络有限公司 | Verification method, system and device for API (application program interface) interface class |
| CN112241370B (en) * | 2020-10-21 | 2023-06-16 | 网易（杭州）网络有限公司 | API interface class checking method, system and device |
| CN113517048A (en) * | 2021-07-12 | 2021-10-19 | 挂号网（杭州）科技有限公司 | Medical record data verification method and device, electronic equipment and storage medium |
| WO2023098043A1 (en) * | 2021-12-03 | 2023-06-08 | 深圳前海微众银行股份有限公司 | Interface parameter checking method and apparatus |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10769228B2 (en) | Systems and methods for web analytics testing and web development | |
| CN111064725A (en) | Code zero intrusion interface verification method and device | |
| US10783116B2 (en) | Systems and methods for managing data | |
| US9384231B2 (en) | Data lineage management operation procedures | |
| CN112506747B (en) | Business process monitoring method and device, electronic equipment and storage medium | |
| US10990607B1 (en) | Systems and methods for log aggregation | |
| US8713368B2 (en) | Methods for testing OData services | |
| US10282461B2 (en) | Structure-based entity analysis | |
| CN110716743B (en) | Aggregation API development method and system suitable for multiparty collaborative development | |
| US11860858B1 (en) | Decoding distributed ledger transaction records | |
| US11297091B2 (en) | HTTP log integration to web application testing | |
| US10192262B2 (en) | System for periodically updating backings for resource requests | |
| US20150339286A1 (en) | Automatically generating certification documents | |
| US12072946B2 (en) | Optimizing scraping requests through browsing profiles | |
| US20220052853A1 (en) | Universal blockchain data model | |
| US20190066012A1 (en) | Enterprise customer website | |
| US20140337069A1 (en) | Deriving business transactions from web logs | |
| US20230269086A1 (en) | Systems and methods for using secure, encrypted communications across distributed computer networks to efficiently index blockchain states for performing blockchain operations in decentralized applications using cryptography-based digital repositories | |
| US20230269085A1 (en) | Systems and methods for using secure, encrypted communications across distributed computer networks to efficiently update cryptography-based digital repositories for performing blockchain operations in decentralized applications | |
| CN112835863A (en) | Processing method and processing device of operation log | |
| US20230244863A1 (en) | System and method for reference validation of spreadsheet | |
| CN115657901A (en) | Service change method and device based on unified parameters | |
| US20210182473A1 (en) | Ad hoc contact data capture | |
| CN117609400A (en) | Data flow chart generation device and method, electronic equipment and storage medium | |
| CN117610078A (en) | Data flow early warning method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: 511356 Room 501, building 2, No. 63, Yong'an Avenue, Huangpu District, Guangzhou, Guangdong Applicant after: Guangzhou lubangtong Internet of things Technology Co.,Ltd. Address before: 510653 3rd floor, building F, kehuiyuan, 95 Daguan Road, Tianhe District, Guangzhou City, Guangdong Province Applicant before: GUANGZHOU ROBUSTEL TECHNOLOGIES Co.,Ltd. |
|
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200424 |