Gateway flow control and authority access control method and system based on ROMA Connect API

By introducing independent gateway services and sliding window algorithms on the front end of the ROMA Connect API gateway, user authentication and fine-grained permission control are realized, the traffic control and permission access problems of API services are solved, system stability and security are ensured, and full link is provided. Logging and troubleshooting capabilities.

CN119071020APending Publication Date: 2024-12-03COSCO SHIPPING TECH CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
CN202411037146.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-30
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

The ROMA Connect API gateway lacks traffic control and permission access control capabilities, resulting in open API services that can be accessed arbitrarily, and cannot achieve fine-grained permission control and fault location, and lacks statistical analysis and logging capabilities for API calls.

Method used

Develop independent gateway services on the front end of the ROMA Connect API gateway, introducing user concepts, access flow control, user permission control and access log capabilities, limiting current through sliding window algorithms, and combining administrator monitoring and auditing systems to achieve user authentication and detailed Granular permission control.

Benefits of technology

Effectively prevent system overload and crash, ensure system stability, protect system resources from unauthorized access, realize full-link logging and troubleshooting, and improve system security and monitoring.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119071020A_ABST
    Figure CN119071020A_ABST
Patent Text Reader

Abstract

The invention belongs to the technical field of network security, and provides a method and a system for gateway flow control and authority access control based on ROMA Connect API (Application Program Interface). An independent gateway service is researched and developed in the front section of an ROMA Connect API gateway, a user concept, an access flow control capability, a user authority control capability, a user access log capability and the like are introduced, and a sliding window algorithm is adopted in a flow control module of a request user / application to solve the flow limiting problem. The algorithm dynamically limits the current according to the request frequency in a certain time window. A permission file system is introduced, permission information of a user is associated with a corresponding API, and fine-grained permission control is achieved. An access log system is introduced to record the access behavior and operation of the user, and important monitoring and auditing basis is provided for a system administrator.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention belongs to the technical field of network security, and in particular relates to a method and system for gateway flow control and authority access control based on ROMA Connect API. Background Art

[0002] ROMA Connect API Gateway implements basic API access capabilities and gateway service forwarding capabilities, but lacks the following capabilities for API service gateways in complex business scenarios:

[0003] 1. The ROMA Connect API gateway lacks traffic control for requests to access API service interfaces, which results in arbitrary access to open API services. First, it does not meet the traffic control requirements of each access interface service (open access APIs may have different traffic control strategies for different API interfaces for different business scenarios, and may also be associated with different access users / applications); at the same time, it does not have the ability to manage the number of consumption of API services. It is even more impossible to perform statistical analysis on API calls.

[0004] 2. The ROMA Connect API gateway lacks authentication for application / user requests to access API interface services, resulting in all externally open API services being accessible to any access endpoint that meets the interface permissions.

[0005] 3. ROMA Connect API Gateway lacks logs for application / user requests that access API interface services. It only provides access logs for back-end access to API interfaces, which makes it impossible to implement full-link logging and backtracking capabilities for end users / applications, and has significant defects in fault location and troubleshooting capabilities for API services. Summary of the invention

[0006] In order to solve the technical problems that the existing ROMA Connect API gateway only has basic API access capability and gateway service forwarding capability, the open API service can be accessed arbitrarily, and the fault location and troubleshooting capabilities of the API service have great defects, the present invention provides a method and system for gateway flow control and permission access control based on ROMA Connect API, develops an independent gateway service in the front end of the ROMA Connect API gateway, and introduces user concepts, access flow control capabilities, user permission management capabilities, and user access log capabilities, etc., which can dynamically limit the flow according to the request frequency within a certain time window, realize fine-grained permission control, and assist administrators in monitoring and auditing the system.

[0007] The specific plan is as follows:

[0008] A gateway traffic control and permission access control method based on ROMA Connect API.

[0009] S1: The user sends a request to the permission control module of the requesting user / application of the gateway service system through the unified API service unified entrance;

[0010] S2: The permission control module of the requesting user / application performs user authentication; specifically, the permission of the current user is obtained by reading the user permission of the user / application configuration submodule in the API application configuration and interface flow control device, and the permission is compared with the permission to access; if the permission does not match, it flows to the API service response module for no permission response; if the authentication is passed, it enters the API request encapsulator submodule in the API application configuration and interface flow control device;

[0011] S3: The API request encapsulator submodule reassembles the request format according to the user API request content and transfers it to the traffic control module of the requesting user / application;

