Method and device for confirming remote user rights of cloud integrated development environment IDE

Abstract

The present disclosure provides a method and device for confirming remote user permissions of a cloud-based integrated development environment (IDE), and relates to the field of computer technology. The specific steps are: receiving an access request sent by a user client, and obtaining the login status attribute information of the user client according to the access request; in response to the login status attribute information being a logged-in state, generating authentication pass information; in response to the authentication pass information, obtaining a target cloud-based IDE identifier according to the access request, and determining the user client's access rights to the target cloud-based IDE according to a permission list. The present disclosure performs authentication through the login status attribute information in the access request, and obtains a permission list according to the access request to determine the user client's access rights to the target cloud-based IDE, thereby preventing unauthorized user clients from accessing the cloud-based IDE and improving the security of the cloud-based IDE.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to a method and device for confirming remote user authority of a cloud integrated development environment (IDE). Background Art

[0002] In the related technology, there are already multiple cloud IDE products for remote development, all of which are based on the browser usage mode, that is, you can access the corresponding cloud IDE by entering a specific http link in the browser. The cloud IDE is deployed in a remote server and is an integrated development environment deployed on the server side. Users can use the cloud IDE to develop and test applications, such as code editing, code debugging, and code refactoring.

[0003] However, the current access method of cloud IDE has poor confidentiality. If other users obtain the http link of the cloud IDE, they can view the code on the browser, which reduces the security of code development. Summary of the invention

[0004] The present invention provides a method and device for confirming remote user rights of a cloud integrated development environment IDE. The technical solution of the present invention is as follows:

[0005] According to a first aspect of an embodiment of the present disclosure, a method for confirming remote user authority of a cloud integrated development environment IDE is provided, comprising:

[0006] Receiving an access request sent by a user client, and acquiring login status attribute information of the user client according to the access request;

[0007] In response to the login status attribute information being a logged-in status, generating authentication pass information;

[0008] In response to the authentication pass information, the target cloud IDE identifier is obtained according to the access request, and the access rights of the user client to the target cloud IDE are determined according to the permission list.

[0009] Optionally, the permission list includes at least one sub-permission list corresponding to a cloud IDE, and determining the access rights of the user client to the target cloud IDE according to the permission list includes:

[0010] Acquire the target sub-authority list in the authority list according to the target cloud IDE identifier;

[0011] The access permission of the user client to the target cloud IDE is determined according to the target sub-permission list, wherein the target sub-permission list includes at least one client identifier.

[0012] Optionally, the step of determining the access rights of the user client to the target cloud IDE according to the target sub-permission list specifically includes:

[0013] In response to the target sub-authority list including a client identifier corresponding to the user client, it is determined that the user client can access the target cloud IDE.

[0014] Optionally, the method further includes:

[0015] Receive a creation request sent by a user client, and create a cloud IDE according to the creation request;

[0016] Receive permission configuration information sent by a user client, and generate a sub-permission list corresponding to the cloud IDE according to the permission configuration information, wherein the permission configuration information includes at least one client identifier.

[0017] Optionally, the step of generating a sub-authority list corresponding to the cloud IDE according to the authority configuration information specifically includes:

[0018] The client identifier in the permission configuration information is obtained, and a sub-permission list corresponding to the cloud IDE created by the client is generated according to the client identifier.

[0019] According to a second aspect of an embodiment of the present disclosure, a cloud-based IDE remote user authority confirmation device is provided, comprising:

[0020] A receiving module, used to receive an access request sent by a user client, and obtain login status attribute information of the user client according to the access request;

[0021] An authentication module, configured to generate authentication pass information in response to the login status attribute information being a logged-in status;

[0022] The authentication module is used to obtain the target cloud IDE identifier according to the access request in response to the authentication pass information, and determine the access rights of the user client to the target cloud IDE according to the permission list.

[0023] Optionally, the authentication module includes:

[0024] A sub-authority list acquisition sub-module, used to acquire the target sub-authority list in the authority list according to the target cloud IDE identifier;

[0025] The permission determination submodule is used to determine the access rights of the user client to the target cloud IDE according to the target sub-permission list, wherein the target sub-permission list includes at least one client identifier.

[0026] Optionally, the authority determination submodule includes:

[0027] The permission determination unit is configured to determine that the user client can access the target cloud IDE in response to the target sub-permission list containing a client identifier corresponding to the user client.

[0028] Optionally, the device further comprises:

[0029] A creation module, used to receive a creation request sent by a user client, and create a cloud IDE according to the creation request;

