An interface verification method, device and storage medium for heterogeneous system integration

Abstract

The application discloses an interface verification method and device for heterogeneous system integration and a storage medium, and aims to solve the technical problem of how to realize legality verification of access between interfaces for heterogeneous system integration. The method comprises the following steps: determining an interface access key generation algorithm corresponding to a first interface and a second interface; the first interface and the second interface are respectively data interaction interfaces corresponding to a first system and a second system; in the case that the second interface needs to access the first interface, the second interface generates a first interface access request based on the interface access key generation algorithm and sends the first interface access request to the first interface; the first interface performs legality verification on the first interface access request based on an interface white list corresponding to the first interface and the interface access key generation algorithm; and in the case that the first interface access request passes the legality verification, the first interface opens access to the second interface. The application realizes legality verification of access between interfaces for heterogeneous system integration through the above method.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to an interface verification method, device and storage medium for heterogeneous system integration. Background Technology

[0002] With the rapid development of modern computer technology and e-commerce technology, there is an urgent need for resource sharing and data communication across different architectures. Traditional data exchange technologies are based on different architectures, such as different operating systems like Windows and Unix, and different database systems like SQL Server and Oracle. To transmit information between these different platforms and database systems, validating the validity of interfaces has become essential.

[0003] Therefore, how to implement the legality verification of inter-interface access for heterogeneous system integration has become an urgent problem to be solved. Summary of the Invention

[0004] This application provides an interface verification method, device, and storage medium for heterogeneous system integration, to solve the following technical problem: how to achieve legality verification of inter-interface access for heterogeneous system integration.

[0005] In a first aspect, embodiments of this application provide an interface verification method for heterogeneous system integration, characterized in that the method includes: determining an interface access key generation algorithm corresponding to a first interface and a second interface; wherein, the first interface is a data interaction interface corresponding to a first system, and the second interface is a data interaction interface corresponding to a second system; when the second interface needs to access the first interface, the second interface generates a first interface access request based on the interface access key generation algorithm and sends the first interface access request to the first interface; the first interface performs a legality verification on the first interface access request based on the interface whitelist corresponding to the first interface and the interface access key generation algorithm; if the first interface access request passes the legality verification, the first interface grants access to the second interface.

[0006] This application provides an interface verification method for heterogeneous system integration. By determining an interface access key generation algorithm corresponding to the first interface and the second interface, a tool is provided for verifying the legitimacy of inter-interface access in heterogeneous system integration. This interface access key generation algorithm eliminates the need for key transmission between the two parties, avoiding the possibility of key disclosure and improving data security.

[0007] In one implementation of this application, before the second interface generates the first interface access request based on the interface access key generation algorithm, the method further includes: determining that the XML format is a data exchange format; parsing the first interface and the second interface to determine the first data transmission format and the second transmission format corresponding to the first interface and the second interface respectively; determining a second conversion rule between the first data transmission format and the XML format, and determining a second conversion rule between the second transmission format and the XML format.

[0008] In one implementation of this application, determining the interface access key generation algorithm corresponding to the first interface and the second interface specifically includes: determining a first key component corresponding to the first interface and determining a second key component corresponding to the second interface; wherein the first key component and the second key component are each composed of several symbols; determining a key component rearrangement function corresponding to the first key component and the second key component; wherein the variable of the key component rearrangement function is the number of accesses, used to rearrange several symbols contained in the first key component and several symbols contained in the second key component; and determining the interface access key generation algorithm based on the first key component, the second key component, and the key component rearrangement function.

[0009] In one implementation of this application, after determining the interface access key generation algorithm corresponding to the first interface and the second interface, the method further includes: pre-setting the interface access key generation algorithm and the interface whitelist corresponding to the first interface in a first system database, and pre-setting the interface access key generation algorithm in a second system database; wherein, the first system database is the system database corresponding to the first system; and the second system database is the system database corresponding to the second system.