[0012] S4: The traffic control module of the requesting user / application uses a sliding window algorithm to check whether the interface exceeds the flow limit times within the time window; if the flow limit times have been exceeded, the request / flow control event is recorded in the API log recording system, and the flow is transferred to the API service response module for flow limit response; if access is allowed, the time window access times of the current interface are updated, and the updated time window access times are detected to determine whether they exceed the set flow limit threshold and written into the API application configuration and the API flow control configuration submodule in the interface flow control device, and at the same time, the API request forwarding event is recorded in the API log recording system and the API request forwarding is performed;

[0013] S5: forward the current API request to the ROMA Connect API module, and trigger the API logging system to record the requesting user and related request information;

[0014] S6: The ROMA Connect API module returns a response to the API logging system, records the response information, and then returns it to the API service response module for a unified response.

[0015] Preferably, the user authentication described in S2 is to determine whether the user has the authority or partial authority to access system resources by verifying the user identity, and the method of verifying the user identity includes username and password verification, API key, and token.

[0016] Preferably, the user / application configuration submodule described in S2 is used to store and manage relevant information of each user or application, including user name, application ID, API access key, so as to distinguish different users or applications, and perform identity authentication and permission control when accessing the interface.

[0017] Preferably, the API request content includes: request method, request URL, request header, and request parameters.

[0018] Preferably, the API request encapsulator submodule includes: an initialization unit for setting the base URL, default request header, and authentication information; a request construction unit for constructing a complete request according to the specific request method, path, and parameters; a request sending unit for executing the constructed request and obtaining a response to send the request; a response processing unit for parsing response data and handling errors and exceptions; a logging unit for recording request and response logs; and a retry mechanism construction unit for automatically retrying when a request fails.

[0019] Preferably, the method for checking whether the user exceeds the current limit in S4 is:

[0020] S41: Record request: record each request, including timestamp and user / application identifier;

[0021] S42: Calculate current traffic: Calculate current traffic based on request records within a certain time window.

[0022] Preferably, the API logging system described in S4 monitors the number of interface calls made by the user through the user log, records each interface request made by the user, and counts the number of calls made to the interface by each user within a specific time.

[0023] Preferably, when the number of times a user calls an interface exceeds a set value within a specific time, frequently calls the interface beyond the authority, or involves other illegal requests, a security warning is output.

[0024] Preferably, the API flow control configuration submodule in S4 sets the number of requests allowed to pass through each API in each time period or the request rate per unit time.

[0025] Preferably, the method for the traffic control module of the requesting user / application to obtain the number of flow limits is: the method for obtaining the number of flow limits is to calculate through the request timestamp recorded in the sliding window limiter; specifically, the number of flow limits for the current request is obtained by querying the number of timestamps in the sliding window.

[0026] Preferably, the response information in S6 includes a response result and a response time.

[0027] A system consisting of a gateway flow control and permission access control method based on ROMA Connect API, comprising:

[0028] API application configuration and interface flow control device: including: user / application configuration submodule, API request encapsulator submodule, API interface flow control configuration submodule;

[0029] The user / application configuration submodule is used for: a permission configuration unit that defines the interface permissions of the user / application, a permission checking unit that checks the interface permissions of the user / application in the API request encapsulator; an integrated current limiting and permission control unit that integrates current limiting and permission checking logic in the encapsulator;

[0030] The API request encapsulator submodule includes: an initialization unit that sets the base URL, default request header, and authentication information; a construction request unit that constructs a complete request according to the specific request method, path, and parameters; a sending request unit that executes the constructed request and obtains a response to send the request; a processing response unit that parses the response data and handles errors and exceptions; a logging unit that records request and response logs; and a retry mechanism construction unit that automatically retries when a request fails.

[0031] Request user / application permission control module: perform user authentication, record and check the current number of requests, and decide whether to limit the flow; specifically, obtain the permissions of the current user by reading the user permissions of the user / application configuration submodule in the API application configuration and interface flow control device, and compare them with the permissions to be accessed; if the permissions do not match, flow to the API service response module for unauthorized response; if the authentication is passed, enter the API application configuration and the API request encapsulator submodule in the interface flow control device;

[0032] Traffic control module for requesting users / applications: used to use the sliding window algorithm to check whether the interface exceeds the flow limit times within the time window; if it does not exceed the flow limit times, the current API request is forwarded to the ROMA Connect API module, and the API logging system is triggered to record the requesting user and related request information;