[0030] The permission list generation module is used to receive permission configuration information sent by the user client, and generate a sub-permission list corresponding to the cloud IDE according to the permission configuration information, wherein the permission configuration information includes at least one client identifier.

[0031] Optionally, the permission list generating module includes:

[0032] The permission list generation submodule is used to obtain the client identifier in the permission configuration information, and generate a sub-permission list corresponding to the cloud IDE created by the client according to the client identifier.

[0033] According to a third aspect of an embodiment of the present disclosure, there is provided an electronic device, including:

[0034] processor;

[0035] a memory for storing instructions executable by the processor;

[0036] The processor is configured to execute the instructions to implement the cloud-based IDE remote user authority confirmation method as described in any one of the first aspects above.

[0037] According to a fourth aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided. When instructions in the storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute a cloud-based IDE remote user authority confirmation method as described in any one of the first aspects above.

[0038] According to a fifth aspect of an embodiment of the present disclosure, a computer program product is provided, including a computer program, wherein when the computer program is executed by a processor, the computer program implements the method according to any one of the above-mentioned first aspects.

[0039] The technical solution provided by the embodiments of the present disclosure brings at least the following beneficial effects:

[0040] Authentication is performed through the login status attribute information in the access request, and a permission list is obtained according to the access request to determine the user client's access rights to the target cloud IDE, thereby preventing unauthorized user clients from accessing the cloud IDE and improving the security of the cloud IDE.

[0041] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] The drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the description are used to explain the principles of the present disclosure, and do not constitute improper limitations on the present disclosure.

[0043] Figure 1 The present invention is a flowchart of a method for confirming the remote user authority of a cloud IDE according to an exemplary embodiment.

[0044] Figure 2 The present invention is a flowchart of a method for confirming the remote user authority of a cloud IDE according to an exemplary embodiment.

[0045] Figure 3 The present invention is a flowchart of a method for confirming the remote user authority of a cloud IDE according to an exemplary embodiment.

[0046] Figure 4 It is a structural diagram of a cloud-based IDE user authority confirmation system provided by related technologies.

[0047] Figure 5 It is a structural diagram of a cloud-based IDE user authority confirmation system provided by related technologies.

[0048] Figure 6 It is a structural diagram of a cloud-based IDE remote user authority confirmation system according to an exemplary embodiment.

[0049] Figure 7 The present invention is a block diagram of a cloud-based IDE remote user authority confirmation device according to an exemplary embodiment.

[0050] Figure 8 It is a block diagram of a device according to an exemplary embodiment.

[0051] Fig. 9 It is a block diagram of a device according to an exemplary embodiment. DETAILED DESCRIPTION

[0052] In order to enable ordinary persons in the art to better understand the technical solutions of the present disclosure, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the accompanying drawings.

[0053] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0054] It should be noted that the user information involved in this disclosure (including but not limited to user device information, user personal information, etc.) is all information authorized by the user or fully authorized by all parties.

[0055] The cloud-based integrated development environment (IDE) is an integrated development environment deployed on the server side, providing developers with a non-stop cloud workstation. Users do not need to install the cloud-based IDE when using it, and can use it anytime and anywhere by opening the browser. The cloud-based IDE includes basic IDE functions such as code highlighting, auto-completion, Git integration, and terminal. It also supports real-time debugging, plug-in extensions, etc., which can help developers quickly complete the development, compilation, and deployment of various applications. The main idea of ​​deploying the IDE program through the cloud server is to log in to the cloud server through ssh, register the IDE program as a systemd system service, start it, and access it through the elastic public network IP bound to the cloud server and the port of the IDE process.

[0056] Currently, there are many cloud IDE products, such as Visual Studio Online, Theia, etc. They are all based on the browser mode, that is, you can access the corresponding cloud IDE by entering a specific http link in the browser, and perform remote development and testing. However, this will cause great security problems. If an illegal user obtains the http link of the cloud IDE, he can view the code on the browser.

[0057] The related technology uses the method of authenticating users to prevent illegal users from logging into the cloud IDE. Figure 4 This is a structural diagram of a cloud IDE user authority confirmation system provided by related technologies. Figure 4As shown in the figure, a unified login interception service is added to the outer layer of the server to determine whether the current user who sends the access request is logged in. If the login interception service determines that the current user is not logged in, the current user needs to log in. After the user logs in, he can access the cloud IDE resources in the server. In this way, only internal users of the company can access the IDE, and illegal external users cannot log in, so their access requests will be intercepted.

