Profile-Based Authentication Module for Account Consent

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing authentication frameworks lack efficiency and usability when granting permission to third-party software applications to access user data, leading to potential security risks and cumbersome user experiences.

Innovation Solution

A computer system and method that includes an authentication module to authenticate credentials, identify associated accounts, and obtain consent for data access, enabling seamless integration with multiple software applications while ensuring security and user control.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If traditional authentication frameworks are used to grant permission to third-party applications, then user data can be accessed by authorized applications, but the process becomes cumbersome and less efficient

Engineering Contradiction:
Improveauthentication efficiencyVSAvoidusability
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The authentication module is designed as a universal component that can serve multiple third-party applications simultaneously. It provides a standardized interface for authentication and authorization that works across different application types, eliminating the need for separate authentication flows for each application and thereby improving efficiency and usability.

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

Solution Approach 2:

The authentication module acts as an intermediary between users and third-party applications. It manages the authentication process centrally, providing a single point of interaction for users regardless of which application they are accessing, thus simplifying the user experience and improving operational ease.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If traditional authentication frameworks are used, then data access can be controlled, but security risks increase due to inefficient authentication processes

Engineering Contradiction:
ImprovesecurityVSAvoidauthentication efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The authentication module implements self-service mechanisms where users can manage their own authentication credentials and authorization preferences without requiring complex manual intervention. The system automatically handles authentication tokens, permission scopes, and session management, reducing security risks associated with manual configuration while maintaining efficient processing.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

By providing a universal authentication module that handles all authentication requests through a standardized secure framework, the system ensures consistent security practices across all third-party applications, eliminating security vulnerabilities that arise from application-specific authentication implementations.

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

3Reliability

If multiple authentication processes are implemented for different applications, then each application can be secured individually, but the overall system complexity increases

Engineering Contradiction:
ImprovesecurityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The authentication module merges multiple application-specific authentication processes into a single unified authentication framework. It consolidates security functions such as credential verification, token management, and permission validation into one centralized module that serves all third-party applications, thereby reducing system complexity while maintaining individual application security through standardized interfaces.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The universal authentication module provides a single secure framework that can authenticate users for any third-party application without requiring separate authentication implementations. This multi-functional approach reduces the number of security protocols that need to be managed individually, simplifying the overall system architecture while preserving security through standardized secure operations.

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

Data Source

PatentUS20250278726A1Systems and methods for executing an authentication module
Publication Date: 2025.09.04 THE TORONTO DOMINION BANK
  • US20250278726A1 patent drawing
  • US20250278726A1 patent drawing
  • US20250278726A1 patent drawing

AI summary

Methods and computer systems for executing an authentication module. Receiving a first request from a first system executing a first software application. In response to receiving the first request, execute an authentication module. Receiving a second request from a second system executing a second software application. In response to receiving the second request, execute the authentication module, wherein executing the authentication module configures the authentication module to authenticate a credential received from the second system as being associated with a particular profile; identify one or more accounts to be used in fulfilling an associated request, the one or more accounts corresponding to the particular profile; and obtain an indication of consent to perform an operation associated with the associated request.