CN116708359A - Interface access method, device, equipment and computer readable storage medium - Google Patents

Abstract

The invention discloses an interface access method, device, equipment and computer-readable storage medium, which are applied in the technical field of the Internet, including: when receiving an intranet resource access request, replacing the public network domain name invoked by the intranet resource access request It is the domain name of the local area network; the domain name of the local area network is analyzed to obtain the address of the target intranet; the virtual private network is used to access the target interface according to the address of the target intranet. The invention analyzes the obtained domain name of the local area network by automatically replacing the domain name to obtain the target intranet address, thereby utilizing the virtual private network to access the target interface according to the target intranet address. Compared with the current need to manually replace the IP address, the gateway can directly resolve the LAN domain name to The target IP improves the access efficiency of the intranet interface.

Description

An interface access method, device, equipment and computer-readable storage medium

technical field

The present invention relates to the technical field of the Internet, in particular to an interface access method, device, equipment and computer-readable storage medium.

Background technique

Due to network problems, some remote offices must use the public network domain name system to access the Internet, and cannot use the intranet domain name system because of the use of the public network domain name system (cost issues, many offices at each station, and few people at each station). Sometimes the server cannot go through the VPN (Virtual Private Network, virtual private network) tunnel, and the client URL is recognized as an external network, which causes the subsequent server to be unable to distinguish correctly, so that the gateway cannot be accessed through the VPN tunnel, thereby affecting the efficiency of access. Or the method of replacing the domain name with an IP is currently used. When the gateway and the server need to replace the gateway, the user needs to be notified to change the IP, which makes the management efficiency low and affects the user experience.

Therefore, when using a VPN tunnel to access the intranet, when the gateway is replaced, the user needs to be notified to change the IP in time, which makes the efficiency of accessing the intranet low. Therefore, it is necessary to improve the access efficiency of the intranet interface and improve the user experience.

Contents of the invention

In view of this, the object of the present invention is to provide an interface access method, device, device and computer-readable storage medium, which solves the technical problem of low interface access efficiency in the prior art.

In order to solve the above technical problems, the present invention provides an interface access method, comprising:

When an intranet resource access request is received, the public domain name invoked by the intranet resource access request is replaced with a local area network domain name;

Analyzing the LAN domain name to obtain the target intranet address;

The virtual private network is used to access the target interface according to the target intranet address.

Optionally, after the said intranet resource access request is received, after replacing the public domain name invoked by the intranet resource access request with a local area network domain name, the method further includes:

An intranet identifier is marked on the request header corresponding to the intranet resource access request.

Optionally, using a virtual private network to access the target interface according to the target intranet address includes:

When the microservice receives the intranet resource access request, use the microservice to determine whether the request header corresponding to the intranet resource access request has the intranet identifier;

When the intranet identifier exists, using the microservice to allow access to the target interface by using the virtual private network according to the target intranet address;

When the intranet identifier does not exist, the microservice is used to determine whether to allow access according to the interface annotation; wherein, the interface annotation is any one of intranet-only access and non-intranet-only access.

Optionally, using a virtual private network to access the target interface according to the target intranet address includes:

When it is determined that the first microservice initiates an interface access request to the second microservice, a Feign mark is added to the interface access request; wherein the Feign mark represents that access between microservices can be trusted.

Optionally, after the said intranet resource access request is received, after replacing the public domain name invoked by the intranet resource access request with a local area network domain name, the method further includes:

Remove said Feign tag at the gateway.

Optionally, using a virtual private network to access the target interface according to the target intranet address includes:

Obtain the intranet annotation information corresponding to the intranet access interface of the target microservice;

The virtual private network is used to access the target interface according to the target internal network address, and the external network request is intercepted by using the internal network annotation information.

The present invention also provides an interface access device, comprising:

A domain name replacement module, configured to replace the public domain name invoked by the intranet resource access request with a local area network domain name when an intranet resource access request is received;

A domain name resolution module, configured to resolve the domain name of the local area network to obtain a target intranet address;

The interface access module is configured to use the virtual private network to access the target interface according to the target intranet address.

Optionally, the interface access device may also include:

The intranet identification adding module is configured to mark the intranet identification on the request header corresponding to the intranet resource access request.

The present invention also provides an interface access device, including:

memory for storing computer programs;

The processor is configured to realize the steps of the above interface access method when executing the computer program.