[0033] API logging system: used to record request / flow control events, record API request forwarding events, record requesting users and related request information, record response information, and monitor when the number of times a user calls the interface exceeds the set value within a specific time, frequently calls the interface with excessive authority, and involves other illegal requests, and output security warnings.

[0034] Beneficial effects:

[0035] The present invention provides a method and system for gateway flow control and permission access control based on ROMA Connect API. An independent gateway service is developed in the front end of the ROMA Connect API gateway, and the user concept, access flow control capability, user permission management capability and user access log capability are introduced. The flow limiting problem is solved by using a sliding window algorithm in the flow control module of the requesting user / application. The algorithm dynamically limits the flow according to the request frequency within a certain time window. A permission file system is introduced to associate the user's permission information with the corresponding API to achieve fine-grained permission control. The access log system is introduced to record the user's access behavior and operations, providing important monitoring and auditing basis for system administrators.

[0036] First, the present invention performs flow control through API application configuration and interface flow control device and the flow control module of the requesting user / application. The flow control can effectively prevent the system from crashing due to overload requests and ensure that the system can run smoothly; flow control refers to limiting the requests of visitors or services to control their access rate. It is usually achieved by setting the number of requests allowed to pass in each time period or the request rate per unit time. Current limiting can protect the back-end service from the risk of overload and ensure the stability of the system. By limiting the rate of requests, too many requests can be prevented from pouring into the system at the same time, thereby avoiding the exhaustion of system resources, resulting in a decline in service quality or downtime. If there is no flow limiting function, the system may be affected by malicious attacks or overload requests, causing the system to crash or fail to work properly. In addition, if some requests are too frequent, system resources may be exhausted, affecting the access experience of other legitimate users.

[0037] Secondly, the present invention performs user authentication through the API application configuration and interface flow control device and the permission management module of the requesting user / application. User authentication can ensure that system resources are only accessed by authorized users, preventing security risks caused by unauthorized access. User authentication refers to the process of verifying the identity of the user to ensure that the user has the authority to access system resources. Identity authentication is usually performed through username and password verification, API keys, tokens, etc. User authentication can protect the system from unauthorized access and ensure that only legitimate users can access system resources. By verifying the identity of the user, it can be ensured that the user can only access the resources to which he has permission, thereby improving the security of the system. If user authentication is lacking, the system may be accessed by unauthorized users, resulting in security risks such as sensitive data leakage and malicious operations. In addition, the inability to authenticate the user will also cause the system to be unable to distinguish the permissions of different users, which may cause resources to be abused or tampered with.

[0038] At the same time, the present invention uses the permission control module of the requesting user / application, the traffic control module of the requesting user / application, the API service response module and the ROMA Connect API module to send request / flow control events, API request forwarding events, requesting users and related request information, and response information to the API log recording system for log monitoring. The user log can count and monitor dimensions such as the number of times the user's interface calls are called. The user log can count and monitor dimensions such as the number of times the user's interface calls are called. By recording each interface request of the user, the system can count the number of times each user calls the interface within a specific time, and can monitor and analyze based on these data to understand the user's behavior pattern, find abnormal behavior or potential security threats. The system can count the number of times each user calls the interface within a specific time, and can monitor and analyze based on these data to understand the user's behavior pattern, find abnormal behavior or potential security threats. If there is a lack of statistics and monitoring of the number of user interface calls, system resources may be over-occupied by some users, thereby affecting the normal use experience of other users, resulting in the problem of uneven resource utilization. In addition, there are statistics and monitoring of dimensions such as the number of user interface calls, and the system cannot promptly discover the user's abnormal behavior, such as frequent illegal requests or abnormally high request frequencies. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 A flow chart of a method for gateway traffic control and permission access control based on ROMA Connect API.

[0040] Figure 2 A system structure diagram of gateway flow control and permission access control based on ROMA Connect API. DETAILED DESCRIPTION

[0041] The present invention will be further described below in conjunction with the accompanying drawings and embodiments.

[0042] like Figure 1 As shown in the figure, a gateway flow control and permission access control method based on ROMA Connect API is provided.

[0043] S1: The user sends a request to the permission control module of the requesting user / application of the gateway service system through the unified API service unified entrance;

