Proxy Server Authentication Context Separation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current authentication solutions for client-server and server-server communication often result in high traffic loads and security risks due to the dependency on traditional server-to-server authentication models, which also dictate client-to-server authentication models, leading to inefficient load balancing and potential security vulnerabilities.

Innovation Solution

Implementing a proxy server that separates authentication protocols and contexts for client-server and server-server communication by determining and using different authentication protocols for each domain, thereby reducing the load on application servers and authentication servers, and enhancing security by independently managing authentication contexts.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If traditional server-to-server authentication models are used for client-to-server authentication, then authentication can be performed using existing protocols, but traffic load on authentication servers and application servers increases significantly

Engineering Contradiction:
Improveauthentication protocol compatibilityVSAvoidtraffic load on servers
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent segments the authentication process into two distinct contexts: server-to-server authentication and client-to-server authentication. Each context uses its own authentication protocol and flow, preventing client authentication traffic from burdening the server-to-server authentication infrastructure. The authentication server maintains separate authentication contexts for different communication domains.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary authentication context mechanism that mediates between client applications and application servers. Instead of direct server-to-server authentication flows for client requests, the system uses an authentication context that is verified by application servers without requiring full authentication server involvement for each client request, thereby reducing traffic load.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If traditional server-to-server authentication models are used for client-to-server authentication, then authentication can be performed using existing protocols, but security risks increase when client applications are not secured

Engineering Contradiction:
Improveauthentication protocol compatibilityVSAvoidsystem security
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments authentication into separate contexts for server-to-server communication and client-to-server communication. This segmentation allows client authentication to use appropriate security measures tailored to client applications, while server-to-server authentication maintains its own security model. The authentication server creates distinct authentication contexts that can be verified without exposing sensitive server-to-server credentials to potentially insecure client applications.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The authentication context acts as an intermediary security mechanism that protects the underlying server-to-server authentication infrastructure. Instead of allowing client applications to directly use server-to-server authentication credentials (which would be insecure), the system issues authentication contexts that can be verified by application servers without revealing sensitive credentials, thus maintaining security while enabling client access.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If traditional server-to-server authentication models are used for client-to-server authentication, then authentication can be performed using existing protocols, but authentication servers and application servers experience high traffic loads

Engineering Contradiction:
Improveauthentication protocol compatibilityVSAvoidserver processing efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent segments the authentication workload by creating separate authentication contexts for different communication domains. Client-to-server authentication requests use a simplified verification process that does not require full authentication server involvement for each request, reducing the processing burden on authentication servers and improving overall system productivity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The authentication context serves as an intermediary that reduces server processing load. Instead of requiring authentication servers to process every client request through full authentication flows, the system issues authentication contexts that can be efficiently verified by application servers, significantly reducing authentication server traffic and improving processing efficiency across the system.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP2537315B1Method and apparatus for providing an authentication context-based session
Publication Date: 2018.04.11 NOKIA TECHNOLOGIES OY
  • EP2537315B1 patent drawingFigure 1
  • EP2537315B1 patent drawingFigure 2
  • EP2537315B1 patent drawingFigure 3

AI summary

An approach is provided for providing separation of authentication protocols and/or authentication contexts for client-server and server-server communication in network communication. A proxy server receives a request to initiate a service session. The request includes a first authentication context. The proxy server request verification of the first authentication context from an authentication server and validates the first authentication context based, at least in part, on the verification. The proxy server implements a second authentication context based, at least in part, on the verification of the first authentication context to initiate the service session.