Resource account management method, device, equipment and system

Abstract

The invention provides a resource account management method, device, equipment and system. The method comprises the following steps: acquiring configuration information and account information of a plurality of resource parties; obtaining a plurality of plug-ins and parameter templates associated with the plug-ins; establishing an adaptation relationship among each plug-in, an account management function of each plug-in and each resource party; when a resource account management request of a target resource party is received, filling the configuration information and account information of the target resource party into a parameter template of a target plug-in adapted to the target resource party according to the adaptation relationship; and based on the parameter template, triggering the target plug-in to link to the target resource party and executing an account management function of the target plug-in. By adopting the method and the device, the account management function of the resource party under various resource configurations can be flexibly compatible, the expansibility is realized, meanwhile, the security of the resource party is protected, and the applicability is high.

Description

Technical Field

[0001] This application relates to the field of account management technology, and mainly to a resource account management method, apparatus, device and system. Background Technology

[0002] Resource account management technology aims to solve the security and management issues of accounts on resource providers such as data center servers, network devices, security devices, and databases. With the development of enterprise informatization, the number and types of resource providers in various enterprises are constantly increasing, and the versions of resource providers are constantly being updated. The update progress of various resource providers varies, and each resource provider has its own corresponding account with different account format requirements. The amount of account information carried by each resource provider is also gradually increasing. Therefore, improving resource account management technology has become one of the most pressing technical problems to be solved.

[0003] The inventors of this application discovered through research and practice that in existing technologies, developing multiple versions of agent programs and deploying them on resource provider hosts to interact with external account management centers, employing a distributed account password storage method based on host agents, is intrusive to resource provider hosts, potentially causing security issues. Furthermore, the management scope is limited to hosts where the agent is installed, resulting in poor flexibility. In addition, existing technologies also employ system code deployment, embedding account management functions for multiple resource providers within the code of the account management system to manage accounts from multiple different resource providers. However, because existing technologies use hard-coded system code to manage accounts from multiple resource providers, the account management system needs to be updated when resource providers change, resulting in a large workload and poor applicability. Summary of the Invention

[0004] This application provides a resource account management method, apparatus, device, and system that can flexibly and compatiblely manage resource accounts under various resource configurations, has scalability, protects resource security, and has high applicability.

[0005] Firstly, this application provides a resource account management method, which includes: obtaining configuration information and account information of multiple resource providers; obtaining multiple plugins and parameter templates associated with the plugins, wherein the plugins have account management functions; establishing an adaptation relationship between each plugin, the account management functions of each plugin, and each resource provider; when receiving a resource account management request from a target resource provider, filling the configuration information and account information of the target resource provider into the parameter template of the target plugin adapted to the target resource provider according to the adaptation relationship, wherein the target resource provider is any one of the multiple resource providers; and triggering the target plugin to link to the target resource provider and execute the account management function of the target plugin based on the parameter template. In this application, an adaptation relationship can be established between each plugin, the account management functions of each plugin, and each resource provider. When a resource account management request is received from the target resource provider, the configuration information and account information of the target resource provider are filled into the parameter template of the target plugin adapted to the target resource provider according to the above adaptation relationship. Then, based on the filled parameter template, the target plugin is triggered to link to the target resource provider and execute the account management function to realize the resource account management of the target resource provider. It can be compatible with the account management of resource providers under various resource configurations, which can improve the flexibility of resource account management. At the same time, it can protect the security of the resource provider and has high applicability.

[0006] In one possible implementation of the first aspect, the above-mentioned triggering of the target plugin to link to the target resource provider and execute the target plugin's account management function based on the parameter template includes: sending the parameter template and the target plugin to a script engine, and having the script engine call the target plugin to link to the target resource provider and execute the target plugin's account management function based on the parameter template. In this application, the parameter template and target plugin, populated with the target resource provider's configuration information and account information, can be sent to the script engine. The script engine can then call the target plugin to link to the target resource provider and execute the target plugin's account management function based on the parameter template, thereby achieving resource account management for the target resource provider. Using a script engine to call the plugin link improves the flexibility and scalability of resource account management, while further protecting the resource security of the resource provider, and has high applicability.

[0007] In one possible implementation of the first aspect, the above-mentioned method of calling the target plugin to link to the target resource provider and execute the target plugin's account management function based on the parameter template using the script engine includes: generating a function script for the target plugin based on the parameter template using the script engine and calling the target plugin to execute the function script, thereby calling the target plugin to link to the target resource provider and execute the target plugin's account management function; wherein, the account management function includes one or more of resource account discovery, resource account addition, resource account deletion, or resource account modification. In this application, the script engine can generate a function script for the target plugin based on the parameter template and call the target plugin to execute the function script, thereby calling the target plugin to link to the target resource provider and execute the target plugin's account management function. Generating function scripts based on the parameter template associated with the plugin and the configuration information and account information filled into the parameter template allows the script engine to call and execute multiple types of plugins to link to resource providers under various resource configurations without modifying the system code. It supports version or type updates of plugins or resource providers, enhances the flexibility and compatibility of calling plugins and executing resource account management, improves scalability, and has high applicability.

[0008] In one possible implementation of the first aspect, establishing the adaptation relationship between each of the aforementioned plugins, the account management functions of each of the aforementioned plugins, and the aforementioned resource providers includes: matching the plugins adapted to each of the aforementioned resource providers and the account management functions of the plugins through a plugin adapter, thereby establishing the adaptation relationship between each of the aforementioned resource providers, the plugins adapted to the aforementioned resource providers, and the account management functions of the plugins. In this application, a plugin adapter is introduced. Through the plugin adapter, the plugins adapted to each resource provider and the account management functions of the plugins can be matched according to the configuration information of each resource provider, thereby establishing the adaptation relationship between each resource provider, plugins, and the account management functions of the plugins. The plugin adapter can support multiple types of plugins and can serve resource providers under multiple resource configurations, improving the compatibility and flexibility of resource account management, enhancing scalability, and reducing unnecessary port calls or data conversions, simplifying development and maintenance work, and improving the overall performance and efficiency of the system.

[0009] In one possible implementation of the first aspect, after establishing the adaptation relationship between each of the aforementioned plugins, the account management function of each of the aforementioned plugins, and each of the aforementioned resource providers, the method further includes: configuring a plugin adapter identifier for each of the aforementioned resource providers, wherein the plugin adapter identifier is used to mark the plugin adapter adapted to each of the aforementioned resource providers, and resource providers with the same configuration information adapt to the same adapter; the step of filling the configuration information and account information of the aforementioned target resource provider into the parameter template of the target plugin adapted to the aforementioned target resource provider according to the aforementioned adaptation relationship when a resource account management request from the target resource provider is received includes: when a resource account management request from the target resource provider is received, triggering the target plugin adapter marked by the target plugin adapter identifier to feed back the target plugin associated with the aforementioned target resource provider according to the aforementioned adaptation relationship, and filling the configuration information and account information of the aforementioned target resource provider into the parameter template of the aforementioned target plugin, wherein the target plugin adapter identifier is a plugin adapter identifier configured for the aforementioned target resource provider. In this application, after establishing the adaptation relationships between various resource providers, plugins, and plugin account management functions, a plugin adapter identifier can be configured for each resource provider. When a resource account management request is received from a target resource provider, the target plugin adapter marked by the target plugin adapter identifier can be triggered to provide feedback on the target plugin associated with the target resource provider based on the target plugin adapter identifier and the adaptation relationship. The configuration information and account information of the target resource provider are then populated into the parameter template of the target plugin. The target plugin adapter identifier allows for quick identification of the target plugin adapter adapted to the target resource provider and retrieval of the adaptation relationships maintained within the target plugin adapter. This enables rapid acquisition of target plugins adapted to the target resource provider, reducing plugin search time overhead, improving plugin resource management efficiency, and optimizing plugin scheduling flexibility. Furthermore, the plugin adapter can support multiple types of plugins, and various types of plugin adapters can serve resource providers under different resource configurations, maintaining the adaptation relationships between resource providers, plugins, and plugin functions. This further improves the compatibility and flexibility of resource account management, enhances scalability, and increases applicability.

[0010] In one possible implementation of the first aspect, before establishing the compatibility relationships between the various plugins, their account management functions, and the resource providers, the method further includes: generating multiple plugins based on plugin development rules and various resource configurations, configuring the account management functions of each plugin, and storing the multiple plugins and their account management functions in a database to generate a plugin resource library; wherein the plugin development rules are used to unify the calling format of each plugin. In this application, multiple plugins can be generated and their account management functions configured based on plugin development rules and various resource configurations. The multiple plugins and their account management functions can be stored to generate a plugin resource library, allowing the plugin resource library to contain plugins applicable to resource providers under various resource configurations. Various resource providers can share the plugin resource library, providing system scalability and compatibility. Simultaneously, the plugin development rules unify the calling format of all plugins in the plugin resource library, reducing development and maintenance costs, facilitating plugin calls by various resource providers, enhancing user experience, and demonstrating high applicability.

[0011] In one possible implementation of the first aspect, the acquisition of multiple plugins and their associated parameter templates includes: dynamically loading plugins and parameter templates that match the configuration information of the resource provider from a pre-built plugin resource library, wherein the parameter templates contain configurable fields and validation rules. In this embodiment, because plugins and parameter templates matching the resource provider's configuration information can be dynamically loaded from a pre-built plugin resource library, the acquisition process of plugins and parameter templates has dynamic matching capabilities. Furthermore, the parameter templates contain configurable fields and validation rules, ensuring the compatibility between the plugins and the resource provider. Simultaneously, the validation rules improve the accuracy of data input, thus enhancing the automation and reliability of resource account management.

