A unified control method and system for cloud desktops with different architectures

Abstract

The present invention relates to a unified control method and system for cloud desktops of different architectures, the method comprising the following steps: obtaining a user password, performing password authentication, if the authentication is passed, obtaining a token that the platform allows access to, and judging whether a session corresponding to the token is obtained; if the session is obtained, indicating that the login is completed, docking with multiple cloud desktops of different architectures is performed, and after docking, session credentials corresponding to multiple cloud desktops of different architectures are obtained; after obtaining the session credentials, the desktop list interface of the cloud desktops of different architectures is called, desktop instance data corresponding to the cloud desktops of multiple different architectures is obtained, and the desktop instance data is sent to the front end; when the front end receives a cloud desktop access signal corresponding to the desktop instance data, the local client corresponding to the desktop instance data is started based on the session credentials, and the cloud desktop is accessed and controlled based on the local client. Compared with the prior art, the present invention has the advantages of high efficiency.

Description

Technical Field

[0001] The present invention relates to the field of cloud desktops, and in particular to a unified control method and system for cloud desktops with different architectures. Background Art

[0002] When switching cloud desktops of different architectures, current cloud desktop technology requires logging into cloud desktops of different architecture types at the same time. It is impossible to uniformly control cloud desktops of different architectures after a one-time login, resulting in repeated logins during the switching process and low efficiency in controlling cloud desktops of different architectures. Summary of the invention

[0003] The purpose of the present invention is to overcome the defects of the above-mentioned prior art and to provide a high-efficiency unified control method and system for cloud desktops with different architectures.

[0004] The purpose of the present invention can be achieved by the following technical solutions:

[0005] A unified control method for cloud desktops with different architectures, the method comprising the following steps:

[0006] Obtain the user password and perform password authentication. If the authentication is successful, obtain the token that the platform allows access to and determine whether the session corresponding to the token is obtained;

[0007] If the session is obtained, it means that the login is completed, and then the pre-configured cloud platform account and cloud platform password are used to connect with multiple cloud desktops of different architectures. After the connection, the session credentials corresponding to the multiple cloud desktops of different architectures are obtained;

[0008] After obtaining the session credentials, call the desktop list interface of the cloud desktops of different architectures, obtain the desktop instance data corresponding to the cloud desktops of multiple different architectures, and send the desktop instance data to the front end;

[0009] When the front end receives a cloud desktop access signal corresponding to the desktop instance data, it starts a local client corresponding to the desktop instance data based on the session credentials, and accesses and controls the cloud desktop based on the local client.

[0010] Furthermore, the process of obtaining the session credential is: obtaining the session identifier and the random token identifier of the session, and saving the session identifier and the random token identifier in the session as the session credential.

[0011] Furthermore, the process of obtaining the session credential is: obtaining the Csrf token and the identity verification identifier, and saving the Csrf token and the identity verification identifier in the session as the session credential.

[0012] Furthermore, the process of obtaining the session credential is: obtaining the security identifier and the user session data, and storing the security identifier and the user session data in the session as the session credential.

[0013] Furthermore, the local client corresponding to the desktop instance data started based on the session credentials is specifically:

[0014] Use the schema to start the local client corresponding to the desktop instance data, assemble the login credentials, desktop service address and session credentials, build the schema URL and return it to the web front end, and start the local client by requesting the schema through the browser.

[0015] Furthermore, the local client corresponding to the desktop instance data started based on the session credentials is specifically:

[0016] The local client corresponding to the desktop instance data is started by downloading and opening the ica file. Through the session credentials, the ica sending interface is requested to obtain the ica file stream. At this time, the file stream is returned to the browser to download the ica file. After the download is complete, the ica file is opened to start the local client.

[0017] Furthermore, the local client corresponding to the desktop instance data started based on the session credentials is specifically:

[0018] The local client corresponding to the desktop instance data is started by downloading and opening the ivy file. The connection interface is requested through the session credentials and the cloud desktop identifier to obtain the ivy file stream. At this time, the file stream is returned to the browser, the ivy file is downloaded, and after the download is complete, the ivy file is opened to start the local client.

[0019] Furthermore, the identity verification identifier is obtained through a login form obtained by a CSRF token.

[0020] Furthermore, the method also includes: after obtaining the desktop instance data, abstractly packaging the desktop instance data, formatting it into unified abstract desktop instance data, and then sending it to the front end.

[0021] A unified control system for cloud desktops of different architectures, the system includes a login authentication module, a cloud desktop docking module, a cloud desktop list acquisition module and a cloud desktop login module, wherein:

[0022] The login authentication module is used to obtain the user password and perform password authentication. If the authentication is successful, the platform will obtain the access token and determine whether the session corresponding to the token is obtained.

[0023] The cloud desktop docking module is used to dock with multiple cloud desktops of different architectures. After docking, the session credentials corresponding to the multiple cloud desktops of different architectures are obtained;

