Data processing method, device, equipment and computer readable storage medium

By dynamically creating springboard Docker containers, the container orchestration technology is used to solve the problem that bastion machine resources cannot be allocated on demand, improving usage rate and stability, and achieving flexible allocation and secure access to bastion machine resources.

CN113765963BActive Publication Date: 2024-12-03BEIJING WODONG TIANJUN INFORMATION TECH CO LTD +1
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202010725591.4
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-07-24
Publication Date
2024-12-03
Estimated Expiration
2040-07-24

AI Technical Summary

Technical Problem

Traditional fortress service requires pre-applying fixed resources, cannot be allocated on demand, and the resource utilization rate is low.

Method used

By dynamically creating a springboard Docker container when a user requests, using container orchestration technology such as Kubernetes, the bastion machine function is realized, allowing the user's exclusive springboard Docker to access the target IP, and realize on-demand allocation and efficient utilization of resources.

Benefits of technology

It improves the utilization rate of bastion machine resources, ensures the stability and security of services, and realizes flexible allocation and recycling of resources through containerization.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113765963B_ABST
    Figure CN113765963B_ABST
Patent Text Reader

Abstract

The embodiment of the present invention provides a data processing method, device, equipment and computer-readable storage medium, the method comprising: in response to a user's bastion host request, creating a jump machine Docker for the user, the jump machine Docker is used to implement the bastion host function; in response to the user's access request to the target IP, accessing the target IP through the user's jump machine Docker. The method of the embodiment of the present invention dynamically creates a jump machine Docker for the user to implement the bastion host function when the user requests the bastion host. When accessing the target IP, the user can access the corresponding target IP through the jump machine Docker that is exclusive to the user, thereby realizing the containerization of the bastion host, realizing the on-demand allocation of bastion host resources, improving the utilization rate of the bastion host, and because the jump machine Docker is exclusive to the user, the stability and security of the bastion host service are guaranteed.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Embodiments of the present invention relate to the field of computer technology, and in particular, to a data processing method, apparatus, device, and computer-readable storage medium. Background Art

[0002] The bastion host is a security audit system that has undergone certain security reinforcement and can resist certain attacks. The main function of the bastion host is to audit and control the terminal operations of logging into the target business server and provide the terminal with single sign-on function. The terminal logs in to the target business server through the bastion host using the Secure Shell (SSH) protocol. The bastion host service can assist users to enter the actual target business server by IP and perform operations while meeting the Sarbanes-Oxley Act (SOX Act) audit and permission security.

[0003] In the process of implementing the present invention, the inventors found that there are at least the following problems in the prior art:

[0004] Traditional bastion host services require a batch of fixed resources to be applied for in advance as bastion hosts, that is, the bastion host IP is fixed. When the bastion host resources are insufficient, temporary capacity expansion is required, and on-demand allocation cannot be achieved. In addition, the utilization rate of bastion host resources is low. Summary of the invention

[0005] Embodiments of the present invention provide a data processing method, apparatus, device and computer-readable storage medium to solve the problem in the prior art that bastion host resources cannot be allocated on demand and have low utilization rates.

[0006] In a first aspect, an embodiment of the present invention provides a data processing method, including:

[0007] In response to a user's bastion host request, a jump server application container engine (Docker) is created for the user, and the jump server Docker is used to implement the bastion host function;

[0008] In response to the user's access request to the target IP, the target IP is accessed through the user's jump server Docker.

[0009] In a second aspect, an embodiment of the present invention provides a data processing method, which is applied to a cluster based on container orchestration technology, where a business Docker, a jump server Docker and a container orchestration service are running on the cluster, and the method includes:

[0010] In response to a bastion host request from a user, a jump server Docker is created for the user through the container orchestration service, wherein the jump server Docker is used to implement a bastion host function;

[0011] In response to the user's access request to the target IP, the service Docker corresponding to the target IP is accessed through the user's jump server Docker.

[0012] In a third aspect, an embodiment of the present invention provides a data processing device, including:

[0013] A container management module, used to create a jump server Docker for the user in response to a bastion host request from the user, wherein the jump server Docker is used to implement the bastion host function;

[0014] The bastion machine module is used to respond to the user's access request to the target IP and access the target IP through the user's jump server Docker.

