Application-Level Authentication for Low-Overhead Action Execution

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing systems for executing actions in cloud-based architectures face inefficiencies and security vulnerabilities due to reliance on digital certificates and middleware layers, consuming significant computing resources and requiring communication with third-party systems for authentication.

Innovation Solution

Implementing application-level multifactor authentication using client digital certificates and login credentials, validated within the system, to authenticate clients and execute actions without middleware layers, thereby reducing resource consumption and enhancing security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If digital certificate authentication with middleware layer is used, then security is improved, but device complexity and resource consumption increase

Engineering Contradiction:

Improveauthentication securityVSAvoidmiddleware layer complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts and removes the middleware layer from the authentication system, allowing the application server to perform authentication directly. This eliminates the intermediate component while maintaining security through direct validation of digital certificates and session tokens between the load balancer and application server.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The load balancer serves as an intermediary that handles SSL termination and digital certificate validation, replacing the need for a separate middleware authentication layer. It mediates between clients and application servers by validating credentials and managing session tokens directly.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If digital certificate validation with third party systems is performed, then authentication reliability is improved, but processing time increases

Engineering Contradiction:

Improveauthentication reliabilityVSAvoidauthentication processing time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary validation by having the load balancer verify digital certificates and issue session tokens before requests reach application servers. This pre-authentication approach eliminates repeated validation delays during each action execution, as subsequent requests use the pre-validated session tokens.

Inventive Principle:

Principle #10Preliminary action

3Reliability

If middleware layer and third party systems are used for authentication, then security is improved, but computing resource consumption increases

Engineering Contradiction:

Improvesystem securityVSAvoidcomputing resource consumption

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent removes the middleware layer entirely, consolidating authentication functionality into the load balancer and application servers. This extraction eliminates the resource overhead of maintaining and operating a separate middleware authentication system while preserving security through direct certificate validation.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The load balancer performs self-service authentication by validating digital certificates and managing session tokens without external third-party systems. Application servers then use these pre-validated tokens for action execution, eliminating repeated resource-intensive validation processes.

Inventive Principle:

Principle #25Self-service

4Reliability

If traditional data center architecture with middleware is used, then authentication security is maintained, but adaptability to cloud-based architecture decreases

Engineering Contradiction:

Improveauthentication securityVSAvoidcloud-based architecture adaptability

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The load balancer is designed to perform multiple functions including SSL termination, digital certificate validation, session token management, and request routing. This multi-functional approach eliminates the need for architecture-specific middleware layers, making the system adaptable to both traditional data center and cloud-based environments.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS20250392584A1Conserving computing resources via application-level authentication of action execution requests

Publication Date: 2025.12.25 TRUIST BANK

AI summary

A system for conserving computing and memory resources and enhancing security by performing application-level multifactor level authentication of a client requesting execution of an action by the system. A request to execute an action sent by the client and received by an action execution application of the system may include compiled client authentication information. The compiled client authentication information may comprise at least a client digital certificate and client login credentials that are unique to the action execution application. The action execution application can authenticate the client relative to the requested action by validating the received client digital certificate against a stored set of previously validated digital certificates, in addition to validating the received client login credentials against a stored set of previously validated login credentials. In response to authenticating the client, the action execution application may execute the requested action.