Impersonation Token Cross-System User Operation Automation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems require users to manually log into multiple systems for performing operations, especially when these systems do not share a common Identity Provider, leading to cumbersome and inefficient user operation management.

Innovation Solution

A method where a first system logs into a second system using impersonation, obtaining an impersonated user access token to perform operations on behalf of the user, allowing seamless operation without the need for the user to log into each system individually, utilizing an impersonation request and validating tokens for access validation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a user manually logs into multiple systems to perform operations, then the user can access and operate on each system, but the operational efficiency and user experience deteriorate due to cumbersome repeated login processes

Engineering Contradiction:
Improveoperational efficiencyVSAvoiduser operation convenience
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The patent introduces an impersonation token as an intermediary mechanism that allows the first system to represent the user when accessing the second system. Instead of requiring the user to manually log into each system, the first system obtains an impersonation token that enables it to perform operations on behalf of the user on the second system, thereby eliminating repeated manual logins and improving operational efficiency

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If systems share a common Identity Provider for authentication, then the user can log in once and access multiple systems, but the system architecture complexity increases due to reliance on common identity infrastructure

Engineering Contradiction:
Improvesingle login accessVSAvoididentity provider dependency
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent segments the authentication process into two independent parts: the first system maintains its own identity provider for user authentication, while the second system accepts impersonation tokens from the first system. This segmentation eliminates the need for a common identity provider across both systems, reducing architectural complexity while still enabling seamless cross-system access

Inventive Principle:
Principle #1Segmentation

3Extent of automation

If a first system acts as an agent to perform user operations on a second system, then automated operations can be performed, but the trust establishment between systems becomes complex requiring manual authorization setup

Engineering Contradiction:
Improveautomated user operationsVSAvoidtrust establishment process
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The patent implements preliminary action by having the first system proactively obtain an impersonation token from the second system before performing any operations. This token is obtained through an impersonation request that includes the user's access token from the first system. Once obtained, the impersonation token can be reused for multiple operations, eliminating the need for repeated manual authorization setup and enabling automated operations

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12149522B2Performance of user operations by a first system on a second system using user impersonation
Publication Date: 2024.11.19 DELL PROD LP
  • US12149522B2 patent drawing
  • US12149522B2 patent drawing
  • US12149522B2 patent drawing

AI summary

Techniques are provided for performing user operations by a first system on a second system using user impersonation. One method comprises receiving, by a first system, a log in of a user to the first system and an operation to be performed by a second system; sending an impersonation request, by the first system to the second system, to obtain an impersonated user access token of the given user for the second system; receiving, by the first system from the second system, in response to the impersonation request, the impersonated user access token of the given user; and providing, by the first system to the second system, the operation with the impersonated user access token of the given user, wherein the second system performs the operation based at least in part on a result of an access validation of the impersonated user access token of the given user.