A method for a clientless remote desktop gateway to call operation and maintenance tools

Abstract

The present invention discloses a method for calling an operation and maintenance tool by a clientless remote desktop gateway, which belongs to the field of network operation and maintenance. The present invention calls the operation and maintenance tool software by the clientless remote desktop gateway. After the account is automatically filled in and configured, the clientless remote desktop gateway notifies the Apphouse to start the operation and maintenance tool software. The Apphouse internal service creates a user, and the operation and maintenance tool software calling program is placed in the created user directory to call up the operation and maintenance tool software. The clientless remote desktop gateway acts as an intermediate proxy gateway, and returns the visual interactive interface of the operation and maintenance tool software to the management platform. The management platform returns the visual interface information of the operation and maintenance tool software to the user's browser client and finally presents it to the user, and the user can perform operation and maintenance operations through the visual interface. The problem that the operation and maintenance tool software must be installed on the user's local computer and the user opens the corresponding operation and maintenance tool when operation and maintenance is required, and the user needs to manually enter the account and password of the connection target is solved.

Description

Technical Field

[0001] The present invention relates to the field of network operation and maintenance, and in particular to a method for calling an operation and maintenance tool via a clientless remote desktop gateway. Background Art

[0002] With the rapid development of information technology and the internet, the level of informatization is increasing, and the technologies used in enterprise systems and services are becoming increasingly large and complex. Enterprises' demand for operations and maintenance management is also increasing. Operations and maintenance teams need to use a variety of operations and maintenance management tools to manage and monitor their large systems and services.

[0003] Under the traditional O&M model, each O&M method requires the installation of a dedicated O&M client tool. This results in high installation and maintenance costs, resource usage, learning curve, and integration difficulties. To address these issues, a unified O&M management platform or tool can be considered. This integrates various O&M functions and provides a unified user interface, reducing administrator workload and improving efficiency.

[0004] In terms of security, under the traditional operation and maintenance model, the use of specialized operation and maintenance client tools usually requires users to provide an account and password for identity authentication, which may lead to some security risks.

[0005] In summary, traditional O&M models require the installation of dedicated client tools for each operation and maintenance method. These tools lack unified management and maintenance methods, hinder account security, and prevent log and video auditing. Clientless remote desktop gateway O&M tool invocation provides a unified browser-based client entry, unified account management, centralized O&M tool management via virtualized containers, password-generating tool invocations, and audit logging and video recording. Summary of the Invention

[0006] In view of the above-mentioned deficiencies in the prior art, the present invention provides a method for calling an operation and maintenance tool by a clientless remote desktop gateway.

[0007] In order to achieve the above-mentioned object of the invention, the technical solution adopted by the present invention is:

[0008] A method for calling an operation and maintenance tool by a clientless remote desktop gateway includes the following steps:

[0009] S1. Obtain access rights to the target operation and maintenance account, log in, connect to the account requiring operation and maintenance, and make an operation and maintenance connection request;

[0010] S2. After receiving the connection request, the management platform calls the target operation and maintenance tool and sends the complete operation and maintenance account information to Apphouse;

[0011] S3. Prepare the operation and maintenance tools. Based on the prepared operation and maintenance tools, the management platform communicates in real time through the clientless remote desktop gateway and performs operation and maintenance operations through command interaction.

[0012] S4. Record user operation logs, actively call the management platform interface to push records, and the clientless desktop gateway records the operation video. After the operation and maintenance operation is completed, the connection is disconnected and the ongoing operation and maintenance status is updated to the historical behavior status.

[0013] Furthermore, the S2 specifically includes the following steps:

[0014] S21. Modify the configuration data of the operation and maintenance tool software before calling the operation and maintenance tool, and set the account information to be filled in on behalf of the user;

[0015] S22. Based on the received configuration data, check whether the parameters are compliant and complete, and check whether the called tools are installed and the version is correct. If not, Apphouse requests to download the correct operation and maintenance tool software from the management platform;

[0016] S23, Apphouse always waits for client connection requests, and when there is a request, it will establish a communication session with the client;

[0017] S24. Apphouse hides the system desktop in the graphical interface and displays the graphical screen that only exists in the operation and maintenance tool software to the user, and authorizes the user to only operate the operation and maintenance tool software;

