Multi-Level Authentication for Shared User Accounts
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Software applications lose accountability and access control when multiple entities share the same user account, as they cannot distinguish between the real identities of parties using the account, leading to compromised security and access management.
Innovation Solution
Implementing a multi-level authentication system that requires both a primary and secondary authentication credential for each user account, allowing the service provider application to uniquely identify each party and grant differential access privileges based on their identity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If multiple entities share the same user account for ease of management, then ease of operation is improved, but accountability and access control are compromised
Solution Approach 1:
The authentication credential is segmented into two distinct parts: a shared account identifier (username) that enables easy access, and a unique secret identifier that maintains accountability. This segmentation allows multiple entities to use the same account while preserving individual identity tracking through the unique secret identifier.
Solution Approach 2:
The unique secret identifier acts as an intermediary mechanism between the shared account and the entity using it. This intermediary enables the system to distinguish between different entities accessing the same account, thereby maintaining accountability without compromising the ease of shared access.
2Device complexity
If a single user account is used by multiple parties, then device complexity is reduced, but measurement precision of user identity is lost
Solution Approach 1:
The authentication system is segmented into two components: a shared account identifier for simple account access and a unique secret identifier for precise identity measurement. This segmentation maintains simple account structure while enabling accurate identity distinction through the unique secret identifier.
Solution Approach 2:
The system adds another dimension to authentication by introducing the unique secret identifier alongside the account identifier. This dimensional addition enables precise identity measurement without complicating the basic account structure, as the unique secret identifier operates in a separate authentication dimension.
Data Source
AI summary
Approaches for performing a multiple level authentication on an entity are provided. A primary authentication credential and a secondary authentication credential may be established for a user account. The primary authentication credential uniquely identifies a particular account of the software application. The secondary authentication credential uniquely identifies an entity, such as a user, application, or device, authorized to use the particular user account. Upon receiving a request to access the software application using the particular user account, a determination is made as to whether the request is accompanied by the primary authentication credentials and a secondary authentication credential associated with the particular user account. Upon determining that the request is accompanied by valid primary and secondary authentication credentials for the user account, limited access, based upon the secondary authentication credential, to the software application using the particular user account is granted.