[0010] In one implementation of this application, the second interface generates a first interface access request based on an interface access key generation algorithm. Specifically, the second interface queries a second access record of the first interface in a second database and determines the historical access count of the first interface and the second interface based on the second access record. Based on the historical access count, the second interface generates an encryption key through the interface access key generation algorithm and encrypts the request content based on the encryption key to generate an encrypted request body. The preset second interface signature information is added to the header of the encrypted request body to generate the first interface access request.

[0011] In one implementation of this application, the first interface verifies the legitimacy of the first interface access request based on the interface whitelist corresponding to the first interface and the interface access key generation algorithm. Specifically, this includes: the first interface determining the second interface identifier based on the second interface signature information contained in the first interface access request, and determining whether the second interface identifier exists in the interface whitelist; if the second interface identifier exists in the interface whitelist, the first interface queries the first access record of the second interface in the first database to determine the historical access count between the first interface and the second interface; based on the historical access count, a decryption key is generated through the interface access key generation algorithm, and the request content is decrypted based on the decryption key to complete the legitimacy verification.

[0012] In one implementation of this application, the method further includes: if the access request to the first interface fails the validity verification, the first interface generates an invalid access notification and sends the invalid access notification to the second interface; wherein the invalid access notification includes a judgment result on whether the second interface identifier is a whitelisted interface, and whether the decryption key can decrypt the request content.

[0013] In one implementation of this application, the interface protocols corresponding to both the first interface and the second interface are WebService interface protocols.

[0014] Secondly, embodiments of this application also provide an interface verification device for heterogeneous system integration, characterized in that the device includes: a processor; and a memory storing executable code thereon, wherein when the executable code is executed, the processor performs a method as described in any one of claims 1-8.

[0015] Thirdly, embodiments of this application also provide a non-volatile computer storage medium for interface verification of heterogeneous system integration, storing computer-executable instructions, characterized in that the computer-executable instructions are configured to: determine an interface access key generation algorithm corresponding to a first interface and a second interface; wherein, the first interface is a data interaction interface corresponding to a first system, and the second interface is a data interaction interface corresponding to a second system; when the second interface needs to access the first interface, the second interface generates a first interface access request based on the interface access key generation algorithm and sends the first interface access request to the first interface; the first interface verifies the legitimacy of the first interface access request based on the interface whitelist corresponding to the first interface and the interface access key generation algorithm; if the first interface access request passes the legitimacy verification, the first interface grants access to the second interface. Attached Figure Description

[0016] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0017] Figure 1 A flowchart illustrating an interface verification method for heterogeneous system integration provided in this application embodiment;

[0018] Figure 2 This is a schematic diagram of the internal structure of an interface verification device for heterogeneous system integration, provided as an embodiment of this application. Detailed Implementation

[0019] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0020] This application provides an interface verification method, device, and storage medium for heterogeneous system integration, to solve the following technical problem: how to achieve legality verification of inter-interface access for heterogeneous system integration.

[0021] The technical solutions proposed in the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0022] Figure 1 This document provides a flowchart of an interface verification method for heterogeneous system integration, as illustrated in an embodiment of this application. Figure 1 As shown in the figure, the interface verification method for heterogeneous system integration provided in this application embodiment specifically includes the following steps:

[0023] Step 101: Determine the interface access key generation algorithm corresponding to the first interface and the second interface.

[0024] First, it should be noted that in the embodiments of this application, the first interface and the second interface are different interfaces from two heterogeneous systems. The system corresponding to the first interface is determined to be the first system, and the system corresponding to the second interface is determined to be the second interface.

[0025] It should also be noted that the interface protocols corresponding to the first interface and the second interface in this application embodiment are both Web Service interface protocols.

[0026] In one embodiment of this application, to ensure system data security, an interface access key generation algorithm is provided for inter-interface access. This algorithm generates corresponding encryption and decryption keys for the accessing and accessed interfaces, respectively.

[0027] In one embodiment of this application, determining the interface access key generation algorithm corresponding to the first interface and the second interface specifically includes the following execution process:

[0028] First, the first key component corresponding to the first interface is determined, and the second key component corresponding to the second interface is determined. It should be noted that both the first and second key components consist of several symbols, all of which are pre-set. Next, the key component rearrangement function corresponding to the first and second key components is determined. The variable of the key component rearrangement function is the number of accesses, used to rearrange the symbols contained in the first and second key components. Based on the first key component, the second key component, and the key component rearrangement function, the interface access key generation algorithm is determined.

[0029] It is understandable that the interface access key generation algorithm for the first interface and the second interface includes, in addition to the first key component, the second key component, and the key component rearrangement function, an algorithm for generating an encryption key or a decryption key based on the number of accesses, an algorithm for implementing encryption based on the encryption key, and an algorithm for implementing decryption based on the decryption key.

[0030] In one embodiment of this application, after determining the interface access key generation algorithm corresponding to the first interface and the second interface, it is also necessary to pre-store the interface access key generation algorithm and the interface whitelist corresponding to the first interface in the first system database, and pre-store the interface access key generation algorithm in the second system database. It is understood that the first system database is the system database corresponding to the first system; the second system database is the system database corresponding to the second system. It is also understood that the second interface also has its corresponding interface whitelist, and the interfaces included in the interface whitelist corresponding to the first interface are the interfaces that can access the first interface.

[0031] Step 102: When the second interface needs to access the first interface, the second interface generates a first interface access request based on the interface access key generation algorithm and sends the first interface access request to the first interface.

[0032] In one embodiment of this application, since a Web Service is a platform-independent, loosely coupled, self-contained, programmable web application, the open XML (a subset of Standard Generalized Markup Language) standard can be used to describe, publish, discover, coordinate, and configure these applications for developing distributed interactive applications. XML (Extensible Markup Language) is an extensible markup language that uses platform-independent, neutral data representation, allowing data to be serialized into a transmittable form that can be easily decoded on any platform. XML is simple to use and has good data storage format, scalability, high structure, and great flexibility. Therefore, before the second interface generates the first interface access request based on the interface access key generation algorithm, the conversion rules between the data transmission format corresponding to the interface and the XML format are also determined to reduce the complexity of data exchange.

[0033] Specifically, the XML format is determined as the data exchange format; the first interface and the second interface are parsed to determine the first data transmission format and the second transmission format corresponding to the first interface and the second interface, respectively; a second conversion rule between the first data transmission format and the XML format is determined, as well as a second conversion rule between the second transmission format and the XML format.

[0034] In one embodiment of this application, after determining the interface access key generation algorithm corresponding to the first interface and the second interface, if the second interface needs to access the first interface, it is first necessary to generate an access request for the first interface based on the interface access key generation algorithm.

[0035] Specifically, the second interface first queries the second database for a second access record related to the first interface, and based on this second access record, determines the historical number of accesses between the first and second interfaces. It should be noted that the second access record is a historical record of mutual accesses between the first and second interfaces, including both accesses from the first and second interfaces. After determining the historical number of accesses, the second interface generates an encryption key based on this historical number using an interface access key generation algorithm, and encrypts the request content using this encryption key to generate an encrypted request body. Finally, a pre-defined second interface signature is added to the header of the encrypted request body to generate the first interface access request. It is understood that the data format of the first access request, including the request content, is XML format obtained after the second conversion format processing.

[0036] Furthermore, after generating the first access request, the second interface will send the first interface access request to the first interface.

[0037] Step 103: The first interface verifies the legitimacy of the access request based on the interface whitelist and interface access key generation algorithm corresponding to the first interface.

[0038] In one embodiment of this application, after the first interface receives the first interface access request, it will perform a legality verification on the access request to determine whether to grant access to the second interface.

[0039] Specifically, the first interface determines the second interface identifier based on the second interface signature information contained in the first interface access request, and checks whether the second interface identifier exists in the interface whitelist. If the second interface identifier exists in the interface whitelist, the first interface queries the first database for the first access record of the second interface to determine the historical access count of the first and second interfaces. It is immediately apparent that the historical access counts determined by the first or second access record are the same; the only difference between the first and second access records is the record subject. Based on the historical access count, a decryption key is generated using an interface access key generation algorithm, and the request content is decrypted based on the decryption key to complete the legitimacy verification. It is understandable that, due to XML format compatibility, after receiving the first access request, the first interface does not need to convert the first access request into the data transmission format corresponding to the first interface.