[0015] In a fourth aspect, an embodiment of the present invention provides a data processing device, including:

[0016] A processor, a memory, and a computer program stored on the memory and executable on the processor;

[0017] Wherein, when the processor runs the computer program, the data processing method described in the first aspect is implemented.

[0018] In a fifth aspect, an embodiment of the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the data processing method described in the first aspect is implemented.

[0019] The data processing method, apparatus, device and computer-readable storage medium provided by the embodiments of the present invention dynamically create a jump server Docker for the user to implement the bastion host function in response to the user's bastion host request. In response to the user's access request to the target IP, the user can access the corresponding target IP through the jump server Docker exclusively used by the user, thereby realizing the containerization of the bastion host, realizing on-demand allocation of bastion host resources, and improving the utilization rate of the bastion host. Moreover, since the jump server Docker is exclusively used by the user, the stability and security of the bastion host service are guaranteed. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 A schematic diagram of a system framework provided by an embodiment of the present invention;

[0021] Figure 2 A flow chart of a data processing method provided in Embodiment 1 of the present invention;

[0022] Figure 3 A flow chart of a data processing method provided in Embodiment 2 of the present invention;

[0023] Figure 4 A schematic diagram of the structure of a data processing device provided in Embodiment 3 of the present invention;

[0024] Figure 5 A schematic diagram of the structure of a data processing device provided in Embodiment 4 of the present invention;

[0025] Figure 6 This is a schematic diagram of the structure of a data processing device provided in Embodiment 5 of the present invention.

[0026] The above drawings have shown clear embodiments of the present invention, which will be described in more detail below. These drawings and text descriptions are not intended to limit the scope of the present invention in any way, but to illustrate the concept of the present invention for those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0027] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Instead, they are merely examples of devices and methods consistent with some aspects of the present invention as detailed in the appended claims.

[0028] First, the terms involved in the embodiments of the present invention are explained:

[0029] Kubernetes: is an open source containerized application management platform for multiple hosts. The goal of Kubernetes is to make the deployment of containerized applications simple and efficient. Kubernetes provides a mechanism for application deployment, planning, updating, and maintenance.

[0030] Sarbanes-Oxley Act (SOX Act): It is a mandatory law for listed companies on the US stock exchange. The SOX Act will audit the IT systems, operation logs, bastion host logs, etc. of listed companies.

[0031] In addition, the terms "first", "second", etc. are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. In the description of the following embodiments, the meaning of "multiple" is more than two, unless otherwise clearly and specifically defined.

[0032] With the continuous development of Cloud Native, cloud services have occupied a very important position in the Internet market, and more and more developers and companies have begun to deploy applications on the cloud. Taking Kubernetes as an example, application development and deployment are very convenient. Because of the Service component, users can update, expand, and shrink capacity without worrying about whether IP changes are affected at the deployment level. However, due to the change of IP, the traditional bastion host service can no longer continue to provide services for cloud native applications.

[0033] The embodiment of the present invention can be specifically applied to a cluster based on container orchestration technology, for example, a cluster based on Kubernetes. The cluster is used to deploy a business system and a bastion host, and users need to access the business system through the bastion host. Figure 1 As shown, the cluster can run business Docker, jump server Docker, bastion host service, and container orchestration service (such as Figure 1 ), and basic services.

[0034] In this embodiment, the business Docker is used to deploy application services, which are business application services that users actually want to access. Users cannot access them directly and need to connect and access them through a jump server.

[0035] The jump server Docker is used to implement the function of the bastion host. When the user chooses to connect to an actual business Docker, the user request is synchronized to the selected actual business Docker, and the access data log is recorded and fed back to the bastion host service for auditing.

[0036] In this embodiment, the container orchestration service is a Kubernetes service as an example for exemplary description. The Kubernetes service is used to create and destroy the jump server Docker. The container orchestration service can also be implemented using Mesos, which is not specifically limited in this embodiment.

[0037] The basic service is used to verify whether the user has the authority to access the application service IP.

[0038] The bastion host service is used to provide a user interface UI for users to apply for a bastion host, and interact with basic services and Kubernetes services to call basic services and Kubernetes services to implement corresponding functions.

