Server-based remote login permission configuration method and device, and electronic equipment

Abstract

The application discloses a server-based remote login permission configuration method and device and electronic equipment. It is related to the field of financial technology or other related technical fields, wherein the method comprises: sending request information of a remote login request to a centralized management platform through a target client, the request information at least including unique identification information of the target client and role information of a target object; receiving the unique identification information and the role information sent by the target client through the centralized management platform, and determining a target server according to the unique identification information and a preset list, and sending the role information to the target server; receiving the role information sent by the centralized management platform through the target server, and configuring remote login permission for the target object according to the role information. The application solves the technical problem that related technologies configure remote login permission for users in an artificial manner, resulting in low permission configuration efficiency.

Description

Technical Field

[0001] This application relates to the field of financial technology or other related technical fields. Specifically, it relates to a server-based remote login permission configuration method, apparatus, and electronic device. Background Technology

[0002] Currently, when maintenance personnel remotely log in to the server to perform maintenance operations through the user centralized management system, they first need to complete the login action in the operation management platform. Then, the operation management platform will redirect them to the user centralized management system, which will verify the information of the corresponding personnel and issue the corresponding remote login permissions after successful matching.

[0003] In existing technologies, operation management platforms are often only configured with traditional operating system types such as Windows and Linux. When maintenance personnel log in to the operation management platform and initiate a remote login request to the server, the centralized user management system can only recognize the traditional operating system type configured on the operation management platform and sends the login request to the server corresponding to that traditional operating system type for personnel information verification. However, if a user logs in to the operation management platform on an operating system type not configured on the platform, since neither the operation management platform nor the centralized user management system can recognize that operating system type, remote login permissions need to be configured manually for the user. Manual methods are not only prone to operational errors but also result in low efficiency in permission configuration.

[0004] There is currently no effective solution to the above problems. Summary of the Invention

[0005] This application provides a server-based remote login permission configuration method, apparatus, and electronic device to at least solve the technical problem that related technologies involve manually configuring remote login permissions for users, resulting in low permission configuration efficiency.

[0006] According to one aspect of this application, a server-based remote login permission configuration method is provided, applied to a remote login permission configuration system, wherein the remote login permission configuration system includes a target client, a centralized management platform, and a target server, comprising: sending remote login request information to the centralized management platform through the target client, wherein the remote login request is a request for login to the target server initiated by a target object, the request information including at least the unique identifier information of the target client and the role information of the target object, the unique identifier information of the target client being used to characterize the operating system type corresponding to the target client, the operating system type corresponding to the target client being the same as the operating system type of the target operating system when the target object logs into the target client; receiving the unique identifier information and the role information sent by the target client through the centralized management platform, determining the target server based on the unique identifier information and a preset list, and sending the role information to the target server, wherein the preset list is used to record the correspondence between the unique identifier information and the target server; and receiving the role information sent by the centralized management platform through the target server, configuring remote login permissions for the target object based on the role information.

[0007] Further, determining the target server based on the unique identifier information and the preset list includes: detecting whether the unique identifier information exists in the preset list through the centralized management platform; if the unique identifier information exists in the preset list, determining the target server corresponding to the unique identifier information through the centralized management platform based on the correspondence.

[0008] Further, configuring remote login permissions for the target object based on the role information includes: detecting whether the role information exists in the database through the target server; if the role information exists in the database, obtaining the remote login permission information corresponding to the role information through the target server; and configuring the remote login permissions for the target object based on the remote login permission information through the target server.

[0009] Furthermore, after detecting whether the unique identifier information exists in the preset list through the centralized management platform, the method further includes: if the unique identifier information does not exist in the preset list, generating login failure information through the centralized management platform and sending the login failure information to the target client.

[0010] Furthermore, after detecting whether the role information exists in the database through the target server, the method further includes: if the role information does not exist in the database, prohibiting the configuration of the remote login permission for the target object through the target server.

[0011] Further, sending the remote login request information to the centralized management platform through the target client includes: responding to the server's remote login instruction through the target client to obtain the unique identification information, wherein the server's remote login instruction is an instruction for the target object to remotely log in to the target server, and the server's remote login instruction carries the target object's role information; generating the remote login request information based on the unique identification information and the target object's role information through the target client, and sending the remote login request information to the centralized management platform.