[0040] In one embodiment of this application, if the first interface access request sent by the second interface fails the legality verification, the first interface will generate an illegal access notification and send the illegal access notification to the second interface; wherein, the illegal access notification includes the judgment result of whether the second interface identifier is a whitelisted interface, and whether the decryption key can decrypt the request content.

[0041] Step 104: If the first interface access request passes the validity verification, the first interface opens access to the second interface.

[0042] In one embodiment of this application, after the second interface completes its access to the first interface, the first interface and the second interface will respectively update their corresponding first access record and second access record.

[0043] Based on the same inventive concept, embodiments of this application also provide an interface verification device for heterogeneous system integration, the internal structure of which is as follows: Figure 2 As shown.

[0044] Figure 2 This is a schematic diagram of the internal structure of an interface verification device for heterogeneous system integration, provided as an embodiment of this application. Figure 2As shown, the device includes: a processor 201; and a memory 202 storing executable instructions, which, when executed, cause the processor 201 to perform an interface verification method for heterogeneous system integration as described above.

[0045] In one embodiment of this application, the processor 201 is used to determine the interface access key generation algorithm corresponding to the first interface and the second interface; wherein, the first interface is the data interaction interface corresponding to the first system, and the second interface is the data interaction interface corresponding to the second system; when the second interface needs to access the first interface, the second interface generates a first interface access request based on the interface access key generation algorithm and sends the first interface access request to the first interface; the first interface performs a legality verification on the first interface access request based on the interface whitelist corresponding to the first interface and the interface access key generation algorithm; if the first interface access request passes the legality verification, the first interface opens access to the second interface.

[0046] Some embodiments of this application provide corresponding to Figure 1 A non-volatile computer storage medium for interface verification of heterogeneous system integration, storing computer-executable instructions configured as follows:

[0047] Determine the interface access key generation algorithm corresponding to the first interface and the second interface; wherein, the first interface is the data interaction interface corresponding to the first system, and the second interface is the data interaction interface corresponding to the second system;

[0048] When the second interface needs to access the first interface, the second interface generates an access request for the first interface based on the interface access key generation algorithm and sends the access request to the first interface.

[0049] The first interface verifies the legitimacy of the access request based on the interface whitelist and interface access key generation algorithm corresponding to the first interface.

[0050] If the first interface access request passes the validity verification, the first interface will then open access to the second interface.

[0051] The various embodiments in this application are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the embodiments for IoT devices and media are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0052] The systems, media, and methods provided in this application are one-to-one correspondences. Therefore, the systems and media also have similar beneficial technical effects as their corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the systems and media will not be repeated here.

[0053] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0054] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0055] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0056] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0057] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0058] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0059] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0060] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0061] The above description is merely an embodiment of this application and is not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. An interface verification method for heterogeneous system integration, characterized in that, The method comprises: determining an interface access key generation algorithm corresponding to a first interface and a second interface; wherein the first interface is a data interaction interface corresponding to a first system, and the second interface is a data interaction interface corresponding to a second system; in the case where the second interface needs to access the first interface, the second interface generates a first interface access request based on the interface access key generation algorithm, and sends the first interface access request to the first interface; the first interface performs legality verification on the first interface access request based on an interface white list corresponding to the first interface and the interface access key generation algorithm; in the case where the first interface access request passes the legality verification, the first interface opens access to the second interface; determining an interface access key generation algorithm corresponding to a first interface and a second interface, specifically comprising: determining a first key component corresponding to the first interface, and determining a second key component corresponding to the second interface; wherein the first key component and the second key component are composed of a plurality of symbols respectively; determining a key component rearrangement function corresponding to the first key component and the second key component; wherein the variable of the key component rearrangement function is the access times, which is used to rearrange the plurality of symbols contained in the first key component and the plurality of symbols contained in the second key component; determining the interface access key generation algorithm based on the first key component, the second key component and the key component rearrangement function.