[0018] S25. The user input instructions are not recorded before they are executed. When the user executes a new instruction, the changes in the operation and maintenance tool software log file are monitored and the changed content is read. The read content is transmitted to the management platform for storage after secondary analysis. The Apphouse virtualization tool software container does not record and store data.

[0019] Furthermore, the S3 specifically includes the following steps:

[0020] S31. Based on the preparation of the operation and maintenance tool software, the clientless remote desktop gateway of the management platform uses a long connection protocol for real-time interactive communication;

[0021] S32. The management platform uses a prescribed protocol instruction in the interaction, and the clientless remote desktop gateway listens to request a connection and parses the content of the protocol instruction;

[0022] S33. Based on the parsed command content, the clientless remote desktop gateway draws the image interface sent back by Apphouse and transmits operation events, while monitoring the connection and data interaction between it and the management platform;

[0023] S34. Parse the command data passed by the management platform and connect to Apphouse as a client, acting as an intermediate layer to perform data parsing between protocol interactions.

[0024] Furthermore, each protocol instruction in the S32 is a comma-delimited data followed by a terminating semicolon, where the first element of the instruction is the instruction opcode, and all subsequent elements are parameters of the instruction. Each element in the list has a positive integer length prefix, and the element value and the prefix are separated by a period.

[0025] Furthermore, the management platform or clientless remote desktop gateway at either end of the real-time communication in S3 can terminate the connection at any time by using the "disconnect" command. If a problem occurs in the management platform or the clientless remote desktop gateway, the clientless remote desktop gateway will send an "error" command to notify the management platform.

[0026] The present invention has the following beneficial effects:

[0027] 1. Call the operation and maintenance tool software in Apphouse through the clientless remote desktop gateway.

[0028] 2. Unified management and installation of operation and maintenance tool software, realizing clientless installation of operation and maintenance tool software.

[0029] 3. Automatically fill in the operation and maintenance account number, and centralize the hosting to ensure that account information is not lost.

[0030] 4. Apphouse automatically installs supported operation and maintenance tools.

[0031] 5. The virtualization container tool automatically installs supported operation and maintenance tools. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Figure 1 Flowchart of the method for calling operation and maintenance tools for a clientless remote desktop gateway. DETAILED DESCRIPTION

[0033] The specific embodiments of the present invention are described below to facilitate understanding of the present invention by those skilled in the art. However, it should be clear that the present invention is not limited to the scope of the specific embodiments. For those skilled in the art, as long as various changes are within the spirit and scope of the present invention as defined and determined by the appended claims, these changes are obvious, and all inventions and creations utilizing the concepts of the present invention are protected.

[0034] A method for calling operation and maintenance tools from a clientless remote desktop gateway, such as Figure 1 As shown, the following steps are included:

[0035] S1. Obtain access rights to the target operation and maintenance account, log in, connect to the account requiring operation and maintenance, and make an operation and maintenance connection request;

[0036] The user logs in to the management platform through multi-factor security authentication and checks whether they have the corresponding access rights to the target operation and maintenance account. If they do not have the permission, they need to apply through the management platform. The user enters the operation and maintenance interface, selects the account to be operated and maintained, and makes an operation and maintenance connection request.

[0037] S2. After receiving the connection request, the management platform calls the target operation and maintenance tool and sends the complete operation and maintenance account information to Apphouse;

[0038] In this embodiment, the following steps are specifically included:

[0039] S21. Modify the configuration data of the operation and maintenance tool software before calling the operation and maintenance tool, and set the account information to be filled in on behalf of the user;

[0040] The clientless remote desktop gateway calls the operation and maintenance tool software. After the account is automatically filled in and configured, the clientless remote desktop gateway notifies Apphouse to start the operation and maintenance tool software. The Apphouse internal service creates a user and places the operation and maintenance tool software call program in the created user directory to call the operation and maintenance tool software. The clientless remote desktop gateway acts as an intermediate proxy gateway and returns the visual interactive interface of the operation and maintenance tool software to the management platform. The management platform returns the visual interface information of the operation and maintenance tool software to the user's browser client and finally presents it to the user. The user can then perform operation and maintenance operations through the visual interface.

