An API call control system and authentication method with different security protection levels for specific domains

By introducing a registration and subscription mechanism into the API call management system in a specific domain, access credentials and encryption keys are generated, and multi-level permission verification is performed. This solves the problem that existing technologies cannot adapt to API scenarios with multiple security protection levels, and achieves highly secure API call authentication and access control.

CN119449446BActive Publication Date: 2026-11-17AVICIT CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202411644950.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-11-18
Publication Date
2026-11-17
Estimated Expiration
2044-11-18

AI Technical Summary

Technical Problem

Existing AK/SK interface authentication methods cannot be applied to API scenarios with multiple security protection levels in specific domains, leading to the leakage of confidential data or unauthorized access, and failing to provide dynamic and multi-dimensional security protection.

Method used

An API call management system for a specific domain was designed, including an API gateway management module, a caller registration module, a subscription module, and an authentication and authorization module. Access credentials and encryption keys are generated through registration and subscription mechanisms to perform multi-level permission verification and access control. The HMAC-SHA256 algorithm is used to generate a signature string for request verification.

Benefits of technology

It implements dynamic and multi-dimensional security protection based on the API's security protection level, prevents unauthorized access, ensures that API callers can only access resources that match their own level, and improves the security and reliability of the authentication process.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119449446B_ABST
    Figure CN119449446B_ABST
Patent Text Reader

Abstract

This invention provides an API call management system and authentication method for different security protection levels in a specific domain. The system isolates APIs according to their security levels and deploys them to matching API gateways, meeting the requirements of resource isolation for different security protection levels in specific domains. Core components include API gateway management, caller registration, API subscription, authentication and authorization, and a display center module. To ensure the security and trustworthiness of API callers, an API call authentication method for different security protection levels in a specific domain is designed, using multi-level authentication control based on authorization credentials, IP address, security level attributes, and access permissions. According to the technical solution of this invention, the authorized scope of API resources is controlled, ensuring that API callers can only access API resources that match their own security protection level, effectively preventing the leakage of confidential data due to unauthorized or unauthorized access, and meeting the high security requirements of API protection in specific domains.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the technical field of computer program data interaction, and specifically to an API call control system and authentication method with different security protection levels for a specific field. Background Technology

[0002] Against the backdrop of the rapid development of modern information technology and the Internet, APIs (Application Programming Interfaces) have become a key technology for data interaction and service integration between different systems. With the widespread use of APIs, security issues have become increasingly prominent, especially in the digital transformation of specific fields. API calls not only need to handle massive amounts of data, but also must ensure the security of the call process and strictly prevent the leakage of confidential information and unauthorized access.

[0003] In certain domains, the security level of an API matches its data security level. However, current mainstream API call authentication and access control methods cannot provide dynamic, multi-dimensional security protection for the call process based on the API's security level. API authentication typically uses the AK / SK method, embedding user information into a key user identifier, which is sent to the server along with the request. An API caller refers to an application or service created or defined by the developer user to initiate an access request to the API via network protocols. Its responsibilities include initiating the call request, passing parameters and authentication information, and receiving the returned response data. Since API callers in certain domains also possess security level attributes, when calling APIs with multiple security levels, one cannot call an API with a higher security level than oneself, otherwise it may lead to the leakage of confidential data or unauthorized access. Existing AK / SK interface authentication methods only include user information and do not include the API caller's security level information, making them unsuitable for multi-security-level API authentication and access control in specific domains. Summary of the Invention

[0004] To address the difficulty of applying the current mainstream AK / SK interface authentication methods to API scenarios with multiple security protection levels in specific domains, this invention provides an API call management system for different security protection levels in specific domains, including:

[0005] API Gateway Management Module: Used to uniformly manage isolated API gateways with different security protection levels, and serves as the unified entry point for the API call management system. API callers initiate access requests through this entry point.