[0039] The data processing method provided by the embodiment of the present invention dynamically creates a jump server Docker for the user to implement the bastion host function when the user requests a bastion host. The user can access the corresponding target IP through the jump server Docker that is exclusive to the user, thereby realizing the containerization of the bastion host, and can realize on-demand allocation of bastion host resources, thereby improving the utilization rate of the bastion host. Moreover, since the jump server Docker is exclusive to the user, the stability and security of the bastion host service are guaranteed.

[0040] The following specific embodiments are used to describe in detail the technical solutions of the present invention and how the technical solutions of the present application solve the above-mentioned technical problems. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present invention will be described below in conjunction with the accompanying drawings.

[0041] Embodiment 1

[0042] Figure 2 This is a flow chart of the data processing method provided in the first embodiment of the present invention. Figure 2 As shown, the specific steps of this method are as follows:

[0043] Step S101: In response to a user's bastion host request, a jump server Docker is created for the user, and the jump server Docker is used to implement the bastion host function.

[0044] In this embodiment, based on the user's bastion host request, a user-exclusive jump server Docker can be created for the user, the bastion host can be containerized, and the bastion host can be allocated on demand.

[0045] Step S102: In response to the user's access request to the target IP, the target IP is accessed through the user's jump server Docker.

[0046] The target IP refers to the IP of the actual application service that the user requests to access, for example, it may be the IP of the service Docker where the actual application service that the user requests to access is located.

[0047] When a user requests to access the target IP, the target IP is accessed through the user's corresponding jump server Docker, which can realize the function of a bastion host.

[0048] The data processing method provided by the embodiment of the present invention dynamically creates a jump server Docker for the user to implement the bastion host function in response to the user's bastion host request. In response to the user's access request to the target IP, the user can access the corresponding target IP through the jump server Docker exclusively used by the user, thereby realizing the containerization of the bastion host, and can realize on-demand allocation of bastion host resources, thereby improving the utilization rate of the bastion host. Moreover, since the jump server Docker is exclusively used by the user, the stability and security of the bastion host service are guaranteed.

[0049] Embodiment 2

[0050] Figure 3 A flow chart of the data processing method provided for the second embodiment of the present invention. On the basis of the above-mentioned embodiment one, in this embodiment, the user's bastion host request includes the application service IP to be accessed. Before creating a jump machine Docker for the user, it is also possible to verify whether the user has the permission to access the application service IP based on the user's identity information; if the user has the permission to access the application service IP, a jump machine Docker is created for the user. In addition, when creating a jump machine Docker for the user, the jump machine Docker is created using the remaining fragmented resources of the physical machine; the jump machine Docker can also be destroyed after the jump machine Docker fails, so that the jump machine Docker resources can be recovered and resource utilization can be improved. Figure 3 As shown, the specific steps of this method are as follows:

[0051] Step S201, in response to the user's bastion host request, the user's bastion host request includes the application service IP to be accessed, and based on the user's identity information, verify whether the user has the authority to access the application service IP.

[0052] In actual applications, users can send bastion host requests to the bastion host service through the UI interface provided by the bastion host service.

[0053] The user's bastion host request includes the application service IP to be accessed. The application service IP to be accessed by the user may be the IP of the business Docker where the application service to be accessed by the user is located.

[0054] For example, based on Figure 1 In the architecture shown, after receiving the user's bastion host request, the bastion host service can send a first HTTP request to the basic service, which can carry the user's identity information and the application service IP required to be applied for. The basic service verifies whether the user has the authority to access the application service IP based on the user's identity information, and feeds back the verification result to the bastion host service.

[0055] The basic service may store the application service corresponding to the application service IP and the permission information of each user corresponding to the application service. The permission information of each user corresponding to the application service may include whether the user has the permission to access the application service and the specific permission information that the user has to access the application service.

[0056] Optionally, the verification results can be returned to the bastion service in JSON format.

[0057] If the verification result is that the user does not have the permission to access the application service IP, step S202 is executed to feedback a prompt message to the user to prompt the user that the user does not have the access permission to the application service IP, and the bastion host will not be allocated to the user.