[0058] However, the login interception service can only determine whether the current user is a logged-in user, so it can only restrict users outside the company from logging into the cloud IDE. However, within the company, there is no restriction between users. For example, user A creates a cloud IDE and does not want others to be able to access it. However, if user B obtains the remote access link of user A's IDE, user B can access the cloud IDE created by user A without user A's authorization. This still leaves the risk of illegal users logging into the cloud IDE.

[0059] Figure 5 This is a structural diagram of a cloud IDE user permission confirmation system provided by the related technology. In each cloud IDE service in the server, it is determined whether the current user who sends the access request is logged in, and whether the current user has the permission to access the current cloud IDE. If the current user is already logged in and has the permission to access the current cloud IDE, the access request of the current user is accepted; otherwise, the access request of the current user is rejected.

[0060] but Figure 4 In this method, each cloud IDE needs to maintain a service module for permission management judgment, which will increase the memory usage of the IDE, increase the overall memory usage, and reduce the operating efficiency of the cloud IDE. In addition, most cloud IDEs do not provide a method for adding permission management modules, and there is no way to customize and modify them.

[0061] Figure 1 is a flow chart of a method for confirming remote user permissions of a cloud IDE according to an exemplary embodiment. Figure 1 As shown, the method is used in a server corresponding to a cloud IDE and includes the following steps.

[0062] Step 101: receiving an access request sent by a user client, and acquiring login status attribute information of the user client according to the access request.

[0063] In the embodiments of this application, in the general development workflow, we will establish a local environment, including IDE and a complete set of local tools, but this local development mode has the following problems: the performance requirements of the development machine are high, and cold compilation takes 40 minutes; the development environment configuration is complex, and the tool environment can be solved through container technology or a series of version management tools, but the network, security and other environment configurations are relatively complex; it depends on specific devices; the giant code base is difficult to manage, and it takes a long time to switch Git branches in the giant code base. Therefore, the concept of remote development came into being, connecting to the cloud IDE on the remote server, completing the development work directly in the server environment, and eliminating the cost of rebuilding and maintaining a set of test environments locally.

[0064] The user client first creates a cloud IDE on the server for development work, and creates a Uniform Resource Locator (URL) corresponding to the cloud IDE to access the corresponding cloud IDE through the URL link, and the URL contains the cloud IDE logo. When the user enters a specific URL in the browser, the user client will send an access request based on the cloud IDE logo in the URL. After the server receives the access request, in order to ensure that only logged-in users can access the cloud IDE, the server obtains the login status attribute information contained in all access requests through the permission interception service to determine whether the user client is logged in.

[0065] Optionally, the step of obtaining the login status information of the user client according to the access request includes:

[0066] Obtaining user status text information in the access request;

[0067] The login status attribute information in the user status text information is read, wherein the login status attribute information includes: a logged in status or a not logged in status.

[0068] The user access request contains Cookie, i.e., user status text information. Cookie is a simple text file stored in the user client. This file is associated with a specific Web document and stores information when the user client accesses the Web document. When the user client accesses the Web document again, this information can be used by the document. Since "Cookie" has the characteristic of being stored on the client, it can realize the function of recording user personal information.

[0069] For example, a website may generate a unique ID for each visitor, and then save it in the form of a cookie file on each user's client. If you use a browser to access the Web, you will see all the cookies saved on the hard disk. In this folder, each file is a text file consisting of a "name / value" pair, and there is another file that stores information about all corresponding websites. Each cookie file here is a simple and ordinary text file. You can see which website has placed a cookie on the machine by looking at the file name.

[0070] The user status text information may include information corresponding to a variety of attributes, including a login status attribute, which indicates whether the user client is in a login state, and the login status attribute includes a logged-in state or a not-logged-in state.

[0071] Step 102: In response to the login status attribute information being the logged-in status, generate authentication pass information.

[0072] In an embodiment of the present application, after obtaining the user login status information according to the permission interception service, it is determined whether the user client is logged in. If the user client is in a logged-in state, it is determined that the user client has passed the authentication, and authentication pass information is generated. The permission interception service accepts and forwards the access request to further determine the permissions of the user client; if the user client is not logged in, it is determined that the user client has not passed the authentication, the permission interception service does not accept the access request, and the permissions of the user client cannot be further determined. If the user client wants to continue to access the cloud IDE, it needs to log in and resend the access request.