[0006] API caller registration module: This module is used by developers to register the IP address and security protection level of API callers to the API call management system. The API caller registration module generates access credentials and keys for request hash encryption for API callers, and works with the API authentication and authorization module to verify content and permissions when API callers initiate API access requests.

[0007] API subscription module: It performs subscription verification based on developer permissions and API caller security protection level. If the verification passes, it adds the caller's credentials to the API access whitelist. When the API caller initiates an access request, it works with the API authentication and authorization module to verify the user's access permissions again.

[0008] API authentication and authorization module: Used to verify the legitimacy of API caller access requests, including: based on the API caller's registration and subscription information, the access request is sequentially verified by credential verification, IP address verification, security protection level verification, request content signature verification, and API access permission verification. After all verifications are passed, the API authentication and authorization module issues a temporary access token to the API caller for subsequent access.

[0009] API Display Center Module: As the portal module of the API call management system, it displays APIs within the developer's authorized scope based on the developer's identity information.

[0010] According to another aspect of the present invention, an API call authentication method for different security protection levels oriented towards a specific domain is also provided, which is executed by an API call control system for different security protection levels oriented towards a specific domain, including:

[0011] Step 101: Receive the IP address and security level of the API caller provided by the developer, and allow the registered API caller;

[0012] Step 102: The API call management system receives the registration information of the API caller, and generates a unique identifier as an access credential based on the caller's IP address and security protection level through a hash signature algorithm. At the same time, the API call management system creates an encryption key that uniquely corresponds to the access credential.

[0013] Step 103: After creating the access credentials and encryption key, the API call management system issues the access credentials and encryption key to the API caller and records their information at the same time;

[0014] Step 104: The API Showcase Center module receives access from developers, allowing them to select the required APIs from the accessible API range, and initiate a subscription request based on the API caller's access credentials to obtain the corresponding API calling permissions;

[0015] Step 105: After receiving the subscription application, the API call control system determines the API caller's IP address, security protection level attribute, and developer based on the access credentials, and compares the security protection level of the API caller with that of the subscribed API: if the API caller's security protection level is lower than that of the subscribed API, the subscription is rejected; otherwise, it is allowed.

[0016] According to another aspect of the present invention, an API call authentication method for different security protection levels oriented to a specific domain is also provided, which is executed based on an API call management system for different security protection levels oriented to a specific domain, including:

[0017] Step 201: The developer constructs an access request to the subscription API, including the following:

[0018] a. HTTP request methods;

[0019] b. Request URI;

[0020] c. Request parameters: including URL query parameters and parameters in the request body;

[0021] d. Request header information;

[0022] e. The subject of the request;

[0023] Step 202: Combine the HTTP request method, request URI, request parameters, request header information, and request body into a string to be signed in a specific order and format to generate a signature. Use an encryption key and the HMAC-SHA256 algorithm to encrypt the constructed string using a hash message authentication code to generate a signature string, which is used to identify the uniqueness and integrity of the current access request. The encryption key generation process is as follows: The API call management system generates a unique identifier as an access credential based on the API caller's IP address and security protection level using a hash signature algorithm. At the same time, the API call management system creates an encryption key that uniquely corresponds to the access credential.

[0024] Step 203: The client sends an API access request, carrying the following information:

[0025] Access credentials;

[0026] Signature: Used to prove that the API access request was initiated by an API caller who has registered in the API call management system and possesses a valid key;

[0027] Key verification information includes the API caller's IP address and security protection level attributes, which are used in the subsequent verification and authentication process.

[0028] Timestamp;

[0029] Step 204: After receiving the API access request, the API call management system performs multi-level authentication on the API access request;

[0030] Step 205: If authentication is successful, match the API caller's access credentials in the API whitelist. If a match is found, it means that the API caller has subscribed to the API and has access rights to the API, so access is allowed; otherwise, the request is rejected.

[0031] Step 206: The API call management system issues a time-sensitive temporary token to the API caller for access;