[0012] Furthermore, after configuring remote login permissions for the target object based on the role information, the method further includes: displaying the operation management functions corresponding to the remote login permissions on the target page of the target client through the target server, wherein the target page is the page for the target object to perform operation and maintenance.

[0013] According to another aspect of this application, a server-based remote login permission configuration device is also provided, applied to a remote login permission configuration system, wherein the remote login permission configuration system includes a target client, a centralized management platform, and a target server, comprising: a first sending module, configured to send request information of a remote login request to the centralized management platform through the target client, wherein the remote login request is a request initiated by a target object to log in to the target server, the request information including at least the unique identifier information of the target client and the role information of the target object, the unique identifier information of the target client being used to characterize the operating system type corresponding to the target client, the operating system type corresponding to the target client being the same as the operating system type of the target operating system in which the target object logs in when logging into the target client; a determining module, configured to receive the unique identifier information and the role information sent by the target client through the centralized management platform, and determine the target server based on the unique identifier information and a preset list, and send the role information to the target server, wherein the preset list is used to record the correspondence between the unique identifier information and the target server; and a configuration module, configured to receive the role information sent by the centralized management platform through the target server, and configure remote login permissions for the target object based on the role information.

[0014] According to another aspect of this application, a computer-readable storage medium is also provided, in which a computer program is stored, wherein the computer program is configured to execute the above-described server-based remote login permission configuration method at runtime.

[0015] According to another aspect of this application, an electronic device is also provided, the electronic device including one or more processors; a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors are configured to run the programs, wherein the programs are configured to execute the above-described server-based remote login permission configuration method at runtime.

[0016] In this application, firstly, the target client sends a remote login request to the centralized management platform. The remote login request is a request initiated by the target object to log in to the target server. The request information includes at least the unique identifier of the target client and the role information of the target object. The unique identifier of the target client is used to characterize the operating system type corresponding to the target client, and the operating system type corresponding to the target client is the same as the operating system type of the target operating system in which the target object logs in. Then, the centralized management platform receives the unique identifier and role information sent by the target client, determines the target server based on the unique identifier and a preset list, and sends the role information to the target server. The preset list records the correspondence between the unique identifier and the target server. Finally, the target server receives the role information sent by the centralized management platform and configures remote login permissions for the target object based on the role information.

[0017] In the above process, by marking the operating system type corresponding to the target client as the unique identifier of the target client, remote login permission configuration is achieved based on the operating system type of the target operating system when the target object logs into the target client. The centralized management platform can automatically identify the operating system type of the target client and the corresponding target server based on the unique identifier and the correspondence recorded in the preset list. The target server automatically configures remote login permissions for the target object, achieving automatic identification of the operating system type of the target object when logging into the target client and configuring the corresponding remote login permissions. This eliminates the need for a manual application process to the administrator to manually issue remote login permissions, avoiding the time-consuming problem caused by human error. This improves the efficiency of permission configuration and solves the technical problem of low efficiency caused by manually configuring remote login permissions for users in related technologies. Attached Figure Description

[0018] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0019] Figure 1 This is a flowchart of an optional server-based remote login permission configuration method according to an embodiment of this application;

[0020] Figure 2 This is a flowchart of another optional server-based remote login permission configuration method according to an embodiment of this application;

[0021] Figure 3 This is a schematic diagram of an optional server-based remote login permission configuration device according to an embodiment of this application;

[0022] Figure 4 This is a schematic diagram of an optional electronic device according to an embodiment of this application. Detailed Implementation

[0023] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0024] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0025] It should be noted that the server-based remote login permission configuration method, device, and electronic device of this application can be used in the field of fintech, as well as in other fields other than fintech. The application fields of the server-based remote login permission configuration method, device, and electronic device of this application are not limited.

[0026] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation portals are provided for users to choose to authorize or refuse.

[0027] Example 1

[0028] According to an embodiment of this application, an optional server-based remote login permission configuration method is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0029] Figure 1 This is a flowchart of an optional server-based remote login permission configuration method according to an embodiment of this application, such as... Figure 1 As shown, this method is applied to a remote login permission configuration system, which includes a target client, a centralized management platform, and a target server. The method includes the following steps:

[0030] Step S101: The remote login request information is sent to the centralized management platform through the target client. The request information includes at least the unique identifier of the target client and the role information of the target object.

