CN115378669A

CN115378669A - Method and device for confirming IDE remote user permission in cloud integrated development environment

Info

Publication number: CN115378669A
Application number: CN202210940202.9A
Authority: CN
Inventors: 刘正阳
Original assignee: Beijing Dajia Internet Information Technology Co Ltd
Current assignee: Beijing Dajia Internet Information Technology Co Ltd
Priority date: 2022-08-05
Filing date: 2022-08-05
Publication date: 2022-11-22

Abstract

The invention provides a method and a device for confirming IDE remote user permission in a cloud integrated development environment, and relates to the technical field of computers. The method comprises the following specific steps: receiving an access request sent by a user client, and acquiring login state attribute information of the user client according to the access request; responding to the login state attribute information as a logged-in state, and generating authentication passing information; and responding to the authentication passing information, acquiring a target cloud IDE identifier according to the access request, and determining the access authority of the user client to the target cloud IDE according to an authority list. According to the method and the device, the login state attribute information in the access request is authenticated, and the authority list is obtained according to the access request to determine the access authority of the user client to the target cloud IDE, so that the user client without authority is prevented from accessing the cloud IDE, and the safety of the cloud IDE is improved.

Description

Method and device for confirming IDE remote user permission in cloud integrated development environment

Technical Field

The disclosure relates to the technical field of computers, and particularly to a method and a device for confirming IDE remote user permission in a cloud integrated development environment.

Background

In the related art, a plurality of cloud IDE products are already used for remote development, and are all based on a mode used by a browser, that is, a specific http link is input in the browser to access a corresponding cloud IDE, the cloud IDE is deployed in a remote server, and is an integrated development environment deployed at a server, and a user can perform application development and test work, such as code editing, code debugging, code reconstruction and the like, through the cloud IDE.

However, the access mode confidentiality of the cloud IDE is poor at present, and if other users acquire the http link of the cloud IDE, the codes can be checked on the browser, so that the code development safety is reduced.

Disclosure of Invention

The invention provides a method and a device for confirming IDE remote user permission in a cloud integrated development environment. The technical scheme of the disclosure is as follows:

according to a first aspect of the embodiments of the present disclosure, a method for confirming rights to an IDE remote user in a cloud integrated development environment is provided, including:

receiving an access request sent by a user client, and acquiring login state attribute information of the user client according to the access request;

responding to the login state attribute information as a logged-in state, and generating authentication passing information;

and responding to the authentication passing information, acquiring a target cloud IDE identifier according to the access request, and determining the access authority of the user client to the target cloud IDE according to an authority list.

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

acquiring the target sub-authority list in the authority list according to the target cloud IDE identification;

and determining the access authority of the user client to the target cloud IDE according to the target sub-authority list, wherein the target sub-authority list comprises at least one client identifier.

Optionally, the step of determining the access right of the user client to the target cloud IDE according to the target sub-right list specifically includes:

and determining that the user client can access the target cloud IDE in response to the fact that the target sub-permission list comprises a client identifier corresponding to the user client.

Optionally, the method further includes:

receiving a creation request sent by a user client, and creating a cloud IDE according to the creation request;

and receiving permission configuration information sent by a user client, and generating 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.

Optionally, the step of generating the sub-permission list corresponding to the cloud IDE according to the permission configuration information specifically includes:

and acquiring a client identifier in the permission configuration information, and generating a sub-permission list corresponding to the cloud IDE created by the client according to the client identifier.

According to a second aspect of the embodiments of the present disclosure, there is provided a cloud IDE remote user permission confirmation apparatus, including:

the system comprises a receiving module, a sending module and a receiving module, wherein the receiving module is used for receiving an access request sent by a user client and acquiring login state attribute information of the user client according to the access request;

the authentication module is used for responding to the login state attribute information as a logged-in state and generating authentication passing information;

and the authentication module is used for responding to the authentication passing information, acquiring a target cloud IDE identifier according to the access request and determining the access authority of the user client to the target cloud IDE according to the authority list.

