Identity Authentication Server API Access ID Validation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing identity authentication methods in network-side servers face system overload and potential denial of service due to frequent unauthorized API calls from malicious third-party developers, leading to performance bottlenecks and system breakdowns.
Innovation Solution
Implement a method for identity authentication that verifies the version character and check characters in the access ID before performing replay attack verification, reducing the number of visits to API audit and frequency control systems by authenticating authorized access IDs first, thereby eliminating the impact of malicious invalid access IDs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the server performs replay attack verification, calling frequency verification, and digital signature verification for every API calling request, then security is improved, but system performance deteriorates due to frequent visits to storage system, API audit system, and frequency control system causing overload and denial of service
Solution Approach 1:
The patent applies preliminary action by verifying the access ID format, version character, and check characters before performing replay attack verification, calling frequency verification, and digital signature verification. This preliminary validation filters out obviously invalid requests early in the authentication process, preventing them from consuming resources in subsequent verification stages. The server checks whether the access ID conforms to the expected format, validates the version character matches the current version, and verifies check characters are correct before proceeding to more resource-intensive verification processes.
Solution Approach 2:
The patent extracts the access ID validation process from the main authentication flow and performs it as a separate preliminary step. By isolating the format verification, version character checking, and check character validation into distinct preliminary operations, the system can quickly identify and reject invalid access IDs without involving the storage system, API audit system, or frequency control system, thereby reducing their visit frequency and preventing system overload.
2Reliability
If the server visits storage system, API audit system, and frequency control system for every authentication request, then authentication completeness is improved, but system complexity increases leading to performance bottlenecks
Solution Approach 1:
The patent segments the authentication process into two distinct phases: preliminary verification (access ID format, version character, check characters) and comprehensive verification (replay attack detection, frequency control, digital signature). This segmentation allows the system to handle simple validation locally without involving external systems, and only engage the storage system, API audit system, and frequency control system when necessary, thereby reducing overall system complexity and improving performance.
Data Source
AI summary
The disclosure relates to a method, apparatus and server for identity authentication, related to communication technique to solve system overload problem caused by invalid access ID attack. The method may include: a server receiving an API calling request from third party developer, the API calling request carrying access ID generated in advance by server and assigned to the third party developer; searching for a version character carried in the access ID; based on a version character generation rule, verifying whether the version number marked by the version character being the same as a version number of the check character generation rule used by the server; when the version character being verified successfully, searching for at least a check character carried in the access ID; and based on the check character generation rule, verifying respectively on the at least a check character. The disclosure is applied to API calling request process.