CAPIF Core Function API Invoker Authentication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing security aspects and information flows of common application program interface (API) frameworks are open, necessitating the need for multiple authentication methods and a secure interface establishment procedure to support various services with different architectural and performance requirements.
Innovation Solution
A system and method for authenticating API invokers using a common application program interface framework (CAPIF) that involves establishing a secure connection with API invokers, determining suitable security methods such as TLS-PSK, TLS-PKI, IKEv2, IPsec, and OAuth 2.0, and enabling secure interface security (C2eIS) for API invokers based on these determined methods.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple authentication methods are implemented to support various services with different architectural and performance requirements, then the adaptability and versatility of the CAPIF framework is improved, but the device complexity and difficulty of implementation increase
Solution Approach 1:
The patent implements a universal authentication framework within CAPIF that can handle multiple authentication methods (OAuth 2.0, OpenID Connect, SAML, WS-Federation) through a single integrated architecture. The framework provides multi-functionality by supporting diverse authentication requirements across different services while maintaining a consistent interface and management mechanism, thereby improving adaptability without proportionally increasing complexity
Solution Approach 2:
The authentication system is segmented into distinct functional components including authentication providers, authentication consumers, authorization servers, and identity providers. Each component has well-defined roles and interfaces, allowing the complex authentication functionality to be divided into manageable modules that can be independently configured and managed, reducing the perceived complexity while maintaining versatility
2Reliability
If a secure interface establishment procedure is implemented to ensure security and integrity of API interactions, then the reliability and security of the system is improved, but the loss of time for authentication and connection establishment increases
Solution Approach 1:
The framework performs preliminary authentication and authorization actions before API interactions begin. By establishing secure connections and validating credentials in advance through pre-configured policies and cached authentication tokens, the system reduces the time required for authentication during actual API calls, thereby minimizing time loss while maintaining high security standards
Solution Approach 2:
The system implements feedback mechanisms where authentication results and security status are continuously monitored and fed back into the architecture. This enables dynamic adjustment of authentication strategies based on real-time conditions, allowing the system to optimize the balance between security measures and time consumption by learning from previous authentication patterns and outcomes
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method and system for authenticating application program interface (API) invokers using a common application program interface framework (CAPIF) is provided. The method includes establishing by a CAPIF core function (CCF) a secure Transport Layers Security (TLS) connection with at least one API invoker, on receiving a connection request from the at least one API invoker to access at least one service API on a CAPIF-2e interface. Further, the method includes determining by the CCF at least one security method to be used by the at least one API invoker for a CAPIF-2e interface security (C2eIS) of the at least one API invoker for accessing the at least one service API on a CAPIF-2e interface. The method further includes enabling the C2eIS by an API exposing function (AEF) the at least one API invoker based on the determined at least one security method.