Authentication System Using Third-Party Authorization Activity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current authentication and authorization methods are vulnerable to unauthorized access due to reliance on single-point credential verification, which can be compromised through fraudulent means, necessitating more efficient and reliable processes to ensure authentic user access.
Innovation Solution
A system and method that utilize the history of previous requests by generating query messages with identifier tags to third-party servers, retrieving authorization activity data, assigning weights to activity values, and applying these to an authorization model to determine whether to grant access, thereby enhancing authentication confidence.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If single-point credential verification is used for authentication, then the authentication process is simple and fast, but the system becomes vulnerable to fraudulent access and lacks reliability
Solution Approach 1:
The patent introduces third-party servers as intermediaries that provide authorization activity data. Instead of relying solely on the server's own credential verification, the system queries third-party servers for additional authentication context, thereby improving reliability without requiring the main server to perform all verification itself
Solution Approach 2:
The authentication process is segmented into multiple independent components: the server computer performs credential verification, while third-party servers provide authorization activity data. This segmentation allows each component to focus on specific authentication tasks, improving overall system reliability while maintaining simplicity in individual components
2Reliability
If third-party data is queried for authentication validation, then authentication confidence and reliability improve, but the system complexity and data processing requirements increase
Solution Approach 1:
The system performs preliminary actions by pre-defining query templates with identifier tags before authentication occurs. These templates specify exactly what data to request from third-party servers, allowing the complex data gathering process to be standardized and simplified during actual authentication events
Solution Approach 2:
The patent changes the parameters of authentication by introducing weighted activity values and confidence thresholds. Instead of simple binary authentication decisions, the system uses weighted sums of authorization activity data, allowing flexible adjustment of reliability requirements without increasing fundamental system complexity
3Productivity
If multiple third-party servers are queried in parallel, then authentication speed and efficiency improve, but the complexity of managing multiple data sources increases
Solution Approach 1:
Query templates with identifier tags are prepared in advance, defining the exact data structure and format needed from each third-party server. This preliminary preparation eliminates the need for complex real-time data parsing and formatting during parallel authentication queries, thereby improving speed without proportionally increasing complexity
Solution Approach 2:
The query template system provides universality by allowing the same template mechanism to work across multiple different third-party servers. Each server may have different data formats, but the template framework handles all of them uniformly, simplifying the management of multiple data sources through a single standardized approach
Data Source
AI summary
Embodiments of the present invention are directed to methods and systems for utilizing the history of previous authentications and authorizations related to third party computers, as factors in determining whether a current request for accessing a resource should be authorized. A processor server computer, in determining whether to authorize access to the resource, may generate and send a query message to one or more of the third party computers to obtain authorization activity that the third party computers may have regarding a user and/or a device associated with the request. The processor server computer may use the authorization activity from the third party computers in determining whether the request is an authentic request and that the request should be authorized.