[0031] In an optional embodiment, a remote login permission configuration system can serve as the execution subject of the server-based remote login permission configuration method in this application embodiment. For ease of description, the remote login permission configuration system will be referred to as the system below.

[0032] In step S101, the remote login request is a request initiated by the target object to log in to the target server. The unique identification information of the target client is used to characterize the operating system type corresponding to the target client. The operating system type corresponding to the target client is the same as the operating system type of the target operating system in which the target object is logged in when logging into the target client.

[0033] Optionally, the operating system type includes, but is not limited to, Windows operating system type, Linux operating system type, cloud operating system type, and network device-specific operating system type.

[0034] Optionally, the target client is the operation management platform where the target object logs in under the target operating system. Optionally, the operation management platform is configured with L single sign-on controls, each single sign-on control corresponding to an operating system type. The target single sign-on control corresponding to the target client is one of the L single sign-on controls, and the operating system type corresponding to this target single sign-on control is the same as the operating system type of the target operating system on which the target object logs in to the operation management platform.

[0035] Optionally, such as Figure 2 As shown, the system sends the remote login request information to the centralized management platform through the target client, including: when the system detects a login action of the target object logging into the operation management platform via a URL, the system automatically identifies the operating system type of the target operating system on the operation management platform, configures a target single sign-on control for the target object that matches the operating system type, and sends the remote login request information to the centralized management platform through the target single sign-on control. For example, when the target object logs into the operation management platform on a cloud operating system, the operation management platform automatically configures a cloud operating system type single sign-on control for the target object and sends the remote login request information to the centralized management platform through the cloud operating system type single sign-on control.

[0036] Step S102: Receive the unique identifier information and role information sent by the target client through the centralized management platform, determine the target server based on the unique identifier information and the preset list, and send the role information to the target server.

[0037] In step S102, a preset list is used to record the correspondence between unique identifier information and target servers. For example, when unique identifier information represents the cloud operating system type, it corresponds to a server of that cloud operating system type.

[0038] Optionally, the target server can be a web server.

[0039] Optionally, such as Figure 2 As shown, the system can receive unique identifier information and role information sent by the target client through a centralized management platform. Then, the system can check if unique identifier information exists in a preset list through the centralized management platform. If unique identifier information exists in the preset list, the system can determine the target server corresponding to the unique identifier information based on the correspondence in the preset list through the centralized management platform, and send the role information to the target server.

[0040] Step S103: Receive role information sent by the centralized management platform through the target server, and configure remote login permissions for the target object based on the role information.

[0041] In step S103, as Figure 2 As shown, the system can receive role information sent by the centralized management platform through the target server, and check whether the target object's role information exists in the database through the target server. If the target object's role information exists in the database, remote login permissions are configured for the target object based on the role information.

[0042] Based on the scheme defined in steps S101 to S103 above, it can be understood that in this embodiment, firstly, the target client sends a remote login request to the centralized management platform. The remote login request is a request initiated by the target object to log in to the target server. The request information includes at least the unique identifier of the target client and the role information of the target object. The unique identifier of the target client is used to characterize the operating system type corresponding to the target client, and the operating system type corresponding to the target client is the same as the operating system type of the target operating system in which the target object logs in. Then, the centralized management platform receives the unique identifier and role information sent by the target client, determines the target server based on the unique identifier and a preset list, and sends the role information to the target server. The preset list is used to record the correspondence between the unique identifier and the target server. Finally, the target server receives the role information sent by the centralized management platform and configures remote login permissions for the target object based on the role information.

[0043] It should be noted that in the above process, by marking the operating system type corresponding to the target client as the unique identifier of the target client, remote login permission configuration is achieved based on the operating system type of the target operating system when the target object logs into the target client. The centralized management platform can automatically identify the operating system type of the target client and the corresponding target server based on the unique identifier and the correspondence recorded in the preset list. The target server automatically configures remote login permissions for the target object, thus automatically identifying the operating system type of the target object when logging into the target client and configuring the corresponding remote login permissions. This eliminates the need for a manual application process to the administrator to manually issue remote login permissions, avoiding the time-consuming problem caused by human error. This improves the efficiency of permission configuration and solves the technical problem of low efficiency caused by manually configuring remote login permissions for users in related technologies.

