Cross-Application Authentication Credential Reuse

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems face challenges in efficiently authenticating users across multiple applications, particularly in scenarios where authentication credentials from one application are not directly applicable to another, leading to redundant user input and potential security vulnerabilities.

Innovation Solution

A system that utilizes successful authentication credentials from one application to validate and execute actions in another application, leveraging a continuum of authentication levels and application function permissions to streamline the authentication process while ensuring security through database comparisons and threshold validation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If authentication credentials are validated separately for each application, then security validation is thorough, but user authentication time and input redundancy increase

Engineering Contradiction:
Improveauthentication securityVSAvoidauthentication time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary authentication validation in a first application, stores the validation result, and reuses it for subsequent applications. This preliminary action eliminates redundant validation steps while maintaining security, as the authentication credential is validated once and the result is cached for future use across multiple applications.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The authentication validation mechanism is designed to be universal across multiple applications. A single validation result from the first application serves multiple functions by being reused to validate credentials in second and subsequent applications, reducing repetitive validation operations while maintaining consistent security standards.

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

2Ease of operation

If authentication credentials are reused across applications, then user input is reduced, but security vulnerabilities may increase

Engineering Contradiction:
Improveuser input reductionVSAvoidsecurity security
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system performs a thorough security validation in advance during the first authentication operation. This preliminary security check ensures that the credential is validated against security policies before being cached for reuse, preventing security vulnerabilities from propagating across multiple applications.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where validation results from the first application are fed into subsequent validation processes. The cached validation result is reviewed and applied consistently across multiple applications, ensuring that security requirements are maintained while enabling credential reuse.

Inventive Principle:
Principle #23Feedback

3Reliability

If separate validation processes are used for each application, then security is maintained, but system complexity increases

Engineering Contradiction:
Improvesecurity validationVSAvoidvalidation system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system merges separate validation processes into a unified validation framework. Validation logic is consolidated and shared across multiple applications, where a single validation mechanism serves multiple applications. This reduces system complexity by eliminating redundant validation code while maintaining comprehensive security validation through the shared framework.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS9525685B2User authentication based on other applications
Publication Date: 2016.12.20 BANK OF AMERICA CORP
  • US9525685B2 patent drawing
  • US9525685B2 patent drawing
  • US9525685B2 patent drawing

AI summary

The present invention includes a system for authenticating a second action based on a first action, wherein the system is configured to: receive a first request to execute a first action associated with a first application; determine that execution of the first action requires user authentication; request one or more authentication credentials from the user; receive a first authentication credential associated with the first action; validate the first authentication credential, thereby resulting in a successful validation of the received first authentication credential; in response to the successful validation, execute the first action; receive a second request to execute a second action associated with a second application; determine that execution of the second action requires user authentication; use the successful validation of the first authentication credential to validate a second authentication credential so that the second action may be executed.