Optionally, the authentication module includes:

a sub-authority list obtaining sub-module, configured to obtain the target sub-authority list in the authority list according to the target cloud IDE identifier;

and the authority determining submodule is used for determining the access authority of the user client to the target cloud IDE according to the target sub-authority list, wherein the target sub-authority list comprises at least one client identifier.

Optionally, the permission determination sub-module includes:

and the permission determining unit is used for responding to a client identifier corresponding to the user client contained in the target sub-permission list and determining that the user client can access the target cloud IDE.

Optionally, the apparatus further comprises:

the system comprises a creation module, a service module and a service module, wherein the creation module is used for receiving a creation request sent by a user client and creating a cloud IDE according to the creation request;

and the permission list generating module is used for receiving permission configuration information sent by a user client and generating 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.

Optionally, the permission list generating module includes:

and the permission list generation submodule is used for acquiring the client identifier in the permission configuration information and generating a sub-permission list corresponding to the cloud IDE created by the client according to the client identifier.

According to a third aspect of an embodiment of the present disclosure, there is provided an electronic apparatus including:

a processor;

a memory for storing the processor-executable instructions;

wherein the processor is configured to execute the instructions to implement the cloud IDE remote user permission validation method of any of the above first aspects.

According to a fourth aspect of embodiments of the present disclosure, there is provided a computer-readable storage medium, wherein instructions of the storage medium, when executed by a processor of an electronic device, enable the electronic device to perform the cloud IDE remote user permission validation method according to any one of the above first aspects.

According to a fifth aspect of embodiments of the present disclosure, there is provided a computer program product comprising a computer program which, when executed by a processor, implements the method according to any one of the above first aspects.

The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects:

and authenticating through the login state attribute information in the access request, and acquiring the authority list according to the access request to determine the access authority of the user client to the target cloud IDE, so that the user client without authority is prevented from accessing the cloud IDE, and the safety of the cloud IDE is improved.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the disclosure and are not to be construed as limiting the disclosure.

Fig. 1 is a flow diagram illustrating a method for cloud IDE remote user permission validation in accordance with an exemplary embodiment.

Fig. 2 is a flowchart illustrating a method for cloud IDE remote user permission validation according to an exemplary embodiment.

Fig. 3 is a flowchart illustrating a method for cloud IDE remote user permission validation according to an exemplary embodiment.

Fig. 4 is a structural diagram of a cloud IDE user permission validation system provided in the related art.

Fig. 5 is a structural diagram of a cloud IDE user permission validation system provided in the related art.

Fig. 6 is a block diagram of a cloud IDE remote user permission validation system in accordance with an exemplary embodiment.

Fig. 7 is a block diagram illustrating a cloud IDE remote user permission validation apparatus according to an example embodiment.

FIG. 8 is a block diagram illustrating an apparatus in accordance with an example embodiment.

FIG. 9 is a block diagram illustrating an apparatus in accordance with an example embodiment.

Detailed Description

In order to make the technical solutions of the present disclosure better understood, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.

It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the foregoing drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the disclosure described herein are capable of operation in other sequences than those illustrated or described herein. The implementations described in the exemplary embodiments below do not represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure as recited in the claims appended hereto.

It should be noted that the user information (including but not limited to user device information, user personal information, etc.) referred to in the present disclosure is information authorized by the user or sufficiently authorized by each party.

An Integrated Development Environment (IDE) is an Integrated Development Environment deployed on a server side, and provides a cloud workstation for developers. The user does not need to install when using the cloud IDE, and the browser can be used by opening anytime and anywhere. The cloud IDE comprises the basic functions of IDE such as code highlighting, automatic completion, git integration, terminals and the like, and simultaneously supports real-time debugging, plug-in extension and the like, so that developers can be helped to quickly complete the development, compiling and deployment of various applications. The method for deploying the IDE program through the cloud server mainly comprises the following steps: ssh logs in the cloud server, an IDE program is registered as a system service, the system service is started, and access and use are carried out through the elastic public network IP bound by the cloud server and the port of the IDE process.

