Machine-Readable Code Authentication Token Transfer
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Users face inconvenience and increased processing resource consumption due to the need to repeatedly input credentials and generate one-time codes for authentication across multiple devices, limiting the number of devices used to access services and wasting resources.
Innovation Solution
A system where a first device generates and sends a machine-readable code with an authentication token to a second device, allowing it to access services without re-entering credentials, by capturing and authenticating the token, thus reducing the need for repeated authentication and resource consumption.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If users input credentials and generate one-time codes for authentication on each device, then service security is maintained, but user convenience deteriorates and processing resource consumption increases
Solution Approach 1:
The system performs preliminary authentication on a first device and stores the authentication result. When the same user accesses from a second device, the pre-stored authentication result is retrieved and applied, eliminating the need to repeat the authentication process. This preliminary action resolves the contradiction by maintaining security while significantly improving convenience and reducing resource consumption.
Solution Approach 2:
The authentication result obtained from the first device is copied and transferred to the second device through machine-readable code. Instead of re-authenticating, the system creates a copy of the valid authentication state, allowing the user to access services on multiple devices without repeating the authentication process, thus improving ease of operation while reducing processing resource consumption.
2Adaptability or versatility
If users manually input credentials on multiple devices, then service access is granted, but time consumption increases
Solution Approach 1:
The system performs authentication preliminarily on the first device and stores the result. When accessing from a second device, the pre-stored authentication result is quickly retrieved and applied, reducing authentication time from minutes to seconds while maintaining multi-device access capability.
Solution Approach 2:
The authentication result is copied from the first device to the second device via machine-readable code transfer. This copying mechanism enables rapid multi-device access without requiring users to re-input credentials, significantly reducing time loss while maintaining adaptability across multiple devices.
3Adaptability or versatility
If the system requires credential re-entry for each device, then security is maintained, but the number of devices that can be used is limited
Solution Approach 1:
The authentication result obtained from one device is made universal and applicable to multiple other devices. Through the machine-readable code transfer mechanism, a single authentication action creates a universally valid credential that can be used across multiple devices, increasing the number of accessible devices without compromising security.
Solution Approach 2:
The authentication result is copied from the source device to multiple target devices through machine-readable code. This copying approach allows the same authenticated identity to access services on multiple devices without requiring separate authentication processes, thereby increasing device adaptability while simplifying the authentication process complexity.
Data Source
AI summary
According to examples, an apparatus may include a processor that may receive a request from a first device for an authentication token for access to a service, determine whether the first device is authorized to receive the authentication token for access to the service, and based on a determination that the first device is authorized to receive the authentication token for access to the service, generate a machine-readable code including the authentication token that a second device is to use for access to the service by the second device. The processor may also send the generated machine-readable code to the first device. The first device may display the machine-readable code and the second device may use a captured image of the machine-readable code to establish an authenticated session to the service on the second device.