Two-Factor API Call Authentication With Certificate And IAM Token
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for securing API-based access to cloud services are computationally expensive, complex, and not user-friendly, lacking robust two-factor authentication mechanisms.
Innovation Solution
A computer-implemented method and system that requires a two-factor authorization process using a client security certificate and an IAM token or API key for authenticating and authorizing user identifiers to access services via a service application programming interface, ensuring both authentication methods are distinct and verified by an identity access management system.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If two-factor authentication is implemented using distinct authentication methods, then security reliability is improved, but device complexity increases
Solution Approach 1:
The authentication system is segmented into two distinct authentication methods (first and second authentication methods) that operate independently but are both required for service access. This segmentation allows each method to be validated separately while collectively providing enhanced security through multiple factors.
Solution Approach 2:
The service application programming interface is designed to universally accept requests from multiple authentication methods, making the system multi-functional in terms of authentication approaches. The same API endpoint handles both first and second authentication methods, providing a unified interface for diverse authentication mechanisms.
2Reliability
If two-factor authorization process is implemented, then security against misuse is improved, but ease of operation deteriorates
Solution Approach 1:
The system performs preliminary validation of authentication methods by receiving and verifying both first and second authentication data before service execution. This preliminary action ensures security requirements are met upfront, preventing unauthorized access while maintaining a clear operational flow for legitimate users.
3Reliability
If distinct authentication methods are required, then security reliability is improved, but productivity deteriorates
Solution Approach 1:
The validation processes for first and second authentication methods are merged into a single service request handling flow. Both authentication validations occur within the same API transaction, combining multiple security checks into one unified operation rather than requiring separate sequential processes.
Data Source
AI summary
A method for authenticating and authorizing a user identifier to access a service is disclosed. The service is activated by a service application programming interface which requires a two-factor authorization to initiate execution of the service for the requesting user identifier. The method receives, by the service API, a service request together with first and second data for a first and a second authentication method, confirming a correctness of the first data as a first identity pass key using the first authentication method, confirming a correctness of the second data as a second identity pass key using the second authentication method and the first identity pass key is input to the second authentication method, and the second authentication method differs from the first authentication method. Having received the confirmed correctness of both the first identity pass key and the second identity pass key, executing the service.