[0044] Optionally, in the server-based remote login permission configuration method provided in this application embodiment, determining the target server based on unique identifier information and a preset list includes: the system can detect whether unique identifier information exists in the preset list through a centralized management platform; if unique identifier information exists in the preset list, the system can determine the target server corresponding to the unique identifier information through the centralized management platform based on the correspondence.

[0045] In an optional embodiment, after detecting whether unique identification information exists in the preset list through the centralized management platform, the method further includes: if no unique identification information exists in the preset list, the system can generate login failure information through the centralized management platform and send the login failure information to the target client.

[0046] To improve system security, in this embodiment, such as Figure 2 As shown, the system uses a centralized management platform to check whether unique identifier information exists in a preset list to determine whether to allow the remote login operation to continue. For example, if unique identifier information does not exist in the preset list, the system prohibits the remote login operation and generates a login failure message through the centralized management platform, which is then sent to the target client; if unique identifier information exists in the preset list, the remote login operation is allowed to continue.

[0047] To further improve the efficiency of permission configuration and avoid the problem of permission configuration failure due to the inability to accurately match the target server, in this embodiment, as follows: Figure 2 As shown, the system can determine the target server corresponding to the unique identifier information through the correspondence recorded in the preset list.

[0048] Optionally, in the server-based remote login permission configuration method provided in this application embodiment, configuring remote login permissions for the target object based on role information includes: the system can detect whether role information exists in the database through the target server; if role information exists in the database, the system can obtain the remote login permission information corresponding to the role information through the target server; and then configure remote login permissions for the target object based on the remote login permission information through the target server.

[0049] In another optional embodiment, after detecting whether role information exists in the database through the target server, the method further includes: if the role information does not exist in the database, the system can prevent the configuration of remote login permissions for the target object through the target server.

[0050] To improve system security and prevent the data on the target server from being arbitrarily modified, in this embodiment, as follows: Figure 2 As shown, the system can determine whether to configure remote login permissions for the target object by checking if role information exists in the database on the target server. For example, if role information exists in the database, the system can obtain the remote login permission information corresponding to the role information from the target server; then, the target server can configure remote login permissions for the target object based on the remote login permission information. If role information does not exist in the database, the system can prohibit the configuration of remote login permissions for the target object from being configured through the target server.

[0051] Optionally, in the server-based remote login permission configuration method provided in this application embodiment, the remote login request information is sent to the centralized management platform through the target client. This includes: the system can respond to the server remote login instruction through the target client to obtain unique identification information, wherein the server remote login instruction is an instruction for the target object to remotely log in to the target server, and the server remote login instruction carries the role information of the target object; then, the target client generates the remote login request information based on the unique identification information and the role information of the target object, and sends the remote login request information to the centralized management platform.

[0052] To improve permission configuration efficiency and avoid the problem of the centralized management platform being unable to identify the operating system type of the target client, in this embodiment, the system obtains the unique identification information corresponding to the target client by responding to the server's remote login command through the target client. Then, the system generates a remote login request based on the unique identification information and the target object's role information carried in the server's remote login command, and sends the remote login request to the centralized management platform. For example, when the target object logs into the operation management platform (i.e., the target client) through the operation management platform's URL under the target operating system, the system identifies the operating system type corresponding to the target operating system and calls the target single sign-on control in the operation management platform. The target object enters its account and password through the target single sign-on control interface to perform the login operation, triggering the server's remote login command. The system responds to the server's remote login command through the operation management platform and obtains the unique identification information. Then, the system generates a remote login request based on the unique identification information and the target object's role information through the target client, and sends the remote login request to the centralized management platform.

[0053] Optionally, in the server-based remote login permission configuration method provided in this application embodiment, after configuring remote login permissions for the target object according to role information, the system can display the operation management functions corresponding to the remote login permissions on the target page of the target client through the target server, wherein the target page is the page for the target object to perform operation and maintenance.

[0054] In this embodiment, after configuring remote login permissions for the target object based on role information, the system can display the operation management functions corresponding to the remote login permissions on the target page of the target client through the target server, so as to facilitate the target object to perform operation and maintenance operations on the target server on the target page and improve the user experience.

