One-Way Encrypted Authentication Token for Secure Client-Server Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing client-server authentication protocols are vulnerable to unauthorized access and resource wastage due to decryptable encryption keys, allowing hackers to compromise authentication processes and waste networking and computing resources.
Innovation Solution
Implementing a one-way encrypted authentication token using a one-way hash, which is computationally infeasible to invert, preventing unauthorized decryption and ensuring secure authentication by generating a replica of the token on the server side for verification.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional client-server authentication protocols using decryptable encryption keys are used, then authentication can be performed, but the system becomes vulnerable to unauthorized access and resource wastage
Solution Approach 1:
The patent extracts the decryption vulnerability from the authentication system by removing the ability to decrypt authentication tokens on the client side. Instead of using traditional encryptable/decryptable key pairs, the system uses one-way hash functions that cannot be reversed, thereby extracting the harmful decryption capability while preserving authentication functionality.
Solution Approach 2:
The patent replaces the mechanical encryption/decryption system with a cryptographic hash function system. Traditional symmetric or asymmetric encryption mechanisms that allow decryption are substituted with one-way hash functions that transform data irreversibly, eliminating the decryption vulnerability while maintaining authentication integrity.
2Ease of operation
If encryption keys are stored on the server device for authentication, then authentication can be performed, but the encryption keys can be compromised by hackers who obtain and misuse them
Solution Approach 1:
The patent extracts the harmful key storage and decryption capability from the server system. Instead of storing encryption keys that can be compromised, the server stores only salt values and uses them to generate one-way hash comparisons, removing the vulnerable key element while preserving authentication functionality.
Solution Approach 2:
The patent inverts the traditional authentication approach where the server decrypts and verifies the client's credentials. Instead, the server uses a one-way hash function to transform the stored salt and compares it with the hash of the received authentication token, reversing the verification mechanism to be unidirectional and不可逆.
3Reliability
If hackers obtain encryption keys and decrypt communications, then they can compromise the authentication protocol, but this requires the system to use more secure but complex authentication mechanisms
Solution Approach 1:
The patent replaces complex multi-layer encryption protocols with a simpler one-way hash comparison mechanism. By substituting the traditional encryption/decryption verification process with a unidirectional hash function approach, the system achieves higher security with reduced protocol complexity.
Solution Approach 2:
The patent changes the fundamental parameter of authentication from reversible encryption to irreversible hashing. This parameter change transforms the authentication mechanism from a bidirectional verification process to a unidirectional comparison process, simplifying the protocol while enhancing security against key compromise.
Data Source
AI summary
A client application component of a device may provide a request to an authentication component of the device for an authentication token, in order to authenticate an application with a server. The authentication component may generate the authentication token to be one-way encrypted, based on a server token and a data string associated with security information corresponding to the application, and device information that identifies the device. The client application component may receive the authentication token from the authentication component. The client application component may generate, based on the authentication token, a client token and transmit the client token to the server to authenticate the client application.