[0024] The cloud desktop list acquisition module is used to call the desktop list interface of cloud desktops of different architectures, obtain desktop instance data corresponding to multiple cloud desktops of different architectures, and send the desktop instance data to the front end;

[0025] The cloud desktop login module is used to start the local client corresponding to the desktop instance data based on the session credentials when the front end receives the cloud desktop access signal corresponding to the desktop instance data, and access and control the cloud desktop based on the local client.

[0026] Compared with the prior art, the present invention has the following advantages:

[0027] The present invention obtains session credentials by docking with multiple cloud desktops of different architectures, starts a local client corresponding to the desktop instance data based on the session credentials, and controls the cloud desktop through the local client. This solves the problem that when switching cloud desktops of different architectures, it is necessary to log in to cloud desktops of different architecture types at the same time, and it is impossible to uniformly control cloud desktops of different architectures after a one-time login. This can reduce the workload of working with multiple cloud desktops and improve the control efficiency of the cloud desktops. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Figure 1 It is a flow chart of the present invention. DETAILED DESCRIPTION

[0029] In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Generally, the components of the embodiments of the present invention described and shown in the drawings here can be arranged and designed in various different configurations.

[0030] Therefore, the following detailed description of the embodiments of the present invention provided in the accompanying drawings is not intended to limit the scope of the invention claimed for protection, but merely represents selected embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0031] Example 1

[0032] The present invention provides a unified control method for cloud desktops of different architectures, and the flow chart of the method is as follows: Figure 1 The method comprises the following steps:

[0033] Get the user password and perform password authentication. If the authentication is successful, get the token that the platform allows access to and determine whether the session corresponding to the token is obtained. The token is used for subsequent use of other functions.

[0034] If the session is obtained, it means that the login is completed. Then, based on the pre-configured cloud platform account and cloud platform password, the system will connect with multiple cloud desktops of different architectures. After the connection, the session credentials corresponding to the cloud desktops of different architectures will be obtained.

[0035] After obtaining the session credentials, the desktop list interface of the cloud desktops of different architectures is called to obtain the desktop instance data corresponding to the cloud desktops of multiple different architectures, and the desktop instance data is sent to the front end.

[0036] When the front end receives a cloud desktop access signal corresponding to the desktop instance data, it starts a local client corresponding to the desktop instance data based on the session credentials, and accesses and controls the cloud desktop based on the local client.

[0037] In some embodiments, the process of obtaining the session credential is: obtaining the session identifier sessionId and the random token identifier randomTokenId of the session, and saving the session identifier sessionId and the random token identifier randomTokenId in the session as the session credential.

[0038] In some embodiments, the process of obtaining the session credentials is: obtaining the Csrf token CsrfToken and the authentication identifier CtxsAuthId, and saving the Csrf token and the authentication identifier CtxsAuthId in the session as the session credentials. The authentication identifier CtxsAuthId is obtained through the login form obtained by the Csrf token CsrfToken, obtaining the token interface of the cloud platform, obtaining the Csrf token CsrfToken, and obtaining the login form through the Csrf token CsrfToken.

[0039] In some embodiments, the process of obtaining the session credentials is: obtaining the security identifier sid and the user session data, and saving the security identifier sid and the user session data in the session as the session credentials.

[0040] In some embodiments, starting the local client corresponding to the desktop instance data based on the session credentials is specifically:

[0041] Use the schema to start the local client corresponding to the desktop instance data, assemble the login credentials loginTicket, desktop service address and session credentials, build the schema url and return it to the web frontend, and start the local client by requesting the schema through the browser.

[0042] In some embodiments, starting the local client corresponding to the desktop instance data based on the session credentials is specifically:

[0043] The local client corresponding to the desktop instance data is started by downloading and opening the ica file. Through the session credentials, the ica sending interface launchica is requested to obtain the ica file stream. At this time, the file stream is returned to the browser to download the ica file. After the download is complete, the ica file is opened to start the local client.

[0044] In some embodiments, starting the local client corresponding to the desktop instance data based on the session credentials is specifically:

[0045] The local client corresponding to the desktop instance data is started by downloading and opening the ivy file. The connection interface connectParamIni is requested through the session credentials and the cloud desktop identifier desktopId to obtain the ivy file stream. At this time, the file stream is returned to the browser, the ivy file is downloaded, and after the download is complete, the ivy file is opened to start the local client.

[0046] The method also includes: after obtaining the desktop instance data, abstractly packaging the desktop instance data, formatting it into unified abstract desktop instance data, and then sending it to the front end.

[0047] The present invention also provides a unified control system for cloud desktops of different architectures, wherein the system includes a login authentication module, a cloud desktop docking module, a cloud desktop list acquisition module and a cloud desktop login module, wherein:

[0048] The login authentication module is used to obtain the user password and perform password authentication. If the authentication is successful, the platform will obtain the access token and determine whether the session corresponding to the token is obtained.

[0049] The cloud desktop docking module is used to dock with multiple cloud desktops of different architectures. After docking, the session credentials corresponding to the multiple cloud desktops of different architectures are obtained;