[0041] S22. Based on the received configuration data, check whether the parameters are compliant and complete, and check whether the called tools are installed and the version is correct. If not, Apphouse requests to download the correct operation and maintenance tool software from the management platform;

[0042] The Apphouse virtualization tool software container uses two types of protocols to achieve external interaction. One type of protocol is graphical interface interaction, which enables users to interact with the target operation and maintenance tool software through a graphical interface. The other type of protocol is through the management platform and the interface of the Apphouse virtualization tool software container for data interaction, including operation and maintenance account configuration, files, monitoring, logs and other interface interactions.

[0043] S23, Apphouse always waits for client connection requests, and when there is a request, it will establish a communication session with the client;

[0044] S24. Apphouse hides the system desktop in the graphical interface and displays the graphical screen that only exists in the operation and maintenance tool software to the user, and authorizes the user to only operate the operation and maintenance tool software;

[0045] S25. The user input instructions are not recorded before they are executed. When the user executes a new instruction, the changes in the operation and maintenance tool software log file are monitored and the changed content is read. The read content is transmitted to the management platform for storage after secondary analysis. The Apphouse virtualization tool software container does not record and store data.

[0046] S3. Prepare the operation and maintenance tools. Based on the prepared operation and maintenance tools, the management platform communicates in real time through the clientless remote desktop gateway and performs operation and maintenance operations through command interaction.

[0047] In this embodiment, the following steps are specifically included:

[0048] S31. Based on the preparation of the operation and maintenance tool software, the clientless remote desktop gateway of the management platform uses a long connection protocol for real-time interactive communication;

[0049] S32. The management platform uses a prescribed protocol instruction in the interaction, and the clientless remote desktop gateway listens to request a connection and parses the content of the protocol instruction;

[0050] S33. Based on the parsed command content, the clientless remote desktop gateway draws the image interface sent back by Apphouse and transmits operation events, while monitoring the connection and data interaction between it and the management platform;

[0051] S34. Parse the command data passed by the management platform and connect to Apphouse as a client, acting as an intermediate layer to perform data parsing between protocol interactions.

[0052] Based on the preparation of the operation and maintenance tool software, the management platform communicates with the clientless remote desktop gateway using a persistent connection protocol for real-time interactive communication. The management platform uses the specified protocol instructions in the interaction, and the clientless remote desktop gateway listens for connection requests. The clientless remote desktop gateway parses the content of the protocol instructions to understand what operations the user needs to perform with the remote server. The clientless remote desktop gateway draws the screen and transmits operation events on the graphical interface sent back by Apphouse, while monitoring the connection and data interaction with the management platform. The command data passed by the management platform is parsed, and it connects to Apphouse as a client, acting as an intermediary to perform data parsing between protocol interactions.

[0053] The clientless remote desktop gateway exchanges commands. Each command is a comma-delimited list of data followed by a terminating semicolon. The first element of the command is the command opcode, and all subsequent elements are the command's parameters. Each element in the list is prefixed with a positive integer length, separated by a period. The length represents the number of characters in the element value. Any number of complete commands constitutes a message, which is sent from the management platform to the clientless remote desktop gateway, or from the clientless remote desktop gateway to the management platform. Commands sent by the management platform are typically control commands and events. Commands from the clientless remote desktop gateway to the management platform are typically instructions for drawing images, using the browser client as the display. The length prefix in each command element means that the parser can quickly jump from one command to another without having to iterate through each character. The protocol interaction phase begins immediately after the connection is established. It starts with a "select" command sent by the client. The command tells the clientless remote desktop gateway which protocol to load, and responds with a "return" command to its protocol version and acceptable parameter names. After receiving the parameters, the client needs to respond with a list of supported command types and the values ​​of the available parameters. The clientless remote desktop gateway marks the connection successfully and then sends a "ready" command to enter the actual interaction phase. The sending and receiving of command data in the actual interaction phase is sent by one end and confirmed by the other end. The content sent by the sender requires the receiver to return a "confirmation" command. The management platform or clientless remote desktop gateway on either end can end the connection at any time and can use the "disconnect" connection command. If there is a problem with the management platform or the clientless remote desktop gateway, the clientless remote desktop gateway will send an "error" command to notify the management platform.