[0044] S2: The permission control module of the requesting user / application performs user authentication; specifically, the permission of the current user is obtained by reading the user permission of the user / application configuration submodule in the API application configuration and interface flow control device, and the permission is compared with the permission to access; if the permission does not match, it flows to the API service response module for no permission response; if the authentication is passed, it enters the API request encapsulator submodule in the API application configuration and interface flow control device;

[0045] S3: The API request encapsulator submodule reassembles the request format according to the user API request content and transfers it to the traffic control module of the requesting user / application;

[0046] Because the request format of different APIs may be different. Generally, an API request format includes the following parts: Request method: GET, POST, PUT, DELETE, etc. Request URL: including base URL and path parameters. Request header: such as Content-Type, Authorization, etc. Request parameters: including query parameters and request body (if any).

[0047] The functions of the API request wrapper include: Initialization: setting the base URL, default request header, authentication information, etc. Build request: build a complete request based on the specific request method, path, and parameters. Send request: execute the built request and get a response. Process response: parse the response data, handle errors and exceptions. Logging: record request and response logs for easy debugging. Retry mechanism: automatically retry when the request fails. Cache: cache some frequently requested data to reduce the number of API calls.

[0048] S4: The traffic control module of the requesting user / application checks whether the interface exceeds the flow limit times within the time window;

[0049] The method for recording the number of current limiting times is:

[0050] Log requests: Log every request, including timestamp and user / application ID.

[0051] Calculate current traffic: Calculate current traffic based on request records within a certain time window.

[0052] If the current limit times have been exceeded, the request / flow control event is recorded in the API log recording system and transferred to the API service response module for current limit response; if access is allowed, the time window access times of the current interface are updated, and the updated time window access times are used to determine whether current limiting is required according to the set current limit threshold and written into the API application configuration and the API flow control configuration submodule in the interface flow control device, and at the same time, the API request forwarding event is recorded in the API log recording system and the API request forwarding is performed;

[0053] S5: forward the current API request to the ROMA Connect API module, and trigger the API logging system to record the requesting user and related request information;

[0054] S6: The ROMA Connect API module returns a response to the API logging system, records the response information, and then returns it to the API service response module for a unified response.

[0055] The user authentication described in S2 is to determine whether the user has the authority or partial authority to access system resources by verifying the user identity. The method of verifying the user identity includes username and password verification, API key, and token.

[0056] The user rights of the user / application configuration submodule described in S2 include: a rights configuration unit: defining the interface rights of the user / application. A rights checking unit: checking the interface rights of the user / application in the API request wrapper. An integrated current limiting and rights control unit: integrating current limiting and rights checking logic in the wrapper.

[0057] The API request format includes: request method, request URL, request header, and request parameters.

[0058] The API request encapsulator submodule includes: an initialization unit that sets the base URL, default request header, and authentication information; a construction request unit that builds a complete request according to the specific request method, path, and parameters; a sending request unit that executes the constructed request and obtains a response to send the request; a processing response unit that parses the response data and handles errors and exceptions; a logging unit that records request and response logs; and a retry mechanism construction unit that automatically retries when a request fails.

[0059] Cache: Cache some frequently requested data to reduce the number of API calls.

[0060] The API logging system described in S4 monitors the number of times a user calls an interface through a user log, records each interface request of a user, and counts the number of times each user calls the interface within a specific time.

[0061] When the number of interface calls by a user exceeds the set value within a specific time, frequently calls the interface beyond the authority, or involves other illegal requests, a security warning will be output.

[0062] The API flow control configuration submodule in S4 sets the number of requests allowed to pass in each time period or the request rate per unit time.

[0063] API interface flow control configuration: configure the request rate limit for each API.

[0064] API request wrapper: sends requests and integrates current limiting logic.

[0065] Traffic control module for requesting users / applications: records and checks the current number of requests and decides whether to limit the flow.

[0066] The method for the traffic control module of the requesting user / application to obtain the flow limiting times is: the method for obtaining the flow limiting times is calculated by the request timestamp recorded in the sliding window flow limiter. Specifically, the flow limiting times of the current request are obtained by querying the number of timestamps in the sliding window.

[0067] The response information in S6 includes the response result and the response time.

[0068] like Figure 2 As shown, a system consisting of a method for gateway flow control and permission access control based on ROMA Connect API includes:

[0069] API application configuration and interface flow control device: including: user / application configuration submodule, API request encapsulator submodule, API interface flow control configuration submodule;

