Container system authorization method and server

Abstract

The application provides a container system authorization method and a server, and the method comprises the following steps: a first server receives a container system login request sent by a client; the first server decrypts an encrypted authorization license in response to the container system login request, and checks the decrypted authorization license; if the check is passed, the first server sends a container system login response to the client, so that the target client logs in the container system. The authorization of the Docker system is realized.

Description

Technical Field

[0001] This application relates to the field of computer technology, and more specifically, to a container system licensing method and server. Background Technology

[0002] Computer software is one of the main technological foundations of modern society and an important product of the information age. The protection of software has become an important aspect of protecting intellectual property rights.

[0003] In related technologies, for software licensing, the software installation terminal usually sends the licensing request to the software administrator, who then authenticates the software installation terminal. Once the authentication is valid, the software administrator returns the licensing information to the software installation terminal.

[0004] However, due to the isolation between Docker services, software licensing for Docker cannot be performed in this way. Summary of the Invention

[0005] The purpose of this application is to provide a container system licensing method and server to license Docker software systems, addressing the shortcomings of the prior art.

[0006] To achieve the above objectives, the technical solutions adopted in the embodiments of this application are as follows:

[0007] In a first aspect, one embodiment of this application provides a container system authorization method applied to a first server, the method comprising:

[0008] Receive container system login requests sent by the target client;

[0009] In response to the container system login request, the received encrypted license is decrypted and the decrypted license is verified.

[0010] If the verification passes, a container system login response is sent to the target client, enabling the target client to log in to the container system.

[0011] In some embodiments, the license includes: a license type and a valid usage period, and the verification of the decrypted license includes:

[0012] Determine whether the authorization type is a preset type and whether the effective usage period meets the preset effective conditions, and obtain the determination result of the authorization type and the determination result of the effective usage period;

[0013] The license is verified based on the results of the authorization type determination and the valid usage period determination.

[0014] In some embodiments, the license further includes: the license registration information of the first server, and the verification of the license based on the determination result of the license type and the determination result of the valid usage period includes:

[0015] If the determination result of the authorization type indicates that the authorization type is the preset type, and the determination result of the effective usage period indicates that the effective usage period meets the preset effective condition, then it is determined whether the authorization registration information is the same as the actual registration information of the first server;

[0016] If the authorized registration information is the same as the actual registration information, then the verification is successful;

[0017] If the authorized registration information is different from the actual registration information, the verification is deemed to have failed.

[0018] In some embodiments, verifying the license based on the determination result of the license type and the determination result of the effective usage period further includes:

[0019] If the result of the authorization type determination indicates that the authorization type is not the preset type, and the result of the valid usage period determination indicates that the valid usage period meets the preset valid condition, then the verification is determined to be successful.

[0020] In some embodiments, the method further includes:

[0021] The validity period in the license is updated by executing a scheduled task.

[0022] In some embodiments, the method further includes:

[0023] If the verification passes, the encrypted license will be added to the blacklist.

[0024] In some embodiments, the license further includes: the number of authorized clients corresponding to the container system; after sending the container system login response to the client, the method further includes:

[0025] Determine the number of login clients that log in to the container system;

[0026] If the number of logged-in clients exceeds the number of authorized clients, an access denial instruction is sent to the target client to prevent the target client from accessing the container system;

[0027] If the number of logged-in clients does not exceed the number of authorized clients, an access instruction is sent to the target client, enabling the target client to access the container system.

[0028] Secondly, another embodiment of this application provides a container system authorization method applied to a second server, the method comprising:

[0029] Map the system information file of the first server to a container file, and read the actual registration information of the first server from the container file;

[0030] The encryption process is performed based on the actual registration information and preset authorization information of the second server to generate an encrypted authorization license.

[0031] The encrypted license is decrypted, and the decrypted license is verified to obtain the verification result.

[0032] If the verification result indicates that the verification is successful, the encryption license is sent to the first server.

[0033] Thirdly, another embodiment of this application provides a container system licensing apparatus, comprising:

[0034] The receiving module is used to receive container system login requests sent by the target client;

[0035] The decryption module is used to respond to the container system login request and decrypt the received encrypted license; the verification module is used to verify the decrypted license.

[0036] The sending module is used to send a container system login response to the target client if the verification passes, so that the target client logs into the container system.