[0012] In one possible implementation of the first aspect, when a new plugin is detected in the plugin repository, the functional declaration of the plugin is automatically scanned; the adaptation relationship is updated based on the functional declaration, and the account management function of the new plugin is matched and tested with the unmatched resource provider. In this embodiment, when a new plugin is detected, its functional declaration is automatically scanned, and the adaptation relationship is updated based on the functional declaration, and the unmatched resource provider is matched and tested. This enables the system to have dynamic plugin discovery and adaptation capabilities, automatically expand the scope of plugin support, reduce manual intervention, and thus improve the scalability and maintenance efficiency of the system.

[0013] In one possible implementation of the first aspect, when a change in the configuration information of the target resource is detected, a re-matching process for the adaptation relationship is triggered. If the original target plugin is no longer compatible, a new plugin is re-matched from the plugin resource library, and the adaptation relationship is updated. In this embodiment, when a change in the resource provider's configuration is detected, a re-matching process for the adaptation relationship is triggered. If no match is found, a new plugin is selected, and the adaptation relationship is updated. This gives the system dynamic adjustment capabilities, enabling it to automatically adapt to changes in the resource provider and avoid functional failure due to configuration changes. Therefore, the system's adaptability can be improved.

[0014] In one possible implementation of the first aspect, the parameter template filling process includes: performing format validation on the configuration information and account information of the target resource provider; triggering an error handling process if the validation fails; and filling the configuration information and account information of the target resource provider into the corresponding positions of the parameter template according to the field mapping relationship when the validation passes. In this embodiment, by performing format validation on the account information of the target resource provider and filling the parameter template according to the field mapping relationship when the validation passes, invalid or erroneous data can be prevented from entering the plugin execution process, and the uniformity of the data structure can be ensured, thus improving the stability and security of account management operations.

[0015] Secondly, this application provides a resource account management device, the device comprising:

[0016] The resource management module is used to obtain configuration information and account information from multiple resource providers;

[0017] The plugin management module is used to obtain multiple plugins and the parameter templates associated with the plugins. The plugins have account management functions.

[0018] The aforementioned plugin management module is also used to establish the management functions of each of the aforementioned plugins, the account management functions of each of the aforementioned plugins, and the adaptation relationships of each of the aforementioned resource providers.

[0019] The account management module is used to, upon receiving a resource account management request from a target resource provider, fill the configuration information and account information of the target resource provider into the parameter template of the target plugin adapted to the target resource provider according to the above adaptation relationship. Based on the above parameter template, the target plugin is triggered to link to the target resource provider and execute the account management function of the target plugin. The target resource provider is any one of the above multiple resource providers.

[0020] Thirdly, this application provides a terminal device, which includes a processor and a memory; the processor is connected to the memory, wherein the memory is used to store program code, and the processor is used to call the program code to execute the steps of the resource account management method provided in the first aspect or any possible implementation of the first aspect.

[0021] Fourthly, this application provides a resource account management system, which includes: a script engine, a plugin adapter, a plugin resource library, and the terminal device provided in the third aspect above.

[0022] Fifthly, this application provides a computer-readable storage medium storing a computer program adapted to be loaded by a processor and to execute the steps of the resource account management method provided in the first aspect or any possible implementation thereof.

[0023] Sixthly, this application provides a computer program product, which includes computer instructions stored in a computer-readable storage medium; a processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the steps of the resource account management method provided in the first aspect or any possible implementation of the first aspect.

[0024] The technical effects of the second, third, fourth, and fifth aspects can be referred to the technical effects of the first aspect and any of its embodiments, and will not be repeated here. Attached Figure Description

[0025] Figure 1 This is a schematic diagram of a system architecture for the resource account management method provided in an embodiment of this application;

[0026] Figure 2 This is a schematic diagram of an application scenario of the resource account management method provided in the embodiments of this application;

[0027] Figure 3 This is a schematic diagram illustrating another application scenario of the resource account management method provided in the embodiments of this application;

[0028] Figure 4 This is a flowchart illustrating a resource account management method provided in an embodiment of this application;

[0029] Figure 5 This is another flowchart illustrating the resource account management method provided in this application embodiment;

[0030] Figure 6 This is another flowchart illustrating the resource account management method provided in this application embodiment;

[0031] Figure 7 This is a schematic diagram of the structure of the resource account management device provided in the embodiments of this application;

[0032] Figure 8This is a schematic diagram illustrating an application scenario of the resource account management system provided in this application embodiment;

[0033] Figure 9 This is a schematic diagram of the structure of the computer device provided in the embodiments of this application. Detailed Implementation

[0034] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0035] With the accelerated advancement of enterprise informatization, the quantity and variety of data center resources (including but not limited to servers, network equipment, security equipment, databases, etc.) are constantly increasing. These resources are frequently updated, but the pace of these updates varies considerably. Simultaneously, each resource is equipped with a corresponding account, and the account format requirements differ across resources, resulting in a rapidly growing volume of account information. This situation presents numerous challenges to resource account management. Therefore, effectively improving resource account management technology to achieve more secure, flexible, compatible, and scalable resource account management holds immense potential for development.

[0036] For ease of description, we will take a terminal device as an example, combined with... Figure 1 The system architecture of the resource account management method provided in the embodiments of this application is described.

[0037] See Figure 1 , Figure 1 This is a schematic diagram of a system architecture for the resource account management method provided in an embodiment of this application. For example... Figure 1As shown, the system architecture may include a business server 100 and a terminal cluster. The terminal cluster may include terminal devices 200a, 200b, 200c, ..., 200n, etc. The business server 100 may be an independent physical server, a server cluster composed of multiple physical servers, or a distributed system. It may also be a cloud server providing basic cloud computing services such as cloud databases, cloud services, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms. The terminal devices (including terminal devices 200a, 200b, 200c, ..., 200n) may be PDAs, smartphones, laptops, desktop computers, tablets, mobile internet devices (MIDs), wearable devices (such as smartwatches, smart bracelets, etc.), smart computers, and other smart terminals, but are not limited to these.

[0038] The service server 100 can establish communication connections with each terminal device in the terminal cluster, and the terminal devices in the terminal cluster can also establish communication connections with each other. In other words, the service server 100 can establish communication connections with each terminal device among terminal devices 200a, 200b, 200c, ..., 200n. For example, terminal device 200a can establish a communication connection with the service server 100. Terminal devices 200a and 200b can establish a communication connection, and terminal devices 200a and 200c can also establish a communication connection. The communication connection method is not limited; it can be established directly or indirectly through wired communication or wireless communication, etc., depending on the actual application scenario. This application does not impose any restrictions on this.

[0039] It should be understood that, such as Figure 1 Each terminal device in the terminal cluster shown can have an application client installed. When the application client runs on each terminal device, it can interact with the aforementioned... Figure 1The business servers 100 shown interact with each other, enabling each business server 100 to obtain business data from each terminal device through interfaces and other paths. This business data can be application data generated during user interaction with the application client, including but not limited to user login accounts and passwords. This application data can be shared with the business server 100. The application client can be an application program, a webpage, or a website, depending on the specific application scenario, and is not limited here. The application client can be a standalone client or an embedded sub-client integrated into a client (e.g., an instant messaging client, a social networking client, etc.), depending on the specific application scenario, and is not limited here. Users can send business data to the business server 100 through the application client. This business data can be used to request the business server 100 to start relevant business processes and return relevant process data to the application client. The business server 100, as the server for the application client, can be a collection of multiple servers, including the backend server corresponding to the application client and a data processing server. The method provided in this embodiment can be provided by, for example... Figure 1 The business server 100 shown can execute the service, but it can also be executed by a terminal device (such as...). Figure 1 The terminal device 200a, terminal device 200b, ..., terminal device 200n shown can be used to execute the operation. Alternatively, the terminal device and the business server can be used together to execute the operation. The specific execution method can be determined according to the actual application scenario, and there are no restrictions here.

[0040] The resource account management method provided in this application is applicable to account management of various types of resources. These various types of resources can cover various hardware, software, data, and network infrastructures relied upon in the enterprise's operation, management, and service delivery processes, including but not limited to: servers, network devices, storage devices, terminal devices, security devices, operating systems, databases, middleware, etc. Servers include, but are not limited to, virtual servers and physical servers. Network devices include, but are not limited to, routers, switches, firewalls, and load balancers. Storage devices include, but are not limited to, disk arrays, network attached storage (NAS), and storage area networks (SAN). Terminal devices include, but are not limited to, personal computers, laptops, and mobile devices. Security devices include, but are not limited to, intrusion detection systems (IDS), intrusion prevention systems (IPS), and authentication devices. Operating systems include, but are not limited to, Windows server operating systems, Linux operating systems, and Unix operating systems. Databases include, but are not limited to, MySQL, Oracle, and SQL Server. Middleware includes, but is not limited to, web servers, application servers, and message queues. Different types of resources can be used for various scenarios, including but not limited to daily operations, business process management, data analysis, information technology (IT) infrastructure management, software development, cloud computing, the Internet of Things, and business innovation. There are no restrictions on their use. These different resource types correspond to various resource accounts, such as domain or local accounts for Windows server operating systems, router administrator accounts, and database user access accounts. There are no restrictions on their use either.

[0041] For ease of subsequent understanding and explanation, in this application, the operating environment will be described as such. Figure 1 The resource account management platform on the business server 100 shown serves as the executor of the resource account management method provided in this application embodiment. The party requiring resource account management through the resource account management platform is considered the resource party. For example, any terminal device (such as terminal device 200c) is used as the target resource party. Figure 2 The application scenarios of the resource account management method provided in the embodiments of this application are described.

