Authentication Service Mediator for Seamless Account Setup
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
There is friction in providing a seamless experience for users to set up accounts across multiple parties, such as financial institutions, due to the lack of integrated methods for digital authentication and data sharing.
Innovation Solution
The system and method for digital authentication as a service involve receiving a Security Assertion Markup Language (SAML) assertion or JSON Web Token (JWT) from an entity website, creating a user profile, generating a username and password, presenting a login page, authenticating the credentials, and returning an authentication status, facilitating seamless integration and data sharing between parties.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If traditional separate account setup methods are used for each financial institution, then each institution can maintain independent customer management, but the user experience becomes fragmented and complex across multiple platforms
Solution Approach 1:
The patent introduces an authentication service as an intermediary between multiple financial institutions and users. This service receives SAML assertions or JWTs from entity websites, creates user profiles, generates credentials, and handles authentication requests. The intermediary consolidates what would otherwise be separate account setup processes into a unified experience, resolving the contradiction by maintaining institutional independence while simplifying user interaction.
Solution Approach 2:
The authentication service performs multiple functions within a single system: receiving customer information, validating customers, creating user profiles, generating credentials, presenting login pages, authenticating users, and returning authentication status. This multi-functionality eliminates the need for separate account setup mechanisms at each institution, improving ease of operation while reducing overall system complexity.
2Adaptability or versatility
If integrated digital authentication methods are implemented across multiple parties, then seamless user experience is achieved, but the system complexity and integration requirements increase
Solution Approach 1:
The authentication service acts as a standardized intermediary that handles integration between multiple financial institutions and users. By providing a uniform interface for receiving SAML assertions and JWTs, creating user profiles, and managing authentication, the system reduces integration complexity while maintaining high adaptability across different institutions.
Solution Approach 2:
The system performs preliminary actions by pre-creating user profiles and generating credentials before actual authentication occurs. Entity websites receive validated customer information and can pre-set up user profiles, which then enable seamless authentication without requiring complex real-time integration decisions, thus reducing overall system complexity.
3Productivity
If customer information is shared between entity websites and authentication servers, then seamless authentication is enabled, but data security and validation requirements increase
Solution Approach 1:
The authentication service performs preliminary validation of customer information received from entity websites before creating user profiles or generating credentials. This advance validation ensures data quality and security are maintained throughout the authentication process, enabling efficient authentication while upholding high reliability standards.
Solution Approach 2:
The system implements feedback mechanisms where the authentication service validates customer information, creates user profiles, and returns authentication status to entity websites. This feedback loop ensures that only validated and secure data is processed, maintaining reliability while enabling efficient cross-platform authentication.
Data Source
AI summary
A method for providing enrollment as a service may include an enrollment as a service computer program: (1) receiving, from an entity website, a SAML assertion or a JSON Web Token comprising a customer identifier and customer information for a validated customer; (2) creating a user profile for the customer identifier and the customer information; (3) creating a username and password for the customer identifier; (4) receiving, from the entity website, an authentication as a service request; (5) presenting a login page at the entity website; (6) receiving, from the login page, the username and password; (7) authenticating the username and password; and (8) returning an authentication status to the entity website.