[0037] In some embodiments, the license includes: a license type and a valid usage period; the verification module is specifically used for:

[0038] Determine whether the authorization type is a preset type and whether the effective usage period meets the preset effective conditions, and obtain the determination result of the authorization type and the determination result of the effective usage period;

[0039] The license is verified based on the results of the authorization type determination and the valid usage period determination.

[0040] In some embodiments, the license further includes: the authorization registration information of the first server, and the verification module is specifically used for:

[0041] If the determination result of the authorization type indicates that the authorization type is the preset type, and the determination result of the effective usage period indicates that the effective usage period meets the preset effective condition, then it is determined whether the authorization registration information is the same as the actual registration information of the first server;

[0042] If the authorized registration information is the same as the actual registration information, then the verification is successful;

[0043] If the authorized registration information is different from the actual registration information, the verification is deemed to have failed.

[0044] In some embodiments, the verification module is specifically used for:

[0045] If the result of the authorization type determination indicates that the authorization type is not the preset type, and the result of the valid usage period determination indicates that the valid usage period meets the preset valid condition, then the verification is determined to be successful.

[0046] In some embodiments, it also includes:

[0047] The processing module is used to update the validity period in the license by executing a scheduled task.

[0048] In some embodiments, the processing module is further configured to: if the verification passes, add the encrypted license to the blacklist.

[0049] In some embodiments, the license further includes: the number of authorized clients corresponding to the container system, and also includes:

[0050] A determination module is used to determine the number of login clients logging into the container system;

[0051] The sending module is further configured to send an access denial instruction to the target client if the number of logged-in clients exceeds the number of authorized clients, so as to prohibit the target client from accessing the container system;

[0052] If the number of logged-in clients does not exceed the number of authorized clients, an access instruction is sent to the target client, enabling the target client to access the container system.

[0053] Fourthly, another embodiment of this application provides a container system licensing apparatus, comprising:

[0054] The processing module is used to map the system information file of the first server to a container file and read the actual registration information of the first server from the container file;

[0055] The encryption module is used to perform encryption processing based on the actual registration information and preset authorization information of the second server to generate an encryption authorization license;

[0056] The decryption module is used to decrypt the encrypted license and verify the decrypted license to obtain the verification result.

[0057] The sending module is used to send the encryption license to the first server if the verification result indicates that the verification is successful.

[0058] Fifthly, another embodiment of this application provides a server, including: a processor, a memory, and a bus, wherein the memory stores a computer program executable by the processor, and when the server is running, the processor communicates with the memory via the bus, and the processor executes the computer program to perform the method described in any of the first aspects.

[0059] In a sixth aspect, another embodiment of this application provides a server, including: a processor, a memory, and a bus, wherein the memory stores a computer program executable by the processor, and when the server is running, the processor communicates with the memory via the bus, and the processor executes the computer program to perform the method described in the second aspect.

[0060] In a seventh aspect, another embodiment of this application provides a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the method described in either the first or second aspect.

[0061] The beneficial effects of this application are:

[0062] This application provides a container system authorization method and server. The method includes: a first server receiving a container system login request from a client; the first server responding to the container system login request, decrypting an encrypted authorization license, and verifying the decrypted authorization license; if the verification passes, the first server sends a container system login response to the client, enabling the target client to log in to the container system. This achieves authorization for the Docker system. Attached Figure Description

[0063] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0064] Figure 1 A flowchart illustrating the container system licensing method provided in this application embodiment. Figure 1 ;

[0065] Figure 2 A flowchart illustrating the container system licensing method provided in this application embodiment. Figure 2 ;

[0066] Figure 3 A flowchart illustrating the container system licensing method provided in this application embodiment. Figure 3 ;

[0067] Figure 4 A flowchart illustrating the container system licensing method provided in this application embodiment. Figure 4 ;

[0068] Figure 5 A flowchart illustrating the container system licensing method provided in this application embodiment. Figure 5 ;

[0069] Figure 6 Schematic diagram of the container system licensing device provided in the embodiments of this application Figure 1 ;

[0070] Figure 7 Schematic diagram of the container system licensing device provided in the embodiments of this application Figure 2 ;

[0071] Figure 8 This is a schematic diagram of the server structure provided in an embodiment of this application;

