Cloud Desktop Client Emergency Authentication Bypass

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

When a management node fails in a cloud desktop system, users are unable to access their desktop virtual machines, leading to downtime and reduced customer satisfaction.

Innovation Solution

An emergency management method that initiates an emergency connection by authenticating a local password corresponding to a user ID, queries a locally stored user information file for desktop list information, and links to the cloud desktop system using a command line parameter, allowing users to access their virtual machines even if the management node is abnormal.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the management node is used for authenticating users and managing desktop connections, then the system can provide centralized control and security, but the system becomes vulnerable to complete downtime when the management node fails

Engineering Contradiction:

Improvesystem availabilityVSAvoidsingle point of failure

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The client device stores authentication information and desktop connection parameters locally in advance. When the management node is accessible, the client pre-loads user credentials and desktop list information into local storage, so that when the management node fails, the client can immediately use the pre-stored information to maintain connectivity without requiring real-time communication with the management node.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent introduces a fallback authentication mechanism that acts as an intermediary between the user and the cloud desktop system. When the management node is unavailable, the client device uses local stored authentication information as an intermediate layer to enable users to still access their desktops, bridging the gap between the failed centralized authentication and the user's need for access.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If the system requires continuous authentication through the management node, then security is maintained, but user access is completely blocked when the management node is abnormal

Engineering Contradiction:

Improveuser access continuityVSAvoidmanagement node failure impact

Core Design Contradiction:

ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The system prepares authentication credentials and desktop connection parameters in advance and stores them locally on the client device. This pre-positioned information acts as a cushion against management node failures, allowing users to continue accessing their desktops even when the centralized authentication service is unavailable, thus mitigating the harmful impact of management node failures.

Inventive Principle:

Principle #11Beforehand cushioning (Prior cushioning)

Solution Approach 2:

The client device creates a local copy of the authentication information and desktop connection parameters that were originally obtained from the management node. This copy allows the client to function independently when the management node is inaccessible, replicating the necessary authentication capabilities without requiring continuous connection to the centralized system.

Inventive Principle:

Principle #26Copying

3Ease of operation

If the client device stores authentication information locally, then emergency access is enabled during management node failures, but security risks increase

Engineering Contradiction:

Improveemergency access capabilityVSAvoidsecurity vulnerability

Core Design Contradiction:

Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The system implements different authentication behaviors based on the operational context. When the management node is accessible, centralized authentication is used for security. When the management node fails, the system switches to using locally stored authentication information to enable emergency access. This contextual differentiation allows the system to optimize for security during normal operation and for accessibility during failures.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

The locally stored authentication information is designed as a temporary fallback mechanism that is activated only when necessary (during management node failures). It is not the primary authentication method but serves as a disposable emergency solution that can be discarded or updated when the management node becomes accessible again, minimizing long-term security risks while providing immediate relief during outages.

Inventive Principle:

Principle #27Cheap short-living objects (Disposable)

Data Source

PatentEP3836507B1Client connection emergency management method, client and computer readable storage medium

Publication Date: 2023.12.20 ZTE CORP

Figure 1~2
Figure 3
Figure 4

AI summary

Provided are an emergency management method for client connection, a client and a computer-readable storage medium. The method includes: in response to confirming that feedback about authentication information times out, starting emergency connection and authenticating a local password corresponding to a user identification, ID; after the authentication of the local password corresponding to the user ID succeeds, querying a locally stored user information file for desktop list information according to the user ID; and displaying the desktop list information, and linking to a cloud desktop system by using a command line parameter in the user information file.