Proxy Credential Injection for Automated Data Aggregation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data collection techniques face challenges such as user unwillingness to share credentials, high costs for secure storage, and limitations from Multi-Factor Authentication and Denial of Service prevention measures, which hinder automated data collection from various data sources.

Innovation Solution

The method involves using a proxy application on a user device to inject user credentials into request data without storing them, allowing an aggregation system to collect data from remote data sources using push notifications and encryption, thereby avoiding credential storage and enabling automated data collection from sources with MFA and DoS prevention measures.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If user credentials are obtained and stored by the data collector for automated data collection, then automation capability is improved, but security cost and storage cost increase significantly

Engineering Contradiction:
Improveautomation capabilityVSAvoidstorage cost
Core Design Contradiction:
Extent of automationVSQuantity of substance

Solution Approach 1:

The patent extracts the credential storage function from the data collector system entirely. Instead of storing credentials centrally, the system uses a distributed approach where credentials remain stored only on user devices. The data collector retrieves credentials temporarily during automated data collection operations and then discards them, eliminating the need for credential storage infrastructure and associated costs.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces an intermediary mechanism where the user device acts as a mediator between the data collector and the credential storage. The user device stores credentials locally and provides them to the data collector temporarily when needed for automated operations, without the data collector ever permanently storing the credentials. This intermediary approach enables automation while avoiding storage costs.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Extent of automation

If user credentials are obtained and stored by the data collector, then automated data collection is enabled, but user trust and willingness to share credentials decrease

Engineering Contradiction:
Improveautomated data collectionVSAvoiduser trust
Core Design Contradiction:
Extent of automationVSObject-affected harmful factors

Solution Approach 1:

The patent removes the credential storage responsibility from the data collector, extracting this sensitive function back to the user's own device. This extraction reassures users that their credentials never leave their control permanently, maintaining trust while still enabling automated data collection through temporary credential access.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system implements self-service by allowing users to maintain control of their own credentials on their own devices. Users willingly share credentials temporarily for automated operations because they retain ultimate control and can revoke access at any time. This self-service model builds user trust while enabling automation.

Inventive Principle:
Principle #25Self-service

3Reliability

If credentials are stored securely with enhanced security measures, then security is improved, but operational complexity and cost increase prohibitively

Engineering Contradiction:
ImprovesecurityVSAvoidoperational complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the security burden from the data collector by removing credential storage entirely. The complex security infrastructure needed to protect stored credentials (encryption, access controls, security audits, etc.) becomes unnecessary because credentials are never stored centrally. Security is maintained through temporary access only, dramatically reducing operational complexity.

Inventive Principle:
Principle #2Taking out (Extraction)

4Ease of operation

If manual credential entry is required for each data source, then user control is maintained, but productivity and automation are reduced

Engineering Contradiction:
Improveuser controlVSAvoiddata collection efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent implements preliminary action by having users enter their credentials once and store them on their own devices. The system then automatically retrieves and uses these stored credentials for subsequent data collection operations without requiring repeated manual entry. This preliminary setup enables both user control and high productivity through automation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Users perform the credential entry action once and the system serves itself automatically for all subsequent operations. The automated data collection process independently retrieves and uses stored credentials without requiring ongoing user intervention, maintaining user control through the initial setup while achieving high productivity through self-service automation.

Inventive Principle:
Principle #25Self-service

Data Source

PatentEP3871396B1Data aggregation applying credentials from proxy entries
Publication Date: 2024.12.18 INTUIT INC
  • EP3871396B1 patent drawingFigure 1
  • EP3871396B1 patent drawingFigure 2
  • EP3871396B1 patent drawingFigure 3

AI summary

Certain aspects of the present disclosure provide techniques for entering user credentials through a proxy. One example method generally includes receiving, at a user device, a push request for user data from a cloud server and receiving a request file from an aggregation system. The method further includes injecting user credentials stored on the user device into the request file, wherein when injected the user credentials replace at least one dummy entry of the request file, and transmitting the request file to a data source associated with the request file. The method further includes receiving user data from the data source and transmitting the user data to the aggregation system.