[0058] If the verification result shows that the user has the permission to access the application service IP, steps S203-S204 are executed to create a jump server Docker for the user, that is, to allocate a bastion host exclusively for the user.

[0059] Step S202: Feedback prompt information to the user.

[0060] In this step, a prompt message can be displayed to the corresponding UI through the bastion host service. The prompt message is used to prompt the user that he does not have the access rights to the currently applied application service IP, so that the user can verify the IP and reapply.

[0061] Step S203: query the database to determine whether the user's jump server Docker exists.

[0062] The database at least stores the following information: user identification, application service IP information, and jump server IP. The user identification may be information such as a user account that can be used to uniquely identify a user. In addition, the database may also include information such as SSH connection jump server commands, passwords, creation time, authorization roles, and authorization duration, which are not specifically limited in this embodiment.

[0063] If the verification result shows that the user has permission to access the application service IP, the bastion host service can query its own database to determine whether the user's jump server Docker already exists.

[0064] Exemplarily, if there is a record containing the current user identifier in the database, if there is a record containing the current user identifier, it means that a jump server Docker has been allocated to the current user, that is, the user's jump server Docker already exists; if there is no record containing the current user identifier, it means that a jump server Docker has not been allocated to the current user, that is, the user's jump server Docker does not exist.

[0065] In this step, if it is determined that the user's jump server Docker does not exist, steps S204-S205 are executed to create a jump server Docker for the user, and the application service IP applied for by the user this time is recorded in the database.

[0066] If it is determined that the user's jump server Docker exists, there is no need to create a jump server Docker for the user again, and step S205 is directly executed to record the application service IP applied by the user this time into the database.

[0067] Step S204: If the user's jump server Docker does not exist, create a jump server Docker for the user, and record the mapping information between the user and the jump server Docker in the database.

[0068] In this embodiment, if it is determined that the user's jump server Docker does not exist, the bastion host service creates a jump server Docker for the user by calling a container orchestration service (such as a Kubernetes service).

[0069] Since business Docker usually occupies a large amount of physical machine resources, the remaining fragmented resources of the physical machine cannot be used. For example, if there are only 0.5 cores and 0.4 GB of memory resources left, it is impossible to allocate excess resources to the business Docker.

[0070] Preferably, the Kubernetes service uses the remaining fragment resources of the physical machine to create a jump server Docker, which can effectively utilize the fragment resources and improve resource utilization.

[0071] For example, you can create a jump server Docker with 0.1 core and 0.2G memory; or, you can create a jump server Docker with 0.1 core and 0.3G memory; or, you can create a jump server Docker with 0.2 core and 0.3G memory, and so on.

[0072] For example, the Kubernetes service creates a jump server Docker with 0.1 cores and 0.2 GB of memory resources according to the user's identity information.

[0073] Optionally, the bastion host service can poll the Kubernetes service interface based on the user's identity information to obtain information about whether the jump server Docker is created successfully.

[0074] When it is determined that the jump server Docker is created successfully, the mapping information between the user and the jump server Docker is recorded in the database.

[0075] Step S205: Add the application service IP to the application service IP information corresponding to the user in the database.

[0076] Among them, the application service IP information corresponding to the user in the database is used to store the application service IP that the user has applied for.

[0077] After the jump server Docker corresponding to the user is determined, in this step, the corresponding relationship between the application service IP and the user and the jump server Docker is recorded by adding the application service IP to the application service IP information corresponding to the user in the database.

[0078] Optionally, the database may store the application service IP information corresponding to each user separately, or the jump server Docker IP corresponding to the user and all application service IPs corresponding to the user may be recorded in the same data table, which is not specifically limited in this embodiment.

[0079] Optionally, a validity period can be set for each application service IP applied for by the user. During the validity period, the user can access the corresponding application service IP through the jump server Docker; after the validity period expires, the user cannot access the corresponding application service IP through the jump server Docker.

[0080] Step S206: Feedback the login information of the jump server Docker to the user.

[0081] After the jump server Docker corresponding to the user is determined, the login information of the jump server Docker corresponding to the user is fed back to the user.

[0082] Among them, the login information of the jump board Docker may include the jump board Docker IP, the login password, and other information required for users to log in to the jump board Docker, which is not specifically limited in this embodiment.