The present invention also provides a computer-readable storage medium, where a program is stored on the readable storage medium, and when the program is executed by a processor, the steps of the above-mentioned interface access method are realized.

It can be seen that when the present invention receives an intranet resource access request, the public domain name called by the intranet resource access request is replaced with a local area network domain name; the local area network domain name is analyzed to obtain the target intranet address; address to access the target interface. It can be seen that the present invention enables the public network domain name system to analyze the LAN domain name by automatically changing the domain name, and automatically obtains the target intranet address, thereby using the virtual private network to access the target interface according to the target intranet address.

Therefore, compared with the current interface access method in which the user needs to manually change the IP address when changing the gateway, the present invention does not need to manually change the IP address when changing the gateway, because when receiving the intranet resource access request, The public domain name called by the intranet resource access request has been replaced with a LAN domain name, so that the gateway can directly resolve the LAN domain name to the target IP, which improves the efficiency of intranet interface access.

In addition, the present invention also provides an interface access device, equipment, and computer-readable storage medium, which also have the above beneficial effects.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only It is an embodiment of the present invention, and those skilled in the art can also obtain other drawings according to the provided drawings without creative work.

Fig. 1 is a flowchart of an interface access method provided by an embodiment of the present invention;

FIG. 2 is an example flow chart of an interface access method provided by an embodiment of the present invention;

Fig. 3 is a schematic diagram of a system architecture corresponding to an interface access method provided by an embodiment of the present invention

FIG. 4 is an example flow diagram of a process of adding an intranet mark provided by an embodiment of the present invention;

Fig. 5 is a flow example diagram of a Feign mark at the microservice place provided by the embodiment of the present invention;

FIG. 6 is a schematic structural diagram of an interface access device provided by an embodiment of the present invention;

Fig. 7 is a schematic structural diagram of an interface access device provided by an embodiment of the present invention.

Detailed ways

In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments It is only some embodiments of the present invention, but not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of the present invention.

Please refer to FIG. 1 , which is a flow chart of an interface access method provided by an embodiment of the present invention. The method can include:

S100. When an intranet resource access request is received, replace the public domain name invoked by the intranet resource access request with a local area network domain name.

The execution subject of this embodiment is a server. Because some remote offices (warehouses, small offices) must use the public network DNS (Domain Name System) due to network problems, they cannot use the intranet DNS, so the "old gateway domain name" is resolved to the external network IP (Internet Protocol, URL), so Unable to access the gateway through a VPN (Virtual Private Network, virtual private network) tunnel, eventually causing our gateway and server to recognize these requested IPs as external network IPs. In order to correctly identify these "remote offices" as intranets, replace the old gateway domain name (public domain name) called by the internal management system with the new gateway domain name (local area network domain name). It is understandable that internal systems (such as oa (office system), erp (enterprise resource planning system), etc.) use the new gateway domain name, and external systems (such as applets, apps (application programs), web malls), because there are external networks For access requirements, use the old gateway domain name.

It should be noted that after the public network domain name invoked by the intranet resource access request is replaced with the LAN domain name when the intranet resource access request is received, it may also include: Web logo. It can be understood that if the intranet identifier is marked on the request corresponding to the IP, the subsequent subject can easily and accurately identify that the type of the intranet resource access request is an intranet. That is, read the http request header "Intranet ID", if it is, it will identify that the user is from the intranet and let it go, otherwise it will reject the request. Therefore, marking the intranet identifier on the request header corresponding to the intranet resource access request can improve the accuracy of request identification.

It should be noted that after receiving the intranet resource access request, after replacing the public domain name invoked by the intranet resource access request with the LAN domain name, it may also include: deleting the Feign mark at the gateway. It is understandable that when there is a Feign tag at the gateway, the Feign tag needs to be deleted at the gateway to prevent external network users from directly adding the Feign tag to the request, thus masquerading as an internal network, resulting in misidentification of subsequent microservices. The Feign mark in this embodiment indicates that the interface can only be trusted for access between microservices (microservice A/microservice B).

S101. Analyzing the LAN domain name to obtain a target intranet address.

In this embodiment, the LAN domain name is resolved to the intranet IP: 10.1.x.x by using the public network DNS at the same time.

S102. Use the virtual private network to access the target interface according to the target intranet address.

