Cross-Environment Token Validation via OAuth 2

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In cloud computing environments, user authentication across multiple environments is inefficient due to the need for multiple username/password entries, as authentication tokens from one environment cannot be used in another, leading to unnecessary authentication processes and token management challenges.

Innovation Solution

Implementing the oAuth 2 protocol to abstract token refreshing and allowing users to authenticate as API users or specific users, with just-in-time token refreshes and storage in an authentication database, optimizing token usage and management across environments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If traditional authentication methods are used in cloud computing environments, then users can access multiple environments, but users must perform multiple username/password entries and cannot reuse authentication tokens across environments, leading to inefficient authentication processes

Engineering Contradiction:
Improveauthentication processVSAvoidauthentication time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent implements a universal authentication token system where a single authentication token obtained in one environment can be reused across multiple environments. The authentication service generates tokens that are valid across environment boundaries, allowing users to authenticate once and access multiple environments without repeated username/password entries, thereby improving ease of operation and reducing authentication time

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Reliability

If authentication tokens are managed separately for each environment, then security is maintained, but token management becomes complex and requires multiple token refreshes

Engineering Contradiction:
Improveauthentication securityVSAvoidtoken management system
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges token management across multiple environments by implementing a centralized authentication service that handles token generation, validation, and refresh operations. Instead of managing separate tokens for each environment, the system consolidates token management into a single unified process, reducing complexity while maintaining security through centralized control and validation mechanisms

Inventive Principle:
Principle #5Merging (Combining)

3Productivity

If users authenticate separately in each environment, then environment-specific security policies are enforced, but the authentication process becomes repetitive and inefficient

Engineering Contradiction:
Improveuser efficiencyVSAvoidauthentication process
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The patent implements preliminary authentication where users authenticate once in a first environment and obtain an authentication token that is then valid for subsequent access to other environments. This preliminary authentication action eliminates the need for repeated username/password entries in subsequent environments, significantly improving user efficiency and ease of operation while maintaining security through token-based validation

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10681039B2User authentication across multiple environments
Publication Date: 2020.06.09 SALESFORCE INC
  • US10681039B2 patent drawing
  • US10681039B2 patent drawing
  • US10681039B2 patent drawing

AI summary

System and methods are described for authenticating users across multiple environments within a cloud-computing environment. A system may receive an indication that a user authenticated within a first environment has performed an action specific to a second environment. The system determines whether a previous action was performed by the user specific to the second environment. In response to determining that no previous action was performed, the system retrieves a first token from an authentication database, wherein the first token is associated with authentication of the user within the first environment. The system then validates the first token, and then generates a second token associated with authentication of the user within the second environment.