[0032] Step 207: When an API caller accesses the corresponding API, it carries a temporary token in the request. After the API call control system verifies that the token is valid and has not expired, it forwards the request to the backend API service and returns the response data.

[0033] The design concept of this invention mainly includes the following:

[0034] (1) An API management system with an API gateway as its core was designed. On the one hand, the system isolates and deploys APIs with different security protection levels to API gateways that match the security protection level of the APIs themselves, so as to meet the security compliance requirements of specific domains for resource isolation of different security protection levels; on the other hand, based on the security protection level attributes of the APIs, the authentication process of API calls with multiple security protection levels is security-hardened. The core components of the API management system include the API gateway management module, the API caller registration module, the API subscription module, the API authentication and authorization module, and the API display center module.

[0035] (2) This method provides an API authorization access method based on a registration and subscription mechanism for a specific domain. Since API callers and APIs need to be differentiated according to security protection levels, this method refines the minimum authorization unit for API access from the developer user to the API caller created or defined by the developer. This method requires API callers to go through a registration and subscription process before requesting API access. The registration process refers to the process by which the API caller submits its IP address and security protection level attributes to the API management system to obtain access credentials and encryption keys; the subscription process refers to the process by which the developer initiates an API access permission application in the API management system based on the API access credentials, and the API management system completes the authorization after verifying the security protection level.

[0036] (3) A multi-level API call authentication and access control method for a specific domain is provided. In this method, when an API caller initiates an access request for the first time, it needs to carry the request signature, IP address, security protection level attributes and credentials. After the API management system compares and verifies the credentials layer by layer, it obtains a temporary token for the corresponding API. In subsequent API accesses, the caller uses the temporary token to access the corresponding API within its validity period to obtain response data.

[0037] Beneficial effects:

[0038] This invention addresses the shortcomings of current AK / SK-based API authentication methods in scenarios with multiple security protection levels in specific domains by establishing a multi-level, fine-grained API call authentication and access control method. The API management system of this invention, based on the security protection level of the API, identifies and manages the security level attributes of API callers through a registration and subscription mechanism. This ensures that API callers can only access API resources matching their own level, effectively preventing the leakage of confidential data due to unauthorized access. Simultaneously, the system employs isolated deployment of API gateways at different levels to strengthen API access control. This invention not only implements multi-dimensional permission verification in the API call process but also introduces a temporary token mechanism, improving the security and reliability of the authentication process and meeting the high security requirements for API protection in specific domains. Attached Figure Description

[0039] Figure 1 This is a diagram illustrating the relationship between the API management system, API callers, and APIs.

[0040] Figure 2 This is an architectural diagram of an API call management system that implements different security protection levels for specific domains.

[0041] Figure 3 This is a flowchart of API callers registering and subscribing in the API management system.

[0042] Figure 4 This is a diagram illustrating the process of API call authentication methods for different security protection levels in a specific domain. Detailed Implementation

[0043] The technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative effort are within the protection scope of the present invention.

[0044] Example 1

[0045] This embodiment details an API call management system with different security protection levels for a specific domain.

[0046] like Figure 1 As shown, this invention provides an API management and usage model applicable to a specific domain, and abstracts the following key roles in the construction and use of the API management system:

[0047] (1) API Gateway: A system component used to centrally manage API interfaces that match its own security protection level, and is responsible for API publishing, authorization, rate limiting, routing and monitoring functions.

[0048] (2) API caller: refers to the application or service created or defined by the developer, which initiates access requests to the API through network protocols, is responsible for initiating call requests, passing parameters and authentication information, and receiving response data.

[0049] (3) API backend service: The system service that provides API interfaces has a corresponding security protection level based on its own data security protection level. The API backend service can provide multiple API interfaces with different security protection levels, but none of them are higher than its own security protection level.

[0050] exist Figure 1 In this API management and usage model, the API backend service publishes the API to the corresponding API gateway based on the API's security protection level attributes, and then manages it uniformly through the API management system. Developers first register API callers with the API management system, and then subscribe to and access the corresponding APIs according to their permissions and the API callers' security protection level attributes.