In this embodiment, the new gateway server can be accessed from the intranet through the VPN tunnel. It should be noted that, the above-mentioned access to the target interface by using the virtual private network according to the target intranet address may include: when the microservice receives an intranet resource access request, using the microservice to determine the request corresponding to the intranet resource access request Whether there is an intranet ID in the header; when there is an intranet ID, use the microservice to allow the virtual private network to access the target interface according to the target intranet address; when there is no internal network ID, use the microservice to access the target interface according to the interface The annotation determines whether access is allowed; wherein, the interface annotation is any one of intranet-only access and non-intranet-only access. In this embodiment, the internal network identifier can be used to directly determine whether the target interface can be accessed, which improves the security of the access. It can be understood that the Internet users in this embodiment continue to use the old gateway domain name (public network domain name), and the server can correctly identify it as the external network IP. The home and the resident office are actually connected to the company VPN (the internal system uses (LAN domain name) and resolves to the intranet IP, and the access server uses the VPN tunnel), and the access server is also through the VPN tunnel, and the server can be correctly identified as the intranet IP. When the intranet identifier does not exist, the microservice is used to annotate the currently accessed interface. If the interface annotation is configured as only intranet access, the microservice rejects access; otherwise, when the interface annotation is not only intranet access, the default Allow access.

It should be noted that, after using the above-mentioned virtual private network to access the target interface according to the target intranet address, it may also include: when it is determined that the first microservice initiates an interface access request to the second microservice, for the interface access request Add a Feign mark; wherein, the Feign mark represents that the access between microservices can be trusted. Feign in this embodiment is marked as an interface called between servers, so the security requirement is the highest, and it is necessary to limit "only server intranet calls". The Feign mark in this embodiment is added at the interface call. It can be understood that as long as microservice A (the first microservice) calls microservice B (the second microservice), the Feign mark will be marked when the request is initiated. mark, which is different from the request that the user directly accesses microservice B. Because the latter is directly initiated by the user (the feign mark forged by the user is cleared at the gateway), there is a need to check whether it is an intranet, while the former is directly initiated by microservice A and is completely trustworthy, so it is marked with Feign. Since the Feign mark is added at the microservice call to prevent external network users from cheating, it can further improve the security of access.

It should be noted that the above-mentioned access to the target interface by using the virtual private network according to the target intranet address may include: obtaining the intranet annotation information corresponding to the intranet access interface of the target microservice; The address accesses the target interface, and uses the intranet annotation information to intercept external network requests.

In the interface access method provided by the embodiment of the present invention, when an intranet resource access request is received, the public domain name invoked by the intranet resource access request is replaced with a local area network domain name; the local area network domain name is analyzed to obtain the target intranet address; The virtual private network accesses the target interface according to the target intranet address. It can be seen that the present invention is compared with the current interface access method in which the user needs to manually change the IP address when replacing the gateway. When the present invention receives an intranet resource access request, it replaces the public domain name called by the intranet resource access request with LAN domain name; analyze the LAN domain name to obtain the target intranet address; use the virtual private network to access the target interface according to the target intranet address. That is, the present invention makes the domain name system of the public network analyze the domain name of the local area network by automatically replacing the domain name, and automatically obtains the target intranet address, thereby utilizing the virtual private network to access the target interface according to the target intranet address, that is, the present invention is replacing When using the gateway, there is no need to manually change the IP address. Since the public domain name invoked by the intranet resource access request has been replaced with the LAN domain name when receiving the intranet resource access request, the gateway can directly resolve the LAN domain name to The target IP improves the efficiency of internal network interface access. Moreover, mark the intranet identifier on the request header corresponding to the intranet resource access request, so that the intranet can be accurately identified later, and the virtual private network can be used to accurately access the target interface; and the Feign mark is added at the microservice call, because Add it at the microservice call, so that the microservices can call each other and improve the efficiency of access; and, you can delete the Feign mark at the gateway to prevent external network users from directly adding the Feign mark to the request, thereby masquerading as an internal network, resulting in subsequent micro-services Misidentification of services; and, use the intranet annotation information to intercept external network requests, improve the accuracy of external network interception, and then improve the security of intranet access.

In order to make the present invention easier to understand, please refer to FIG. 2 for details. FIG. 2 is an example flow diagram of an interface access method provided by an embodiment of the present invention, which may specifically include:

S200, replacing the public network domain name invoked by the internal management system with a local area network domain name.

