Secure Private Key Distribution in Web API Clusters
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing private key distribution methods for authorization instances in web API service clusters are vulnerable to attacks, as private signature keys are stored in configuration files that can be compromised, allowing unauthorized access to resources.
Innovation Solution
A private key distribution system where each authorization instance generates host instance key pairs, with a signature key leader instance encrypting and transmitting the private signature key to requesting instances, eliminating the need for configuration files and enhancing security by storing keys in memory and using IP address verification.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If private signature keys are stored in configuration files for authorization instances, then key distribution is simplified, but security is compromised due to vulnerability to attacks
Solution Approach 1:
The patent extracts the private signature key from static configuration files and moves it to dynamic memory storage. The key is generated by a leader instance and distributed securely to follower instances during runtime, eliminating the security vulnerability of storing keys in persistent configuration files that can be compromised.
Solution Approach 2:
The patent introduces a leader-follower architecture where the leader instance acts as an intermediary for key distribution. The leader generates the private signature key, encrypts it with the follower's public host key, and transmits it securely. This intermediary mechanism enables secure key distribution without requiring direct access to configuration files.
2Productivity
If private signature keys are distributed to multiple authorization instances, then access token generation capability is improved, but security risk increases due to potential key compromise
Solution Approach 1:
The patent segments the authorization service into leader and follower instances with distinct roles. The leader instance holds and manages the private signature key in memory, while follower instances can request encrypted copies for access token generation. This segmentation limits key exposure and enables multiple instances to perform authorization functions without all instances needing full key access.
Solution Approach 2:
The patent changes the state of the private signature key from persistent storage in configuration files to transient memory storage. The key exists only in memory during runtime and is automatically cleared when instances restart, fundamentally changing the key's lifecycle parameters to reduce attack surface and compromise risk.
3Duration of action of stationary object
If configuration files are used for key storage, then persistent storage is utilized, but security is reduced due to file system vulnerabilities
Solution Approach 1:
The patent fundamentally changes the storage medium parameter from persistent file system storage to transient memory storage. Keys are loaded into memory when instances start and automatically cleared when instances stop, eliminating the security vulnerabilities associated with file system storage while maintaining key availability during service operation.
Solution Approach 2:
The patent transitions from static configuration file storage to dynamic memory-based key management. The key is generated dynamically by the leader instance and distributed dynamically to follower instances based on their public host keys. This dynamic approach replaces the static, vulnerable file-based system with a flexible, secure memory-based system.
Data Source
AI summary
A method, a computer program product, and a system for distributing a private signature key between authorization instances. The method includes registering a plurality of authorization instances in a configuration file and generating host instance key pairs by each of the authorization instances. The method also includes storing the public host keys in the shared database and electing one of the authorization instances to be a signature key leader instance. The method includes generating, by the signature key leader instance, a signature key pair. The signature key pair includes a public signature key and a private signature key. The method also includes storing the public signature key in the shared database and transmitting an encrypted private signature key to a requesting authorization instance of the authorization instances. The method further includes decrypting the encrypted private signature key using the private host key generated by the requesting authorization instance.