[0051] like Figure 2 As shown, this invention designs an API call management system with different security protection levels for a specific field. Its core modules include an API gateway management module, an API caller registration module, an API subscription module, an API authentication and authorization module, and an API display center module.

[0052] API Gateway Management Module: This module centrally manages isolated API gateways with different security levels. On one hand, it distributes control policies such as routing, degradation, rate limiting, and circuit breaking to each API gateway. On the other hand, it serves as the unified entry point for the API call management system. API callers initiate access requests through this entry point, and after successful authorization verification, the API call management system routes the request to the appropriate API gateway with the corresponding security level via a load balancing mechanism. For example... Figure 2 As shown, the API gateway management module manages API gateways at various security protection levels. Figure 2The example illustrates API gateways with three security protection levels. As a core component of the API call management system, the API gateway is responsible for accessing and managing the API interfaces published by backend services.

[0053] API Caller Registration Module: Before calling an API, developers must register the API caller's IP address, security level, and other information with the API management system. The API caller registration module generates access credentials and a key for request hash encryption for the API caller, and works with the API authentication and authorization module to verify content and permissions when the API caller initiates an API access request.

[0054] API subscription module: It performs subscription verification based on developer permissions and API caller security protection level. If the verification passes, it adds the caller's credentials to the API access whitelist. When the API caller initiates an access request, it works with the API authentication and authorization module to verify the user's access permissions again.

[0055] The API authentication and authorization module verifies the legitimacy of API caller requests. Based on the API caller's registration and subscription information, the module sequentially verifies the access request's credentials, IP address, security protection level, request content signature, and API access permissions. After all verifications pass, the module issues a temporary access token to the API caller for subsequent access. Subsequent requests only require verification of the token's validity. After multi-level verification, the system forwards the request to the corresponding API gateway and ultimately routes it to the appropriate API backend service.

[0056] API Showcase Center Module: As the portal module of the API management system, it displays APIs within the developer's authorized scope based on their identity information. The showcase center provides basic information about the API interfaces, calling methods, and return result descriptions, allowing developers to select and call them as needed.

[0057] The system according to the embodiments of the present invention uses an API gateway as the core component to build a unified management and control system for API interfaces with different security protection levels; it designs a registration and subscription mechanism for API callers before access and a multi-level authentication method for API call access to ensure the security and trustworthiness of the requester, prevent the leakage of confidential data, and solve the problem that the current mainstream authentication and access control methods of the Internet cannot provide dynamic and multi-dimensional security protection for API calls according to the security protection level.

[0058] The API management system includes an API gateway management module, an API caller registration module, an API subscription module, an API authentication and authorization module, and an API display center module. These modules work together to handle the registration and subscription processes before API callers initiate access requests, as well as multi-level authentication during request initiation.

[0059] Example 2

[0060] This embodiment details the process of API call authentication methods for different security protection levels in a specific domain.

[0061] Based on the API call management system proposed in Embodiment 1, through... Figure 3 The illustrated process implements API call authentication methods for different security levels tailored to specific domains, including API caller registration and API subscription. It refines the minimum authorization unit for API access from the developer to the application or service level, ensuring controlled API access and preventing the leakage of confidential information. The specific steps are as follows:

[0062] Step 101: Receive the IP address and security level of the API caller provided by the developer, and allow the registered API caller. This is because before accessing the API control system, the API caller needs to register their information with the API call control system to obtain access credentials that identify their information and encryption keys used for request signing.

[0063] Step 102: The API call management system receives the registration information of the API caller. Based on the caller's IP address, security protection level, and other necessary information, it generates a unique identifier as an access credential using a hash signature algorithm. Simultaneously, the API call management system creates an encryption key uniquely corresponding to the access credential, used for encrypting the client's API request content and for the API call management system to perform signature comparison on the request content.