Currently, there are a plurality of cloud IDE products, such as Visual Studio Online, thia, etc., which are all based on the mode used by the browser, that is, a specific http link is input in the browser to access the corresponding cloud IDE, and perform remote development and test work. However, a great safety problem exists, and if an illegal user acquires the http link of the cloud IDE, the code can be checked on the browser.

In the related art, a method for authenticating a user is adopted to prevent an illegal user from logging in a cloud IDE, and fig. 4 is a structural diagram of a cloud IDE user permission confirmation system provided by the related art. As shown in fig. 4, a unified login interception service is added in the outer layer of the server to determine whether the current user sending the access request is logged in. If the login interception service judges that the current user does not log in, the current user needs to log in, and the user can access the cloud IDE resources in the server after logging in, so that only the internal user of a company can access the IDE, and the access request of an illegal external user can be intercepted because the illegal external user cannot log in.

However, the login interception service can only judge whether the current user is a login user, so that only users outside the company can be limited, and users outside the company are not allowed to log in the cloud IDE. However, inside the company, there is no restriction between users, such as user a creating a cloud IDE and not wishing others to access it. However, if user B obtains the remote access link to user a's IDE, user B is a cloud IDE that can be accessed to user a's creation without authorization from user a. Therefore, the hidden danger that an illegal user logs in the cloud IDE still exists.

Fig. 5 is a structural diagram of a cloud IDE user permission validation system provided in the related art. Judging whether a current user sending an access request logs in each cloud IDE service in a server or not, judging whether the current user has the authority of accessing the current cloud IDE or not, and if the current user logs in and has the authority of accessing the current cloud IDE, receiving the access request of the current user; otherwise, the access request of the current user is rejected.

However, in the method of fig. 4, a service module for authority management and judgment needs to be maintained inside each cloud IDE, which may increase the memory occupation of the IDE, increase the overall memory usage, and reduce the operating efficiency of the cloud IDE. And most cloud IDE do not provide a method for adding a permission management module, and have no way to customize and modify.

Fig. 1 is a flowchart illustrating a method for confirming remote user permissions in a cloud IDE according to an exemplary embodiment, where the method is applied to a server corresponding to the cloud IDE, as shown in fig. 1, and includes the following steps.

Step 101, receiving an access request sent by a user client, and obtaining login state attribute information of the user client according to the access request.

In the embodiment of the present application, in a general development workflow, we will establish a set of local environments including an IDE and a whole set of local tools, but the local development mode has the following problems: the requirement on the performance of a development machine is high, and cold compiling is carried out once for 40 minutes; the development environment configuration is complex, the tool environment can be solved by a container technology or a series of version management tools, but the environment configuration such as network and safety is complex; depending on the particular device; the huge code base is difficult to manage, and the huge code base needs a long time to switch the multiple Git branches. Therefore, the concept of remote development is developed at the end, the cloud IDE on the remote server is connected, the development work is directly completed in the server environment, and the cost of local reconstruction and maintenance of a set of test environment is saved.

The user client side firstly creates a cloud IDE (integrated development environment) for development work at a server, and creates a Uniform Resource Locator (URL) corresponding to the cloud IDE so as to access the corresponding cloud IDE through the URL link, wherein the URL includes an identifier of the cloud IDE. When a user inputs a specific URL in a browser, a user client sends an access request according to the identification of a cloud IDE in the URL. And after the server receives the access request, in order to ensure that only the login user can access the cloud IDE, the login state attribute information contained in all the access requests is obtained through the authority intercepting service to judge whether the user client logs in.

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

acquiring user state text information in the access request;

reading login state attribute information in the user state text information, wherein the login state attribute information comprises: logged or not logged in.

The user access request comprises Cookie, namely user state text information. A Cookie is a simple text file stored on a user's client that is associated with a particular Web document and stores information about when the user's client accesses the Web document. This information is available to the user client when the user client accesses the Web document again. Since "Cookie" has a characteristic that it can be saved on the client, it can implement a function of recording personal information of the user.

