Mobile Device Authentication Profile Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In a network environment, users face complexity in accessing data from multiple servers with different authentication codes, and shared mobile devices complicate the management of various authentication protocols for multiple users and servers.
Innovation Solution
A mobile device with an authenticator that stores profiles and tokens, allowing secure registration with servers, generating unique secrets based on device IDs, and synchronizing these secrets for efficient authentication across multiple servers, enabling single-device access to multiple servers with user-specific profiles and applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple authentication protocols are implemented for different servers on a single mobile device, then access to multiple servers is enabled, but device complexity increases
Solution Approach 1:
The authentication system is segmented into separate authentication profiles stored in a secure database. Each profile corresponds to a specific server and contains server-specific authentication credentials. This segmentation allows the system to manage multiple authentication protocols independently without increasing overall system complexity, as each protocol is isolated in its own profile container.
Solution Approach 2:
An intermediary authentication manager component is introduced between the applications and the authentication protocols. This manager automatically selects and switches between different authentication profiles based on the target server, shielding applications from the complexity of multiple protocols. The intermediary handles the protocol selection and credential retrieval, simplifying the interface for both applications and users.
2Adaptability or versatility
If multiple users share a mobile device with different authentication keys, then multi-user access is enabled, but ease of operation decreases
Solution Approach 1:
The authentication system is segmented into separate user profiles stored in a secure database. Each user profile contains authentication credentials specific to that user. This segmentation allows multiple users to share the device while maintaining separate authentication contexts, preventing credential confusion and improving ease of operation for each user.
Solution Approach 2:
The authentication system provides self-service functionality by automatically detecting the current user and selecting the appropriate authentication profile without requiring manual intervention. The system autonomously manages user identification and credential selection, eliminating the need for users to manually switch between different authentication keys or configurations.
3Reliability
If manual credential input is required for each server access, then authentication security is maintained, but loss of time increases
Solution Approach 1:
Authentication credentials are pre-stored in secure profiles within the database before access is needed. When a user needs to access a server, the system retrieves the pre-configured credentials from the appropriate profile, eliminating the need for manual entry. This preliminary preparation of authentication data maintains security through secure storage while significantly reducing authentication time.
Solution Approach 2:
The system implements feedback mechanisms where authentication success or failure is automatically detected and processed. Upon successful authentication, the system establishes a session and provides feedback to the application, enabling seamless access without repeated manual authentication. This feedback loop optimizes the authentication process by learning from previous interactions and streamlining future access operations.
Data Source
AI summary
A mobile device may include an authenticator and a processor. The authenticator may store one or more profiles associated with one or more keys to access one or more servers. The processor may embed one of the keys in data to be communicated to one of the servers to request access from the one of the servers. The authenticator may compare the one or more profiles to a set of parameters based upon at least one of a user's identification information, a selected program to request access, identification information of the one of the servers, identification information of an authentication register, to determine whether to select one of the profiles. If the authenticator selects one of the profiles, the authenticator may generate the one of the keys based on the selected one of the profiles.