[0064] Step 103: After creating the access credentials and encryption key, the API call management system issues the access credentials and encryption key to the API caller and records their information so that when an API access request is received, the access credentials and encryption key can be used to verify the legitimacy of the request.

[0065] Step 104: The API Showcase Center module receives access from developers, allowing them to select the required API from the range of accessible APIs, and initiate a subscription request based on the API caller's access credentials to obtain the corresponding API calling permissions.

[0066] Step 105: After receiving a subscription request, the API call control system determines the API caller's IP address, security protection level, and developer information based on the access credentials, and compares the API caller's security protection level with that of the subscribed API. To prevent unauthorized access to confidential data, the system strictly restricts subscription permissions based on security protection levels: subscription is rejected when the API caller's security protection level is lower than that of the subscribed API, and allowed otherwise. The API call control system maintains an access whitelist for each API; after successful subscription, the API caller's credentials are added to the API's whitelist.

[0067] Example 3

[0068] This embodiment details the multi-level call authentication process for API request access based on an API management system.

[0069] Based on the API management system of Embodiment 1, and combined with the API caller registration and subscription process in Embodiment 2, this invention, through, as follows Figure 4 The illustrated process implements multi-level IP address authentication for API access. The specific steps are as follows:

[0070] Step 201: Developers construct access requests to the subscription API, typically including the following:

[0071] a. HTTP request methods: such as GET, POST, DELETE, etc.;

[0072] b. Request URI: The path to the requested resource, such as / api / v1 / resource;

[0073] c. Request parameters: These include URL query parameters and parameters in the request body, and they usually need to be sorted in alphabetical order;

[0074] d. Request header information: including Host, Date, and custom header information;

[0075] e. Request Body: If it is a POST or PUT request, the content of the request body may need to be hashed.

[0076] Step 202: Combine the API request method (GET, POST, etc.), request URI, request headers and parameters, and request body in a specific order and format to form a string to be signed, thus generating a signature. An example format is as follows:

[0077]

[0078] The constructed string is encrypted using an encryption key and the HMAC-SHA256 algorithm to generate a signature string, which is used to identify the uniqueness and integrity of the current access request. The encryption key generation process is as follows: the API call management system generates a unique identifier as an access credential based on the API caller's IP address and security level using a hash signature algorithm. Simultaneously, the API call management system creates an encryption key that uniquely corresponds to the access credential.

[0079] Step 203: The client sends an API call request, carrying the following information:

[0080] (1) Access credentials: Passed as a request header or URL parameter to indicate the identity of the API caller.

[0081] (2) Signature: Used to prove that the request was initiated by an API caller who has registered with the API call management system and has a valid key. The signature is usually attached to the API call request as a request header or as a URL parameter.

[0082] (3) Key verification information: including the IP address and security protection level of the API caller, which are used for subsequent verification and authentication processes.

[0083] (4) Timestamp: To prevent backtracking attacks, timestamps are usually added to ensure that the signature of each request is unique and has a short validity period.

[0084] The client is a smart device that accommodates API callers.

[0085] Step 204: After receiving the API call request, the API call management system performs multi-level authentication on the request, specifically including:

[0086] (1) Credential verification: Verify whether the API caller has registered in the API call management system based on the credential information of the API caller. If the credential does not exist or is invalid, the request will be rejected.

[0087] (2) IP address verification: Query the IP address provided during registration based on the API caller's credentials and compare it with the IP address sent by the client. If they do not match, the request is rejected.

[0088] (3) Security protection level verification: Based on the API caller's credentials, query the security protection level information provided during registration and compare it with the security protection level information of the API being called. If the API caller's security protection level is higher than or equal to the security protection level of the API being called, access is allowed; otherwise, the request is rejected.