[0042] See Figure 2 , Figure 2 This is a schematic diagram illustrating an application scenario of the resource account management method provided in this application embodiment. For example... Figure 2 As shown, the resource account management platform can provide a user interface (such as user interface 1) to display multiple resource providers that the platform can operate on. The user interface can display information in various ways, including but not limited to tables, charts, lists, and cards, depending on the specific application scenario. It is understood that the resource account management platform can store configuration and account information for these multiple resource providers. Configuration information includes, but is not limited to, the type and version of the resource provider, while account information includes, but is not limited to, account name, account type, account validity period, and account status. These details can be determined based on the actual application scenario and are not limited here. Figure 2 As shown, the resource account management platform provides a "Resource Provider List" in User Interface 1 to display multiple resource providers for which the platform can currently perform resource account management. This list displays configuration and account information for each resource provider, including but not limited to "Number," "Resource Provider Name," "Resource Provider Type," and "Resource Provider Version." User Interface 1 may also include components such as "Add" and "Refresh" buttons. Upon receiving a click on the "Add" button, a pop-up window or a new user interface (such as User Interface 2) can be displayed in User Interface 1 to obtain the configuration and account information of the newly added resource provider. Figure 2 As shown, the resource account management platform can expand user interface 2 upon receiving a click on the "Add" button in user interface 1. User interface 2 can provide multiple input text boxes, drop-down lists for type selection, "Save" buttons, and "Cancel" buttons. In user interface 2, configuration and account information of the newly added resource provider can be collected through text box input and drop-down list selection. It can be understood that configuration information may include, but is not limited to, resource provider type and version, and account information may include, but is not limited to, account name and account type. Here, resource providers include, but are not limited to, servers, network devices, storage devices, terminal devices, security devices, operating systems, databases, middleware, etc., which can be determined according to the actual application scenario and are not limited here. When the resource account management platform receives a click on the "Save" button in user interface 2, it can store the collected configuration and account information of the newly added resource provider and refresh the newly added resource provider in the resource provider list shown in user interface 1.

[0043] In addition, the resource account management platform can provide a user interface (such as user interface 3) to display all plugins in the plugin resource library. The display method can include, but is not limited to, tables, charts, lists, cards, etc., depending on the actual application scenario and is not restricted here. It can be understood that the plugin resource library associated with the resource account management platform can store various types of plugins to adapt to various types of resource providers and provide various account management functions. For example... Figure 2 As shown, the resource account management platform provides a "Plugin Management" section in user interface 3 to display plugins in the plugin resource library associated with the platform. This can be displayed in a list format, including but not limited to information such as "Number," "Plugin Name," "Plugin Function," and "Compatibility Relationship." User interface 3 may also include components such as "Add" and "Refresh" buttons. When a click on the "Add" button is received, a pop-up window can be displayed in user interface 3, or a new user interface (such as user interface 4) can be switched to obtain the newly added plugin. Here, the resource account management platform can collect the plugin file, plugin name, plugin version, plugin automation method, and associated parameter templates through the aforementioned user interface for adding plugins. This allows it to obtain the newly added plugin file and account management functions. Specific details can be determined based on the actual application scenario and are not limited here. Figure 2 As shown, the resource account management platform can open user interface 4 when it receives a click on the "Add" button in user interface 3. User interface 4 can include multiple input text boxes, a drop-down list providing type selection, "Save" buttons, and "Cancel" buttons. In user interface 4, plugin files can be uploaded, and plugin details can be entered through the text boxes. These details can include, but are not limited to, the plugin name, plugin type, and parameter template, depending on the specific application scenario. The plugin type can be related to the type and version of the resource provider to which the plugin is applicable, and this can also be determined based on the specific application scenario. When the resource account management platform receives a click on the "Save" button in user interface 4, it can store the obtained plugin file and plugin details to obtain the newly added plugin and plugin account management functions. It is understandable that the parameter template associated with a plugin can be uploaded through user interface 3, generated by the resource account management platform based on historically uploaded plugin-associated parameter templates, or entered in the text box of user interface 4. The plugin's parameter template can be related to the plugin's account management function. A plugin can have at least one account management function, the specifics of which can be determined based on the actual application scenario and are not limited here. For ease of description, this example uses one plugin corresponding to one account management function. Figure 2The plugin_2 shown in User Interface 3 corresponds to the "Account Change" function. After adding the plugin, the Resource Account Management Platform can store it in the plugin resource library, which means it can be found in the "Plugin Management" list shown in User Interface 3.

[0044] Furthermore, the resource account management platform can provide a user interface (such as user interface 5) to display the compatibility relationships between plugins, resource providers, and plugin functions, and can also provide a user interface to add or modify these compatibility relationships. Figure 2 As shown, the resource account management platform provides a "Plugin Adaptation Management" list in User Interface 5 to display the adaptation relationships between plugins, resource providers, and plugin functions. For example, plugin_2's plugin function is "Account Change," and its adaptation relationship is not established, meaning that plugin_2 has not yet been bound to a resource provider. User Interface 5 can also display all resource provider names (not shown in the figure) under the types of resource providers applicable to each plugin, providing a reference for establishing adaptation relationships. User Interface 5 can also include components such as "Add," "Refresh," and checkboxes. When the resource account management platform detects that a checkbox corresponding to a plugin is checked and the "Add" button is clicked, it can display a pop-up window in User Interface 5 or switch to a new user interface (such as User Interface 6) to obtain the newly added adaptation relationship. Figure 2 As shown, assuming we are adding a new compatibility relationship for plugin_2, we can check the corresponding checkbox for plugin_2 in user interface 5 and click the "Add" button. The resource account management platform can then open user interface 6. User interface 6 can include multiple input text boxes, a drop-down list for selecting resource providers, a "Save" button, and a "Cancel" button. In user interface 6, we can establish a compatibility relationship between plugin_2 and a specific resource provider. The drop-down list can display all resource providers (not shown in the figure) that plugin_2 is compatible with for selection. When the resource account management platform receives a click on the "Save" button in user interface 6, it can save the compatibility relationship between plugin_2, the plugin function (i.e., "Account Change"), and the selected resource providers, so that resource providers can subsequently call plugin_2 to perform the account management function of account change. Optionally, the content of user interface 3 and user interface 5 can be displayed in one user interface, and the content of user interface 4 and user interface 6 can also be displayed in one user interface. Thus, the entered information can be obtained on one page to create a new plugin and complete the adaptation relationship binding. In other words, the acquisition of information such as plugin details and the establishment of plugin adaptation relationship do not need to jump to multiple user interfaces for entry. They can be obtained through one user interface. The specific method can be determined according to the actual application scenario and is not limited here.

[0045] For ease of understanding, let's assume the target resource provider has established a compatibility relationship with plugin_2. When the resource account management platform receives an "account change" request from the target resource provider, it can, based on the aforementioned compatibility relationship, call the stored configuration and account information of the target resource provider to populate the parameter template associated with plugin_2. Then, it sends plugin_2 and the populated parameter template to the script engine. Here, the script engine of the resource account management platform can be deployed on the target resource provider. Based on the aforementioned parameter template, the script engine can generate a functional script for plugin_2 and call plugin_2 to execute this script, thereby linking plugin_2 to the target resource provider and performing the "account change" function on the target resource provider's account information.

[0046] For easier understanding, please refer to [link / reference]. Figure 3 , Figure 3 This is a schematic diagram illustrating another application scenario of the resource account management method provided in this application embodiment. A resource account management platform is used as the executor of the resource account management method provided in this application embodiment. Figure 3As shown, the resource account management platform can include functional components such as a plugin management module, an account management module, a script engine, a plugin adapter, and a resource management module. The script engine can be deployed on the target resource provider. The components in the resource account management platform and their deployment locations can be determined based on the actual application scenario and are not limited here. The resource account management platform can obtain configuration information and account information from multiple resource providers. Here, the configuration information of the resource provider may include, but is not limited to, the type or version of the resource provider. For example, the resource account management platform can obtain the type of the resource provider as a host, and obtain the host version and the account information linked to the host, etc., which can be determined based on the actual application scenario and are not limited here. Furthermore, the resource account management platform can store the above-mentioned configuration information and account information of the resource providers in a database. The resource account management platform can establish the adaptation relationship between the account management functions of various resource providers and plugins through the plugin adapter. In this case, the parameter templates associated with plugins can be stored in the plugin resource library (not shown in the figure). Plugins can have account management functions such as account modification and account discovery. Furthermore, when the resource account management platform receives a resource management request (such as an "account change" request) from a target resource provider (any one of the resource providers), the platform can obtain a plugin that has established an adaptation relationship with the target resource provider through a plugin adapter, using it as the target plugin. The platform then retrieves the target resource provider's configuration and account information from the database and populates it into the parameter template associated with the target plugin. Further, the resource account management platform can send the target plugin and the populated parameter template to the script engine. Here, the script engine of the resource account management platform can be deployed on the target resource provider. Based on the parameter template, the script engine can generate a functional script for the target plugin and call the target plugin to execute this script, triggering the target plugin to link to the target resource provider and execute account management functions (such as the "account change" function for account information in the target resource provider). For details on how the resource account management platform establishes the adaptation relationship and how it calls the target plugin to execute account management functions based on the script engine, please refer to the implementation methods described in the following embodiments; further details are omitted here.