This embodiment does not limit a specific internal management system. For example, the internal management system may be internal software of the enterprise; or the internal management system may also be a small program within the enterprise. For ease of understanding, please refer to FIG. 3 , which is a schematic diagram of a system architecture corresponding to an interface access method provided by an embodiment of the present invention. Internal management system: APP (Application, application program), small programs, etc. within the enterprise; Server Load Balancing (ServerLoad BalancingN, SLB): Server Load Balancing (ServerLoad Balancing), which can be regarded as an extension of HSRP (Hot Standby Router Protocol), realizes Load balancing among multiple servers. A virtual server represents a cluster of multiple real servers. When a client initiates a connection to a virtual server, it is forwarded to a real server through a load balancing algorithm. Gateway: Gateway (Gateway) is also known as an Internet connector and a protocol converter. The gateway implements network interconnection on the transport layer and is the most complex network interconnection device, which is only used for the interconnection of two networks with different high-level protocols. Gateways can be used for both WAN interconnection and LAN interconnection. Microservice A: Microservices can run in their "own programs" and communicate with HTTP (HyperTextTransfer Protocol, Hypertext Transfer Protocol)-type API (Application Program Interface, Application Programming Interface) through "lightweight devices". The point is that the service can run in its own program. Through this, we can distinguish service exposure from microservice architecture (distribute an API in an existing system). Microservice A can directly call the interface of microservice B.

S201. Use the public network DNS to resolve the local area network domain name to a target intranet address.

S202, realizing access from the target intranet address to the target gateway server through the VPN.

S203. Add an intranet mark to the request header corresponding to the LAN domain name at the gateway, and delete the Feign mark when there is a Feign mark at the gateway.

For the specific process of this embodiment, please refer to FIG. 4 . FIG. 4 is an example flow diagram of a process of adding an intranet mark provided by an embodiment of the present invention. Step 1: Use the gateway to check whether the user's requested IP is an intranet. In step 2, if the IP requested by the user is an intranet, the request header is marked as "1"; in step 3, otherwise, it is marked as "0"; in step 4, the HTTP request header corresponding to the user's requested IP clears the Feign flag.

S204, adding a Feign mark at the microservice; wherein, the Feign mark indicates a request initiated by the trusted microservice.

The specific application process of the Feign mark at the microservice in this embodiment can refer to Figure 5. Figure 5 is an example diagram of the process of a Feign mark at the microservice provided by the embodiment of the present invention. Step 1: Determine whether the microservice is internal only Network access, step 2: when only intranet access is allowed, access is not allowed and judge whether the URL is in the anonymous table, step 3: otherwise, access is allowed; step 4: when it is not only intranet access, allow access to the target interface corresponding to the microservice . Step 5: When the URL (uniform resource locator) is not in the anonymous table, access is not allowed and judge whether it is the server intranet 192.168 according to the request header; Step 6: When it is in the anonymous table, allow access; Step 7: When it is not in the server When the network is 192.168, access is not allowed and judge whether it has a feign mark. Step 8: When it is the server intranet 192.168, allow access; Step 9: When it has a feign mark, allow access. Step 10: When it does not have a feign mark, Access is not allowed and judge whether there is an intranet flag, step 11: when there is an intranet flag, allow access, step 12: otherwise, not allow access.

An interface access device provided by an embodiment of the present invention is introduced below, and the interface access device described below and the interface access method described above may be referred to in correspondence.

Please refer to FIG. 6 for details. FIG. 6 is a schematic structural diagram of an interface access device provided by an embodiment of the present invention, which may include:

The domain name replacement module 100 is used to replace the public network domain name invoked by the intranet resource access request with a local area network domain name when the intranet resource access request is received;

The domain name resolution module 200 is configured to resolve the domain name of the local area network to obtain the target intranet address;

The interface access module 300 is configured to use the virtual private network to access the target interface according to the target intranet address.

Further, based on the above embodiment, the above interface access device may further include:

The intranet identification adding module is configured to mark the intranet identification on the request header corresponding to the intranet resource access request.

Further, based on the above-mentioned embodiment, the above-mentioned interface access module 300 may include:

An intranet identifier determination unit, configured to use the microservice to determine whether the request header corresponding to the intranet resource access request has the intranet identifier when the microservice receives the intranet resource access request;

An interface access unit, configured to use the microservice to allow the virtual private network to access the target interface according to the target intranet address when the intranet identifier exists;

An interface access judging unit, configured to use the microservice to determine whether to allow access according to the interface annotation when the intranet identifier does not exist; wherein, the interface annotation is any of intranet access only and non-intranet access A sort of.