[0089] (4) Request Content Signature Verification: Based on the access request data (including request method, URI, request parameters, header information, etc.), reconstruct the string to be signed according to step 202. Query the corresponding encryption key using the API caller's access credentials, and use this encryption key and the HMAC-SHA256 algorithm to encrypt the reconstructed string, generating a signature for the API call control system. Compare the signature sent by the client with the generated signature; if they do not match, reject the request.

[0090] Step 205: If all the above verifications pass, match the API caller's access credentials in the API whitelist. If a match is found, it means that the API caller has subscribed to the API and has access rights to the API, so access is allowed; otherwise, the request is rejected.

[0091] Step 206: The API call management system issues a time-sensitive temporary token to the API caller for access.

[0092] Step 207: When an API caller accesses the corresponding API, they include a temporary token in their request, eliminating the need for the authentication steps described above. After verifying the token's validity and expiration, the API call management system forwards the request to the backend API service and returns the response data.

[0093] According to the method of this invention, the API caller registration and subscription mechanism requires callers to register their IP address, security protection level attributes, and other information in the API management system before initiating an API access request. The management system then issues access credentials and encryption keys. API callers subscribe to APIs within their authorized scope that have a lower security protection level than their own, based on the access credentials. This mechanism refines the smallest authorized unit for API access to the API caller (the application or service created or defined by the developer), ensuring that the access process is controlled and preventing the leakage of confidential information.

[0094] The multi-level API call authentication method performs multi-level verification on the access credentials, IP address, security protection level attributes, and request content signature carried in the request when the API caller initiates an access request for the first time, and issues a temporary token for accessing the corresponding API. In subsequent accesses, the API caller uses the valid temporary token to access the corresponding API and obtain response data.

Claims

1. An API call management system with different security protection levels for a specific domain, characterized in that, include: API Gateway Management Module: Used to uniformly manage isolated API gateways with different security protection levels, and serves as the unified entry point for the API call management system. API callers initiate access requests through this entry point. API caller registration module: This module is used by developers to register the IP address and security protection level of API callers to the API call management system. The API caller registration module generates access credentials and keys for request hash encryption for API callers, and works with the API authentication and authorization module to verify content and permissions when API callers initiate API access requests. API subscription module: The subscription is verified based on the developer's permissions and the security protection level of the API caller. If the verification is successful, the caller's credentials are added to the API access whitelist. When an API caller initiates an access request, the collaborative API authentication and authorization module verifies the user's access permissions again. API authentication and authorization module: Used to verify the legitimacy of API caller access requests, including: based on the API caller's registration and subscription information, the access request is sequentially verified by credential verification, IP address verification, security protection level verification, request content signature verification, and API access permission verification. After all verifications are passed, the API authentication and authorization module issues a temporary access token to the API caller for subsequent access. API Display Center Module: As the portal module of the API call management system, it displays APIs within the developer's authorized scope based on the developer's identity information; The verification performed by the API authentication module includes: Credential verification: Verify whether the API caller is registered in the API call management system based on the API caller's access credentials. If the credentials do not exist or have expired, the access request will be rejected. IP address verification: Query the IP address provided during registration based on the API caller's access credentials and compare it with the IP address sent by the client. If they do not match, the access request is rejected. Security protection level verification: Based on the API caller's access credentials, query the security protection level information provided during registration and compare it with the security protection level information of the API being called. If the API caller's security protection level is higher than or equal to the security protection level of the API being called, access is allowed; otherwise, the access request is rejected. Request content signature verification: Combine the data of the access request into a string to be signed in a specific order and format, query the corresponding encryption key through the API caller's access credentials, and use the encryption key to encrypt the string to be signed with the HMAC-SHA256 algorithm to generate a signature on the API call control system side. Compare the signature sent by the client with the generated signature. If they do not match, the access request is rejected. API access permission verification: The API caller's access credentials are matched against the whitelist of API users. If a match is found, it means that the API caller has subscribed to the API and has access rights to it, and access is allowed; otherwise, the access request is denied.