[0047] In this embodiment, the resource account management method can be executed by a resource account management platform deployed on the business server 100. Any terminal device (e.g., terminal device 200c) can be used as the target resource. The script engine can be deployed on the target resource. The resource account management platform can obtain the configuration information and account information of the target resource and retrieve plugins from the plugin resource library that have established an adaptation relationship with the target resource as target plugins. When the resource account management platform receives a resource account management request (e.g., account change) from the target resource, it fills the configuration information and account information of the target resource into the parameter template of the target plugin adapted to the target resource according to the aforementioned adaptation relationship. Based on the filled parameter template, the target plugin is triggered to link to the target resource and execute the account management function, thereby realizing the resource account management of the target resource (e.g., changing account information). This enables the resource account management function of the target resource, is compatible with account management of resource providers under various resource configurations, improves the flexibility of resource account management, protects the security of the resource provider, and has high applicability.

[0048] It is understood that in the specific implementation of this application, data related to object information is involved. When the embodiments of this application are applied to specific products or technologies, permission or consent from the object is required, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0049] The following will combine Figures 4 to 9 The resource account management method, apparatus, device and system provided in the embodiments of this application will be described in detail.

[0050] See Figure 4 , Figure 4 This is a flowchart illustrating a resource account management method provided in an embodiment of this application. Figure 4 As shown, this resource account management method may include at least the following S401 to S405:

[0051] S401 retrieves configuration and account information from multiple resource providers.

[0052] In some feasible implementations, the resource account management platform can obtain configuration information and account information from multiple resource providers. Here, the above configuration information and account information can be collected by guiding input or importing through user interface, or by connecting to the clients of each resource provider through interface, etc. The specific method can be determined according to the actual application scenario, and no restrictions are imposed here.

[0053] In some feasible implementations, the aforementioned resource providers may include, but are not limited to, servers, network devices, storage devices, terminal devices, security devices, operating systems, databases, or middleware, etc., specifically determined according to the actual application scenario, and are not limited here. The aforementioned servers may include, but are not limited to, virtual servers and physical servers. The aforementioned network devices may include, but are not limited to, routers, switches, firewalls, load balancers, etc. The aforementioned storage devices may include, but are not limited to, disk arrays, network-attached storage, storage area networks, etc. The aforementioned terminal devices may include, but are not limited to, personal computers, laptops, mobile devices, etc. The aforementioned security devices may include, but are not limited to, intrusion detection systems, intrusion prevention systems, authentication devices, etc. The aforementioned operating systems may include, but are not limited to, Windows server operating systems, Linux operating systems, Unix operating systems, etc. The aforementioned databases may include, but are not limited to, MySQL, Oracle, SQL Server, etc. The aforementioned middleware may include, but is not limited to, web servers, application servers, message queues, etc. Different types of resource providers can be applied to various scenarios including, but not limited to, daily operations of enterprises, business process management, data analysis, IT infrastructure management, software development, cloud computing, the Internet of Things, and business innovation, and are not limited here.

[0054] It is understood that the above configuration information is associated with resource providers. Resource provider configuration information may include, but is not limited to, the type or version of the resource provider. For example, the resource account management platform can obtain information such as the resource provider being a host, the host being a Linux operating system (i.e., the type of resource provider), and the Linux system version of the host (i.e., the version of the resource provider). The specific details can be determined based on the actual application scenario and the resource provider, and are not limited here. Account information may include account information related to connections between the resource provider and external resource providers, enabling communication and data exchange between different systems, applications, or services. Here, multiple types of resource providers can correspond to multiple types of account information. Different account information can have different account formats. The type of account information can be categorized based on permission level, usage scenario, lifecycle, purpose, and authentication method, and can be determined based on the actual application scenario. For example, domain accounts or local accounts for Windows server operating systems, router administrator accounts, database user access accounts, etc., are not limited here. It is understood that resource provider account information may include, but is not limited to, the resource accounts and account formats connected to the resource provider, and can be determined based on the actual application scenario, and are not limited here.

[0055] In some feasible implementations, after obtaining multiple configuration information and account information from multiple resource providers, the configuration information and account information can be stored in a database or a resource information set respectively, or the configuration information and account information can be stored in the cloud and retrieved when needed later. The specific implementation can be determined according to the actual application scenario, and no restrictions are imposed here.

[0056] In this embodiment, configuration information and account information corresponding to each resource provider can be obtained and stored for subsequent reading and use. Here, configuration information may include, but is not limited to, the type and version of the resource provider, and account information may include, but is not limited to, information on the connection relationship between internal or external resource providers. The obtained configuration information and account information of each resource provider can participate in the implementation of subsequent resource account management functions. For specific implementation methods, please refer to the implementation methods described in the following embodiments, which will not be elaborated here.

[0057] S402, obtain multiple plugins and parameter templates associated with the above plugins, the above plugins have account management functions.

[0058] In some feasible implementations, the resource account management platform can obtain multiple plugins and their associated parameter templates. Here, the platform can guide users to upload plugin files and associated parameter templates through a user interface, or retrieve historically uploaded plugins and their associated parameter templates from the plugin resource library. Alternatively, users can input parameter templates into text boxes on the platform. The specific implementation depends on the actual application scenario and is not limited here. It is understood that parameter templates can include, but are not limited to, a series of preset rules, configurable fields, and association logic, which can be determined based on the actual application scenario and are not limited here. Here, the aforementioned configurable fields can cover the resource provider's configuration information and account information, so that the resource's configuration information and account information can be filled into the configurable part of the parameter template later. For example, the parameter template can preset configurable information such as the resource provider's type, version, and basic configuration. Simultaneously, the parameter template can also pre-design configurable account information, such as the resource provider's login account and password, and the target account information for which account management is expected to be implemented, etc., without limitation here. Here, the plugin's account management functions include, but are not limited to, account discovery, account modification, and account deletion. The specific functions can be determined based on the actual application scenario and are not limited here. The account discovery function can detect and identify all existing account information of the resource provider and its associated information (such as creation time, last login time, group affiliation, and bound permission policies). This function can be used to check the compliance of the resource provider's account information (e.g., identifying accounts that have not been used for a long time). The account modification function can be used to adjust the information of one or more target accounts in the resource provider's account information (such as account permissions, account format, and account attributes), such as changing the department to which a target account belongs or adding / removing its tags. The account deletion function can be used to remove account information and its associated permissions. For example, it can delete high-risk target account information and revoke its access permissions to the resource provider. All of the above account management functions can be determined based on the actual application scenario and are not limited here. It can be understood that the plugin's account management functions can be executed in conjunction with parameter templates (which can include configurable security policies, permission sets, account information, etc.). In other words, the plugin's parameter template is related to the plugin's account management function. The parameter template can provide preset rules and configurable fields for executing the account management function. For example, when the plugin executes the "account change" function (such as adjusting user permissions), its function execution directly depends on the account information that can be configured in the parameter template. The specifics can be determined according to the actual application scenario, which will not be elaborated here.

[0059] In some feasible implementations, multiple plugins can be generated based on plugin development rules and various resource configurations, and account management functions can be configured for each plugin. The resource account management platform can acquire these generated plugins with account management functions and store them, along with their respective account management functions, in a database to generate a plugin resource library. The plugin development rules can be used to unify the calling format of each plugin. Here, the plugin development rules can be a standardized development specification to ensure that the plugin development process meets usage requirements. Plugin development rules may include, but are not limited to, interface specifications, data formats, security requirements, performance requirements, compatibility requirements, and calling formats, which can be determined based on the actual application scenario and are not limited here. Optionally, the plugin resource library can be located in locations including, but not limited to, cloud platforms, network-attached storage devices, and servers, which can be determined based on the actual application scenario and are not limited here. It is understood that developing multiple plugins based on plugin development rules and resource configurations allows for the design of plugins and plugin functions suitable for various resource providers, while ensuring that all developed plugins can be called through a unified calling format, thus ensuring the standardization and normalization of the plugin development process. After plugin development is complete, the resource account management platform can test and verify each plugin to ensure it functions correctly and meets business requirements, such as performing account management functions. This testing and verification process can include, but is not limited to, unit testing, integration testing, performance testing, and security testing. After passing testing and verification, the plugin and its functionalities are stored, which can be located in locations including, but not limited to, cloud platforms, network-attached storage devices, and servers, to generate a plugin resource library for unified plugin management. Storing plugins in a plugin resource library facilitates dynamic plugin loading and supports dynamic loading or unloading, ensuring flexibility and scalability in plugin usage. Furthermore, it facilitates monitoring the plugin's running status and enables regular plugin maintenance, the specifics of which can be determined based on the actual application scenario and are not limited here. In this embodiment, multiple plugins can be generated based on plugin development rules and various resource configurations, and account management functions for each plugin can be configured. The aforementioned multiple plugins and their account management functions can be stored to generate a plugin resource library. This allows the plugin resource library to contain plugins applicable to resource providers under various resource configurations, which can be called by different resource providers. The plugin resource library can be shared by different resource providers, which can improve the scalability and compatibility of the system. At the same time, the plugin development rules unify the calling format of all plugins in the plugin resource library, which can reduce development and maintenance costs, facilitate the use of plugins by different resource providers, enhance user experience, and have high applicability.

[0060] In some feasible implementations, plugins and parameter templates matching the configuration information of the aforementioned resource providers can be dynamically loaded from a pre-built plugin resource library. The parameter templates contain configurable fields and validation rules. Specifically, the system first accesses the pre-built plugin resource library and establishes an index based on dimensions such as plugin type and applicable resource provider. When receiving configuration information from a resource provider, the system extracts key feature parameters through a configuration parsing engine and dynamically retrieves a set of plugins that meet the conditions in the resource library based on a feature matching algorithm. Simultaneously, the system loads the parameter templates bound to each plugin. These templates use a preset format definition and include validation rules such as the data type and value range of configurable fields. During the loading process, the system checks plugin version compatibility and template integrity to ensure that only validated plugins and templates are loaded into memory. Because plugins and parameter templates that match the resource provider's configuration information can be dynamically loaded from a pre-built plugin repository, the process of obtaining plugins and parameter templates has dynamic matching capabilities. Furthermore, the parameter templates contain configurable fields and validation rules, which can ensure the compatibility between plugins and resource providers. At the same time, the validation rules improve the accuracy of data input, thus enhancing the automation and reliability of resource account management.

