Authorization Code Delivery for Persistent Account Connections
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing authentication techniques for accessing user accounts, such as usernames and passwords, are susceptible to fraud and require frequent re-authentication, causing disturbances and security risks.
Innovation Solution
A system that establishes a persistent data connection using a generated authorization code transmitted to the user's contact information, eliminating the need for traditional authentication methods and ensuring secure access to user accounts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional username and password authentication is used, then users can access their accounts, but the system becomes susceptible to fraud and data breaches
Solution Approach 1:
The patent extracts the authentication credential from the traditional username/password format and replaces it with a biometric verification process. The system obtains biometric data from the user, compares it against stored templates, and uses the result to authorize access. This extraction eliminates the vulnerable credential storage mechanism while maintaining access functionality.
Solution Approach 2:
The patent substitutes the mechanical authentication system (username/password entry and verification) with a biometric-based system. Instead of relying on memorized credentials that can be stolen, the system uses physical or behavioral characteristics (fingerprints, facial recognition, voice patterns) that are inherently harder to compromise, thereby reducing fraud risk while maintaining access reliability.
2Reliability
If re-authentication is required after a short period, then security is maintained, but user convenience is reduced and disturbance increases
Solution Approach 1:
The patent implements dynamic authentication behavior where the system adapts its security requirements based on the situation. Instead of forcing periodic re-authentication, the system uses biometric verification at the point of access and can maintain persistent sessions when the biometric verification succeeds. This dynamic approach allows the system to maintain security through intelligent decision-making rather than rigid time-based rules, thereby improving user convenience while preserving security.
3Ease of operation
If username and password are stored in a repository, then authentication can be performed, but the system becomes vulnerable to data breaches
Solution Approach 1:
The patent extracts the authentication mechanism away from centralized credential repositories. Instead of storing usernames and passwords that could be stolen in a database breach, the system uses biometric templates that are either stored locally on devices or encrypted in a way that prevents extraction of usable credentials. This extraction eliminates the vulnerable centralized credential storage while maintaining the ability to perform authentication.
Solution Approach 2:
The patent introduces biometric verification as an intermediary between the user and the authentication system. Rather than directly storing and verifying passwords, the system uses biometric templates as an intermediary that can be verified without exposing the actual credentials. This intermediary layer protects against data breaches by ensuring that even if stored data is compromised, the actual authentication credentials remain secure.
Data Source
AI summary
Disclosed herein are system, method, and computer program product embodiments for establishing a persistent data connection between an end-user application and an institution, comprising: receiving a request to access an account at the institution associated with the user; obtaining information identifying the user; locating the account associated with the user based on the information identifying the user; retrieving, from the institution, contact information linked to the account associated with the user; generating an authorization code associated with the request to access the account; transmitting the authorization code using the contact information linked to the account associated with the user; prompting the user for the authorization code; and in response to receiving the authorization code from the user, approving the request to access the account.