Dual Token Authentication Mechanism for Transport Channel Flexibility

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current authentication mechanisms in distributed computing are inefficient as they require re-authentication when switching transport channels, limiting flexibility and performance, and are often tied to specific transport channels, which can lead to increased resource usage and security vulnerabilities.

Innovation Solution

A dual-token authentication mechanism that generates a client token and an endpoint token, allowing multiple transport channels to be used simultaneously while maintaining authentication state, enabling the server to send messages over any available channel without re-authenticating the client endpoint.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If re-authentication is required when switching transport channels, then security is maintained, but system performance deteriorates and flexibility is reduced

Engineering Contradiction:
Improveauthentication securityVSAvoidsystem performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The authentication credentials are segmented into two distinct tokens: a client token that identifies the client process and an endpoint token that identifies the specific endpoint. This segmentation allows the system to verify credentials independently for each token, enabling flexible transport channel switching without requiring complete re-authentication, thus maintaining security while improving performance

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The authentication process performs preliminary actions by generating and storing both client token and endpoint token in advance. These pre-generated tokens are then reused across multiple transport channels, eliminating the need for repeated authentication sequences and reducing system performance overhead while maintaining security验证

Inventive Principle:
Principle #10Preliminary action

2Reliability

If authentication is tied to specific transport channels, then channel-specific security is ensured, but adaptability and versatility are reduced

Engineering Contradiction:
Improvechannel-specific securityVSAvoidtransport channel flexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The dual-token authentication mechanism creates universal credentials that are not bound to any specific transport channel. The client token and endpoint token combination can be used across multiple different transport channels (such as TCP, UDP, or other communication protocols), allowing the same authenticated session to adapt to different channel requirements while maintaining security

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

Solution Approach 2:

The tokens act as intermediaries between the authentication process and the transport channel selection. Instead of directly binding authentication to a specific channel, the tokens serve as channel-agnostic credentials that mediate access across multiple channels, providing both security and flexibility

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If multiple endpoints use separate connections, then authentication independence is maintained, but resource usage increases

Engineering Contradiction:
Improveauthentication independenceVSAvoidresource usage
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

Multiple endpoints associated with the same client process can share the same client token and authenticate using the same endpoint token. This merging of authentication credentials allows multiple endpoints to use fewer separate connections while maintaining authentication independence through the token-based verification mechanism, thereby reducing overall resource usage

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS10110582B2Dual token based authentication and transport mechanism
Publication Date: 2018.10.23 SAP SE
  • US10110582B2 patent drawing
  • US10110582B2 patent drawing
  • US10110582B2 patent drawing

AI summary

A client token is generated for a client process in response to a client token request. An authentication request including the client token is received from a client endpoint associated with the client process. The client endpoint is authenticated, including generating and providing an endpoint token to the client endpoint. A first mapping between the client token and transport channels used for messages received from the client process and a second mapping between the client endpoint and the client token are generated. A first message is received over a first transport channel from the client endpoint, the message including the client token and the endpoint token. A response to the first message is sent to the client endpoint over a second transport channel, without re-authenticating the client endpoint, the second transport channel being different than the first transport channel and being selected based on the first and second mappings.