Authentication Broker for Multi-Server Security
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional authentication systems fail to share information about failed login attempts across multiple authentication servers, which can lead to security vulnerabilities and inability to effectively identify high-risk transactions, such as fraud attempts, due to lack of knowledge about previous failed requests from the same client machine.
Innovation Solution
An authentication broker is used to communicate information from a first authentication server to a second authentication server, allowing both servers to perform their respective authentications regardless of the success or failure of the first authentication, and sending a unified rejection message to the application server without specifying which authentication failed, thus enhancing security and robustness.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If supplemental authentication is performed only after successful first authentication, then authentication flow is simplified, but security is weakened because failed attempts from same client machine are not shared between authentication servers
Solution Approach 1:
An authentication broker is introduced as an intermediary component that receives authentication requests from the application server, coordinates with multiple authentication servers, and manages the authentication flow. The broker shares client machine knowledge between authentication servers without requiring direct complex interactions between them, thus improving security while maintaining manageable system architecture.
Solution Approach 2:
The authentication broker performs preliminary actions by collecting and storing client machine identification information and authentication history before the actual authentication decision is made. This preliminary data gathering enables subsequent authentication servers to make informed security decisions without adding complexity to their core authentication functions.
2Reliability
If authentication servers operate independently without sharing failed attempt information, then system complexity is reduced, but ability to identify high-risk transactions is compromised
Solution Approach 1:
The authentication broker implements feedback mechanisms by capturing authentication outcomes (both successful and failed) from authentication servers and using this information to update client machine profiles. This feedback loop enables authentication servers to identify high-risk transactions by analyzing patterns of failed attempts across multiple servers without requiring direct information sharing between them.
3Ease of operation
If the system indicates which authentication failed to the user, then user feedback is improved, but security is weakened because fraudsters can exploit this knowledge to evade authentication
Solution Approach 1:
The system converts the potentially harmful information about which authentication failed into a beneficial security feature by implementing uniform rejection messaging. Instead of revealing which authentication server rejected the user, the system provides consistent feedback that prevents fraudsters from exploiting knowledge of authentication failures. This approach maintains user-friendly feedback while enhancing security through information obfuscation.
Data Source
AI summary
A method performed by a computing device is described. The method includes (a) receiving an authentication request from an application server seeking to authenticate a user for access to a service provided by the application server, (b) communicating with a first authentication server to obtain a first authentication of the user, (c) communicating with a second authentication server to obtain a second authentication of the user, the second authentication server being distinct from the first authentication server and the second authentication being of a type distinct from the first authentication, (d) rejecting the authentication request if and only if one or both of the first authentication and the second authentication is negative, and (e) upon rejecting the authentication request, sending a rejection message to the application server without informing the application server whether the first authentication or the second authentication was negative.