[0061] In some feasible implementations, when the system detects a new plugin in the plugin resource library, it first automatically scans the plugin's functional declaration file to extract key information such as the types of resource providers supported by the plugin and the interface specifications for account management functions. Subsequently, the adaptation relationship management engine matches this declaration information with the configuration information of currently unadapted resource providers, calculates a compatibility score using a rule engine, and filters out a list of potentially compatible resource providers. For each candidate resource provider, the system automatically creates a test environment to simulate real business scenarios, calling the new plugin's account management interface and verifying whether the returned results meet the expected response specifications. After the test passes, the system updates the global adaptation relationship mapping table, officially including the plugin in the available plugin set of the corresponding resource provider. In this embodiment, by simulating resource provider configuration information to call the new plugin and verifying whether its returned results meet the expected response specifications, the matching test has automated verification capabilities, ensuring the compatibility and functionality of the new plugin before actual use. Therefore, it can reduce the risk of adaptation errors and improve system stability.

[0062] S403, establish the above-mentioned plugins, the account management functions of the above-mentioned plugins, and the adaptation relationship of the above-mentioned resource providers.

[0063] In some feasible implementations, the resource account management platform can establish compatibility relationships between various plugins, their account management functions, and resource providers through manual binding or automatic adaptation. The specific method can be determined based on the actual application scenario and is not limited here. It is understood that resource providers exist in various types or versions, and the resource providers applicable to a plugin are also influenced by factors such as the resource provider's type or version, the plugin's type or version, the plugin's account management functions, and the parameter templates associated with the plugin. Matching and binding can be performed to establish compatibility relationships between plugins, plugin functions, and resource providers. Here, establishing compatibility relationships can be achieved by defining interfaces and protocols, associating with configuration files, establishing registration mechanisms, using event-driven mechanisms, creating relationship tables, etc., and the specific method can be determined based on the actual application scenario and is not limited here.

[0064] In some feasible implementations, the resource account management platform can use a plugin adapter to match the plugins and account management functions adapted to each of the aforementioned resource providers, thereby establishing an adaptation relationship between the resource providers, their adapted plugins, and the plugins' account management functions. Here, the plugin adapter may include, but is not limited to, components or modules such as plugin interfaces, plugin implementation classes, adapter interfaces, adapter classes, configuration information, and manager classes. These components or modules can be integrated into the plugin adapter or separated from it, depending on the actual application scenario, and are not limited here. It can be understood that the plugin adapter can receive configuration information from each resource provider, retrieve various types of plugins from the plugin resource library based on the received configuration information, and return a list of matched plugins. Here, the configuration information can be the type of resource provider; based on the type of resource provider, available plugins in the plugin resource library are queried. Through the plugin adapter, an adaptation relationship between resource providers, plugins, and plugin functions can be established. It is understandable that a plugin adapter can obtain a plugin matching the resource provider based on parameters including but not limited to configuration information. The plugin and resource provider can be bound together using the adapter class within the plugin adapter (i.e., establishing the adaptation relationship as described above). Here, the binding process uses the adapter class to adapt the plugin's functionality to the resource provider's interface, passing the resource provider's reference to the plugin and vice versa, thus establishing an adaptation relationship between the resource provider, the plugin, and the plugin's functionality. This facilitates subsequent bidirectional communication and data transmission. Through this adaptation relationship, the resource provider can subsequently call the functions provided by the plugin. It is also understandable that after establishing the adaptation relationship between the resource provider, the plugin, and the plugin's functionality through the plugin adapter, the resource account management platform can store this adaptation relationship in storage spaces including but not limited to memory, databases, metadata services, and configuration files for subsequent maintenance and retrieval by the plugin adapter. The specific storage method can be determined based on the actual application scenario and is not limited here. Optionally, the resource account management platform may call one or more verification methods, including but not limited to connection testing, status testing, and functional testing, to test the compatibility between the plugin, the plugin function, and the resource provider, so as to ensure that the plugin and the resource provider are correctly associated, the plugin function is normal, and the resource provider responds normally. The specific method can be determined according to the actual application scenario, and there are no restrictions here.In this embodiment, a plug-in adapter is introduced. The plug-in adapter can match the configuration information of each resource provider to obtain the plug-ins and account management functions of each plug-in, so as to establish the adaptation relationship between each resource provider, plug-in, and plug-in account management function. The plug-in adapter can support multiple types of plug-ins and can serve resource providers under multiple resource configurations. It can improve the compatibility and flexibility of resource account management, enhance scalability, reduce unnecessary port calls or data conversions, simplify development and maintenance, and improve the overall performance and efficiency of the system.

[0065] Optionally, in some feasible implementations, after establishing the aforementioned plugins, their account management functions, and the adaptation relationships of the resource providers, the resource account management platform can configure plugin adapter identifiers for each resource provider. These identifiers mark the plugin adapters adapted to each resource provider, with resource providers using the same configuration information adapting to the same adapter. It can be understood that the resource account management platform can adapt different plugin adapters to resource providers with different configuration information. The plugin adapter identifier can be used to mark the plugin adapters adapted to the resource provider in the system, facilitating subsequent queries of the resource provider's adapted plugin adapters. Simultaneously, the plugin adapter corresponding to the resource provider can maintain the adaptation relationships between the resource provider, plugins, and plugin functions. Therefore, the corresponding plugin adapter can be found by identifying the plugin adapter identifier, facilitating queries of the adaptation relationships between the resource provider and the plugin. Here, the plugin adapter identifier can be a simple string, a universally unique identifier (UUID), a tag, or a more complex metadata structure, which can be determined according to the actual application scenario and is not limited here. For example, assuming the target resource is a MySQL resource, the resource account management platform can provide a MySQL plugin adapter to establish an adaptation relationship between the MySQL resource, the plugin, and the plugin functionality. After the above adaptation relationship is bound, the resource account management platform can automatically tag the MySQL resource with a plugin adapter identifier. For example, the MySQL resource can be tagged with `plugin:mysql-adapter`. Subsequently, the resource account management platform can find the MySQL plugin adapter based on the `plugin:mysql-adapter` tag on the MySQL resource, and then trigger the MySQL plugin adapter to return the plugin associated with the MySQL resource according to the above adaptation relationship, so as to execute the plugin's account management function. For details, please refer to the following embodiments, which will not be elaborated here. In this embodiment, after establishing the adaptation relationship between various resource providers, plugins, and plugin account management functions, a plugin adapter identifier can be configured for each resource provider. The plugin adapter identifier is used to mark the plugin adapter adapted by each resource provider. Resource providers with the same configuration information can adapt to the same adapter. In subsequent workflows, by identifying the plugin adapter identifier of the resource provider, the resource provider can be quickly identified and the plugins that have established an adaptation relationship with the resource provider can be located. This reduces the time overhead of plugin search, improves the efficiency of plugin resource management, and optimizes the flexibility of plugin scheduling. At the same time, the plugin adapter can support multiple types of plugins and serve resource providers under various resource configurations, which can improve the compatibility and flexibility of resource account management, enhance scalability, and increase applicability.

[0066] In some feasible implementations, when a change in the configuration information of the target resource is detected, a rematching process for the adaptation relationship is triggered. If the original target plugin is no longer compatible, a new plugin is rematched from the plugin resource library, and the adaptation relationship is updated. Specifically, the system continuously detects configuration information change events of the target resource through a configuration detection module. When a change is detected, the rematching process for the adaptation relationship is automatically triggered. First, the system compares the compatibility of the changed resource configuration with the original plugin. If the verification finds that the original plugin is no longer compatible (e.g., interface protocol change, data format mismatch, etc.), the intelligent plugin matching engine is activated. Based on the new configuration characteristics of the resource (including but not limited to API specifications, authentication methods, data models, etc.), the system selects the new plugin with the highest compatibility score from the plugin resource library. After matching is completed, the system automatically completes the loading and initialization of the new plugin and updates the adaptation relationship mapping table. In this embodiment, when a change in the resource configuration is detected, a rematching process for the adaptation relationship is triggered. If there is no match, a new plugin is selected and the adaptation relationship is updated. This gives the system dynamic adjustment capabilities, enabling it to automatically adapt to changes in the resource and avoid functional failure due to configuration changes, thus improving the system's adaptability.

[0067] In some feasible implementations, after executing the account management function, the operation logs returned by the target plugin are received, the operation logs are associated with and stored with the account information of the target resource provider, and a visual audit report is generated. In this embodiment of the application, receiving the operation logs after executing the account management function, associating and storing them with the account information of the target resource provider, and generating a visual audit report can completely record the account change history and provide visual analysis methods, thus enhancing the auditability of the system and facilitating compliance checks and problem backtracking.

[0068] S404, When a resource account management request from the target resource provider is received, the configuration information and account information of the target resource provider are filled into the parameter template of the target plugin adapted by the target resource provider according to the above adaptation relationship, wherein the target resource provider is any one of the above multiple resource providers.

