Account Security Replication for Seamless Data Platform Failover

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional data platforms require manual management of account security configurations across multiple deployments, leading to inefficiencies and disruptions during failover scenarios, necessitating manual re-configuration and re-authentication by end users.

Innovation Solution

An approach for automatically replicating security configurations from a primary account to a secondary account, including identity management, authorization, and authentication configurations, ensuring seamless failover without manual intervention.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual management of account security configurations is used across multiple deployments, then administrative control and customization are maintained, but operational efficiency decreases and failover disruptions occur

Engineering Contradiction:

Improveoperational efficiencyVSAvoidmanual re-configuration burden

Core Design Contradiction:

ProductivityVSEase of operation

Solution Approach 1:

The patent automatically copies security configurations from a primary account to a secondary account during replication. The system captures security configuration data including identity management settings, authorization policies, and authentication methods from the primary account and replicates them to the secondary account, eliminating manual re-configuration efforts and improving operational efficiency during failover scenarios

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The patent performs preliminary replication of security configurations before failover is needed. By maintaining updated copies of security configurations in advance in the secondary account, the system ensures that when failover occurs, users can seamlessly connect to the secondary account without manual re-configuration, thus improving ease of operation

Inventive Principle:

Principle #10Preliminary action

2Reliability

If security configurations are manually re-configured during failover, then security accuracy is maintained, but time loss and operational disruption increase

Engineering Contradiction:

Improvesecurity configuration accuracyVSAvoidfailover time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system automatically copies validated security configurations from the primary account to the secondary account, maintaining security configuration accuracy without requiring manual verification. This automated copying process preserves the integrity and accuracy of security settings while eliminating the time loss associated with manual re-configuration during failover

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The patent performs preliminary replication of security configurations before failover is needed, ensuring that accurate security settings are already in place in the secondary account. This advance preparation maintains security reliability while reducing failover time to minimal levels

Inventive Principle:

Principle #10Preliminary action

3Ease of operation

If automatic replication of security configurations is implemented, then failover seamless is achieved, but system complexity increases

Engineering Contradiction:

Improvefailover seamlessVSAvoidreplication system complexity

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The patent implements automatic copying of security configurations through a structured replication process that captures configuration data from the primary account and replicates it to the secondary account. This automated approach achieves seamless failover by eliminating manual intervention, with the system handling the complexity of configuration replication internally

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The replication system is designed to handle multiple types of security configurations universally, including identity management settings, authorization policies, and authentication methods. This multi-functional replication capability achieves seamless failover across different security configuration types while managing system complexity through a unified replication framework

Inventive Principle:

Principle #6Universality (Multi-functionality)

4Reliability

If comprehensive security configurations are replicated, then security coverage is improved, but data synchronization overhead increases

Engineering Contradiction:

Improvesecurity coverageVSAvoidsynchronization overhead

Core Design Contradiction:

ReliabilityVSLoss of energy

Solution Approach 1:

The patent copies comprehensive security configurations including identity management settings, authorization policies, and authentication methods from the primary to secondary account. This comprehensive copying improves security coverage by ensuring all security aspects are replicated, while the automated process manages synchronization overhead efficiently

Inventive Principle:

Principle #26Copying

Data Source

PatentUS12608491B2Account replication including security configurations

Publication Date: 2026.04.21 SNOWFLAKE INC

AI summary

A request to replicate a first account maintained by a data platform is received. Based on the request, account data associated with the account is accessed. The account data comprises security configurations for the first account. In response to the request, the first account is replicated using the account data. A second account results from replicating the first account. The replicating of the first account comprises automatically replicating the security configurations for the first account to the second account. The replicating of the security configurations comprises replicating an identity management configuration of the first account; replicating an authorization configuration of the first account; and replicating an authentication configuration of the first account.