Authentication Token for Multi-App Access

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Users face burdensome authentication processes when accessing multiple applications, particularly in mobile device-based transactions, as they need to individually authenticate and verify their identity for each application, which can be time-consuming and inconvenient.

Innovation Solution

A system that uses previously validated authentication credentials to create an authentication token accessible by multiple applications, reducing the need for repeated authentication by leveraging a primary level of user authentication to authenticate non-framework applications, with options to adjust the degree of confidence based on user preferences and authentication types.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If individual authentication is required for each application, then security is improved, but user convenience deteriorates

Engineering Contradiction:

ImprovesecurityVSAvoiduser convenience

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The system performs preliminary authentication through a framework application before the user needs to access other applications. The authentication credentials are validated in advance and stored as an authentication token, so when the user subsequently accesses other applications, the authentication has already been completed, eliminating the need for repeated authentication and improving convenience while maintaining security.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The authentication token created through framework application authentication is designed to be universally accessible by multiple applications. This single authentication credential serves multiple functions across different applications, allowing the user to access various applications without repeating the authentication process, thus resolving the contradiction between security and convenience.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Ease of operation

If authentication credentials are validated for multiple applications, then user burden is reduced, but system complexity increases

Engineering Contradiction:

Improveuser burdenVSAvoidsystem complexity

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The system introduces an intermediary authentication token that mediates between the framework application and other applications. Instead of directly managing complex authentication credentials across multiple applications, the system uses this token as an intermediary layer that simplifies the authentication process for users while managing the complexity internally within the system.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Speed

If authentication token is created based on primary authentication, then authentication speed is improved, but security risk increases

Engineering Contradiction:

Improveauthentication speedVSAvoidsecurity risk

Core Design Contradiction:

SpeedVSReliability

Solution Approach 1:

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS9398000B2Providing authentication using previously-validated authentication credentials

Publication Date: 2016.07.19 BANK OF AMERICA CORP

AI summary

Embodiments of the invention are directed to systems, methods and computer program products for providing authentication using previously-validated authentication credentials. An exemplary apparatus is configured to receive a request to access a framework application, request, from a user, one or more authentication credentials corresponding to a primary level of user authentication, receive and validate the one or more authentication credentials, create, using the framework application, an authentication token based at least partially on the validation of the primary level of user authentication, wherein the authentication token is accessible by a plurality of applications, receive a request, from the user, to access one or more non-framework applications; and authenticate the one or more non-framework applications, where authenticating the non-framework applications requires accessing the authentication token created by the framework application such that the authentication is at least partially based on the primary level of user authentication.