For example, a Web site may generate a unique ID for each visitor and store it in the form of a Cookie file on each user client. If the Web is accessed using a browser, all cookies stored on the hard disk are seen. Each file in the folder is a text file consisting of a "name/value" pair, and a file stores information of all corresponding Web sites. Each Cookie file is here a simple and plain text file. It can be seen through the file name which Web site placed the Cookie on the machine.

The user state text information may include information corresponding to a plurality of attributes, including a login state attribute, where the login state attribute represents whether the user client is in a login state, and the login state attribute includes a logged-in state or a logged-out state.

And 102, responding to the login state attribute information as a logged-in state, and generating authentication passing information.

In the embodiment of the application, after the user login state information is acquired according to the permission interception service, whether a user client logs in is judged, if the user client is in a logged-in state, the user client is determined to pass authentication, authentication passing information is generated, and the permission interception service receives and forwards the access request so as to further determine the permission of the user client; and if the user client is in a non-login state, determining that the user client is not authenticated, not accepting the access request by the permission interception service, and not further determining the permission of the user client, and if the user client wants to continue accessing the cloud IDE, retransmitting the access request after login.

And 103, responding to the authentication passing information, acquiring a target cloud IDE identifier according to the access request, and determining the access authority of the user client to the target cloud IDE according to an authority list.

In the embodiment of the application, if the authentication passing information is generated, whether the user client has the authority to access the target cloud IDE is further judged through the authority management service. The authority management service can determine a target cloud IDE according to the identification of the target cloud IDE in the access request and acquire an authority list corresponding to the target cloud IDE, wherein the authority list is

The method comprises the mapping relation from a target cloud IDE to a user client identifier, and according to a user client corresponding to the target cloud IDE

And the end identification acquires corresponding user clients which have the authority of accessing the target cloud IDE.

And authenticating through the login state information in the access request, and determining the authority of the user client according to the authority list of the target cloud IDE, so that the authority management of the user access request is realized, the risk that the cloud IDE is logged in by an illegal user is reduced, and the safety of cloud development is improved.

Optionally, the access request includes an identifier of the target cloud IDE.

In the embodiment of the application, the access request is sent through a URL. In one possible embodiment, the URL link domain name is in the format id.xxx.com, where id is the identification of the target cloud IDE and 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 with id 4 in a server, it needs to input 4.Xxx.com in a browser to access the cloud IDE.

Fig. 2 is a flowchart illustrating a method for confirming remote user permission in a cloud IDE according to an exemplary embodiment, where as shown in fig. 2, the method is used in a server corresponding to the cloud IDE, and step 103 in fig. 1 specifically includes the following steps.

Step 201, obtaining the target sub-permission list in the permission list according to the target cloud IDE identification.

In the embodiment of the application, the permission list includes a plurality of sub-permission lists, each sub-permission list is used for managing the access permission of a corresponding cloud IDE, the sub-permission lists include the mapping relation between the corresponding cloud IDE and the user client, and the user client included in the sub-permission lists has the permission to access the corresponding cloud IDE. And determining a corresponding target sub-authority list according to the target cloud IDE identification.

Step 202, determining the access authority of the user client to the target cloud IDE according to the target sub-authority list, wherein the target sub-authority list comprises at least one client identifier.

In the embodiment of the application, the client identifier corresponds to the user client, and if the target sub-permission list contains the client identifier corresponding to the user client, it is indicated that the user client has the permission to access the target cloud IDE.

Optionally, step 202 in fig. 2 specifically includes:

Fig. 3 is a flowchart illustrating a method for confirming remote user permissions in a cloud IDE according to an exemplary embodiment, where as shown in fig. 3, the method is applied to a server corresponding to the cloud IDE, and the method in fig. 1 further includes the following steps.

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

in this application embodiment, the user client can send and establish the request to establish the cloud IDE in the server, include the project address of cloud IDE in the request of establishing, also promptly the URL still includes information such as the project name, the operational environment, the code source of cloud IDE, and the user client can dispose suitable cloud IDE according to self demand.

