Client Token Authentication Server Intermediary Security
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing security systems face challenges in securely authenticating users and facilitating transactions over communications networks, particularly in preventing attacks like phishing, pharming, and brute force attacks that compromise user data and financial information.
Innovation Solution
A secure authentication and transaction system that utilizes a Client Token connected to an Authentication Server, eliminating the need for users to provide sensitive information directly to websites. This system employs one-way hash functions and MSR encryption to ensure secure transactions and protects against various malicious attacks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If users provide sensitive information directly to websites for authentication and transactions, then the authentication process is simple and direct, but the security risk increases due to potential interception and fraudulent use by hackers
Solution Approach 1:
The patent introduces an authentication server as an intermediary between the user's client token and the website. The client token communicates exclusively with the authentication server, which then communicates with the website. This intermediary architecture ensures that sensitive authentication data never reaches the website directly, eliminating the security vulnerability while maintaining operational simplicity.
2Object-affected harmful factors
If a client token directly connects to an authentication server to send authentication data, then security is improved by preventing data interception, but the device complexity increases
Solution Approach 1:
The system is segmented into distinct functional components: a client token residing on the user's device, an authentication server, and the website. Each component has a specific responsibility - the token stores and transmits authentication data, the server verifies and manages credentials, and the website provides services. This segmentation isolates sensitive operations to the token-server communication channel, enhancing security while keeping each component relatively simple.
3Ease of manufacture
If traditional authentication methods are used where users provide login credentials to websites, then the system is easy to implement, but it becomes vulnerable to phishing and pharming attacks
Solution Approach 1:
The authentication server acts as a trusted intermediary that the client token communicates with exclusively. Since the token contains the authentication server's public key and communicates only with that specific server, phishing and pharming attacks become ineffective - malicious websites cannot intercept authentication data because the token never sends data to them. This approach adds minimal implementation complexity while providing robust protection.
Data Source
AI summary
A secure user authentication system, operable over a client-server communications network to authenticate a system user. The system includes an application server which includes a site which is able to be enabled, and an authentication server, which is able to enable the application server site. The authentication server includes a core database, and receives and stores user authentication-enabling data in the core database. The system further includes a client, and a client program which is able to be actuated in the client. The client program includes the user authentication-enabling data. Upon actuation, the client program automatically directly connects to the authentication server, and sends the client authentication-enabling data to the authentication server, for secure user authentication by the authentication server.