Public Key Backup Client Authentication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing backup systems face inefficiencies in installing client backup software and authenticating clients, particularly in large enterprises with numerous machines and geographically separated sites, as they require manual intervention and password management, which is time-consuming and burdensome.
Innovation Solution
The implementation of a public key encryption system allows for automated installation of client backup software and authentication, using private/public key certificate files stored on the backup server, enabling secure communication and authentication without the need for physical administrator intervention, and allowing mobile clients to connect to different local area networks automatically.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual installation and authentication of client backup software is performed, then security and control are improved, but time consumption and administrative burden increase
Solution Approach 1:
The system performs preliminary actions by pre-configuring authentication credentials and backup policies on the backup server before clients need to be authenticated. The backup server proactively discovers new clients on the network and automatically provisions them with necessary authentication information, eliminating the need for manual administrator intervention at the client level.
Solution Approach 2:
The backup server autonomously performs authentication and client registration without requiring manual administrator intervention. The system self-services by automatically detecting new clients on the network, provisioning them with authentication credentials, and registering them in the backup database, thereby reducing administrative burden while maintaining security.
2Productivity
If automated push installation is used for backup software, then installation speed is improved, but distribution of unique passwords and security credentials becomes difficult
Solution Approach 1:
The system extracts the password distribution problem from the installation process by using public key infrastructure. Instead of trying to push passwords through automated installation tools, the system separates authentication credentials into public keys (which can be freely distributed) and private keys (which remain secure on the server), allowing automated installation without credential distribution complexity.
Solution Approach 2:
The system changes the authentication parameter from passwords to public key certificates. This parameter change enables automated installation because public keys can be freely distributed and installed without security concerns, while the corresponding private keys remain securely stored on the backup server for authentication purposes.
3Adaptability or versatility
If mobile clients connect to different LANs, then mobility and versatility are improved, but automatic authentication across sites becomes impossible
Solution Approach 1:
The backup server implements universal authentication by storing multiple private keys corresponding to different site backup servers. A mobile client can authenticate with any site's backup server using the appropriate public key, enabling the system to serve multiple functions across different locations without requiring manual configuration at each site.
Solution Approach 2:
The backup server acts as an intermediary that facilitates authentication between mobile clients and various site backup servers. By maintaining a repository of private keys and using public key infrastructure, the backup server mediates the authentication process, allowing clients to automatically authenticate with any site they connect to without manual administrator intervention.
Data Source
AI summary
A method of automatically authenticating clients on a computer system network enables clients on the network to be automatically logged in and added to a backup database and assigned for backup. The method employs a public key/private key encryption system in which clients have a public key and the backup server has a private key. The backup server interrogates new clients to determine client status and whether the client supports the public key/private key certificate. If it does, the backup server uses key values from the client decrypted using its private key to generate encryption keys which are employed in an algorithm for securely communicating with the client to log the client into a backup database. Otherwise, the backup server uses a password entered by a user in the client for generating the encryption keys. Additionally, the method enables backup software and public keys to be automatically push installed on the clients.