Step 302, receiving authority configuration information sent by a user client, and generating a sub-authority list corresponding to the cloud IDE according to the authority configuration information, wherein the authority configuration information includes at least one client identifier.

In the embodiment of the application, the authority configuration information sent by the user client determines the authority of the cloud IDE, namely which user clients can access the cloud IDE.

Optionally, step 302 in fig. 3 specifically includes:

In the embodiment of the application, a sub-permission list corresponding to the cloud IDE is created according to the client identification in the permission configuration information, the sub-permission list comprises the client identification in the permission configuration information, and the user clients corresponding to the client identifications have permission to access the cloud IDE.

Fig. 6 is a block diagram of a cloud IDE remote user permission validation system in accordance with an exemplary embodiment. As shown in fig. 6, the system includes: the system comprises a user client, a permission interception service, a permission management service and a cloud IDE, wherein the permission interception service, the permission management service and the cloud IDE belong to a server.

The user client wants to access a specific target cloud IDE, and needs to input a URL link corresponding to the target cloud IDE to send an access request to the server. If the target cloud IDE is the cloud IDE1 and the corresponding URL connection is 4.ide.com, "4.ide.com" is input in the browser to send an access request to the server. The permission interception service firstly receives the access request, determines whether a user client logs in according to the login state attribute information in the Cookie, and generates authentication failure information if the user client is in a non-login state; and if the access request is in the login state, generating authentication passing information and forwarding the access request to the target IDE. The authority management service acquires a sub-authority list corresponding to the target cloud IDE according to the identification of the target cloud IDE in the access request, determines whether a client identification corresponding to the user client exists in the sub-authority list, and determines that the user client can access the target cloud IDE if the client identification exists.

Fig. 7 is a block diagram illustrating a cloud IDE remote user permission validation apparatus according to an exemplary embodiment. Referring to fig. 7, the apparatus 700 includes:

a receiving module 710, configured to receive an access request sent by a user client, and obtain login state attribute information of the user client according to the access request;

the authentication module 720, configured to generate authentication passing information in response to that the login state attribute information is a logged-in state;

an authentication module 730, configured to respond to the authentication passing information, and obtain a target cloud IDE identifier according to the access request, where the authentication module includes:

Optionally, the permission determination sub-module includes:

Optionally, the apparatus further comprises:

and the authority list generating module is used for receiving authority configuration information sent by a user client and generating a sub-authority list corresponding to the cloud IDE according to the authority configuration information, wherein the authority configuration information includes at least one client identifier.

Optionally, the permission list generating module includes:

and the permission list generation submodule is used for acquiring the client identification in the permission configuration information and generating a sub-permission list corresponding to the cloud IDE created by the client according to the client identification.

With regard to the apparatus in the above embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be described in detail here.

Fig. 8 is a block diagram illustrating an apparatus 800 for cloud IDE remote user permission validation in accordance with an example embodiment. For example, the apparatus 800 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, an exercise device, a personal digital assistant, and the like.

Referring to fig. 8, the apparatus 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.

The processing component 802 generally controls overall operation of the device 800, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing component 802 may include one or more processors 820 to execute instructions to perform all or a portion of the steps of the methods described above. Further, the processing component 802 can include one or more modules that facilitate interaction between the processing component 802 and other components. For example, the processing component 802 may include a multimedia module to facilitate interaction between the multimedia component 808 and the processing component 802.

The memory 804 is configured to store various types of data to support operation at the device 800. Examples of such data include instructions for any application or method operating on device 800, contact data, phonebook data, messages, pictures, videos, and so forth. The memory 804 may be implemented by any type or combination of volatile or non-volatile memory devices 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 or optical disks.

Power components 806 provide power to the various components of device 800. The power components 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the apparatus 800.