[0069] In some feasible implementations, the resource account management platform can periodically or continuously detect whether it has received a resource account management request. When a resource account management request is received, it retrieves a plugin that is compatible with the target resource as the target plugin, and fills the target resource's configuration information and account information into the target plugin's parameter template. It can be understood that some or all of the account information required for resource account management, as well as the resource's configuration information, can be filled into the target plugin's parameter template. Then, based on the filled parameter template, the target plugin can be invoked to link to the target resource to perform the corresponding account management function. For example, assuming that "account discovery" resource account management is desired for the target resource, the aforementioned parameter template can have pre-configured fields for the resource's configuration information (such as resource type, version, basic configuration, etc.) and account information (such as initial account username, account permissions, etc.). The resource account management system can then, based on the current task (i.e., "account discovery"), retrieve the target resource's configuration information from storage space and fill it into the corresponding position in the parameter template. Here, configurable fields such as the type and version of the resource provider predefined in the parameter template will be overwritten or filled with the specific type and version in the target resource provider's configuration information, so that the target plugin can link to the target resource provider later. At the same time, configurable account information such as the username, role, and permissions preset in the parameter template can also be overwritten or filled with the account information in the aforementioned storage space. This allows the target plugin to know the basic information such as the target resource provider's account format and the initial account information. After linking to the target resource provider, it can scan the resource provider's account information and obtain all account information, basic account information, and account status that the target resource provider currently possesses. Here, the all account information can be added or deleted compared to the initial account information mentioned above, and the account information corresponding to the target account in the storage space can be updated to complete the "account discovery" function. The specifics can be determined according to the actual application scenario and are not limited here.

[0070] Optionally, in some feasible implementations, when a resource account management request is received, it can first be determined whether the request is valid. Only after confirming the validity of the request can the target plugin adapted to the target resource be retrieved. It is understood that the adaptation relationship can be stored in locations including, but not limited to, databases, configuration files, and cloud platform services. Before retrieving the adaptation relationship of the target resource, the identity of the current target resource can be identified. This identification can be performed through methods including, but not limited to, historical resource data and resource identifiers. The specific method can be determined based on the actual application scenario and is not limited here. For example, if the target resource's identity is verified, the resource account management request sent by the target resource is considered valid. After confirming the validity of the request, a plugin with an adaptation relationship to the target resource can be retrieved from the plugin resource library and used as the target plugin. Here, plugin idle state identification can also be achieved through plugin status monitoring, resource usage detection, and user activity detection. The specific method can be determined based on the actual application scenario and is not limited here.

[0071] In some feasible implementations, the parameter template filling process includes format validation of the target resource provider's account information; if validation fails, an error handling process is triggered; when validation passes, the account information is filled into the corresponding position of the parameter template according to the field mapping relationship. Specifically, the system first performs multi-dimensional validation of the configuration information and account information provided by the target resource provider through a data validation engine, including data type checks (such as strings, numbers, etc.), format matching (password complexity rules), mandatory field integrity checks, and business logic compliance checks (such as account validity period); a hierarchical error handling mechanism is adopted during the validation process, attempting to automatically correct minor format problems, and immediately terminating the process and generating an exception report containing error details and repair suggestions for serious errors; when all validations pass, the system calls the field mapping processor to accurately match the source account information to the corresponding field position of the parameter template according to predefined mapping rules, while performing real-time encryption processing on sensitive fields. In this embodiment, by performing format validation on the configuration information and account information of the target resource provider, and triggering an error handling process when the validation fails, and filling the parameter template according to the field mapping relationship when the validation passes, invalid or erroneous data can be prevented from entering the plugin execution process, and the uniformity of the data structure can be ensured. Therefore, the stability and security of account management operations can be improved.

[0072] Optionally, in some feasible implementations, when a resource account management request is received from the target resource provider, the resource account management platform can trigger the target plugin adapter marked by the target plugin adapter identifier to feed back the target plugin associated with the target resource provider according to the aforementioned adaptation relationship, and fill the configuration information and account information of the target resource provider into the parameter template of the target plugin. It is understood that the aforementioned target plugin adapter identifier is a plugin adapter identifier configured for the target resource provider; for details, please refer to the embodiment of the plugin adapter identifier in the above embodiments, which will not be elaborated here. In other words, the resource account management platform can obtain the target plugin adapter identifier of the target resource provider and identify the target plugin adapter marked by the target plugin adapter identifier based on this identifier, thereby triggering the target plugin adapter to feed back the target plugin associated with the target resource provider according to the aforementioned adaptation relationship. It is understood that the target plugin adapter can be used to maintain the adaptation relationship between the target resource provider, the target plugin, and the account management function of the target plugin. The aforementioned adaptation relationship can be stored in storage spaces including but not limited to memory, database, metadata services, and configuration files for maintenance and querying. The specific storage space can be determined according to the actual application scenario and is not limited here. The resource account management platform uses the target plugin adapter to populate the configuration and account information of the target resource into the parameter template of the target plugin. For example, assuming the target resource is a MySQL resource and the target plugin is a mysql-password-rotate-plugin instance, the MySQL plugin adapter of the resource account management platform can maintain the adaptation relationship between the MySQL resource, the target plugin mysql-password-rotate-plugin instance, and the target plugin functionality. After the adaptation relationship is established, the resource account management platform automatically tags the MySQL resource with the plugin:mysql-adapter tag as the identifier of the target adapter. When the resource account management platform receives a resource account management request from a MySQL resource, it can locate the MySQL plugin adapter through the `plugin:mysql-adapter` tag on the MySQL resource. This triggers the MySQL plugin adapter to return the target plugin instance `mysql-password-rotate-plugin` associated with the matched MySQL resource based on the aforementioned adaptation relationship. The configuration information and account information of the MySQL resource in the calling storage space can then be filled into the parameter template of the target plugin instance `mysql-password-rotate-plugin`. This allows the target plugin instance `mysql-password-rotate-plugin` to link to the target resource and execute the aforementioned target plugin function. The specific implementation can be determined based on the actual application scenario and is not limited here.In this embodiment, when a resource account management request from a target resource provider is received, the target plugin adapter marked by the target plugin adapter identifier can be triggered to feed back the target plugin associated with the target resource provider based on the adaptation relationship, and the configuration information and account information of the target resource provider can be filled into the parameter template of the target plugin. The target plugin adapter identifier can quickly identify the target plugin adapter adapted to the target resource provider and obtain the adaptation relationship maintained in the target plugin adapter, thereby quickly obtaining the target plugin adapted to the target resource provider. This reduces the time overhead of plugin lookup, improves the efficiency of plugin resource management, optimizes the flexibility of plugin scheduling, and allows the plugin adapter to support multiple types of plugins. Furthermore, various types of plugin adapters can serve resource providers under multiple resource configurations, maintaining the adaptation relationship between resource providers, plugins, and plugin functions. This improves the compatibility and flexibility of resource account management, enhances scalability, and has high applicability.

[0073] S405, based on the above parameter template, trigger the above target plugin to link to the above target resource provider and execute the above target plugin's account management function.

[0074] In some feasible implementations, based on a parameter template populated with the target resource provider's configuration and account information, the resource account management platform can trigger the target plugin to link to the target resource provider and execute account management functions. It is understood that the target plugin can read information from the populated parameter template, including but not limited to the target resource provider's access address, authentication information, communication protocol, and account information, to link to the target resource provider. The specific details can be determined based on the actual application scenario and are not limited here. Furthermore, the target plugin can also read the target resource provider's account information from the parameter template to execute the target plugin's account management functions on the aforementioned target resource provider's account. Here, the account management functions may include, but are not limited to, one or more of the following: resource account discovery, resource account addition, resource account deletion, or resource account modification. The specific details can be determined based on the actual application scenario and are not limited here.

[0075] In some feasible implementations, the resource account management platform can send the aforementioned parameter template and target plugin to the script engine. The script engine then calls the target plugin based on the parameter template, links to the target resource, and executes the target plugin's account management function. Here, the script engine can be one of a JavaScript engine, Python engine, Lua engine, Groovy engine, etc., and the specific choice is determined based on the actual application scenario without restriction. It is understood that the script engine can be deployed locally on the target resource or in the environment to which the target resource belongs, depending on the actual application scenario without restriction. It is understood that the script engine can pass necessary parameters to the target plugin based on the parameter template, such as the target resource's access address, authentication information, communication protocol, and account information, etc., depending on the actual application scenario and the resource, without restriction. In this embodiment, the configuration information and account information of the target resource provider, along with the parameter template and target plugin, can be sent to the script engine. The script engine then calls the target plugin based on the parameter template to link to the target resource provider and execute the target plugin's account management function, thereby realizing the resource account management of the target resource provider. The method of calling the plugin link through the script engine can improve the flexibility and scalability of resource account management. At the same time, it can further protect the security of the resource provider and has high applicability.

[0076] Furthermore, in some feasible implementations, the resource account management platform can generate a functional script for the target plugin based on the parameter template using the aforementioned script engine, and then call the target plugin to execute the functional script. This allows the target plugin to link to the target resource provider and perform its account management functions. These account management functions include one or more of the following: resource account discovery, resource account addition, resource account deletion, or resource account modification. Here, the parameter template can contain, but is not limited to, the target resource provider's access address and authentication information. The resource account management platform can configure the link path from the target plugin to the target resource provider based on the access address, and configure the linking account based on the authentication information. The link path and linking account can be used to trigger the target plugin to link to the target resource provider. The specific configuration and linking process can be determined according to the actual application scenario and are not limited here. Furthermore, the resource account management platform can obtain the target resource provider's account information from the parameter template using the script engine and configure the working parameters for the target plugin to perform resource account management functions based on this account information, thereby generating the functional script for the target plugin. Here, the aforementioned working parameters are used to trigger the target plugin to execute the account management function for the target resource account. In this embodiment, the script engine can generate a functional script for the target plugin based on the parameter template, and call the target plugin to execute the functional script, thereby linking the target plugin to the target resource and executing the target plugin's account management function. Generating functional scripts based on the parameter template associated with the plugin and the configuration and account information filled into the parameter template allows the script engine to call and execute multiple types of plugins to link to resource providers under various resource configurations without modifying the system code. This supports version or type updates for plugins or resource providers, enhances the flexibility and compatibility of calling plugins and executing resource account management, improves scalability, and increases applicability.

