OTP Authentication Key Management via Server-Side Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing user authentication methods, particularly those involving OTP devices, are cumbersome and insecure, requiring multiple devices for different financial institutions and are vulnerable to hacking and password management issues.
Innovation Solution
A user authentication method that generates and manages a common authentication key using a private password and a mechanical unique key, combined with a certificate authority's unique key, to perform secure authentication without storing passwords, enhancing security through multi-element linked to time-based calculations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple OTP devices are used for different financial institutions, then authentication coverage is improved, but device complexity and user burden increase
Solution Approach 1:
The patent implements a universal authentication system where a single OTP device can be used across multiple financial institutions. The server stores multiple unique keys corresponding to different financial institutions, allowing the same OTP device to generate authentication codes for various institutions without requiring users to carry multiple devices.
Solution Approach 2:
The patent combines multiple authentication functions into a single OTP device. Instead of requiring separate devices for each financial institution, the system merges the authentication capabilities by storing multiple institution-specific keys on the server side, allowing one device to serve multiple purposes.
2Reliability
If password management is implemented by the server, then authentication security is improved, but user convenience deteriorates due to regular password changes
Solution Approach 1:
The patent extracts the password management burden from the user by implementing a system where the server handles all authentication key management. Users simply use their OTP device without needing to remember, change, or manage passwords, as the server automatically manages the unique keys and authentication process.
Solution Approach 2:
The system implements self-service authentication where the OTP device automatically generates authentication codes based on stored unique keys. The server automatically manages key storage, retrieval, and rotation without requiring user intervention for password changes or management tasks.
3Reliability
If unique keys are stored on OTP devices, then authentication capability is improved, but security vulnerability increases when devices are lost or keys flow out
Solution Approach 1:
The patent segments the authentication system into two parts: the OTP device stores only a generic authentication algorithm, while the sensitive unique keys are stored separately on the server. This segmentation ensures that even if the OTP device is lost, the attacker cannot authenticate without the server-stored keys, significantly reducing security vulnerability.
Solution Approach 2:
The server acts as an intermediary that holds the sensitive unique keys. Instead of storing keys directly in the OTP device, the system uses the server as a secure intermediary that manages key distribution and validation, reducing the security risk associated with device loss or key exposure.
4Reliability
If financial institutions issue new OTP devices to all clients after key exposure, then security is restored, but time and expense increase enormously
Solution Approach 1:
Instead of requiring physical reissuance of OTP devices to all clients, the system uses virtual key copying. When security concerns arise, the server can generate new unique keys and distribute them digitally to OTP devices, eliminating the need for physical device reissuance and significantly reducing time and expense.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A user authentication method with enhanced security is provided. The method includes generating a first common authentication key if a user of the user terminal enters a private password and providing the generated first common authentication key to an authentication server, registering the first common authentication key and user information by matching the first common authentication key with the user information, generating a second common authentication key in real time if the user enters the private password, generating a server authentication key, generating first server authentication information by calculating a one time password (OTP) by using the server authentication key as an operation key, generating a user authentication key, generating first user authentication information by calculating an OTP by using the user authentication key as an operation key, and performing user authentication based on whether the first server authentication is identical to the first user authentication.