[0072] Figure 9 This is a schematic diagram of the server structure provided in an embodiment of this application. Detailed Implementation

[0073] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. It should be understood that the accompanying drawings in this application are for illustrative and descriptive purposes only and are not intended to limit the scope of protection of this application. Furthermore, it should be understood that the schematic drawings are not drawn to scale. The flowcharts used in this application illustrate operations implemented according to some embodiments of this application. It should be understood that the operations in the flowcharts may not be implemented in sequence, and steps without logical contextual relationships may be reversed or implemented simultaneously. In addition, those skilled in the art, guided by the content of this application, may add one or more other operations to the flowcharts, or remove one or more operations from the flowcharts.

[0074] Furthermore, the described embodiments are merely some, not all, of the embodiments of this application. The components of the embodiments of this application described and illustrated herein can typically be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely to illustrate selected embodiments of the application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.

[0075] It should be noted that the term "comprising" will be used in the embodiments of this application to indicate the presence of the features declared thereafter, but does not exclude the addition of other features.

[0076] Docker is an open-source application container engine. Due to the isolation between services in the Docker system, current software licensing schemes are incompatible with Docker, resulting in licensing issues. Therefore, this application provides a flexible, effective, more widely applicable, more secure, and more manageable software licensing and authentication scheme for Docker. This scheme reads the registration information of the server deploying the Docker system, generates a corresponding license using a license generation module, verifies the license using a license verification module, and performs service authorization (i.e., if verification passes, the license is sent to the server deploying the Docker system). Finally, the server's service verification module verifies the license and updates the authorization status (i.e., if verification passes, the client can log in to the container system), thus enabling authorization for the Docker system.

[0077] The container system licensing method provided in this application will be described in detail below with reference to several specific embodiments.

[0078] Figure 1 A flowchart illustrating the container system licensing method provided in this application embodiment. Figure 1 ,like Figure 1 As shown, the method includes:

[0079] S101, The first server receives the container system login request sent by the client.

[0080] S102. The first server responds to the container system login request, decrypts the encrypted license, and verifies the decrypted license.

[0081] S103. If the verification passes, the first server sends a container system login response to the target client, enabling the target client to log in to the container system.

[0082] The target client can be any client that has a container system deployed, and the first server has a container system deployed, which can be a Docker system.

[0083] The client sends a container system login request to the first server. The first server receives the container system login request from the target client, decrypts the received encrypted license, and verifies the decrypted license. The encrypted license is sent to the first server by the second server, which is the container system's license management server. That is, the second server pre-generates the license, encrypts it to obtain the encrypted license, and sends the encrypted license to the first server. The first server can store the encrypted license. When it receives the container system login request from the target client, it responds to the container system login request by decrypting the pre-stored encrypted license and verifying the decrypted license.

[0084] The encrypted license can be obtained by encrypting the license using an encryption algorithm, including but not limited to Advanced Encryption Standard (AES) and MD5 Message-Digest Algorithm (MD5), to ensure the security of the transmitted content.

[0085] If the verification passes, the first server sends a container system login response to the target client, enabling the target client to log in to the container system. In some embodiments, the method further includes:

[0086] If the verification passes, the encrypted license will be added to the blacklist.

[0087] If the verification passes, the encrypted license is added to the blacklist. This prevents the encrypted license from being used again when a container system login request is received from a client, thus avoiding the multiple uses of a single license.

[0088] It should be noted that the license includes the effective usage period of the container system. When the first server verifies the license, it can check whether the effective usage period of the container system meets the preset validity conditions. If the preset validity conditions are met, it means that the first server and the client can use the container system within the effective trial period. If the preset validity conditions are not met, it means that the first server and the client cannot use the container system. The preset validity conditions can be that the effective trial period is greater than zero days.

[0089] Alternatively, the encrypted license can be uploaded to the management page of the container system on the first server, so that the first server can decrypt the encrypted license in the container environment corresponding to the container system and verify the decrypted license.

[0090] In the container system authorization method of this embodiment, the first server receives a container system login request sent by the client, responds to the container system login request by decrypting the encrypted authorization license, and verifies the decrypted authorization license. If the verification passes, the first server sends a container system login response to the client, enabling the target client to log in to the container system. This achieves authorization of the Docker system.