[0077] To facilitate understanding of the resource account management method process, the embodiments of this application combine... Figure 5 and Figure 6 This example uses a resource account management platform as the implementing entity. (See [link]) Figure 5 , Figure 5 This is another flowchart illustrating the resource account management method provided in this application embodiment. For example... Figure 5As shown, the resource account management platform can obtain the configuration and account information of resource providers. These resource providers can include, but are not limited to, servers, network devices, storage devices, terminal devices, security devices, operating systems, databases, middleware, etc. The platform can use a plugin adapter to match compatible plugins and their account management functions from the plugin resource library based on the resource provider's configuration information. The resource provider's configuration information can include its type or version; for example, the platform can obtain information such as the resource provider being a host and its version. The specific details are determined based on the actual application scenario and the resource provider, and are not limited here. The plugin resource library contains plugins of various types and account management functions, and these plugins can be designed based on the same set of plugin development rules. It can be understood that the plugins obtained by the plugin adapter based on the resource provider's configuration information are suitable for that resource provider. The acquisition of configuration and account information can be done periodically by the resource account management platform or initiated proactively by each resource provider, depending on the actual application scenario, and is not limited here. Furthermore, the resource account management platform can establish compatibility relationships between resource providers, plugins, and plugin functionalities through plugin adapters. This compatibility process involves using the adapter class of the plugin adapter to adapt the plugin's functionality to the resource provider's interface, passing resource provider references to plugins and vice versa, thus establishing the compatibility relationship between resource providers, plugins, and plugin functionalities. This facilitates subsequent bidirectional communication and data transmission between resource providers and plugins. Through this compatibility relationship, resource providers can subsequently utilize the functionalities provided by the plugins. The specific process for establishing this compatibility relationship can be determined based on the actual application scenario and is not limited here. Furthermore, the resource account management platform can assign plugin adapter identifiers to each resource provider. These identifiers are used to mark the plugin adapters adapted to by each resource provider; resource providers with the same configuration information can adapt to the same adapter. It is understandable that plugin adapter identifiers can be used to mark the plugin adapters adapted by resource providers in the system, facilitating subsequent queries of these adapters. Simultaneously, the plugin adapters corresponding to resource providers can maintain the compatibility relationships between resource providers, plugins, and plugin functionalities. Therefore, by identifying the plugin adapter identifier, the corresponding plugin adapter can be found, enabling queries of the compatibility relationship between resource providers and plugins. Here, the plugin adapter identifier can be a simple string, a universally unique identifier (UUID), a tag, or a more complex metadata structure; the specific method can be determined based on the actual application scenario and is not limited here.

[0078] For further details, please refer to the following: Figure 6 , Figure 6 This is another flowchart illustrating the resource account management method provided in this application embodiment. Figure 6 The process shown can be considered as... Figure 5 The process shown occurs after receiving a resource account management request from the target resource provider. Figure 6 The target resource shown can be Figure 5 Any of the resource providers shown will not be elaborated upon here. Figure 6 As shown, when the resource account management platform receives a resource account management request from the target resource provider, it can locate the target plugin adapter based on the target plugin adapter identifier on the target resource provider. This triggers the target plugin adapter to return the associated target plugin based on the adaptation relationship, filling the target resource provider's configuration information and account information into the target plugin's parameter template. Further, the resource account management platform can send the parameter template and the target plugin to the script engine. The script engine generates a functional script for the target plugin based on the parameter template and calls the target plugin to execute the script, thus linking the target plugin to the target resource provider and executing its account management function. Here, the parameter template can contain, but is not limited to, the target resource provider's access address and authentication information. The resource account management platform can configure the link path from the target plugin to the target resource provider based on the access address and the link account based on the authentication information. The link path and link account can be used to trigger the target plugin to link to the target resource provider. The specific configuration and linking processes can be determined based on the actual application scenario and are not limited here. Furthermore, the resource account management platform can obtain the target resource provider's account information from the parameter template through the script engine and configure the working parameters for the target plugin to perform resource account management functions based on the aforementioned account information, thereby generating the functional script for the target plugin. Here, the aforementioned working parameters are used to trigger the target plugin to perform account management functions for the aforementioned account information of the target resource account. It can be understood that resource account management content may include, but is not limited to, one or more of the following: resource account discovery, resource account addition, resource account deletion, or resource account modification. The specific details can be determined according to the actual application scenario and are not limited here.

[0079] In summary, the resource account management method provided in this application can obtain configuration and account information from multiple resource providers, as well as multiple plugins with account management functions and their corresponding parameter templates. This establishes an adaptation relationship between each plugin, its account management function, and each resource provider. When a resource account management request from a target resource provider is received, the configuration and account information of the target resource provider are filled into the parameter template of the target plugin adapted to that resource provider, based on the aforementioned adaptation relationship. Then, based on the filled parameter template, the target plugin is triggered to link to the target resource provider and execute the account management function, thereby achieving resource account management for the target resource provider. This method is compatible with account management for resource providers under various resource configurations, improving the flexibility of resource account management while protecting the security of resource providers, and exhibiting high applicability. Therefore, the resource account management method provided in this application can enhance user experience and strengthen the market competitiveness of products, providing various enterprises with a highly compatible, flexible, and secure resource account management solution.

[0080] Based on the description of the above embodiments of the resource account management method, this application also discloses a resource account management device. This resource account management device can be applied to… Figures 1 to 6 In the resource account management method of the illustrated embodiment, the device is used to execute the steps in the resource account management method. Here, the resource account management device can be the one described above. Figures 1 to 6 The entity executing the resource account management method in the illustrated embodiment. See also... Figure 7 , Figure 7 This is a schematic diagram of the structure of the resource account management device provided in this application embodiment. In this application embodiment, the resource account management device 70 can operate the following modules:

[0081] Resource management module 710 is used to obtain configuration information and account information from multiple resource providers;

[0082] The plugin management module 720 is used to obtain multiple plugins and the parameter templates associated with the above plugins. The above plugins have account management functions.

[0083] The aforementioned plugin management module 720 is also used to establish the account management functions for each of the aforementioned plugins and the adaptation relationships for each of the aforementioned resource providers.

[0084] The account management module 730 is used to, upon receiving a resource account management request from a target resource provider, fill the configuration information and account information of the target resource provider into the parameter template of the target plugin adapted to the target resource provider according to the above adaptation relationship, and based on the above parameter template, trigger the target plugin to link to the target resource provider and execute the account management function of the target plugin, wherein the target resource provider is any one of the above multiple resource providers.

[0085] In some feasible implementations, the above Figures 4 to 6 The implementation methods provided for each step in the resource account management method shown can be derived from... Figure 7 The various modules of the illustrated device are executed. For example, the above... Figure 4 In the resource account management method shown, step S401 can be performed by... Figure 7 The resource management module 710 in the device shown executes steps S402 and S403, which can be performed by... Figure 7 The plug-in management module 720 in the device shown executes steps S404 and S405, which can be performed by... Figure 7 The account management module 730 in the device shown is executed. The implementation method of the above-mentioned unit can be found in the implementation methods provided in the various steps of the above embodiments, and will not be repeated here.

[0086] In the embodiments of this application, the above Figure 7 The modules in the illustrated device can be individually or entirely combined into one or more other modules, or some of the modules can be further divided into multiple functionally smaller modules. This achieves the same operation without affecting the technical effects of the embodiments of this application. The above modules are based on logical function division. In practical applications, the function of one module can be implemented by multiple modules, or the function of multiple modules can be implemented by one module. In other feasible implementations of this application, the above device may also include other modules. In practical applications, these functions can also be implemented with the assistance of other modules, and can be implemented collaboratively by multiple modules, without limitation.

[0087] In summary, the resource account management device provided in this application embodiment comprises at least a resource management module, a plugin management module, and an account management module. It can acquire configuration and account information from multiple resource providers, as well as multiple plugins with account management functions and their corresponding parameter templates. This allows for the establishment of compatibility relationships between plugins, their account management functions, and various resource providers. When a resource account management request from a target resource provider is received, the configuration and account information of the target resource provider are filled into the parameter template of the target plugin adapted to that resource provider, based on the aforementioned compatibility relationships. Then, based on the filled parameter template, the target plugin is triggered to link to the target resource provider and execute the account management function, thereby achieving resource account management for the target resource provider. This device is compatible with account management for resource providers under various resource configurations, improving the flexibility of resource account management while protecting the security of resource providers, and exhibiting high applicability. Therefore, the resource account management device provided in this application embodiment can enhance user experience and strengthen the market competitiveness of products, providing a high-quality, large-scale, and efficient resource account management solution for various enterprises.

[0088] See Figure 8 , Figure 8 This is a schematic diagram illustrating an application scenario of the resource account management system provided in this application embodiment. For example... Figure 8 The resource account management system shown may include, for example: Figure 7 The resource account management device 70 shown may further include a script engine 71, a plugin adapter 72, and a plugin resource library 73 to execute the above-mentioned functions. Figures 3 to 6 The authentication method shown above provides the implementation of each step, that is, the above Figures 3 to 6 The implementation methods provided by each step in the authentication method shown can be derived from... Figure 8 The system shown executes the resource account management device 70, script engine 71, plugin adapter 72, and plugin resource library 73. For example, the above... Figure 3 The resource account management method shown can be used by Figure 8 The various modules in the resource account management device 70 execute the above. Figure 5 The resource account management method shown can be executed by the resource account management device 70, the plug-in adapter 72, and the plug-in resource library 73. Figure 6 The resource account management method shown is compared to Figure 5 A script engine 71 is introduced, which can be executed by the resource account management device 70, the script engine 71, the plugin adapter 72, and the plugin resource library 73. Here, the resource account management system can act as the executor of the aforementioned method embodiment; the specific execution method can be found in the aforementioned method embodiment, and will not be elaborated further here.