2. An API call authentication method for different security protection levels in a specific domain, characterized in that, Executed by the API call management system for different security protection levels oriented to a specific domain, as described in claim 1, including: Step 101: Receive the IP address and security level of the API caller provided by the developer, and allow the registered API caller; Step 102: The API call management system receives the registration information of the API caller, and generates a unique identifier as an access credential based on the caller's IP address and security protection level through a hash signature algorithm. At the same time, the API call management system creates an encryption key that uniquely corresponds to the access credential. Step 103: After creating the access credentials and encryption key, the API call management system issues the access credentials and encryption key to the API caller and records their information at the same time; Step 104: The API Showcase Center module receives access from developers, allowing them to select the required APIs from the accessible API range, and initiate a subscription request based on the API caller's access credentials to obtain the corresponding API calling permissions; Step 105: After receiving the subscription application, the API call control system determines the API caller's IP address, security protection level attribute, and developer based on the access credentials, and compares the security protection level of the API caller with that of the subscribed API: if the API caller's security protection level is lower than that of the subscribed API, the subscription is rejected; otherwise, it is allowed.

3. An API call authentication method for different security protection levels in a specific domain, characterized in that, Based on the API call management system for different security protection levels in a specific domain as described in claim 1, the system includes: Step 201: The developer constructs an access request to the subscription API, including the following: a. HTTP request methods; b. Request URI; c. Request parameters: including URL query parameters and parameters in the request body; d. Request header information; e. The subject of the request; Step 202: Combine the HTTP request method, request URI, request parameters, request header information, and request body into a string to be signed in a specific order and format to generate a signature. Use an encryption key and the HMAC-SHA256 algorithm to encrypt the constructed string using a hash message authentication code to generate a signature string, which is used to identify the uniqueness and integrity of the current access request. The encryption key generation process is as follows: The API call management system generates a unique identifier as an access credential based on the API caller's IP address and security protection level using a hash signature algorithm. At the same time, the API call management system creates an encryption key that uniquely corresponds to the access credential. Step 203: The client sends an API access request, carrying the following information: Access credentials; Signature: Used to prove that the API access request was initiated by an API caller who has registered in the API call management system and possesses a valid key; Key verification information includes the API caller's IP address and security protection level attributes, which are used in the subsequent verification and authentication process. Timestamp; Step 204: After receiving the API access request, the API call management system performs multi-level authentication on the API access request; Step 205: If authentication is successful, match the API caller's access credentials in the API whitelist. If a match is found, it means that the API caller has subscribed to the API and has access rights to the API, so access is allowed; otherwise, the request is rejected. Step 206: The API call management system issues a time-sensitive temporary token to the API caller for access; Step 207: When an API caller accesses the corresponding API, it carries a temporary token in the request. After the API call control system verifies that the token is valid and has not expired, it forwards the request to the backend API service and returns the response data.

4. The API call authentication method for different security protection levels in a specific domain as described in claim 3, characterized in that, Step 204 includes: Credential verification: Verify whether the API caller is registered in the API call management system based on the API caller's credential information. If the credential does not exist or is invalid, the request is rejected. IP address verification: Query the IP address provided during registration based on the API caller's credentials and compare it with the IP address sent by the client. If they do not match, the request is rejected. Security protection level verification: Based on the API caller's credentials, query the security protection level information provided during registration and compare it with the security protection level information of the API being called. If the API caller's security protection level is higher than or equal to the security protection level of the API being called, access is allowed; otherwise, the request is rejected. Request content signature verification: Based on the data of the API access request, reconstruct the string to be signed according to step 202, query the corresponding encryption key through the API caller's access credentials, and use the encryption key and HMAC-SHA256 algorithm to encrypt the reconstructed string to generate a signature on the API call management system side. Compare the signature sent by the client with the generated signature. If they do not match, the request is rejected.

Citation Information

Patent Citations

  • Micro-service access control method, system and device based on security attribute

    CN114422183A

  • Cross-resource pool API gateway application access authorization and management method and system

    CN118740464A