[0091] Figure 2 A flowchart illustrating the container system licensing method provided in this application embodiment. Figure 2 ,like Figure 2 As shown, in step S102, the first server verifies the decrypted license, including:

[0092] S201. The first server determines whether the authorization type is a preset type and whether the validity period meets the preset validity conditions, and obtains the judgment result of the authorization type and the judgment result of the validity period.

[0093] The default type can be the official usage type of the container system, and the license includes the license type and the validity period of the license.

[0094] The first server decrypts the encrypted license to obtain the license, then verifies the license type in the license to determine if the license type is a preset type and obtains the result of the license type determination. It also determines whether the validity period meets the preset validity conditions and obtains the result of the validity period determination. The preset validity condition can be that the validity period is greater than zero days.

[0095] S202. The first server verifies the license based on the results of the authorization type determination and the valid usage period determination.

[0096] The first server verifies the license based on the results of the authorization type determination and the validity period determination. In some embodiments, if the authorization type determination indicates that the authorization type of the container system is a preset type, and the validity period determination indicates that the validity period meets the preset validity conditions, then the license verification is deemed successful.

[0097] In some embodiments, if the determination result of the authorization type indicates that the authorization type of the container system is not a preset type and the determination result of the effective usage period indicates that the effective usage period meets the preset effective conditions, then the verification is determined to be successful. That is, when the authorization type of the container system is a built-in trial version, the determination result of the effective usage period is further determined to indicate whether the effective usage time meets the preset effective conditions. If the effective usage time meets the preset effective conditions, then the license verification is determined to be successful.

[0098] It should be noted that if the validity period meets the preset validity conditions, the license is valid, meaning the license has not expired. If the validity period does not meet the preset validity conditions, the license is invalid, meaning the license has expired and the license verification fails.

[0099] In the container system authorization method of this embodiment, the first server verifies the authorization license according to the authorization type and the effective usage period, which can ensure that the client can use the container system within the effective usage period.

[0100] Figure 3 A flowchart illustrating the container system licensing method provided in this application embodiment. Figure 3 ,like Figure 3 As shown, in step S202, the first server verifies the license based on the results of the authorization type determination and the valid usage period determination, including:

[0101] S301. If the determination result of the authorization type indicates that the authorization type is a preset type, and the determination result of the effective usage period indicates that the effective usage period meets the preset effective conditions, then determine whether the authorization registration information is the same as the actual registration information of the first server.

[0102] S302. If the authorized registration information is the same as the actual registration information, the first server determines that the verification has passed.

[0103] S303. If the authorized registration information is different from the actual registration information, the first server determines that the verification has failed.

[0104] The license also includes the authorization registration information of the first server. The authorization registration information includes, but is not limited to, the identifier of the central processing unit (CPU) and the media access control address (MAC) of the first server contained in the license. The actual registration information of the first server is the actual registration information of the first server obtained when the license is verified. The actual registration information includes, but is not limited to, the identifier of the actual CPU and the MAC address of the first server, which are unique identifiers of the first server.

[0105] If the result of the authorization type determination indicates that the authorization type is the preset type, and the result of the valid usage period determination indicates that the valid usage period meets the preset valid conditions, then it is determined whether the authorization registration information is the same as the actual registration information of the first server. If the authorization registration information is the same as the actual registration information, it means that the authorization license is valid, that is, the authorization license verification passes. If the authorization registration information is different from the actual registration information, it means that the authorization license is invalid, that is, the authorization license verification fails.

[0106] It should be noted that the license may also include other license-related information, such as: the authorizing entity, the number of authorized login clients, and remarks. The authorizing entity refers to the software provider of the container system, which indicates ownership of the software. The number of authorized login clients refers to the number of clients that can simultaneously log in to the container system as specified in the license. Remarks refer to some relevant remarks in the license.

[0107] In some embodiments, the method further includes:

[0108] Update the validity period of the license by executing a scheduled task.

[0109] After receiving the encrypted license from the second server, the first server can decrypt the license to obtain the license itself. The license includes a validity period. The first server can execute a scheduled task to update the validity period of the license. That is, every time the first server executes a scheduled task, the validity period of the license is updated. This can effectively reduce the impact of malicious modification of the first server's time on the validity period of the license, thus preventing malicious modification of the first server's time to extend the validity period of the license.