[0073] Step 103 , in response to the authentication pass information, obtaining the target cloud IDE identifier according to the access request, and determining the access rights of the user client to the target cloud IDE according to the permission list.

[0074] In the embodiment of the present application, if the authentication pass information is generated, the permission management service is used to further determine whether the user client has the permission to access the target cloud IDE. The permission management service can determine the target cloud IDE according to the identifier of the target cloud IDE in the access request, and obtain the permission list corresponding to the target cloud IDE.

[0075] contains the mapping relationship between the target cloud IDE and the user client identifier.

[0076] The terminal identifier obtains the corresponding user client, which has the authority to access the target cloud IDE.

[0077] Authentication is performed through the login status information in the access request, and the permissions of the user client are determined according to the permission list of the target cloud IDE, thereby realizing permission management of user access requests, reducing the risk of illegal users logging into the cloud IDE, and improving the security of cloud development.

[0078] Optionally, the access request includes an identifier of a target cloud IDE.

[0079] In the embodiment of the present application, the access request is sent through a URL. In a possible embodiment, the URL link domain name is in the format of id.xxx.com, where id is the identifier of the target cloud IDE, which is used to indicate a specific cloud IDE, and xxx.com represents a root domain name. For example, if a user client creates a cloud IDE in the server, and its id is 4, then if you want to access the cloud IDE, you need to enter 4.xxx.com in the browser.

[0080] Figure 2 is a flow chart of a method for confirming remote user permissions of a cloud IDE according to an exemplary embodiment. Figure 2 As shown, the method is used in the server corresponding to the cloud IDE, Figure 1 Step 103 in the method specifically includes the following steps.

[0081] Step 201: Obtain the target sub-authorization list in the authorization list according to the target cloud IDE identifier.

[0082] In the embodiment of the present application, the permission list includes multiple sub-permission lists, each of which is used to manage the access rights of a corresponding cloud IDE, and the sub-permission list includes a mapping relationship between the corresponding cloud IDE and the user client, wherein the user client included has the permission to access the corresponding cloud IDE. The corresponding target sub-permission list can be determined according to the target cloud IDE identifier.

[0083] Step 202: Determine the access rights of the user client to the target cloud IDE according to the target sub-authority list, wherein the target sub-authority list includes at least one client identifier.

[0084] In the embodiment of the present application, the client identifier corresponds to the user client. If the target sub-authority list includes the client identifier corresponding to the user client, it means that the user client has the authority to access the target cloud IDE.

[0085] Optional, Figure 2 Step 202 in the embodiment specifically includes:

[0086] In response to the target sub-authority list including a client identifier corresponding to the user client, it is determined that the user client can access the target cloud IDE.

[0087] Figure 3 is a flow chart of a method for confirming remote user permissions of a cloud IDE according to an exemplary embodiment. Figure 3 As shown, the method is used in the server corresponding to the cloud IDE, Figure 1 The method further comprises the following steps.

[0088] Step 301, receiving a creation request sent by a user client, and creating a cloud IDE according to the creation request;

[0089] In an embodiment of the present application, a user client can send a creation request to create a cloud IDE in a server. The creation request includes the project address of the cloud IDE, that is, the URL, and also includes information such as the project name, operating environment, and code source of the cloud IDE. The user client can configure a suitable cloud IDE according to its own needs.

[0090] Step 302: Receive permission configuration information sent by the user client, and generate a sub-permission list corresponding to the cloud IDE according to the permission configuration information, wherein the permission configuration information includes at least one client identifier.

[0091] In the embodiment of the present application, the permission configuration information sent by the user client is used to determine the permissions of the cloud IDE, that is, which user clients can access the cloud IDE.

[0092] Optional, Figure 3 Step 302 in the method specifically includes:

[0093] The client identifier in the permission configuration information is obtained, and a sub-permission list corresponding to the cloud IDE created by the client is generated according to the client identifier.

[0094] In an embodiment of the present application, a sub-permission list corresponding to the cloud IDE is created based on the client identifier in the permission configuration information, and the sub-permission list includes the client identifier in the permission configuration information. The user clients corresponding to these client identifiers have the permission to access this cloud IDE.

[0095] Figure 6 1 is a structural diagram of a cloud IDE remote user authority confirmation system according to an exemplary embodiment. Figure 6 As shown, the system includes: a user client, a permission interception service, a permission management service and a cloud IDE, and the permission interception service, the permission management service and the cloud IDE belong to the server.