[0083] For example, a bastion host service may display the login information of the jump server Docker on the user interface.

[0084] Optionally, the bastion host service may also display a command containing login information of the jump server Docker on the user interface, and the user may connect to the corresponding jump server Docker by executing the command.

[0085] Step S207: In response to the user's request to connect to the bastion host, after the user's login information is verified, the application service IP to which the user has access rights is obtained according to the user's identity information.

[0086] When the user needs to connect to the bastion host, he sends a connection request to the corresponding jump server Docker through the local SSH tool according to the user's login information to connect to the jump server Docker. After the jump server Docker verifies the user's login information, the jump server Docker can obtain the user's identity information.

[0087] The jump server Docker sends a second HTTP request containing the user's identity information to the bastion server service. After receiving the second HTTP request, the bastion server service obtains the application service IP to which the user has access rights by querying the database according to the user's identity information.

[0088] Specifically, the application service IP that the user has applied for is obtained from the database through the bastion host service, and the basic service is used to verify whether the user currently has the access rights to the application service IP that the user has applied for. The application service IP that the user has access rights to is determined, so that the user's permissions can be verified again.

[0089] In a possible implementation, if the applied application service IP has a validity period, the application service IP applied by the user within the validity period is obtained from the database through the bastion host service.

[0090] For example, the jump server Docker can send a third HTTP request containing the user identity to the basic service. After receiving the third HTTP request, the basic service verifies whether the user currently has access rights to each application service IP that has been applied for, determines the application service IP that the user currently has access rights to among the application service IPs that the user has applied for, and then returns the application service IP that the user currently has access rights to to the bastion service.

[0091] Optionally, the basic service can return the application service IP address that the user currently has access rights to the bastion service in JSON format.

[0092] Furthermore, after obtaining the application service IP to which the user has access rights, the application service IP information corresponding to the user in the database can be updated based on the application service IP to which the user has access rights currently determined, to ensure that the user has access rights to all application service IPs recorded in the application service IP information corresponding to the user in the database.

[0093] For example, when the business Docker corresponding to the application service IP applied by the user becomes invalid, the business Docker may be allocated to another application service for use. In other words, the actual application service corresponding to the application service IP has changed, and the user may no longer have the authority to access the application service IP. Therefore, the corresponding information in the database needs to be updated to achieve accurate control of the user's access rights.

[0094] Exemplarily, after the bastion host service obtains the application service IP to which the user has access rights, it first updates the application service IP information corresponding to the user in the database.

[0095] Step S208: Display the application service IP addresses to which the user has access rights through the front-end page for the user to choose to access.

[0096] After determining the application service IPs to which the user has access rights, the application service IPs to which the user has access rights are displayed through a front-end page for the user to choose to access.

[0097] For example, after the bastion service obtains the application service IP to which the user has access rights, it can also return the application service IP to which the user has access rights in json format to the corresponding jump server Docker. The jump server Docker displays the application service IP to which the user has access rights on the corresponding front-end page, and the user can browse the application service IPs that currently have access rights and select a target IP to access.

[0098] Step S209: In response to the user's access request to the target IP, the target IP is accessed through the user's jump server Docker.

[0099] After the user selects a target IP, he can initiate an access request to the target IP through the front-end page corresponding to the jump server Docker, and implement various access operations on the application service corresponding to the target IP.

[0100] Every time a user accesses the application service corresponding to the target IP, it will pass through the jump server Docker and then be transparently transmitted to the business Docker of the application service corresponding to the target IP for operation.

[0101] Step S210: Record and store the access data log of the user accessing the target IP.

[0102] In this embodiment, each access operation of the user to the application service corresponding to the target IP will pass through the jump server Docker, and then transparently transmitted to the business Docker of the application service corresponding to the target IP for operation.

[0103] In this step, the access data log of the user accessing the target IP can be recorded and stored.

[0104] Specifically, the jump server Docker can record access data logs and send the access data logs to the bastion server service, which will store the access data logs to facilitate SOX audits.

[0105] Among them, the access data log may include target IP, user information, access time, access operation commands and other information. The information recorded in the access data log may include configuration and adjustment according to SOX audit requirements, which is not specifically limited in this embodiment.