[0110] For example, the effective usage period is in days, and the timer cycle of the scheduled task is one day. If the scheduled task is executed at 0:00 AM each time, the effective usage period value in the license will be decremented by one each time. Alternatively, the first server executes the scheduled task once per minute and records a tag value. When the tag value is 24*60 (one day), the effective usage period value in the license will be decremented by one.

[0111] Figure 4 A flowchart illustrating the container system licensing method provided in this application embodiment. Figure 4 ,like Figure 4 As shown, in step S103, after the first server sends a container system login response to the target client, the method further includes:

[0112] S401. The first server determines the number of clients that will log in to the container system.

[0113] S402. If the number of logged-in clients exceeds the number of authorized clients, the first server sends an access denial instruction to the target client to prevent the target client from accessing the container system.

[0114] S403. If the number of logged-in clients does not exceed the number of authorized clients, the first server sends an access instruction to the target client, enabling the target client to access the container system.

[0115] The license also includes the number of authorized clients corresponding to the container system. The number of authorized login clients refers to the number of clients that can log in to the container system simultaneously as specified in the license.

[0116] The first server sends a container system login response to the target client. After the target client logs into the container system, the first server can also determine the number of clients logged into the container system, including the target client. If the number of logged-in clients exceeds the number of authorized clients, the first server sends an access denial instruction to the target client to prevent the target client from accessing the container system. If the number of logged-in clients does not exceed the number of authorized clients, the first server sends an access instruction to the target client, allowing the target client to access the container system. In other words, the first server implements client control, counts the number of successfully logged-in clients, and prohibits the target client from accessing the system when the number exceeds the number of authorized clients.

[0117] Figure 5 A flowchart illustrating the container system licensing method provided in this application embodiment. Figure 5 ,like Figure 5 As shown, the method includes:

[0118] S501, The second server maps the system information file of the first server to a container file, and reads the actual registration information of the first server from the container file.

[0119] The first server can be a user server, and the second server can be an authorization management server for the container system. The second server can obtain the system information file of the first server through the information acquisition service. The system information file includes the actual registration information of the first server, including but not limited to the unique identifier of the first server such as the actual CPU identifier and MAC address.

[0120] The container system can be the Docket system. Due to the virtualization and information isolation characteristics of the Docket system, it is not possible to directly read the registration information of the first server in the Docket system. Therefore, in this embodiment, the second server can obtain the system information file of the first server, map the system information file to the container file of the Docket system according to the mapping relationship between the system information file and the container file of the Docket system, and read the actual registration information of the first server from the container file.

[0121] For example, regarding CPU identifiers, due to the virtualization and information isolation characteristics of the Docker system, it is not possible to read the relevant CPU identifiers within the Docker system. Therefore, when deploying and starting the Docker system, the system information file of the first server is mapped to the corresponding container file, and the corresponding CPU information is read from the container file.

[0122] Regarding MAC addresses, since Docker creates different virtual network IPs when the system is created, and these IPs change in real time, it is impossible to obtain the MAC address from the IP. In this case, a mapping method can be used to read the MAC addresses of all network cards of the first server from the container, and then concatenate the read MAC addresses to obtain the MAC address of the first server.

[0123] S502. The second server encrypts the actual registration information and generates an encrypted license.

[0124] S503, the second server decrypts the encrypted license and verifies the decrypted license to obtain the verification result.

[0125] S504. If the verification result indicates that the verification is successful, the second server sends an encryption license to the first server.

[0126] The second server can use a preset license authorization tool to encrypt the actual registration information and other authorization information using an encryption algorithm to generate an encrypted authorization license. Other authorization information includes: authorization type, valid trial period of the license, authorizing entity, number of authorized login clients, and remarks.

[0127] The second server can use AES and MD5 algorithms to encrypt the actual registration information and other authorization information to obtain an authorization license, thereby ensuring the security of the transmitted content. The second server can also verify the accuracy of the authorization license. Therefore, the second server decrypts the encrypted authorization license and verifies the decrypted authorization license file to obtain the verification result. The authorization license file may include the authorization registration information of the first server. The authorization registration information may be the same as or different from the actual registration information. If they are different, it indicates that there is an error in the encryption and decryption process.