Further, based on any of the above-mentioned embodiments, the above-mentioned interface access device may further include:

A Feign mark adding module, configured to add a Feign mark to the interface access request when it is determined that the first microservice initiates an interface access request to the second microservice; wherein, the Feign mark represents that the access between microservices can be trusted.

Further, based on the above embodiment, the above interface access device may further include:

The Feign mark deletion unit is configured to delete the Feign mark at the gateway.

Further, based on any of the above-mentioned embodiments, the above-mentioned interface access module 300 may include:

The intranet annotation information acquisition module is used to obtain the intranet annotation information corresponding to the intranet access interface of the target microservice;

The external network request interception module is used to use the virtual private network to access the target interface according to the target internal network address, and use the internal network annotation information to intercept external network requests.

It should be noted that the order of the modules and units in the above-mentioned interface access device can be changed back and forth without affecting the logic.

The interface access device provided by the embodiment of the present invention may include: a domain name replacement module 100, configured to replace the public network domain name invoked by the intranet resource access request with a local area network domain name when an intranet resource access request is received; domain name resolution The module 200 is configured to analyze the LAN domain name to obtain the target intranet address; the interface access module 300 is configured to use a virtual private network to access the target interface according to the target intranet address. It can be seen that the present invention is compared with the current interface access method in which the user needs to manually change the IP address when replacing the gateway. When the present invention receives an intranet resource access request, it replaces the public domain name called by the intranet resource access request with LAN domain name; analyze the LAN domain name to obtain the target intranet address; use the virtual private network to access the target interface according to the target intranet address. That is, the present invention makes the domain name system of the public network analyze the domain name of the local area network by automatically replacing the domain name, and automatically obtains the target intranet address, thereby utilizing the virtual private network to access the target interface according to the target intranet address, that is, the present invention is replacing When using the gateway, there is no need to manually change the IP address. Since the public domain name invoked by the intranet resource access request has been replaced with the LAN domain name when receiving the intranet resource access request, the gateway can directly resolve the LAN domain name to The target IP improves the efficiency of internal network interface access. Moreover, mark the intranet identifier on the request header corresponding to the intranet resource access request, so that the intranet can be accurately identified later, and the virtual private network can be used to accurately access the target interface; and the Feign mark is added at the microservice call, because Add it at the interface call, so that microservices can call each other and improve access efficiency; and, you can delete the Feign tag at the gateway to prevent external network users from directly adding Feign tags to the request, thereby masquerading as an intranet, resulting in subsequent microservices In addition, use the intranet annotation information to intercept external network requests, improve the accuracy of external network interception, and then improve the security of intranet access.

An interface access device provided by an embodiment of the present invention is introduced below, and the interface access device described below and the interface access method described above may be referred to in correspondence.

Please refer to FIG. 7. FIG. 7 is a schematic structural diagram of an interface access device provided by an embodiment of the present invention, which may include:

memory 10 for storing computer programs;

The processor 20 is configured to execute a computer program to implement the above interface access method.

The memory 10 , the processor 20 , and the communication interface 30 all communicate with each other through the communication bus 40 .

In the embodiment of the present invention, the memory 10 is used to store one or more programs. The program may include program codes, and the program code includes computer operation instructions. In the embodiment of the present invention, the memory 10 may store the following functions: program:

When receiving an intranet resource access request, replace the public domain name invoked by the intranet resource access request with the LAN domain name;

Analyze the LAN domain name to obtain the target intranet address;

Use the virtual private network to access the target interface according to the target intranet address.

In a possible implementation, the memory 10 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and at least one application program required by a function; the data storage area may store The data created.

Additionally, memory 10 may include read-only memory and random-access memory, and provides instructions and data to the processor. A portion of the memory may also include NVRAM. The memory stores operating systems and operating instructions, executable modules or data structures, or their subsets, or their extended sets, wherein the operating instructions may include various operating instructions for implementing various operations. An operating system may include various system programs for implementing various basic tasks as well as handling hardware-based tasks.

The processor 20 can be a central processing unit (Central Processing Unit, CPU), a specific application integrated circuit, a digital signal processor, a field programmable gate array or other programmable logic devices, and the processor 20 can be a microprocessor or any conventional processors, etc. The processor 20 can call programs stored in the memory 10 .

The communication interface 30 may be an interface of a communication module, and is used for connecting with other devices or systems.

