Secure Authentication via Service-Specific Tokens

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional authentication approaches in computing environments are either insecure due to reliance on single credentials for multiple services, inconvenient for users due to multiple login requirements, or limited in functionality and security due to token-based systems that prevent access to external resources.

Innovation Solution

A secure authentication process that generates unique secure information associated with a user, excluding their credentials, to establish a chain of authentication through intermediary services, ensuring each service in the chain uses unique authentication information, preventing credential storage or transmission within the environment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If traditional authentication approaches use single credentials for multiple services, then ease of operation is improved, but security deteriorates

Engineering Contradiction:
Improveease of operationVSAvoidsecurity
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent segments authentication credentials by creating service-specific tokens for each service in the chain. Instead of using a single credential across multiple services, the system generates distinct authentication tokens (first secure information, second secure information, third secure information) that are validated by respective services using unique secret keys, thereby maintaining security while enabling convenient access.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an authentication entity as an intermediary that issues service-specific tokens to users. This intermediary validates user credentials and generates authenticated tokens that users present to various services, eliminating the need for users to directly manage multiple credentials while maintaining strong security through the intermediary's validation process.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If token-based authentication systems are used, then security is improved, but adaptability deteriorates

Engineering Contradiction:
ImprovesecurityVSAvoidadaptability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent creates a universal authentication mechanism that works across multiple services and computing environments. The authentication entity issues tokens that can be used to access any service in the chain, and the chain-of-authentication approach can be applied to various service types (job-execution services, data services, etc.), providing both security and broad adaptability.

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

Solution Approach 2:

The patent implements a dynamic authentication system where tokens are generated on-demand for each service access request. The authentication chain is established dynamically as users navigate through services, with each service validating tokens specific to it. This dynamic approach maintains security while adapting to different service requirements and user access patterns.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS10742619B1Secure authentication for a computing environment
Publication Date: 2020.08.11 SAS INSTITUTE INC
  • US10742619B1 patent drawing
  • US10742619B1 patent drawing
  • US10742619B1 patent drawing

AI summary

In one example, a control node can receive a job request from a client device to perform a job using a computing environment, where the job request includes first secure information and second secure information. The control node can authenticate the user by validating the second secure information using a first secret key. The control node can then obtain access to a job-execution service of a server node within the computing environment using the first secure information. For example, the control node can use the first secure information to obtain third secure information that is specific to the server node, and then transmit the third secure information to the server node. The server node can validate the third secure information and responsively authorize the control node to access the job-execution service. The control node can then initiate execution of the job on the server node on behalf of the user.