[0128] To ensure the accuracy of the encrypted license sent to the first server, the second server decrypts the license and verifies the registration information within it. If the verification result indicates that the registration information matches the actual registration information, the verification passes, and the encrypted license is sent to the first server. If the verification result indicates that the registration information does not match the actual registration information, the verification fails.

[0129] In the container system authorization method of this embodiment, after the second server generates the authorization license, it verifies the authorization license. If the verification passes, it sends the encrypted authorization license to the first server, thus ensuring the accuracy of the sent authorization license.

[0130] Figure 6 Schematic diagram of the container system licensing device provided in the embodiments of this application Figure 1 This device can be integrated into the first server. For example... Figure 6 As shown, the device includes:

[0131] The receiving module 601 is used to receive the container system login request sent by the target client;

[0132] The decryption module 602 is used to respond to the container system login request and decrypt the received encrypted license; the verification module 603 is used to verify the decrypted license.

[0133] The sending module 604 is used to send a container system login response to the target client if the verification passes, so that the target client logs into the container system.

[0134] In some embodiments, the license includes: a license type and a valid usage period; the verification module 603 is specifically used for:

[0135] Determine whether the authorization type is a preset type and whether the effective usage period meets the preset effective conditions, and obtain the determination result of the authorization type and the determination result of the effective usage period;

[0136] The license is verified based on the results of the authorization type determination and the valid usage period determination.

[0137] In some embodiments, the license further includes: the authorization registration information of the first server, and the verification module 603 is specifically used for:

[0138] If the determination result of the authorization type indicates that the authorization type is the preset type, and the determination result of the effective usage period indicates that the effective usage period meets the preset effective condition, then it is determined whether the authorization registration information is the same as the actual registration information of the first server;

[0139] If the authorized registration information is the same as the actual registration information, then the verification is successful;

[0140] If the authorized registration information is different from the actual registration information, the verification is deemed to have failed.

[0141] In some embodiments, the verification module 603 is specifically used for:

[0142] If the result of the authorization type determination indicates that the authorization type is not the preset type, and the result of the valid usage period determination indicates that the valid usage period meets the preset valid condition, then the verification is determined to be successful.

[0143] In some embodiments, it also includes:

[0144] Processing module 605 is used to update the validity period in the license by executing a scheduled task.

[0145] In some embodiments, the processing module 605 is further configured to: if the verification passes, add the encrypted license to the blacklist.

[0146] In some embodiments, the license further includes: the number of authorized clients corresponding to the container system, and also includes:

[0147] Module 606 is used to determine the number of login clients logging into the container system;

[0148] The sending module 604 is further configured to send an access denial instruction to the target client if the number of logged-in clients exceeds the number of authorized clients, so as to prohibit the target client from accessing the container system;

[0149] If the number of logged-in clients does not exceed the number of authorized clients, an access instruction is sent to the target client, enabling the target client to access the container system.

[0150] The description of the processing flow of each module in the device and the interaction flow between each module can be found in the relevant description of the method executed by the first server in the above method embodiment, and will not be described in detail here.

[0151] Figure 7 Schematic diagram of the container system licensing device provided in the embodiments of this application Figure 2 This device can be integrated into a second server. For example... Figure 7 As shown, the device includes:

[0152] Processing module 701 is used to map the system information file of the first server to a container file and read the actual registration information of the first server from the container file;

[0153] Encryption module 702 is used to perform encryption processing based on the actual registration information and preset authorization information of the second server to generate an encryption authorization license;

[0154] The decryption module 703 is used to decrypt the encrypted license and verify the decrypted license to obtain a verification result.

[0155] The sending module 704 is used to send the encryption license to the first server if the verification result indicates that the verification is successful.

[0156] The description of the processing flow of each module in the device and the interaction flow between each module can be found in the relevant description of the method executed by the second server in the above method embodiment, and will not be described in detail here.

[0157] Figure 8 This is a schematic diagram of the server structure provided in the embodiments of this application, such as... Figure 8 As shown, the server includes a processor 801, a memory 802, and a bus 803. The memory 802 stores a computer program that can be executed by the processor 801. When the server is running, the processor 801 and the memory 802 communicate through the bus 803. The processor 801 executes the computer program to perform the method executed by the first server in the above method embodiment.