[0055] Therefore, the method provided in this application, by marking the operating system type corresponding to the target client as the unique identifier of the target client, enables remote login permission configuration based on the operating system type of the target operating system when the target object logs into the target client. The centralized management platform can automatically identify the operating system type of the target client and the corresponding target server based on the unique identifier and the correspondence recorded in the preset list. The target server automatically configures remote login permissions for the target object. This allows maintenance personnel (i.e., the target object) to automatically identify the operating system type of the target object when logging into the target client and configure the corresponding remote login permissions without switching the website of the operation management platform. It also eliminates the need for manual application to the administrator to manually issue remote login permissions, avoiding the time-consuming problem caused by human error. This improves the efficiency of permission configuration and solves the technical problem of low efficiency caused by manual configuration of remote login permissions in related technologies.

[0056] Example 2

[0057] According to an embodiment of this application, an embodiment of a server-based remote login permission configuration device is provided, wherein... Figure 3 This is a schematic diagram of an optional server-based remote login permission configuration device according to an embodiment of this application, such as... Figure 3 As shown, the device includes:

[0058] The first sending module 301 is used to send the request information of the remote login request to the centralized management platform through the target client. The remote login request is a request initiated by the target object to log in to the target server. The request information includes at least the unique identification information of the target client and the role information of the target object. The unique identification information of the target client is used to characterize the operating system type corresponding to the target client. The operating system type corresponding to the target client is the same as the operating system type of the target operating system in which the target object is logged in when logging into the target client.

[0059] The determination module 302 is used to receive the unique identification information and role information sent by the target client through the centralized management platform, determine the target server based on the unique identification information and the preset list, and send the role information to the target server. The preset list is used to record the correspondence between the unique identification information and the target server.

[0060] Configuration module 303 is used to receive role information sent by the centralized management platform through the target server, and configure remote login permissions for the target object based on the role information.

[0061] It should be noted that the first sending module 301, the determining module 302 and the configuration module 303 mentioned above correspond to steps S101 to S103 in the above embodiment 1. The examples and application scenarios implemented by the three modules and the corresponding steps are the same, but are not limited to the content disclosed in the above embodiment 1.

[0062] Optionally, the determining module includes: a first detection unit, used to detect whether unique identification information exists in the preset list through a centralized management platform; and a first determining unit, used to determine the target server corresponding to the unique identification information based on the correspondence relationship through the centralized management platform when unique identification information exists in the preset list.

[0063] Optionally, the configuration module includes: a second detection unit, used to detect whether role information exists in the database through the target server; a first acquisition unit, used to acquire remote login permission information corresponding to the role information through the target server if the role information exists in the database; and a first configuration unit, used to configure remote login permissions for the target object based on the remote login permission information through the target server.

[0064] Optionally, the server-based remote login permission configuration device further includes: a generation module, which, after detecting whether unique identification information exists in the preset list through the centralized management platform, generates login failure information through the centralized management platform if no unique identification information exists in the preset list, and sends the login failure information to the target client.

[0065] Optionally, the server-based remote login permission configuration device further includes a blocking module, which, after detecting whether role information exists in the database through the target server, blocks the configuration of remote login permissions for the target object if the role information does not exist in the database.

[0066] Optionally, the first sending module includes: a second acquisition unit, configured to acquire unique identification information by responding to a remote login instruction from the target client, wherein the remote login instruction is an instruction for the target object to remotely log in to the target server, and the remote login instruction carries the role information of the target object; and a first processing unit, configured to generate request information for a remote login request based on the unique identification information and the role information of the target object through the target client, and send the request information for the remote login request to the centralized management platform.

[0067] Optionally, the server-based remote login permission configuration device further includes: a display module, used to display the operation management functions corresponding to the remote login permissions on the target page of the target client through the target server after configuring remote login permissions for the target object according to role information, wherein the target page is the page for the target object to perform operation and maintenance.

[0068] Example 3

[0069] According to another aspect of the embodiments of this application, a computer-readable storage medium is also provided, in which a computer program is stored, wherein the computer program is configured to execute the above-described server-based remote login permission configuration method at runtime.

[0070] Example 4

[0071] According to another aspect of the embodiments of this application, an electronic device is also provided, wherein, Figure 4 This is a schematic diagram of an optional electronic device according to an embodiment of this application, such as... Figure 4 As shown, the electronic device includes one or more processors; and a memory for storing one or more programs, which, when executed by one or more processors, enable the one or more processors to run the programs, wherein the programs are configured to execute the aforementioned server-based remote login permission configuration method at runtime.

