Encrypted Session Tickets for Automated Backup Authentication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional client/server authentication mechanisms, such as username/passwords, are not conducive to automated workflow processes, particularly in scenarios like backup and recovery operations, where secure access to resources is required without storing user credentials.

Innovation Solution

The system generates an encrypted ticket containing the necessary privileges for a client to access resources, which is transmitted to the client, encoded with additional attributes, and then evaluated by the server to determine permission, ensuring secure access without requiring stored credentials, and maintaining backwards compatibility with legacy systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If traditional username/password authentication is used, then client/server authentication can be established, but it is not conducive to automated workflow processes and requires storing user credentials

Engineering Contradiction:
Improveautomated workflow processesVSAvoidauthentication mechanism complexity
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The patent extracts the authentication credentials from the traditional username/password model and replaces them with encrypted tickets. The ticket contains encoded user attributes and privileges that can be automatically processed without human intervention, enabling automated workflows while eliminating the need to store sensitive credential information in plaintext.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces an encrypted ticket as an intermediary between the client and server authentication processes. Instead of directly exchanging usernames and passwords, the system uses tickets that mediate the authentication process, allowing automated workflows to proceed securely without exposing sensitive credential information.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If user credentials are stored for authentication, then authentication can be performed, but security is compromised and automated workflows become more complex

Engineering Contradiction:
Improveauthentication securityVSAvoidautomated workflow capability
Core Design Contradiction:
ReliabilityVSExtent of automation

Solution Approach 1:

The patent employs disposable encrypted tickets that have limited validity periods and are single-use or limited-use authentication mechanisms. These tickets replace long-lived stored credentials with short-lived, expendable authentication tokens that enhance security while being easily generated and validated in automated workflows.

Inventive Principle:
Principle #27Cheap short-living objects (Disposable)

3Reliability

If encrypted tickets are implemented, then secure access without stored credentials is achieved, but compatibility with legacy systems must be maintained

Engineering Contradiction:
Improveaccess securityVSAvoidlegacy system compatibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent designs the encrypted ticket system to serve multiple functions: it provides secure authentication for modern systems while maintaining compatibility with legacy systems through appropriate encoding and validation mechanisms. The ticket structure is designed to be universally applicable across different system architectures and time periods.

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

Data Source

PatentUS9442808B1Session tickets for a backup and recovery system
Publication Date: 2016.09.13 EMC IP HLDG CO LLC
  • US9442808B1 patent drawing
  • US9442808B1 patent drawing
  • US9442808B1 patent drawing

AI summary

A ticket request is transmitted from an execution engine to an authentication engine. In response, a ticket comprising privileges is received from the authentication engine. The ticket is transmitted to a client, and a service request including the ticket is received back from the client. A service is executed in response to the ticket received from the client and results are transmitted to the client.