[0089] Optionally, in some feasible implementations, the plug-in adapter can be located within the resource account management device. That is, the resource account management device can consist of a resource management module, a plug-in management module, an account management module, and a plug-in adapter. The resource account management device can connect to an external plug-in resource library and a script engine deployed on the resource provider to realize the module functions in the aforementioned embodiments. The specific implementation can be determined according to the actual application scenario and is not limited here.

[0090] See Figure 9 , Figure 9 This is a schematic diagram of the structure of the computer device provided in an embodiment of this application. Figure 9 As shown, the computer device 900 can be used for the above-mentioned Figures 4-6The execution entity in the corresponding embodiment. The computer device 900 may include: a processor 901, a network interface 904, and a memory 905. Furthermore, the computer device 900 may also include: a user interface 903, and at least one communication bus 902. The communication bus 902 is used to implement communication between these components. The user interface 903 may include a display screen and a keyboard; optionally, the user interface 903 may also include a standard wired interface or a wireless interface. The network interface 904 may optionally include a standard wired interface or a wireless interface (such as a Wi-Fi interface). The memory 905 may be high-speed random access memory (RAM) or non-volatile memory, such as at least one disk storage device. Optionally, the memory 905 may also be at least one storage device located remotely from the aforementioned processor 901. Figure 9 As shown, the memory 905, which is a computer-readable storage medium, may include an operating system, a network communication module, a user interface module, and a device control application program.

[0091] The network interface 904 in the computer device 900 can also be connected to the aforementioned Figure 1 The terminal device 200c in the corresponding embodiment connects to the network, and the optional user interface 903 may further include a display screen and a keyboard. Figure 9 In the computer device 900 shown, the network interface 904 provides network communication functionality; the user interface 903 is mainly used to provide an input interface for developers; and the processor 901 can be used to call the device control application stored in the memory 905 to implement the aforementioned... Figure 3 Resource account management method in the corresponding embodiment.

[0092] It should be understood that the computer device 900 described in the embodiments of this application can execute the foregoing text. Figures 4 to 6 The description of the resource account management method in the corresponding embodiments will not be repeated here. Furthermore, the beneficial effects of using the same method will also not be repeated.

[0093] This application also provides a computer-readable storage medium storing a computer program, the computer program including program instructions, which are implemented when executed by a processor. Figures 4 to 6 For details on the resource account management methods provided in each step, please refer to the above. Figures 4 to 6 The implementation methods provided for each step will not be elaborated here.

[0094] The aforementioned computer-readable storage medium can be the resource account management device provided in any of the foregoing embodiments or the internal storage unit of the aforementioned computer device, such as the hard disk or memory of the computer device. The computer-readable storage medium can also be an external storage device of the computer device, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., provided on the computer device. Furthermore, the computer-readable storage medium can include both internal storage units and external storage devices of the computer device. The computer-readable storage medium is used to store the computer program and other programs and data required by the computer device. The computer-readable storage medium can also be used to temporarily store data that has been output or will be output.

[0095] The term "comprising," and any variations thereof, in the specification, claims, and drawings of this application are intended to cover non-exclusive inclusion. For example, a process, method, apparatus, product, or device that includes a series of steps or units is not limited to the steps or modules listed, but may optionally include steps or modules not listed, or may optionally include other steps or units inherent to such processes, methods, apparatus, products, or devices.

[0096] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application.

[0097] The methods and related apparatuses provided in this application are described with reference to the method flowcharts and / or structural diagrams provided in this application. Specifically, each block of the method flowchart and / or structural diagram, as well as combinations of blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing device to create a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing device, generate instructions for implementing the process. Figure 1 A schematic diagram of one or more processes and / or structures. Figure 1The computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 A schematic diagram of one or more processes and / or structures. Figure 1 The functions specified in one or more boxes. These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable apparatus for implementing the process. Figure 1 A process or multiple processes and / or structures illustrate the steps of the functions specified in one or more boxes.

[0098] The above-disclosed embodiments are merely preferred embodiments of this application and should not be construed as limiting the scope of this application. Therefore, any equivalent variations made in accordance with the claims of this application shall still fall within the scope of this application.

Claims

1. A method for managing resource accounts, characterized in that, The method includes: Obtain configuration and account information from multiple resource providers; Obtain multiple plugins and parameter templates associated with the plugins, wherein the plugins have account management functions; Establish the account management functions for each plugin and the adaptation relationships for each resource provider. When a resource account management request from a target resource provider is received, the configuration information and account information of the target resource provider are filled into the parameter template of the target plugin adapted by the target resource provider according to the adaptation relationship, wherein the target resource provider is any one of the plurality of resource providers; Based on the parameter template, the target plugin is triggered to link to the target resource provider and execute the target plugin's account management function.

2. The method according to claim 1, characterized in that, The step of triggering the target plugin to link to the target resource provider and execute the target plugin's account management function based on the parameter template includes: The parameter template and the target plugin are sent to the script engine. The script engine then calls the target plugin based on the parameter template to link to the target resource provider and executes the target plugin's account management function.

3. The method according to claim 2, characterized in that, The step of calling the target plugin to link to the target resource provider and executing the target plugin's account management function through the script engine based on the parameter template includes: The script engine generates a functional script for the target plugin based on the parameter template and calls the target plugin to execute the functional script, thereby linking the target plugin to the target resource provider and executing the target plugin's account management function. The account management function includes one or more of the following: resource account discovery, resource account addition, resource account deletion, or resource account modification.

4. The method according to claim 1, characterized in that, The establishment of the various plugins, the account management functions of the various plugins, and the adaptation relationships of the various resource providers includes: By matching the plugin adapters, the plugins adapted to each resource provider and the account management functions of the plugins are obtained, so as to establish the adaptation relationship between each resource provider, the plugins adapted to the resource provider, and the account management functions of the plugins.

5. The method according to claim 4, characterized in that, After establishing the compatibility relationships between each plugin, the account management function of each plugin, and each resource provider, the method further includes: Configure a plugin adapter identifier for each of the resource providers, wherein the plugin adapter identifier is used to mark the plugin adapter adapted to each of the resource providers, and resource providers with the same configuration information are adapted to the same adapter. When a resource account management request from a target resource provider is received, the configuration information and account information of the target resource provider are filled into the parameter template of the target plugin adapted by the target resource provider according to the adaptation relationship, including: When a resource account management request is received from the target resource provider, the target plugin adapter marked by the target plugin adapter identifier is triggered to feed back the target plugin associated with the target resource provider according to the adaptation relationship. The configuration information and account information of the target resource provider are filled into the parameter template of the target plugin. The target plugin adapter identifier is the plugin adapter identifier configured for the target resource provider.

6. The method according to any one of claims 1-5, characterized in that, Before establishing the compatibility relationships between each plugin, the account management function of each plugin, and each resource provider, the method further includes: Multiple plugins are generated based on plugin development rules and various resource configurations, and the account management function of each plugin is configured. The multiple plugins and the account management function of each plugin are stored in the database to generate a plugin resource library. The plugin development rules are used to standardize the calling format of each plugin.

7. The method according to any one of claims 1-5, characterized in that, The process of obtaining multiple plugins and the parameter templates associated with those plugins includes: The plugin and parameter template that match the configuration information of the resource provider are dynamically loaded from a pre-built plugin repository, wherein the parameter template contains configurable fields and validation rules.

8. The method according to any one of claims 1-5, characterized in that, The method further includes: When a new plugin is detected in the plugin repository, the function declaration of the plugin is automatically scanned; Based on the aforementioned functional declaration, update the adaptation relationship and conduct matching tests between the unadapted resource providers and the account management function of the new plugin.

9. The method according to any one of claims 1-5, characterized in that, The method further includes: When a change in the configuration information of the target resource is detected, the adaptation relationship rematch process is triggered. If the original target plugin is no longer compatible, a new plugin will be matched from the plugin repository and the compatibility relationship will be updated.

10. The method according to any one of claims 1-5, characterized in that, The process of filling in the parameter template includes: The configuration information and account information of the target resource provider are validated in a specific format. When the verification passes, the configuration information and the account information are filled into the corresponding positions of the parameter template according to the field mapping relationship.

11. A resource account management device, characterized in that, The device includes: The resource management module is used to obtain configuration information and account information from multiple resource providers; The plugin management module is used to obtain multiple plugins and the parameter templates associated with the plugins. The plugins have account management functions. The plugin management module is also used to establish the account management functions of each plugin and the adaptation relationship of each resource provider. The account management module is used to, upon receiving a resource account management request from a target resource provider, fill the configuration information and account information of the target resource provider into the parameter template of the target plugin adapted by the target resource provider according to the adaptation relationship, and based on the parameter template, trigger the target plugin to link to the target resource provider and execute the account management function of the target plugin, wherein the target resource provider is any one of the multiple resource providers.

12. A terminal device, characterized in that, The terminal device includes a processor and a memory; The processor is connected to the memory, wherein the memory is used to store program code, and the processor is used to call the program code to execute the method as described in any one of claims 1-10.

13. A resource account management system, characterized in that, The resource account management system includes: a script engine, a plugin adapter, a plugin resource library, and the terminal device as described in claim 12.

Images