[0054] S4. Record user operation logs, actively call the management platform interface to push records, and the clientless desktop gateway records the operation video. After the operation and maintenance operation is completed, the connection is disconnected and the ongoing operation and maintenance status is updated to the historical behavior status.

[0055] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowcharts and / or block diagrams, as well as combinations of processes and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowcharts and / or block diagrams. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0056] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0057] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0058] Specific embodiments are used in the present invention to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core ideas. At the same time, for those skilled in the art, according to the ideas of the present invention, there may be changes in the specific implementation methods and application scopes. In summary, the contents of this specification should not be understood as limiting the present invention.

[0059] Those skilled in the art will appreciate that the embodiments described herein are intended to help readers understand the principles of the present invention, and it should be understood that the scope of protection of the present invention is not limited to such specific descriptions and embodiments. Those skilled in the art can make various other specific variations and combinations based on the technical teachings disclosed in the present invention without departing from the essence of the present invention, and such variations and combinations are still within the scope of protection of the present invention.

Claims

1. A method for calling an operation and maintenance tool by a clientless remote desktop gateway, characterized in that: The steps include: S1. Obtain access rights to the target operation and maintenance account and log in, connect to the account that needs operation and maintenance, and make an operation and maintenance connection request; S2. After receiving the connection request, the management platform calls the target operation and maintenance tool and sends the complete operation and maintenance account information to Apphouse. The specific steps include the following: S21. Modify the configuration data of the operation and maintenance tool software before calling the operation and maintenance tool, and set the account information to be filled in; S22. Based on the received configuration data, check whether the parameters are compliant and complete, and check whether the called tool has been installed and the version is correct. If it is not installed or the version is incorrect, Apphouse downloads the correct operation and maintenance tool software from the management platform through a request; S23, Apphouse always waits for client connection requests, and establishes a communication session with the client when there is a request; S24. Apphouse hides the system desktop in the graphical interface and displays the graphical screen that only exists in the operation and maintenance tool software to the user, and authorizes the user to only have the authority to operate the operation and maintenance tool software; S25. Do not record the user input commands before they are executed. When the user executes a new command, monitor the changes in the operation and maintenance tool software log file, read the changes, and transmit the read content to the management platform for storage after secondary analysis. The Apphouse virtualization tool software container does not record and store data. S3. Prepare the operation and maintenance tools. Based on the prepared operation and maintenance tools, the management platform communicates in real time through the clientless remote desktop gateway and performs operation and maintenance operations through command interaction. The specific steps include: S31. Based on the prepared operation and maintenance tool software, the management platform uses a long connection protocol to conduct real-time interactive communication through a clientless remote desktop gateway; S32, the management platform uses the specified protocol instructions in the interaction, and the clientless remote desktop gateway listens to request a connection and parses the content of the protocol instructions; S33. Based on the parsed instruction content, the clientless remote desktop gateway draws the image interface sent back by Apphouse and transmits operation events, while monitoring the connection and data interaction between the clientless remote desktop gateway and the management platform; S34, parse the command data passed by the management platform, and connect to Apphouse as a client, acting as an intermediate layer to perform data parsing between protocol interactions; S4. Record user operation logs, actively call the management platform interface to push records, and the clientless desktop gateway records the operation video. After the operation and maintenance operation is completed, the connection is disconnected and the ongoing operation and maintenance status is updated to the historical behavior status.

2. The method for calling an operation and maintenance tool by a clientless remote desktop gateway according to claim 1, characterized in that: Each protocol instruction in the S32 is a comma-delimited data followed by a terminating semicolon, wherein the first element of the instruction is the instruction opcode, and all subsequent elements are parameters of the instruction. Each element in the list has a positive integer length prefix, and the element value and the prefix are separated by a period.

3. The method for calling an operation and maintenance tool by a clientless remote desktop gateway according to claim 1, characterized in that: The management platform or clientless remote desktop gateway at either end of the real-time communication in the S3 can terminate the connection at any time using the "disconnect" connection command. If a problem occurs with the management platform or the clientless remote desktop gateway, the clientless remote desktop gateway will send an "error" command to notify the management platform.

Images