[0072] like Figure 4 As shown, this application embodiment provides an electronic device, which includes a processor, a memory, and a program stored in the memory and executable on the processor. When the processor executes the program, it performs the following steps:

[0073] The target client sends a remote login request to the centralized management platform. This remote login request is initiated by the target object to log in to the target server. The request information includes at least the target client's unique identifier and the target object's role information. The target client's unique identifier identifies the operating system type of the target client, and this operating system type is the same as the target operating system the target object is using when logging in. The centralized management platform receives the unique identifier and role information from the target client, determines the target server based on the unique identifier and a pre-defined list, and sends the role information to the target server. The pre-defined list records the correspondence between unique identifiers and target servers. The target server receives the role information from the centralized management platform and configures remote login permissions for the target object based on the role information.

[0074] Optionally, when the processor executes the program, it also performs the following steps: detecting whether there is unique identification information in the preset list through the centralized management platform; if there is unique identification information in the preset list, determining the target server corresponding to the unique identification information through the centralized management platform based on the correspondence.

[0075] Optionally, when the processor executes the program, it also performs the following steps: checks whether role information exists in the database through the target server; if role information exists in the database, obtains the remote login permission information corresponding to the role information through the target server; and configures remote login permissions for the target object based on the remote login permission information through the target server.

[0076] Optionally, the processor may also perform the following steps when executing the program: after detecting whether there is unique identification information in the preset list through the centralized management platform, if there is no unique identification information in the preset list, generate login failure information through the centralized management platform and send the login failure information to the target client.

[0077] Optionally, the processor may also perform the following steps when executing the program: after checking whether role information exists in the database through the target server, if the role information does not exist in the database, the target server shall prevent the configuration of remote login permissions for the target object.

[0078] Optionally, when the processor executes the program, it also performs the following steps: responding to the server's remote login instruction through the target client to obtain unique identification information, wherein the server's remote login instruction is an instruction for the target object to remotely log in to the target server, and the server's remote login instruction carries the target object's role information; generating remote login request information through the target client based on the unique identification information and the target object's role information, and sending the remote login request information to the centralized management platform.

[0079] Optionally, when the processor executes the program, it also performs the following steps: after configuring remote login permissions for the target object based on role information, the operation management functions corresponding to the remote login permissions are displayed on the target page of the target client through the target server, wherein the target page is the page for the target object to perform operation and maintenance.

[0080] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0081] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0082] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual couplings, direct couplings, or communication connections may be through some interfaces; indirect couplings or communication connections between units or modules may be electrical or other forms.

[0083] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0084] 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. The integrated unit can be implemented in hardware or as a software functional unit.

[0085] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or 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 of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

[0086] The above are merely preferred embodiments of this application. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A server-based remote login permission configuration method, characterized in that, This is applied to a remote login permission configuration system, wherein the remote login permission configuration system includes a target client, a centralized management platform, and a target server, including: The remote login request is sent to the centralized management platform through the target client. The remote login request is a request initiated by the target object to log in to the target server. The request information includes at least the unique identification information of the target client and the role information of the target object. The unique identification information of the target client is used to characterize the operating system type corresponding to the target client. The operating system type corresponding to the target client is the same as the operating system type of the target operating system in which the target object is logged in when logging into the target client. The centralized management platform receives unique identification information and role information sent by the target client, determines the target server based on the unique identification information and a preset list, and sends the role information to the target server. The preset list is used to record the correspondence between the unique identification information and the target server. The unique identification information represents a server of a specific operating system type, which includes at least: Windows operating system type, Linux operating system type, and cloud operating system type. The target server receives role information sent by the centralized management platform and configures remote login permissions for the target object based on the role information. Configure remote login permissions for the target object based on the role information, including: The target server is used to check whether the role information exists in the database. If the role information exists in the database, the remote login permission information corresponding to the role information is obtained through the target server; The target server configures remote login permissions for the target object based on the remote login permission information; wherein, the operation management platform is configured with multiple single sign-on controls, each single sign-on control corresponding to an operating system type, and the target single sign-on control corresponding to the target client is one of the multiple single sign-on controls, and the operating system type corresponding to the target single sign-on control is the same as the operating system type of the target operating system in which the target object logs into the operation management platform; the operation management platform automatically identifies the operating system type of the target operating system in which the target object is located; Sending remote login request information to the centralized management platform through the target client includes: By responding to the server remote login command through the target client, the unique identification information is obtained, wherein the server remote login command is the command for the target object to remotely log in to the target server, and the server remote login command carries the role information of the target object; The target client generates the remote login request information based on the unique identifier information and the role information of the target object, and sends the remote login request information to the centralized management platform. Determining the target server based on the unique identifier information and the preset list includes: The centralized management platform is used to detect whether the unique identifier information exists in the preset list. If the unique identifier information exists in the preset list, the target server corresponding to the unique identifier information is determined by the centralized management platform based on the correspondence.

