Multiple Database Access Tokens for Single User Identity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current software testing methods require developers and testers to create and manage multiple user entities with different access rights, leading to inefficiencies in login/logout processes and resource authorization, as existing token generation mechanisms only provide a single token per user entity, limiting the ability to simulate various permission sets during development and testing.
Innovation Solution
The method generates multiple temporary user identities with corresponding tokens or maps tokens to existing users with matching permissions, allowing for different access levels and reducing repetitive login/logout actions by using the Dichotomy algorithm to separate resource access from user authorization, thereby accelerating development and testing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a single token is generated per user entity, then the token management is simple, but the ability to simulate various permission sets during development and testing is limited
Solution Approach 1:
The patent segments the permission system by generating multiple distinct tokens for a single user entity, where each token represents a different permission set. This allows the user to simulate different user roles and access levels without creating multiple user entities, thereby resolving the contradiction between adaptability and complexity.
Solution Approach 2:
The patent makes a single user entity universal by enabling it to hold multiple tokens with different permission sets. This multi-functionality allows one user entity to simulate various user roles and access scenarios, improving adaptability while avoiding the need to manage multiple user entities.
2Productivity
If multiple user entities are created with different access rights, then various permission sets can be simulated, but the login/logout processes and resource authorization become inefficient
Solution Approach 1:
The patent merges the functionality of multiple user entities into a single user entity by allowing one user to hold multiple tokens with different permission sets. This eliminates the need to create and manage multiple user entities for testing different access rights, thereby reducing login/logout operations and improving testing efficiency.
Solution Approach 2:
The system performs preliminary action by pre-generating multiple tokens with different permission sets and assigning them to a user entity before testing begins. This allows the user to immediately switch between different permission scenarios without performing repeated login/logout actions, saving time during the testing process.
3Adaptability or versatility
If multiple user entities are managed, then different access rights can be tested, but system resource consumption increases
Solution Approach 1:
The patent creates virtual copies of permission sets through multiple tokens assigned to a single user entity, rather than creating actual multiple user entities. This copying approach maintains the adaptability to test different access rights while minimizing system resource consumption by reusing the same user entity infrastructure.
Data Source
AI summary
A computer-implemented method for use with a database computer system including a database data set that includes machine readable data in the form of a plurality of records, the computer-implemented method comprising: (i) defining a plurality of sets of permission rule(s); (ii) receiving a first user profile for a first user; (iii) establishing a plurality of user identities to the first user; (iv) generating a plurality of tokens; and (v) for each given user identity of the first user, adding a given token of the plurality of tokens to the first user profile and associating the given user identity and the given token.