[0050] The cloud desktop list acquisition module is used to call the desktop list interface of cloud desktops of different architectures, obtain desktop instance data corresponding to multiple cloud desktops of different architectures, and send the desktop instance data to the front end;

[0051] The cloud desktop login module is used to start the local client corresponding to the desktop instance data based on the session credentials when the front end receives the cloud desktop access signal corresponding to the desktop instance data, and access and control the cloud desktop based on the local client.

[0052] The preferred specific embodiments of the present invention are described in detail above. It should be understood that a person skilled in the art can make many modifications and changes based on the concept of the present invention without creative work. Therefore, any technical solution that can be obtained by a person skilled in the art through logical analysis, reasoning or limited experiments based on the concept of the present invention on the basis of the prior art should be within the scope of protection determined by the claims.

Claims

1. A unified control method for cloud desktops with different architectures, characterized in that: The method comprises the following steps: Obtain the user password and perform password authentication. If the authentication is successful, obtain the token that the platform allows access to and determine whether the session corresponding to the token is obtained; If the session is obtained, it means that the login is completed, and then the pre-configured cloud platform account and cloud platform password are used to connect with multiple cloud desktops of different architectures. After the connection, the session credentials corresponding to the multiple cloud desktops of different architectures are obtained; After obtaining the session credentials, call the desktop list interface of the cloud desktops of different architectures, obtain the desktop instance data corresponding to the cloud desktops of multiple different architectures, and send the desktop instance data to the front end; When the front end receives a cloud desktop access signal corresponding to the desktop instance data, it starts a local client corresponding to the desktop instance data based on the session credentials, and accesses and controls the cloud desktop based on the local client; The process of obtaining the session credential is as follows: obtaining the session identifier and the random token identifier of the session, and storing the session identifier and the random token identifier in the session as the session credential; The process of obtaining the session credential is: obtaining the CSRF token and the authentication identifier, and saving the CSRF token and the authentication identifier in the session as the session credential; the process of obtaining the session credential is: obtaining the security identifier and the user session data, and saving the security identifier and the user session data in the session as the session credential; The authentication identifier is obtained through the login form obtained by the CSRF token.

2. According to claim 1, a unified control method for cloud desktops with different architectures is characterized in that: The local client corresponding to launching the desktop instance data based on the session credentials is: Use the schema to start the local client corresponding to the desktop instance data, assemble the login credentials, desktop service address and session credentials, build the schema URL and return it to the web front end, and start the local client by requesting the schema through the browser.

3. According to claim 1, a unified control method for cloud desktops with different architectures is characterized in that: The local client corresponding to launching the desktop instance data based on the session credentials is: The local client corresponding to the desktop instance data is started by downloading and opening the ica file. Through the session credentials, the ica sending interface is requested to obtain the ica file stream. At this time, the file stream is returned to the browser to download the ica file. After the download is complete, the ica file is opened to start the local client.

4. According to claim 1, a unified control method for cloud desktops with different architectures is characterized in that: The local client corresponding to launching the desktop instance data based on the session credentials is: The local client corresponding to the desktop instance data is started by downloading and opening the ivy file. The connection interface is requested through the session credentials and the cloud desktop identifier to obtain the ivy file stream. At this time, the file stream is returned to the browser, the ivy file is downloaded, and after the download is complete, the ivy file is opened to start the local client.

5. The unified control method of cloud desktops with different architectures according to claim 1, characterized in that: The method also includes: after obtaining the desktop instance data, abstractly packaging the desktop instance data, formatting it into unified abstract desktop instance data, and then sending it to the front end.

6. A unified control system for cloud desktops of different architectures, characterized in that: The system includes a login authentication module, a cloud desktop docking module, a cloud desktop list acquisition module and a cloud desktop login module, wherein: The login authentication module is used to obtain the user password and perform password authentication. If the authentication is successful, the platform will obtain the access token and determine whether the session corresponding to the token is obtained. The cloud desktop docking module is used to dock with multiple cloud desktops of different architectures. After docking, the session credentials corresponding to the multiple cloud desktops of different architectures are obtained; The cloud desktop list acquisition module is used to call the desktop list interface of cloud desktops of different architectures, obtain desktop instance data corresponding to multiple cloud desktops of different architectures, and send the desktop instance data to the front end; The cloud desktop login module is used to start the local client corresponding to the desktop instance data based on the session credentials when the front end receives the cloud desktop access signal corresponding to the desktop instance data, and access and control the cloud desktop based on the local client; The process of obtaining the session credential is: obtaining the session identifier and random token identifier of the session, and saving the session identifier and random token identifier in the session as the session credential; the process of obtaining the session credential is: obtaining the Csrf token and the authentication identifier, and saving the Csrf token and the authentication identifier in the session as the session credential; the process of obtaining the session credential is: obtaining the security identifier and the user session data, and saving the security identifier and the user session data in the session as the session credential; The authentication identifier is obtained through the login form obtained by the CSRF token.

Images