Database Password Vault Automation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for changing database passwords across multiple sites are inefficient due to manual operations, making them non-scalable for large corporations that require secure and reliable data protection and availability.

Innovation Solution

A system and method that utilize a password change daemon to generate a vault for storing password change status and secrets, allowing automated password changes across primary and standby databases, enabling coordinated password updates between sites.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual operations are used to change passwords across multiple sites, then security control is maintained, but efficiency and scalability deteriorate

Engineering Contradiction:
Improvesecurity controlVSAvoidpassword change efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

A centralized vault server is introduced as an intermediary between primary and standby database systems. The vault stores password secrets and coordinates password changes across multiple sites, enabling automated password updates while maintaining security control through centralized management rather than manual operations at each site.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The password change system enables automated self-service operations where the standby database automatically retrieves and applies password changes from the vault without requiring manual intervention. The system performs password updates autonomously based on coordinated triggers, improving efficiency while maintaining security through automated protocols.

Inventive Principle:
Principle #25Self-service

2Productivity

If automated password change systems are implemented, then efficiency and scalability improve, but system complexity increases

Engineering Contradiction:
Improvepassword change scalabilityVSAvoidsystem architecture complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The password management system is segmented into distinct functional components: a centralized vault server for storing password secrets, primary database systems for initiating changes, and standby database systems for applying changes. This segmentation allows each component to perform its specific function independently, reducing overall system complexity while enabling scalability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The vault server serves multiple functions: storing password secrets, coordinating password changes between primary and standby systems, and providing a centralized management interface. This multi-functionality reduces the need for separate specialized systems, thereby reducing complexity while maintaining scalability.

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

3Reliability

If passwords are changed periodically for security, then security is improved, but operational overhead increases

Engineering Contradiction:
ImprovesecurityVSAvoidoperational time for password changes
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Password secrets are pre-stored in the centralized vault before actual password changes are needed. When a password change is triggered, the system quickly retrieves pre-prepared password information from the vault and applies it automatically, eliminating the time-consuming process of generating and distributing new passwords manually across multiple sites.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10523425B2Database password changes
Publication Date: 2019.12.31 SALESFORCE INC
  • US10523425B2 patent drawing
  • US10523425B2 patent drawing
  • US10523425B2 patent drawing

AI summary

Systems and methods for changing database passwords are described. A first server computing system receives an indication to perform a password change process for an administrative account of an associated database. The server generates a vault configured to store a password change status and a password secret associated with the account. The server sets the password change status to a first value to indicate that the server is performing the password change process and then performs the password change process for the account. The server then sets the password change status to a second value to enable a second server computing system to perform a second password change process for a second administrative account of a database associated with the second server system. The database associated with the second server computing system is a standby database of the database associated with the first server system.