HTTP Authentication Optimization via Stored Credential Cookies

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

HTTP header-based authentication introduces latency and processing overhead due to frequent 401/407 challenges, which require additional round trips between the client and server for credential verification.

Innovation Solution

An application management computing device optimizes authentication by checking for stored user network identification information; if available, it uses this information to complete authentication, reducing the need for multiple challenges by utilizing a stored cookie with current authentication details.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If HTTP 401/407 challenge is sent for each new TCP connection, then authentication security is maintained, but latency and round trip time increase

Engineering Contradiction:
Improveauthentication securityVSAvoidlatency and round trip time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary authentication by storing user network identification information (cookies) during the initial login process. This stored information is then reused for subsequent requests, eliminating the need to repeat the full authentication challenge-response cycle and reducing latency while maintaining security.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates a copy of the authentication credentials in the form of a cookie that is stored on the client device. This copy allows the client to present proof of authentication without requiring the server to re-verify credentials, thus reducing round trip time while maintaining authentication integrity.

Inventive Principle:
Principle #26Copying

2Reliability

If server verifies credentials for each request, then authentication reliability is ensured, but processing overhead on server increases

Engineering Contradiction:
Improveauthentication reliabilityVSAvoidserver processing capacity
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system extracts the credential verification step from every request processing cycle. Instead of verifying full credentials on each request, the server only validates the previously issued cookie, which is a much simpler operation. This extraction significantly reduces server processing overhead while maintaining authentication reliability.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The authentication system transitions to a self-service model where the client device maintains its own authentication state through stored cookies. The server only needs to validate these self-generated proofs rather than actively managing credential verification for every interaction, thereby reducing processing overhead.

Inventive Principle:
Principle #25Self-service

3Reliability

If multiple 401/407 challenges are exchanged, then authentication completeness is achieved, but number of round trips increases

Engineering Contradiction:
Improveauthentication completenessVSAvoidnumber of round trips
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The complete authentication exchange is performed preliminarily during the initial login sequence, with the result (cookie) being stored for future use. This preliminary completion of authentication eliminates the need for repeated challenge-response round trips, reducing the number of exchanges while ensuring authentication completeness through the stored proof.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9172753B1Methods for optimizing HTTP header based authentication and devices thereof
Publication Date: 2015.10.27 F5 NETWORKS INC
  • US9172753B1 patent drawing
  • US9172753B1 patent drawing
  • US9172753B1 patent drawing

AI summary

A method, non-transitory computer readable medium and application management computing device includes receiving at an application management computing device a request from a client computing device which requires authentication. A determination is made by the application management computing device whether user network identification information currently is stored for the requesting client computing device. The stored user network identification information for the authentication is obtained by the application management computing device when the user network identification information is determined to be currently stored for the requesting client computing device. The authentication is completed by the application management computing device with the obtained user network identification information.