Of course, it should be noted that the structure shown in FIG. 7 does not constitute a limitation on the interface access device in the embodiment of the present invention. In practical applications, the interface access device may include more or less components than those shown in FIG. 7 , Or combine certain parts.

The computer-readable storage medium provided by the embodiments of the present invention is introduced below, and the computer-readable storage medium described below and the interface access method described above may refer to each other correspondingly.

The present invention also provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the steps of the above-mentioned interface access method are realized.

The computer-readable storage medium may include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk, etc., which can store program codes. medium.

Each embodiment in this specification is described in a progressive manner, each embodiment focuses on the difference from other embodiments, and the same or similar parts of each embodiment can be referred to each other. As for the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and for relevant details, please refer to the description of the method part.

Professionals can further realize that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, computer software or a combination of the two. In order to clearly illustrate the possible For interchangeability, in the above description, the composition and steps of each example have been generally described according to their functions. Whether these functions are executed by means of hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present invention.

Finally, it should also be noted that in this article, relationships such as first and second etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that these entities or operations, any such actual relationship or order exists. Furthermore, the term "comprises", "comprising", or any other variation is intended to cover a non-exclusive inclusion such that a process, method, article, or apparatus comprising a set of elements includes not only those elements, but also items not expressly listed. other elements, or also include elements inherent in such a process, method, article, or apparatus.

The interface access method, device, equipment and computer-readable storage medium provided by the present invention have been introduced in detail above. In this paper, specific examples are used to illustrate the principle and implementation of the present invention. The description of the above embodiments is only It is used to help understand the method of the present invention and its core idea; at the same time, for those of ordinary skill in the art, according to the idea of the present invention, there will be changes in the specific implementation and scope of application. In summary, this The content of the description should not be construed as limiting the present invention.

Claims (10)

1. An interface access method, characterized in that, comprising: When an intranet resource access request is received, the public domain name invoked by the intranet resource access request is replaced with a local area network domain name; Analyzing the LAN domain name to obtain the target intranet address; The virtual private network is used to access the target interface according to the target intranet address. 2. The interface access method according to claim 1, characterized in that, after the internal network resource access request is received, after the public network domain name called by the internal network resource access request is replaced with a local area network domain name, include: An intranet identifier is marked on the request header corresponding to the intranet resource access request. 3. The interface access method according to claim 2, wherein said utilizing a virtual private network to access the target interface according to the target intranet address comprises: When the microservice receives the intranet resource access request, use the microservice to determine whether the request header corresponding to the intranet resource access request has the intranet identifier; When the intranet identifier exists, using the microservice to allow access to the target interface by using the virtual private network according to the target intranet address; When the intranet identifier does not exist, the microservice is used to determine whether to allow access according to the interface annotation; wherein, the interface annotation is any one of intranet-only access and non-intranet-only access. 4. The method for accessing an interface according to claim 1, further comprising: When it is determined that the first microservice initiates an interface access request to the second microservice, a Feign mark is added to the interface access request; wherein the Feign mark represents that access between microservices can be trusted. 5. The interface access method according to claim 4, characterized in that, after the internal network resource access request is received, after the public network domain name called by the internal network resource access request is replaced with a local area network domain name, include: Remove said Feign tag at the gateway. 6. The interface access method according to any one of claims 1 to 5, wherein said utilizing a virtual private network to access the target interface according to the target intranet address comprises: Obtain the intranet annotation information corresponding to the intranet access interface of the target microservice; The virtual private network is used to access the target interface according to the target internal network address, and the external network request is intercepted by using the internal network annotation information. 7. An interface access device, characterized in that it comprises: A domain name replacement module, configured to replace the public domain name invoked by the intranet resource access request with a local area network domain name when an intranet resource access request is received; A domain name resolution module, configured to resolve the domain name of the local area network to obtain a target intranet address; The interface access module is configured to use the virtual private network to access the target interface according to the target intranet address. 8. The interface access device according to claim 7, characterized in that, the interface access device may also include: The intranet identification adding module is configured to mark the intranet identification on the request header corresponding to the intranet resource access request. 9. An interface access device, characterized in that it comprises: memory for storing computer programs; A processor, configured to implement the steps of the interface access method according to any one of claims 1 to 6 when executing the computer program. 10. A computer-readable storage medium, characterized in that a program is stored on the readable storage medium, and when the program is executed by a processor, the steps of the interface access method according to any one of claims 1 to 6 are implemented .