[0106] Exemplarily, the jump server Docker can use a socket communication method based on the TCP protocol to send the access data log to the bastion server service.

[0107] In a possible implementation of this embodiment, after creating a jump server Docker for the user, steps S211 and S212 may be performed to set a validity period for the jump server Docker and to destroy the jump server Docker after the validity period expires, thereby reclaiming the resources occupied by the jump server Docker.

[0108] Step S211, setting and storing the validity period of the jump server Docker.

[0109] In this embodiment, this step is executed after creating a jump machine Docker for the user, and can be executed before, after, or in parallel with step S205. This embodiment is exemplified by executing after step S206. The order of step S206 and step S205 is not limited here.

[0110] Step S212: When the validity period of the jump server Docker expires, the jump server Docker is destroyed.

[0111] Optionally, after creating a jump board Docker for a user, the validity period of the jump board Docker can also be set and stored. In this step, when the validity period of the jump board Docker expires, the jump board Docker is destroyed to reclaim the resources corresponding to the jump board Docker.

[0112] In another implementation of this embodiment, when a recovery instruction for the bastion host of the specified IP is received, the jump server Docker corresponding to the specified IP can be destroyed to recover the corresponding resources.

[0113] For example, when it is confirmed that the user no longer needs the bastion host of the specified IP, or the user is not allowed to use the bastion host of the specified IP, a reclaim instruction for the bastion host of the specified IP can be issued to the bastion host service through the front-end page or in the form of a command.

[0114] The embodiment of the present invention cooperates with the container resource scheduling to realize the jump board Docker used by the user, which is a bastion host resource exclusively enjoyed by the user. The remaining fragmented resources of the physical machine can be used to create the jump board Docker, and the corresponding resources can be recovered after the jump board Docker fails. While ensuring the stability of the business, it can realize the on-demand allocation of bastion host resources and improve the utilization rate of the bastion host. Furthermore, in this embodiment, each time when applying for the bastion host service, it will be verified whether the user has the access rights to the applied application service IP, and when the user connects to the jump board Docker, it will be verified again whether the user has the access rights to the applied application service IP. Through the strong consistency verification method, it is verified twice whether the user has the access rights to the application service IP, which can ensure that the connection to the bastion host is trusted and safe.

[0115] Embodiment 3

[0116] Figure 4 The data processing device provided in the third embodiment of the present invention can execute the processing flow provided in the data processing method embodiment. Figure 4 As shown, the data processing device 30 includes: a container management module 301 and a bastion host module 302.

[0117] Specifically, the container management module 301 is used to respond to the user's bastion host request and create a jump machine Docker for the user, and the jump machine Docker is used to implement the bastion host function.

[0118] The bastion host module 302 is used to respond to the user's access request to the target IP and access the target IP through the user's jump server Docker.

[0119] The device provided in the embodiment of the present invention can be specifically used to execute the method embodiment provided in the above-mentioned embodiment 1, and the specific functions will not be repeated here.

[0120] The data processing method provided by the embodiment of the present invention dynamically creates a jump server Docker for the user to implement the bastion host function in response to the user's bastion host request. In response to the user's access request to the target IP, the user can access the corresponding target IP through the jump server Docker exclusively used by the user, thereby realizing the containerization of the bastion host, and can realize on-demand allocation of bastion host resources, thereby improving the utilization rate of the bastion host. Moreover, since the jump server Docker is exclusively used by the user, the stability and security of the bastion host service are guaranteed.

[0121] Embodiment 4

[0122] Figure 5FIG. 4 is a schematic diagram of the structure of a data processing device provided in Embodiment 4 of the present invention. Based on the above Embodiment 3, in this embodiment, Figure 5 As shown, the data processing device 30 further includes: an authority verification module 303, which is used to:

[0123] The user's bastion host request includes the application service IP to be accessed. Based on the user's identity information, it is verified whether the user has the authority to access the application service IP.

[0124] The container management module 301 is also used to create a jump server Docker for the user if the user has the authority to access the application service IP.

[0125] In a possible implementation, the container management module 301 is further configured to:

[0126] The database is queried to determine whether the user's jump board Docker exists; if the user's jump board Docker does not exist, a jump board Docker is created for the user, and the mapping information between the user and the jump board Docker is recorded in the database.

