Native Account Provisioning via Centralized Authentication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The proliferation of user accounts across different websites and services leads to inefficiencies, security risks, and privacy concerns due to manual account creation, password management, and the use of single sign-on services that do not allow access if the user closes their account.

Innovation Solution

A system and method for creating and managing user accounts using an authentication system that determines if a user is registered and authenticated, generating a user account for third-party systems, and transmitting necessary properties to create or log into accounts securely and efficiently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual account creation is used for each website, then users can access multiple services, but users must repeatedly enter personal information and manage multiple passwords which is time-consuming and resource-intensive

Engineering Contradiction:
Improveaccess to multiple servicesVSAvoidtime for account creation and management
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent merges multiple account management functions into a single authentication system. The system consolidates user profiles, credentials, and service access permissions into one centralized platform, allowing users to manage all their service accounts through a unified interface rather than separately managing each account.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The authentication system is designed as a universal platform that can access multiple third-party services. It provides multi-functional capabilities including account creation, login, information management, and service access control, replacing the need for separate account management systems for each service.

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

2Adaptability or versatility

If users manually create accounts on multiple platforms, then they can access various features, but they may use weak or reused passwords which increases security vulnerabilities

Engineering Contradiction:
Improveaccess to website featuresVSAvoidaccount security
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system implements self-service password generation and management capabilities. Users can automatically generate strong, unique passwords for each service through the authentication system, which handles password creation, storage, and management without requiring user intervention in the complex security protocols.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The authentication system acts as an intermediary between users and third-party services. It manages credentials securely on behalf of users, transmitting only necessary authentication information to services while maintaining secure storage and control of sensitive data within the authentication system itself.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If personal information is dispersed across numerous platforms, then users can access various services, but users lose track of where their data is stored and how it is being used which raises privacy concerns

Engineering Contradiction:
Improveservice access capabilityVSAvoiddata location and usage tracking
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The system segments data management into distinct functional areas: profile information storage, credential management, service access permissions, and audit logs. Each third-party service interaction is separated into discrete authorized data transmissions, allowing users to track and control what information is shared with each service independently.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The authentication system provides a universal data management interface that consolidates visibility into all personal information stored across different services. Users can access a centralized view of their data, see where it is stored, control its usage, and manage permissions uniformly across all connected platforms.

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

4Ease of operation

If traditional single sign-on services are used, then account management is simplified, but users cannot access website accounts if they close their single sign-on account

Engineering Contradiction:
Improveaccount management simplicityVSAvoidaccount access availability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system merges the benefits of single sign-on convenience with native account creation. Users can create accounts directly on third-party services while the authentication system maintains a linked profile, providing both the simplicity of centralized management and the reliability of direct service account ownership.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The authentication system serves as an intermediary layer that maintains user profiles and credentials independently of any single service. This allows users to access services through the authentication system even if they close or lose access to individual service accounts, as the authentication system retains the necessary credentials and profile information.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20260032118A1System and method for native user account creation, access, and management
Publication Date: 2026.01.29 SHAVERS CONNOR W
  • US20260032118A1 patent drawing
  • US20260032118A1 patent drawing
  • US20260032118A1 patent drawing

AI summary

A system comprises a processor and a memory. The memory comprises a non-transitory medium storing processor-executable instructions that when executed by the processor, causes the processor to: receive an indication from a user to create a native user account with a third-party system; determine if the user has an account profile registered with an authentication system; register the account profile if not already registered; determine if the user is authenticated with the authentication system; generate a user account for the third-party system with user account properties; and transmit the user account properties to the third-party system to create the native user account. The creation of the native user account may be accomplished without requesting additional input from the user beyond providing the indication.