Authentication Token Remote Data Fetching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional authentication tokens, such as smart cards, have limited memory and processing power, which restricts their functionality in modern communication environments, and existing methods like biometric data authentication may not be sufficient for secure and trustworthy identification in electronic communication systems.
Innovation Solution
The solution involves a method and apparatus that utilize a Trusted Platform Module (TPM) or a smart card with control circuitry, memory, and input/output circuitry, which can communicate with a client device to perform authentication by storing and managing cryptographic keys and certificates, and can optionally use a driver software to fetch and decrypt data from a remote server for authentication, extending the capabilities beyond the token's limitations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If conventional authentication tokens (smart cards) are used, then portability and basic authentication are achieved, but memory capacity and processing power are insufficient for modern communication environments
Solution Approach 1:
The authentication system is divided into two parts: a lightweight token for portability and a remote server for data storage. The token contains only essential authentication objects (certificates, keys) while additional authentication data is stored remotely and fetched when needed, separating the portable component from the data storage component.
Solution Approach 2:
The solution extends from a single-dimension token to a multi-dimensional system by adding a remote storage dimension. Authentication objects are no longer confined to the token's internal memory but can be retrieved from an external remote server, effectively increasing the available storage capacity without increasing token physical size.
2Adaptability or versatility
If more authentication data is stored locally in the token, then authentication capability is improved, but the token's limited memory and processing power become insufficient
Solution Approach 1:
Authentication objects are pre-configured in the token during manufacturing or initial setup. The token is prepared with the necessary software and basic authentication data before deployment, enabling it to independently retrieve and use authentication objects from the remote server without requiring complex processing or additional local storage.
Solution Approach 2:
A remote server acts as an intermediary between the token and the authentication system. The server stores additional authentication objects and provides them to the token when needed, mediating between the token's limited storage and the requirement for comprehensive authentication capability.
3Quantity of substance
If authentication data is fetched from remote storage, then token storage limitations are overcome, but additional communication and processing steps are required
Solution Approach 1:
The token retrieves authentication objects from remote storage in advance of when they are needed for authentication. By pre-fetching and caching authentication data, the system reduces the time required during actual authentication operations, as the token can use locally cached data rather than repeatedly accessing remote storage.
Data Source
AI summary
An authentication method in a device is presented. The solution comprises receiving (400) a request to authenticate a user to an external service; determining (402) that the request requires data not stored in a token operationally connected to the device; controlling transmission (404) of a request regarding the data to a remote storage; controlling reception (406) of encrypted data from the remote storage; providing (408) the data to the token; controlling (410) token to authenticate the user; controlling (412) token to decrypt the data and utilising (414) the data when providing a response to the authentication request to the external service.