[0127] In a possible implementation, the container management module 301 is further configured to:

[0128] Add the application service IP to the application service IP information corresponding to the user in the database.

[0129] In a possible implementation, the container management module 301 is further configured to:

[0130] Use the remaining fragmented resources of the physical machine to create a jump server Docker.

[0131] In a possible implementation, the container management module 301 is further configured to:

[0132] Set and store the validity period of the springboard Docker.

[0133] In a possible implementation, the container management module 301 is further configured to:

[0134] When the validity period of the jump server Docker expires, the jump server Docker is destroyed.

[0135] In a possible implementation, the container management module 301 is further configured to:

[0136] Feedback the user the login information of the jump server Docker.

[0137] In a possible implementation, the authority verification module 303 is further used to:

[0138] In response to the user's request to connect to the bastion host, after the user's login information is verified, the application service IP to which the user has access rights is obtained based on the user's identity information; the application service IP to which the user has access rights is displayed through the front-end page for the user to choose to access.

[0139] In a possible implementation, the container management module 301 is further configured to:

[0140] Update the application service IP information to which the user has access rights in the database according to the application service IP to which the user has access rights.

[0141] In a possible implementation, the bastion server module 302 is further configured to:

[0142] Record and store the access data log of the user accessing the target IP.

[0143] The device provided in the embodiment of the present invention can be specifically used to execute the method embodiment provided in the above-mentioned embodiment 2, and the specific functions will not be repeated here.

[0144] The embodiment of the present invention cooperates with the container resource scheduling to realize the jump board Docker used by the user, which is a bastion host resource exclusively enjoyed by the user. The remaining fragmented resources of the physical machine can be used to create the jump board Docker, and the corresponding resources can be recovered after the jump board Docker fails. While ensuring the stability of the business, it can realize the on-demand allocation of bastion host resources and improve the utilization rate of the bastion host. Furthermore, in this embodiment, each time when applying for the bastion host service, it will be verified whether the user has the access rights to the applied application service IP, and when the user connects to the jump board Docker, it will be verified again whether the user has the access rights to the applied application service IP. Through the strong consistency verification method, it is verified twice whether the user has the access rights to the application service IP, which can ensure that the connection to the bastion host is trusted and safe.

[0145] Embodiment 5

[0146] Figure 6 This is a schematic diagram of the structure of a data processing device provided in Embodiment 5 of the present invention. Figure 6 As shown, the data processing device 100 includes: a processor 1001 , a memory 1002 , and a computer program stored in the memory 1002 and executable on the processor 1001 .

[0147] Among them, when the processor 1001 runs the computer program, it implements the data processing method provided by any of the above method embodiments.

[0148] The data processing method provided by the embodiment of the present invention dynamically creates a jump server Docker for the user to implement the bastion host function in response to the user's bastion host request. In response to the user's access request to the target IP, the user can access the corresponding target IP through the jump server Docker exclusively used by the user, thereby realizing the containerization of the bastion host, and can realize on-demand allocation of bastion host resources, thereby improving the utilization rate of the bastion host. Moreover, since the jump server Docker is exclusively used by the user, the stability and security of the bastion host service are guaranteed.

[0149] In addition, an embodiment of the present invention further provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the data processing method provided by any of the above method embodiments is implemented.

[0150] Those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example for illustration. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. The specific working process of the device described above can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.

[0151] It should be understood that, although the various steps in the flowchart in the above-described embodiment are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless there is a clear description in this article, the execution of these steps is not strictly limited in order, and they can be executed in other orders. Moreover, at least a portion of the steps in the figure may include a plurality of sub-steps or a plurality of stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and their execution order is not necessarily carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

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

[0153] It should be understood that the present invention is not limited to the exact construction that has 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 invention is limited only by the appended claims.

Claims

