User-to-User Authentication Using Contact Data Tokens
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing user authentication methods, including username-password combinations and two-factor authentication, are inadequate in preventing identity fraud and social hacking, as they do not verify user identity beyond initial access to a system.
Innovation Solution
A user-to-user authentication method using contact data-based tokens, such as unique links, codes, or biometric data, is implemented to enhance security by verifying the identity of communicating users during ongoing connections.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If username and password authentication is used, then ease of operation is improved, but reliability deteriorates due to vulnerability to brute force attacks and social hacking
Solution Approach 1:
The authentication process is segmented into multiple independent stages: initial system access authentication (username/password), followed by communication establishment, and then dynamic re-authentication during the communication. This segmentation allows each stage to use appropriate authentication strength without overwhelming the user at once.
Solution Approach 2:
The system performs preliminary authentication actions by establishing baseline security through username/password verification before communication begins. Additionally, the system prepares re-authentication mechanisms in advance that can be activated during communication if suspicious activity is detected or upon user request.
2Reliability
If two-factor authentication is implemented, then reliability is improved, but device complexity increases
Solution Approach 1:
The authentication mechanism transitions from static (username/password only) to dynamic, where additional re-authentication steps are activated on-demand during communication. The system adapts the authentication complexity based on the communication context, user requests, or detected anomalies, rather than requiring high complexity from the outset.
Solution Approach 2:
The authentication system serves multiple functions: initial access control, ongoing communication security verification, and fraud detection. By making the authentication mechanism multi-functional and context-aware, the system avoids the need for permanently complex authentication flows while maintaining high security when needed.
3Reliability
If user-to-user authentication is added during communication, then reliability is improved, but loss of time increases due to additional verification steps
Solution Approach 1:
Instead of continuous authentication throughout communication, the system implements periodic re-authentication at strategically chosen moments. This could be triggered by communication milestones, user requests, or anomaly detection, balancing security verification with minimal disruption to the communication flow.
Solution Approach 2:
The system enables users to self-initiate re-authentication when they suspect compromise or want to verify their communication partner's identity. This user-driven approach allows authentication to occur only when necessary, reducing overall time loss while maintaining security when users are actively engaged.
4Reliability
If biometric authentication is used for re-authentication, then reliability is improved, but ease of operation deteriorates due to additional steps required
Solution Approach 1:
The system applies preliminary anti-action by implementing biometric re-authentication specifically to counteract potential fraud or account compromise. Rather than using biometrics for all authentication scenarios, it selectively deploys this strong counter-measure when fraud risk is present or when users request enhanced verification, neutralizing the threat without imposing biometric requirements in all cases.
Data Source
AI summary
A method for user authentication during a connection between a first user and a second user can include receiving an authentication request from the first user for authenticating the second user, executing an authentication process of the first user, receiving contact data of the second user from the first user, sending a Token to the second user wherein the Token is based on and/or addressed by the contact data, requesting execution of an authentication process of the second user based on the Token, generating a result for the authentication process for the second user and providing the result of the authentication process of the second user to the first user and/or to the second user.