2. The interface verification method for heterogeneous system integration of claim 1, wherein, Before the second interface generates the first interface access request based on the interface access key generation algorithm, the method further comprises: determining that the XML format is a data exchange format; parsing the first interface and the second interface to determine a first data transmission format and a second transmission format corresponding to the first interface and the second interface respectively; determining a second conversion rule between the first data transmission format and the XML format, and determining a second conversion rule between the second transmission format and the XML format.

3. The interface verification method for heterogeneous system integration of claim 1, wherein, After determining the interface access key generation algorithm corresponding to the first interface and the second interface, the method further comprises: presetting the interface access key generation algorithm and an interface white list corresponding to the first interface in a first system database, and presetting the interface access key generation algorithm in a second system database; wherein the first system database is a system database corresponding to the first system; and the second system database is a system database corresponding to the second system.

4. The interface verification method for heterogeneous system integration of claim 3, wherein, The second interface generates the first interface access request based on the interface access key generation algorithm, specifically comprising: the second interface queries a second access record of the first interface in the second system database, and determines a historical access times of the first interface and the second interface based on the second access record; the second interface generates an encryption key based on the historical access times through the interface access key generation algorithm, and performs encryption processing on the request content based on the encryption key to generate an encrypted request body; Add the preset second interface signature information to the encrypted request body header to generate a first interface access request.

5. The interface verification method for heterogeneous system integration of claim 4, wherein, The first interface performs legality verification on the first interface access request based on an interface white list corresponding to the first interface and the interface access key generation algorithm, specifically including: The first interface determines a second interface identifier based on the second interface signature information contained in the first interface access request, and determines whether the second interface identifier exists in the interface white list; In a case where the second interface identifier exists in the interface white list, the first interface queries a first access record of the second interface in the first system database to determine a historical access frequency of the first interface and the second interface; Based on the historical access frequency, a decryption key is generated by the interface access key generation algorithm, and the request content is decrypted based on the decryption key to complete the legality verification.

6. The interface verification method for heterogeneous system integration of claim 5, wherein, The method further includes: In a case where the first interface access request fails to pass the legality verification, the first interface generates an illegal access notification and sends the illegal access notification to the second interface; The illegal access notification contains a judgment result of whether the second interface identifier is a white list interface, and whether the decryption key can decrypt the request content.

7. The interface verification method for heterogeneous system integration of claim 1, wherein, The interface protocols corresponding to the first interface and the second interface are both Web Service interface protocols.

8. An interface verification device for heterogeneous system integration, characterized by, The device includes: a processor; and a memory having executable code stored thereon, which, when executed, causes the processor to perform a method according to any one of claims 1-7.

9. A non-transitory computer storage medium storing computer-executable instructions for interface verification for heterogeneous system integration, the computer-executable instructions comprising: The computer executable instructions are configured to: determine an interface access key generation algorithm corresponding to the first interface and the second interface; wherein the first interface is a data interaction interface corresponding to a first system, and the second interface is a data interaction interface corresponding to a second system; in a case where the second interface needs to access the first interface, the second interface generates a first interface access request based on the interface access key generation algorithm, and sends the first interface access request to the first interface; the first interface performs legality verification on the first interface access request based on an interface white list corresponding to the first interface and the interface access key generation algorithm; in a case where the first interface access request passes the legality verification, the first interface opens access to the second interface; determining an interface access key generation algorithm corresponding to the first interface and the second interface specifically includes: determining a first key component corresponding to the first interface and a second key component corresponding to the second interface; wherein the first key component and the second key component are composed of a plurality of symbols respectively; determining a key component rearrangement function corresponding to the first key component and the second key component; wherein the variable of the key component rearrangement function is an access frequency, which is used to rearrange the plurality of symbols contained in the first key component and the plurality of symbols contained in the second key component; determining the interface access key generation algorithm based on the first key component, the second key component, and the key component reordering function.

Images