[0158] Figure 9 This is a schematic diagram of the server structure provided in the embodiments of this application, such as... Figure 9As shown, the server includes a processor 901, a memory 902, and a bus 903. The memory 902 stores a computer program that can be executed by the processor 901. When the server is running, the processor 901 communicates with the memory 902 through the bus 903. The processor 901 executes the computer program to perform the method executed by the second server in the above method embodiment.

[0159] This application also provides a computer-readable storage medium storing a computer program, which is executed by a processor to perform the above-described method embodiments.

[0160] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems and devices described above can be referred to the corresponding processes in the method embodiments, and will not be repeated here. In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. Furthermore, multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed mutual coupling or direct coupling or communication connection can be through some communication interfaces; the indirect coupling or communication connection of devices or modules can be electrical, mechanical, or other forms.

[0161] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. If the functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0162] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application.

Claims

1. A method of authorizing a container system, the method comprising: The method is applied to a first server, the first server is a user server of a container system, and the method comprises the following steps: receiving a container system login request sent by a target client; decrypting an encrypted authorization license received in response to the container system login request, and verifying the decrypted authorization license, the encrypted authorization license being sent by a second server to the first server, the second server being an authorization management server of the container system, the encrypted authorization license being generated by the second server by mapping a system information file of the first server into a container file, reading actual registration information of the first server from the container file, and performing encryption processing according to the actual registration information; if the verification is passed, sending a container system login response to the target client, so that the target client logs in the container system; the authorization license further comprises: a number of authorized clients corresponding to the container system, after the container system login response is sent to the client, the method further comprises the following steps: determining the number of login clients logging in the container system; if the number of login clients exceeds the number of authorized clients, sending an access prohibition indication to the target client to prohibit the target client from accessing the container system; if the number of login clients does not exceed the number of authorized clients, sending an access indication to the target client, so that the target client accesses the container system.

2. The method of claim 1, wherein, the authorization license comprises: an authorization type and a valid use period, the verification of the decrypted authorization license comprises the following steps: determining whether the authorization type is a preset type and whether the valid use period meets a preset valid condition to obtain a determination result of the authorization type and a determination result of the valid use period; verifying the authorization license according to the determination result of the authorization type and the determination result of the valid use period.

3. The method of claim 2, wherein, the authorization license further comprises: authorization registration information of the first server, and the verification of the authorization license according to the determination result of the authorization type and the determination result of the valid use period comprises the following steps: if the determination result of the authorization type indicates that the authorization type is the preset type, and the determination result of the valid use period indicates that the valid use period meets the preset valid condition, determining whether the authorization registration information is same as actual registration information of the first server; if the authorization registration information is same as the actual registration information, it is determined that the verification is passed; if the authorization registration information is not same as the actual registration information, it is determined that the verification fails.

4. The method of claim 3, wherein, the verification of the authorization license according to the determination result of the authorization type and the determination result of the valid use period further comprises the following steps: if the determination result of the authorization type indicates that the authorization type is not the preset type, and the determination result of the valid use period indicates that the valid use period meets the preset valid condition, it is determined that the verification is passed.

5. The method of claim 2, wherein, the method further comprises the following steps: updating the valid use period in the authorization license by executing a timing task.

6. The method of claim 1, wherein, The method further comprises: If the verification passes, the encrypted authorization license is added to a blacklist.

7. A method of authorizing a container system, the method comprising: Applied to the second server, the method comprises: Mapping the system information file of the first server to a container file, reading the actual registration information of the first server from the container file; According to the actual registration information, performing encryption processing to generate an encrypted authorization license; Decrypting the encrypted authorization license, and verifying the decrypted authorization license to obtain a verification result; If the verification result indicates that the verification passes, the encrypted authorization license is sent to the first server, and the first server is used to execute the method of any one of claims 1-6.

8. A server, characterized by Comprise: A processor, a memory and a bus, the memory stores a computer program executable by the processor, when the server is running, the processor and the memory communicate through the bus, and the processor executes the computer program to execute the method of any one of claims 1-6.

9. A server, characterized by Comprise: A processor, a memory and a bus, the memory stores a computer program executable by the processor, when the server is running, the processor and the memory communicate through the bus, and the processor executes the computer program to execute the method of any one of claims 1-6.

Images