2. The method according to claim 1, characterized in that, After detecting whether the unique identifier information exists in the preset list through the centralized management platform, the method further includes: If the unique identifier is not found in the preset list, a login failure message is generated through the centralized management platform and sent to the target client.

3. The method according to claim 1, characterized in that, After detecting whether the role information exists in the database via the target server, the method further includes: If the role information does not exist in the database, the remote login permission will be disabled for the target object through the target server.

4. The method according to claim 1, characterized in that, After configuring remote login permissions for the target object based on the role information, the method further includes: The target server displays the operation and management functions corresponding to the remote login permissions on the target page of the target client, wherein the target page is the page for the target object to perform operation and maintenance.

5. A server-based remote login permission configuration device, characterized in that, This is applied to a remote login permission configuration system, wherein the remote login permission configuration system includes a target client, a centralized management platform, and a target server, including: The first sending module is used to send the request information of the remote login request to the centralized management platform through the target client. The remote login request is a request initiated by the target object to log in to the target server. The request information includes at least the unique identification information of the target client and the role information of the target object. The unique identification information of the target client is used to characterize the operating system type corresponding to the target client. The operating system type corresponding to the target client is the same as the operating system type of the target operating system in which the target object is logged in when logging into the target client. The determination module is used to receive unique identification information and role information sent by the target client through the centralized management platform, determine the target server based on the unique identification information and a preset list, and send the role information to the target server. The preset list is used to record the correspondence between the unique identification information and the target server. The unique identification information represents a server corresponding to a specific operating system type, and the specific operating system type includes at least: Windows operating system type, Linux operating system type, and cloud operating system type. The configuration module is used to receive role information sent by the centralized management platform through the target server, and configure remote login permissions for the target object based on the role information; The configuration module includes: a second detection unit, used to detect whether role information exists in the database through the target server; a first acquisition unit, used to acquire the remote login permission information corresponding to the role information through the target server if the role information exists in the database; and a first configuration unit, used to configure remote login permissions for the target object based on the remote login permission information through the target server. The operation management platform is configured with multiple single sign-on controls, each of which corresponds to an operating system type. The operation management platform automatically identifies the operating system type of the target operating system in which the target object is located. The target single sign-on control corresponding to the target client is one of the multiple single sign-on controls, and the operating system type corresponding to the target single sign-on control is the same as the operating system type of the target operating system in which the target object is located when logging into the operation management platform. The first sending module includes: a second acquisition unit, used to acquire unique identification information by responding to a remote login instruction from a server through a target client, wherein the remote login instruction is an instruction for a target object to remotely log in to a target server, and the remote login instruction carries the role information of the target object; and a first processing unit, used to generate request information for a remote login request based on the unique identification information and the role information of the target object through a target client, and send the request information for the remote login request to a centralized management platform. The determining module includes: a first detection unit, used to detect whether unique identification information exists in the preset list through a centralized management platform; and a first determining unit, used to determine the target server corresponding to the unique identification information based on the correspondence relationship through the centralized management platform when unique identification information exists in the preset list.

6. A computer-readable storage medium, characterized in that, A computer-readable storage medium stores a computer program, wherein the computer program is configured to execute, at runtime, the server-based remote login permission configuration method as described in any one of claims 1 to 4.

7. An electronic device, characterized in that, It includes one or more processors and a memory, the memory being used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors cause the one or more processors to implement the server-based remote login permission configuration method according to any one of claims 1 to 4.

Images