[0096] If the user client wants to access a specific target cloud IDE, it needs to enter the URL link corresponding to the target cloud IDE to send an access request to the server. If the target cloud IDE is cloud IDE1, and its corresponding URL connection is 4.ide.com, enter "4.ide.com" in the browser to send an access request to the server. The permission interception service first receives the access request, and determines whether the user client is logged in based on the login status attribute information in the cookie. If the user client is not logged in, it generates authentication failure information; if the user client is logged in, it generates authentication success information and forwards the access request to the target IDE. The permission management service obtains the sub-permission list corresponding to the target cloud IDE based on the identifier of the target cloud IDE in the access request, and determines whether the client identifier corresponding to the user client exists in the sub-permission list. If the client identifier exists, it determines that the user client can access the target cloud IDE.

[0097] Figure 7 1 is a block diagram of a cloud IDE remote user authority confirmation device according to an exemplary embodiment. Figure 7 , the device 700 comprises:

[0098] The receiving module 710 is used to receive an access request sent by a user client, and obtain the login status attribute information of the user client according to the access request;

[0099] An authentication module 720 is used to generate authentication pass information in response to the login status attribute information being a logged-in status;

[0100] The authentication module 730 is used to obtain the target cloud IDE identifier according to the access request in response to the authentication pass information. Optionally, the authentication module includes:

[0101] A sub-authority list acquisition sub-module, used to acquire the target sub-authority list in the authority list according to the target cloud IDE identifier;

[0102] The permission determination submodule is used to determine the access rights of the user client to the target cloud IDE according to the target sub-permission list, wherein the target sub-permission list includes at least one client identifier.

[0103] Optionally, the authority determination submodule includes:

[0104] The permission determination unit is configured to determine that the user client can access the target cloud IDE in response to the target sub-permission list containing a client identifier corresponding to the user client.

[0105] Optionally, the device further comprises:

[0106] A creation module, used to receive a creation request sent by a user client, and create a cloud IDE according to the creation request;

[0107] The permission list generation module is used to receive permission configuration information sent by the user client, and generate a sub-permission list corresponding to the cloud IDE according to the permission configuration information, wherein the permission configuration information includes at least one client identifier.

[0108] Optionally, the permission list generating module includes:

[0109] The permission list generation submodule is used to obtain the client identifier in the permission configuration information, and generate a sub-permission list corresponding to the cloud IDE created by the client according to the client identifier.

[0110] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0111] Figure 8 1 is a block diagram of a device 800 for remote user authority confirmation of a cloud IDE according to an exemplary embodiment. For example, the device 800 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.

[0112] Reference Figure 8 , the device 800 may include one or more of the following components: a processing component 802 , a memory 804 , a power component 806 , a multimedia component 808 , an audio component 810 , an input / output (I / O) interface 812 , a sensor component 814 , and a communication component 816 .

[0113] The processing component 802 generally controls the overall operation of the device 800, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component 802 may include one or more processors 820 to execute instructions to complete all or part of the steps of the above-mentioned method. In addition, the processing component 802 may include one or more modules to facilitate the interaction between the processing component 802 and other components. For example, the processing component 802 may include a multimedia module to facilitate the interaction between the multimedia component 808 and the processing component 802.

[0114] The memory 804 is configured to store various types of data to support operations on the device 800. Examples of such data include instructions for any application or method operating on the device 800, contact data, phone book data, messages, pictures, videos, etc. The memory 804 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0115] The power supply component 806 provides power to the various components of the device 800. The power supply component 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device 800.

[0116] The multimedia component 808 includes a screen that provides an output interface between the device 800 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 808 includes a front camera and / or a rear camera. When the device 800 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

[0117] The audio component 810 is configured to output and / or input audio signals. For example, the audio component 810 includes a microphone (MIC), and when the device 800 is in an operating mode, such as a call mode, a recording mode, and a speech recognition mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in the memory 804 or sent via the communication component 816. In some embodiments, the audio component 810 also includes a speaker for outputting audio signals.

[0118] I / O interface 812 provides an interface between processing component 802 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include but are not limited to: home button, volume button, start button, and lock button.