[0070] The user / application configuration submodule is used to store and manage relevant information of each user or application, including user name, application ID, API access key, etc. This information is used to distinguish different users or applications and perform identity authentication and permission control when accessing the interface;

[0071] The API request encapsulator submodule is used to receive the authenticated API request, and reassemble the request format according to the user API request content, and then transfer it to the traffic control module of the requesting user / application;

[0072] Request user / application permission control module: used for user authentication; specifically, by reading the user permissions of the user / application configuration submodule in the API application configuration and interface flow control device, obtain the permissions of the current user, and compare them with the permissions to be accessed; if the permissions do not match, flow to the API service response module for unauthorized response; if the authentication is passed, enter the API request encapsulator submodule in the API application configuration and interface flow control device;

[0073] Traffic control module for requesting users / applications: used to check whether the interface exceeds the flow limit times within the time window; if not, the current API request is forwarded to the ROMA Connect API module, and the API logging system is triggered to record the requesting user and related request information;

[0074] API logging system: used to record request / flow control events, record API request forwarding events, record requesting users and related request information, record response information, and monitor when the number of times a user calls the interface exceeds the set value within a specific time, frequently calls the interface with excessive authority, and involves other illegal requests, and output security warnings.

[0075] Example 2: Assume that user user_123 wants to obtain user information through our API. The user will send an HTTP GET request.

[0076] Request processing details:

[0077] (1) Receiving request: User user_123 sends an HTTP GET request to the / users / 12345 endpoint, with a Bearer Token for authentication.

[0078] (2) Initialize the API request wrapper: During initialization, it accepts the API base URL, request header, current limit configuration, and user permission configuration.

[0079] (3) Logging request information At the beginning of request processing, detailed information of the request is recorded, such as the request method, URL, user ID, and request parameters.

[0080] (4) Permission check: Check whether user_123 has permission to access the / users / 12345 endpoint.

[0081] (5) Traffic monitoring: Get the flow limiter of the corresponding API endpoint. Check whether the user's request exceeds the set flow limit threshold. If the user's request exceeds the limit, return an error message and record a warning log.

[0082] (6) Send actual request: Send HTTP request to the real address. If the request is successful, process the response and record the response information. If the request fails, record HTTP error or other exceptions.

[0083] (7) Logging response information: Recording detailed information of the response to help track the processing and results of the request.

[0084] It will be easily understood by those skilled in the art that the above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for gateway flow control and authority access control based on ROMAConnect API, characterized in that: S1: The user sends a request to the permission control module of the requesting user / application of the gateway service system through the unified API service unified entrance; S2: The permission control module of the requesting user / application performs user authentication; specifically, the permissions of the current user are obtained by reading the user permissions of the user / application configuration submodule in the API application configuration and the interface flow control device, and comparing them with the permissions to be accessed; If the permissions do not match, the flow goes to the API service response module for an unauthorized response; if the authentication passes, it enters the API request encapsulator submodule in the API application configuration and interface flow control device; S3: The API request encapsulator submodule reassembles the request format according to the user API request content and transfers it to the traffic control module of the requesting user / application; S4: The traffic control module of the requesting user / application uses a sliding window algorithm to check whether the interface exceeds the flow limit times within the time window; If the current limit times have been exceeded, the request / flow control event is recorded in the API log recording system and transferred to the API service response module for current limit response; if access is allowed, the time window access times of the current interface are updated, and the updated time window access times are detected to determine whether they exceed the set current limit threshold and written into the API application configuration and the API flow control configuration submodule in the interface flow control device, and at the same time, the API request forwarding event is recorded in the API log recording system and the API request forwarding is performed; S5: forward the current API request to the ROMAConnect API module, and trigger the API logging system to record the requesting user and related request information; S6: The ROMAConnect API module returns a response to the API logging system and records the response information, and then returns to the API service response module for a unified response.

2. A method for gateway flow control and authority access control based on ROMAConnect API according to claim 1, characterized in that: The user authentication described in S2 is to determine whether the user has the authority or partial authority to access system resources by verifying the user identity. The method of verifying the user identity includes username and password verification, API key, and token.

3. A method for gateway flow control and authority access control based on ROMAConnect API according to claim 1, characterized in that: The user / application configuration submodule described in S2 is used to store and manage relevant information of each user or application, including user name, application ID, API access key, so as to distinguish different users or applications and perform identity authentication and permission control when accessing the interface.

