Pooled Computing Authentication With Dynamic Token Enrollment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The process of repeatedly authenticating with shared computing devices is time-consuming and prone to errors, and existing solutions like operator-specific fobs increase system complexity and resource requirements.
Innovation Solution
A system that dynamically enrolls token identifiers on physical tokens, allowing operators to authenticate without pre-provisioning, reducing the need for repeated authentication data entry and minimizing system complexity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If operators use shared computing devices with pre-provisioned accounts, then authentication can be performed, but the process becomes time-consuming and error-prone due to repeated authentication data entry
Solution Approach 1:
The system performs preliminary actions by pre-generating authentication tokens and storing them in a token pool before operators need them. When an operator needs authentication, they can immediately use a pre-generated token without going through the time-consuming process of entering authentication data repeatedly. This resolves the contradiction by preparing authentication credentials in advance, eliminating both time loss and entry errors.
Solution Approach 2:
The system creates copies of authentication credentials in the form of tokens that can be used multiple times. Instead of requiring operators to repeatedly enter their actual authentication data (username, password), the system generates token copies that serve the same authentication purpose but can be input without error and retrieved quickly from the token pool, thus improving reliability and reducing time.
2Loss of time
If operator-specific authentication devices like fobs are deployed, then authentication speed improves, but system complexity and resource requirements increase
Solution Approach 1:
The system implements a universal token pool that serves all operators and all computing devices within the group. Instead of deploying operator-specific devices like individual fobs for each user, a single shared token pool provides authentication services universally to all operators across multiple devices. This multi-functional approach reduces system complexity while maintaining fast authentication, as the same token pool serves multiple purposes and users without requiring separate infrastructure for each operator.
Solution Approach 2:
The system enables operators to self-service authentication by allowing them to independently retrieve tokens from the pool without requiring administrative provisioning or complex device management. Operators can autonomously obtain authentication credentials when needed, eliminating the need for complex device distribution and management infrastructure that would otherwise be required for operator-specific authentication devices.
3Reliability
If pre-provisioned authentication accounts are used for each device, then access control is maintained, but the complexity of managing authentication data across multiple devices increases
Solution Approach 1:
The system introduces an intermediary token pool that mediates between the authentication server and multiple computing devices. Instead of directly managing authentication data on each device or maintaining complex one-to-one mappings between operators and devices, the token pool serves as an intermediary layer that simplifies access control. Tokens in the pool encapsulate authentication credentials and can be distributed to any device in the group, maintaining security while reducing the complexity of managing authentication data across multiple devices.
Data Source
AI summary
A method includes: storing an account identifier and authentication data associated with the account identifier; receiving, from a client computing device, a token identifier, requesting the authentication data from the client computing device; in response to receiving the authentication data, generating token enrollment data associating the token identifier with the account identifier; and transmitting the token enrollment data for storage in association with the client computing device.