[0119] The sensor assembly 814 includes one or more sensors for providing various aspects of status assessment for the device 800. For example, the sensor assembly 814 can detect the open / closed state of the device 800, the relative positioning of components, such as the display and keypad of the device 800, and the sensor assembly 814 can also detect the position change of the device 800 or a component of the device 800, the presence or absence of user contact with the device 800, the orientation or acceleration / deceleration of the device 800, and the temperature change of the device 800. The sensor assembly 814 may include a proximity sensor configured to detect the presence of a nearby object without any physical contact. The sensor assembly 814 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 814 may also include an accelerometer, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0120] The communication component 816 is configured to facilitate wired or wireless communication between the device 800 and other devices. The device 800 can access a wireless network based on a communication standard, such as WiFi, a carrier network (such as 2G, 3G, 4G or 5G), or a combination thereof. In an exemplary embodiment, the communication component 816 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 816 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0121] In an exemplary embodiment, the apparatus 800 may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors or other electronic components to perform the above method.

[0122] In an exemplary embodiment, a storage medium including instructions is also provided, such as a memory 804 including instructions, and the instructions can be executed by the processor 820 of the device 800 to complete the above method. Optionally, the storage medium can be a non-transitory computer-readable storage medium, for example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0123] Fig. 9is a block diagram of a device 900 for confirming remote user authority of a cloud IDE according to an exemplary embodiment. For example, the device 900 can be provided as a server. Fig. 9 , the apparatus 900 includes a processing component 922, which further includes one or more processors, and a memory resource represented by a memory 932 for storing instructions, such as an application, that can be executed by the processing component 922. The application stored in the memory 932 may include one or more modules, each corresponding to a set of instructions. In addition, the processing component 922 is configured to execute the instructions to perform the above method.

[0124] The device 900 may also include a power supply component 926 configured to perform power management of the device 900, a wired or wireless network interface 950 configured to connect the device 900 to a network, and an input / output (I / O) interface 958. The device 900 may operate based on an operating system stored in the memory 932, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, or the like.

[0125] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present disclosure are indicated by the following claims.

[0126] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A method for confirming remote user rights of a cloud integrated development environment IDE, characterized in that: include: Receiving an access request sent by a user client, and acquiring login status attribute information of the user client according to the access request; In response to the login status attribute information being a logged-in status, generating authentication pass information; In response to the authentication pass information, obtaining the target cloud IDE identifier according to the access request, and determining the access rights of the user client to the target cloud IDE according to the permission list; The permission list includes at least one sub-permission list corresponding to a cloud IDE, and determining the access rights of the user client to the target cloud IDE according to the permission list includes: Acquire the target sub-authority list in the authority list according to the target cloud IDE identifier; The access permission of the user client to the target cloud IDE is determined according to the target sub-permission list, wherein the target sub-permission list includes at least one client identifier.

2. The method according to claim 1, characterized in that The step of determining the access rights of the user client to the target cloud IDE according to the target sub-permission list specifically includes: In response to the target sub-authority list including a client identifier corresponding to the user client, it is determined that the user client can access the target cloud IDE.

3. The method according to claim 2, characterized in that The method further comprises: Receive a creation request sent by a user client, and create a cloud IDE according to the creation request; Receive permission configuration information sent by a user client, and generate a sub-permission list corresponding to the cloud IDE according to the permission configuration information, wherein the permission configuration information includes at least one client identifier.

4. The method according to claim 3, characterized in that The step of generating a sub-authority list corresponding to the cloud IDE according to the authority configuration information specifically includes: The client identifier in the permission configuration information is obtained, and a sub-permission list corresponding to the cloud IDE created by the client is generated according to the client identifier.

5. A cloud IDE remote user authority confirmation device, characterized in that: include: A receiving module, used to receive an access request sent by a user client, and obtain login status attribute information of the user client according to the access request; An authentication module, configured to generate authentication pass information in response to the login status attribute information being a logged-in status; An authentication module, configured to obtain the target cloud IDE identifier according to the access request in response to the authentication pass information, and determine the access rights of the user client to the target cloud IDE according to the permission list; Wherein, the authentication module includes: A sub-authority list acquisition sub-module, used to acquire the target sub-authority list in the authority list according to the target cloud IDE identifier; The permission determination submodule is used to determine the access rights of the user client to the target cloud IDE according to the target sub-permission list, wherein the target sub-permission list includes at least one client identifier.

6. An electronic device, characterized in that: include: processor; a memory for storing instructions executable by the processor; The processor is configured to execute the instructions to implement the cloud-based IDE remote user authority confirmation method as described in any one of claims 1 to 4.

7. A computer-readable storage medium, when the instructions in the storage medium are executed by a processor of an electronic device, enables the electronic device to execute the cloud-based IDE remote user authority confirmation method as described in any one of claims 1 to 4.

8. A computer program product, comprising a computer program, which, when executed by a processor, implements the method according to any one of claims 1 to 4.

Images