The multimedia component 808 includes a screen that provides an output interface between the device 800 and a 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 an input signal from a 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 boundary of a 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 facing camera and/or a rear facing camera. The front-facing camera and/or the rear-facing camera may receive external multimedia data when the device 800 is in an operating mode, such as a shooting mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

The audio component 810 is configured to output and/or input audio signals. For example, the audio component 810 includes a Microphone (MIC) configured to receive external audio signals when the apparatus 800 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may further be stored in the memory 804 or transmitted via the communication component 816. In some embodiments, audio component 810 also includes a speaker for outputting audio signals.

The I/O interface 812 provides an interface between the processing component 802 and peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to: a home button, a volume button, a start button, and a lock button.

The sensor assembly 814 includes one or more sensors for providing various aspects of state assessment for the device 800. For example, the sensor assembly 814 may detect the open/closed state of the device 800, the relative positioning of components, such as a display and keypad of the apparatus 800, the sensor assembly 814 may also detect a change in position of the apparatus 800 or a component of the apparatus 800, the presence or absence of user contact with the apparatus 800, orientation or acceleration/deceleration of the apparatus 800, and a change in temperature of the apparatus 800. 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 a light 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 acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

The communication component 816 is configured to facilitate communication between the apparatus 800 and other devices in a wired or wireless manner. The apparatus 800 may access a wireless network based on a communication standard, such as WiFi, an operator 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 further includes a Near Field Communication (NFC) module to facilitate short-range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, ultra Wideband (UWB) technology, bluetooth (BT) technology, and other technologies.

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, micro-controllers, microprocessors, or other electronic components for performing the above-described methods.

In an exemplary embodiment, a storage medium comprising instructions, such as the memory 804 comprising instructions, executable by the processor 820 of the apparatus 800 to perform the method described above is also provided. Alternatively, the storage medium may be a non-transitory computer readable storage medium, which may be, for example, a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.

Fig. 9 is a block diagram illustrating an apparatus 900 for cloud IDE remote user permission validation in accordance with an example embodiment. For example, the apparatus 900 may be provided as a server. Referring to fig. 9, the apparatus 900 includes a processing component 922, which further includes one or more processors, and memory resources, represented by memory 932, for storing instructions, such as applications, that are executable by the processing component 922. The application programs stored in memory 932 may include one or more modules that each correspond to a set of instructions. Further, the processing component 922 is configured to execute instructions to perform the above-described methods.

The device 900 may also include a power 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 apparatus 900 may operate based on an operating system, such as Windows Server, mac OS XTM, unixTM, linuxTM, freeBSDTM or the like, stored in the memory 932.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It will be understood that the present disclosure is not limited to the precise arrangements 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 IDE remote user permission in a cloud integrated development environment is characterized by comprising the following steps:

2. The method of claim 1, wherein the permission list includes a sub-permission list corresponding to at least one cloud IDE, and the determining the access permission of the user client to the target cloud IDE according to the permission list includes:

acquiring the target sub-permission list in the permission list according to the target cloud IDE identification;

3. The method according to claim 2, wherein the step of determining the access right of the user client to the target cloud IDE according to the target sub-right list specifically comprises:

4. The method of claim 3, further comprising:

5. The method according to claim 4, wherein the step of generating the sub-permission list corresponding to the cloud IDE according to the permission configuration information specifically comprises:

6. A long-range user permission confirmation device of high in clouds IDE, its characterized in that includes:

the system comprises a receiving module, a login state attribute information acquiring module and a login state attribute information acquiring module, wherein the receiving module is used for receiving an access request sent by a user client and acquiring the login state attribute information of the user client according to the access request;

7. The apparatus of claim 6, wherein the authentication module comprises:

8. An electronic device, comprising:

a processor;

a memory for storing the processor-executable instructions;

wherein the processor is configured to execute the instructions to implement the cloud IDE remote user permission validation method of any of claims 1-5.

9. A computer-readable storage medium having instructions which, when executed by a processor of an electronic device, enable the electronic device to perform the cloud IDE remote user permission validation method of any of claims 1 to 5.

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