4. A method for gateway flow control and authority access control based on ROMAConnect API according to claim 1, characterized in that: The API request content includes: request method, request URL, request header, and request parameters.

5. A method for gateway flow control and authority access control based on ROMAConnect API according to claim 1, characterized in that: The API request encapsulator submodule includes: an initialization unit that sets the base URL, default request header, and authentication information; a construction request unit that builds a complete request according to the specific request method, path, and parameters; a sending request unit that executes the constructed request and obtains a response to send the request; a processing response unit that parses the response data and handles errors and exceptions; a logging unit that records request and response logs; and a retry mechanism construction unit that automatically retries when a request fails.

6. A method for gateway flow control and authority access control based on ROMAConnect API according to claim 1, characterized in that: The method in S4 to check whether the user exceeds the flow limit is: S41: Record request: record each request, including timestamp and user / application identifier; S42: Calculate current traffic: Calculate current traffic based on request records within a certain time window.

7. A method for gateway flow control and authority access control based on ROMAConnect API according to claim 1, characterized in that: The API logging system described in S4 monitors the number of times a user calls an interface through a user log, records each interface request of a user, and counts the number of times each user calls the interface within a specific time.

8. A method for gateway flow control and authority access control based on ROMAConnect API according to claim 5, characterized in that: When the number of interface calls by a user exceeds the set value within a specific time, frequently calls the interface beyond the authority, or involves other illegal requests, a security warning will be output.

9. A method for gateway flow control and authority access control based on ROMAConnect API according to claim 1, characterized in that: The API flow control configuration submodule in S4 sets the number of requests allowed to pass through each API in each time period or the request rate per unit time.

10. A method for gateway flow control and authority access control based on ROMAConnect API according to claim 1, characterized in that: The method for the traffic control module of the requesting user / application to obtain the number of flow limits is: the method for obtaining the number of flow limits is to calculate the request timestamp recorded in the sliding window limiter; specifically, the number of flow limits for the current request is obtained by querying the number of timestamps in the sliding window.

11. A method for gateway flow control and authority access control based on ROMAConnect API according to claim 1, characterized in that: The response information in S6 includes the response result and the response time.

12. A system based on a method of gateway flow control and authority access control based on ROMAConnect API according to any one of claims 1 to 11, characterized in that: include: API application configuration and interface flow control device: including: user / application configuration submodule, API request encapsulator submodule, API interface flow control configuration submodule; The user / application configuration submodule is used for: a permission configuration unit that defines the interface permissions of the user / application, a permission checking unit that checks the interface permissions of the user / application in the API request encapsulator; an integrated current limiting and permission control unit that integrates current limiting and permission checking logic in the encapsulator; The API request encapsulator submodule includes: an initialization unit that sets the base URL, default request header, and authentication information; a construction request unit that constructs a complete request according to the specific request method, path, and parameters; a sending request unit that executes the constructed request and obtains a response to send the request; a processing response unit that parses the response data and handles errors and exceptions; a logging unit that records request and response logs; and a retry mechanism construction unit that automatically retries when a request fails. Request user / application permission control module: perform user authentication, record and check the current number of requests, and decide whether to limit the flow; specifically, obtain the permissions of the current user by reading the user permissions of the user / application configuration submodule in the API application configuration and interface flow control device, and compare them with the permissions to be accessed; if the permissions do not match, flow to the API service response module for unauthorized response; if the authentication is passed, enter the API application configuration and the API request encapsulator submodule in the interface flow control device; Traffic control module for requesting users / applications: used to use the sliding window algorithm to check whether the interface exceeds the flow limit times within the time window; if it does not exceed the flow limit times, the current API request is forwarded to the ROMA Connect API module, and the API logging system is triggered to record the requesting user and related request information; API logging system: used to record request / flow control events, record API request forwarding events, record requesting users and related request information, record response information, and monitor when the number of times a user calls the interface exceeds the set value within a specific time, frequently calls the interface with excessive authority, and involves other illegal requests, and output security warnings.

Citation Information

Patent Citations

  • Method of limiting network flow through API gateway

    CN109218212A

  • micro-service-based API gateway security management method and a micro-service-based API gateway security management system

    CN109756448A

  • Authentication method and device based on unified gateway, equipment and storage medium

    CN112039909A

  • Zero-trust API gateway dynamic trust evaluation and access control method and system based on machine learning

    CN114465807A

  • Safety management and control method for micro-service gateway request

    CN117675282A