1. A data processing method, characterized in that: include: In response to a user's bastion host request, a jump server Docker is created for the user; the jump server Docker is used to implement the bastion host function; the user's bastion host request includes the application service IP to be accessed; In response to the user's access request to the target IP, access the target IP through the user's jump server Docker; In response to the user's bastion host request, before creating a jump server Docker for the user, the process further includes: Verify, based on the user's identity information, whether the user has the authority to access the application service IP; If the user has the permission to access the application service IP, a jump server Docker is created for the user; After creating a jump machine Docker for the user, it also includes: Add the application service IP to the application service IP information corresponding to the user in the database to record the corresponding relationship between the application service IP and the user and the jump server Docker; Feedback the login information of the jump server Docker to the user; In response to the user's request to connect to the bastion host, after the user's login information is verified, the application service IP to which the user has access rights is obtained according to the user's identity information; The application service IP to which the user has access rights is displayed through the front-end page for the user to choose to access.

2. The method according to claim 1, characterized in that In response to the user's bastion host request, creating a jump server Docker for the user includes: Query the database to determine whether there is a jump server Docker of the user; If the jump board Docker of the user does not exist, a jump board Docker is created for the user, and mapping information between the user and the jump board Docker is recorded in the database.

3. The method according to claim 2, characterized in that After recording the mapping information between the user and the jump server Docker in the database, the method further includes: The application service IP is added to the application service IP information corresponding to the user in the database.

4. The method according to any one of claims 1 to 3, characterized in that The step of creating a jump server Docker for the user includes: The jump server Docker is created by utilizing the remaining fragment resources of the physical machine.

5. The method according to any one of claims 1 to 3, characterized in that: After creating a jump machine Docker for the user, it also includes: The validity period of the jump server Docker is set and stored.

6. The method according to claim 5, characterized in that Also includes: When the validity period of the jump server Docker expires, the jump server Docker is destroyed.

7. The method according to claim 1, characterized in that After obtaining the application service IP to which the user has access rights according to the identity information of the user, the method further includes: According to the application service IP to which the user has access rights, the application service IP information to which the user has access rights in the database is updated.

8. The method according to claim 1, characterized in that Also includes: Record and store the access data log of the user accessing the target IP.

9. A data processing method, characterized in that: Applied to a cluster based on container orchestration technology, the cluster runs business Docker, jump machine Docker and container orchestration service, the method includes: In response to a user's bastion host request, a jump server Docker is created for the user through the container orchestration service, and the jump server Docker is used to implement the bastion host function; the user's bastion host request includes the application service IP to be accessed; In response to the user's access request to the target IP, access the service Docker corresponding to the target IP through the user's jump server Docker; Before the container orchestration service creates a jump server Docker for the user, the process further includes: Verify, based on the user's identity information, whether the user has the authority to access the application service IP; If the user has the permission to access the application service IP, then create the jump server Docker for the user; After creating the jump machine Docker for the user, it also includes: Add the application service IP to the application service IP information corresponding to the user in the database to record the corresponding relationship between the application service IP and the user and the jump server Docker; Feedback the login information of the jump server Docker to the user; In response to the user's request to connect to the bastion host, after the user's login information is verified, the application service IP to which the user has access rights is obtained according to the user's identity information; The application service IP to which the user has access rights is displayed through the front-end page for the user to choose to access.

10. A data processing device, characterized in that: include: A container management module is used to create a jump server Docker for the user in response to a user's bastion server request, wherein the jump server Docker is used to implement the bastion server function; the user's bastion server request includes the application service IP to be accessed; A bastion machine module, used to respond to the user's access request to the target IP and access the target IP through the user's jump server Docker; The authority verification module is used to verify whether the user has the authority to access the application service IP according to the identity information of the user; The container management module is further configured to create a jump server Docker for the user if the user has permission to access the application service IP; and to feed back login information of the jump server Docker to the user; The permission verification module is further used to add the application service IP to the application service IP information corresponding to the user in the database, so as to record the corresponding relationship between the application service IP and the user and the jump server Docker; In response to the user's request to connect to the bastion host, after the user's login information is verified, the application service IP to which the user has access rights is obtained based on the user's identity information; the application service IP to which the user has access rights is displayed through the front-end page for the user to choose to access.

11. A data processing device, characterized in that: include: A processor, a memory, and a computer program stored on the memory and executable on the processor; Wherein, when the processor runs the computer program, the method according to any one of claims 1 to 9 is implemented.

12. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 9 is implemented.

Citation Information

Patent Citations

  • Docker technology based cloud jump server system

    CN105610946A