Authority management method and device, equipment and medium

Abstract

The invention provides an authority management method and device, equipment and a medium, and belongs to the technical field of computers. The method comprises the steps that configuration data corresponding to a plurality of micro application programs are obtained from front-end development devices corresponding to the micro application programs respectively, and the configuration data comprise permission data; displaying an authority management interface; and in response to dragging a first node of the permission tree of the first micro-application program into the permission tree of the second micro-application program in the permission management interface, adding permission data corresponding to the first node into page data of the second micro-application program, so that the second micro-application program has a front-end permission corresponding to the first node. According to the scheme, the code of the second micro-application does not need to be manually modified, and the development efficiency is improved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a permission management method, device, equipment and medium. Background Art

[0002] With the continuous development of computer technology, applications provide more and more functions. In order to facilitate the maintenance of applications, currently, applications can be split into multiple micro-applications according to their functions. Each micro-application is developed independently and then assembled according to requirements. Since each micro-application is developed independently, when it is necessary to use a unified authentication logic on the front end of multiple micro-applications, the development teams of multiple micro-applications need to edit the code of their respective micro-applications respectively, which leads to low development efficiency. Summary of the invention

[0003] The embodiment of the present application provides a permission management method, device, equipment and medium, which improves development efficiency. The technical solution is as follows:

[0004] In one aspect, a rights management method is provided, the method comprising:

[0005] Acquire configuration data corresponding to the plurality of micro-applications from front-end development devices corresponding to the plurality of micro-applications, the configuration data including permission data, which is data for implementing the front-end permissions provided by the micro-applications;

[0006] Displaying a permission management interface, wherein the permission management interface is used to display a permission tree of the plurality of micro-applications based on the permission data of the plurality of micro-applications;

[0007] In response to dragging the first node of the permission tree of the first micro-application to the permission tree of the second micro-application in the permission management interface, the permission data corresponding to the first node is added to the page data of the second micro-application so that the second micro-application has the front-end permission corresponding to the first node.

[0008] In a possible implementation, the page data includes a first view component; and adding the permission data corresponding to the first node to the page data of the second micro-application so that the second micro-application has the front-end permission corresponding to the first node includes:

[0009] The permission data corresponding to the first node is added to the first view component of the second micro-application so that the second micro-application displays the access options corresponding to the front-end permission in the display area corresponding to the first view component, and the front-end permission is the front-end permission corresponding to the first node.

[0010] In a possible implementation, the first view component is a menu view component.

[0011] In a possible implementation, the permission data includes a route of the front-end permission corresponding to the first node, and in response to dragging the first node of the permission tree of the first micro-application to the permission tree of the second micro-application in the permission management interface, adding the permission data corresponding to the first node to the page data of the second micro-application so that the second micro-application has the front-end permission corresponding to the first node, including:

[0012] In response to dragging the first node of the permission tree of the first micro-application to the permission tree of the second micro-application in the permission management interface, the route in the permission data corresponding to the first node is added to the page data of the second micro-application so that the page of the second micro-application has the function of accessing the front-end permission corresponding to the first node.

[0013] In a possible implementation, after adding the permission data corresponding to the first node to the page data of the second micro-application, the method further includes:

[0014] Updating the page access address of the second micro-application;

[0015] Sending an updated page access address and the page data after adding the permission data to the server of the main application, so that the server replaces the page access address of the second micro-application with the updated page access address, and replaces the page data of the second micro-application with the page data after adding the permission data, the main application including the multiple micro-applications.

[0016] In a possible implementation, the configuration data further includes a page access address of the micro-application; and the method further includes:

[0017] Displaying a menu management interface corresponding to the main application, the menu management interface including a menu of the main application and program identifiers corresponding to the plurality of micro-applications, the menu of the main application including program identifiers of each micro-application launched in the main application;

[0018] In response to adding the program identifier of the third micro-application to the menu, the program identifier and page access address of the third micro-application are added to the menu view component of the main application; or, in response to deleting the program identifier of the fourth micro-application from the menu, the program identifier and page access address of the fourth micro-application are deleted from the menu view component of the main application.

[0019] In a possible implementation, the configuration data further includes a page access address of the micro-application, the page access address includes a timestamp, and different timestamps correspond to different versions of the micro-application; the method further includes:

[0020] For any micro-application, if the timestamp in the obtained page access address is different from the timestamp in the page access address obtained last time, the configuration data of the micro-application is sent to the server corresponding to the main application so that the server updates the configuration data of the micro-application, and the main application includes the multiple micro-applications.

[0021] In another aspect, a rights management device is provided, the device comprising:

[0022] An acquisition module, used to acquire configuration data corresponding to the plurality of micro-applications from front-end development devices corresponding to the plurality of micro-applications, wherein the configuration data includes permission data, and the permission data is data for implementing the front-end permissions provided by the micro-applications;

[0023] A display module, configured to display a permission management interface, wherein the permission management interface is configured to display a permission tree of the plurality of micro-applications based on the permission data of the plurality of micro-applications;

[0024] An adding module is used to add permission data corresponding to the first node of the permission tree of the first micro-application to the permission tree of the second micro-application in response to dragging the first node of the permission tree of the first micro-application in the permission management interface, so that the second micro-application has the front-end permission corresponding to the first node.

[0025] In one possible implementation, the page data includes a first view component; the adding module is used to add the permission data corresponding to the first node to the first view component of the second micro-application, so that the second micro-application displays the access options corresponding to the front-end permissions in the display area corresponding to the first view component, and the front-end permissions are the front-end permissions corresponding to the first node.

[0026] In a possible implementation, the first view component is a menu view component.

[0027] In one possible implementation, the permission data includes the route of the front-end permission corresponding to the first node, and the adding module is used to add the route in the permission data corresponding to the first node to the page data of the second micro-application in response to dragging the first node of the permission tree of the first micro-application to the permission tree of the second micro-application in the permission management interface, so that the page of the second micro-application has the function of accessing the front-end permission corresponding to the first node.

[0028] In a possible implementation manner, the device further includes:

[0029] An updating module, used for updating the page access address of the second micro-application;

[0030] A sending module is used to send an updated page access address and page data after adding the permission data to the server of the main application, so that the server replaces the page access address of the second micro-application with the updated page access address, and replaces the page data of the second micro-application with the page data after adding the permission data. The main application includes the multiple micro-applications.

[0031] In a possible implementation, the configuration data also includes a page access address of the micro-application; the display module is further used to display a menu management interface corresponding to the main application, the menu management interface includes a menu of the main application and program identifiers corresponding to the multiple micro-applications, and the menu of the main application includes program identifiers of each micro-application launched in the main application;

[0032] The adding module is also used to, in response to adding the program identifier of the third micro-application to the menu, add the program identifier and page access address of the third micro-application to the menu view component of the main application; or, in response to deleting the program identifier of the fourth micro-application from the menu, delete the program identifier and page access address of the fourth micro-application from the menu view component of the main application.

[0033] In a possible implementation, the configuration data further includes a page access address of the micro-application, the page access address includes a timestamp, and different timestamps correspond to different versions of the micro-application; the device further includes:

[0034] The sending module is used to send the configuration data of any micro-application to the server corresponding to the main application if the timestamp in the page access address obtained is different from the timestamp in the page access address obtained last time, so that the server updates the configuration data of the micro-application, and the main application includes the multiple micro-applications.

[0035] On the other hand, a configuration device is provided, which includes a processor and a memory, wherein at least one program code is stored in the memory, and the at least one program code is loaded and executed by the processor to implement the permission management method as described in any of the above implementations.

[0036] On the other hand, a computer-readable storage medium is provided, wherein at least one program code is stored in the computer-readable storage medium, and the at least one program code is loaded and executed by a processor to implement the rights management method as described in any of the above implementations.

[0037] On the other hand, a computer program product is provided, the computer program product comprising at least one program code, the at least one program code being loaded and executed by a processor to implement the rights management method as described in any of the above implementations.

[0038] The beneficial effects of the technical solution provided by the embodiments of the present application include at least:

[0039] An embodiment of the present application provides a permission management method, which can add a node of a permission tree of a first micro-application to a permission tree of a second micro-application through a permission management interface, so that permission data corresponding to the first node is added to the page data of the second micro-application. Since the permission data is data used to implement the front-end permissions provided by the micro-application, after adding the permission data corresponding to the first node, the second micro-application can also implement the permissions corresponding to the first node, without manually modifying the code of the second micro-application, thereby improving development efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0041] Figure 1 It is a schematic diagram of an implementation environment provided by an embodiment of the present application;

[0042] Figure 2 It is a flowchart of a permission management method provided by an embodiment of the present application;

[0043] Figure 3 It is a flowchart of a permission management method provided by an embodiment of the present application;

[0044] Figure 4 It is a structural diagram of a rights management device provided in an embodiment of the present application;

[0045] Figure 5 It is a structural diagram of a rights management device provided in an embodiment of the present application;

[0046] Figure 6 It is a structural diagram of a configuration device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0047] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below in conjunction with the accompanying drawings.

[0048] The terms "first", "second", "third" and "fourth" etc. in the specification and claims of the present application and the drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes steps or units that are not listed, or optionally includes other steps or units inherent to these processes, methods, products or devices.

[0049] The permission management method provided in the embodiment of the present application can be applied to the permission management of multiple micro-applications in the same application. For example, the permission management method provided in the embodiment of the present application can be applied to browser applications with separated front-end and back-end development, and can realize dynamic update of micro-applications in browser applications and front-end permission management.

[0050] The permission management method provided in the embodiment of the present application is performed by a configuration device. In some embodiments, the configuration device includes a data aggregation management module, a product line management module and a permission tree management module. Among them, the aggregation management module is used to aggregate the configuration data of each micro-application, and when the configuration data of any micro-application is updated, the updated configuration data is promptly synchronized to the server of the main application to achieve the update of the client. Product line management is used to manage which micro-application entrances are displayed in the menu of the main application to control the online and offline of the micro-application. The permission tree management module is used to uniformly manage the permission trees of multiple micro-applications, and the front-end permissions provided by any micro-application can be transplanted to another micro-application.

[0051] Figure 1 is a schematic diagram of an implementation environment provided by an embodiment of the present application, such as Figure 1 As shown, the implementation environment includes a front-end development device 101 corresponding to a plurality of micro-applications, a configuration device 102, a server 103 corresponding to a main application, and a plurality of terminals 104 for accessing the main application. The front-end development device 101 establishes a communication connection with the configuration system 102, the configuration system 102 establishes a communication connection with the server 103 corresponding to the main application, and the server 103 establishes a communication connection with the plurality of terminals 104.

[0052] Among them, the front-end development device 101 can be any device with front-end development function, such as a desktop computer, a laptop computer, a tablet computer, a mobile phone, etc., and the embodiment of the present application does not limit the front-end development device. The configuration device 102 can be a desktop computer, a laptop computer, a tablet computer, a server, etc., and the embodiment of the present application does not limit the configuration device 102. The server 103 is the background server of the main application, and the main application includes the multiple micro-applications. The terminal 104 can be a computer, a mobile phone, a tablet computer or other terminals.

[0053] In some embodiments, the developer of the micro-application revises the micro-application in the front-end development device 101 of the micro-application. After the revision is completed, the front-end development device 101 sends the configuration data of the micro-application to the configuration device 102. The configuration device 102 synchronizes the latest micro-application version to the server 103 based on the configuration data, so that the developer does not need to manually modify the code in the server 103 to update the micro-application. In addition, the configuration device 102 also provides a permission management interface, through which the front-end permissions provided by any micro-application can be transplanted to another micro-application. In some embodiments, the configuration device 102 also provides a menu management interface, through which any micro-application can be launched and unlaunched.

[0054] Figure 2 is a flowchart of a permission management method provided in an embodiment of the present application. The present application embodiment takes the configuration device as an example for illustrative explanation. Figure 2 , the method comprising:

[0055] 201. A configuration device obtains configuration data corresponding to a plurality of micro-applications from front-end development devices corresponding to the plurality of micro-applications, wherein the configuration data includes permission data, and the permission data is data for implementing the front-end permissions provided by the micro-applications.

[0056] The front-end development device corresponding to the micro-application is a device used to develop the front-end code of the micro-application. After the micro-application is put into use, the front-end development device can also revise the micro-application, change the page display style of the micro-application during the revision, and increase, reduce or change the front-end permissions of the micro-application. Front-end permissions refer to the access and / or operation permissions to page resources. For example, to add query permissions in the micro-application, it is necessary to provide page resources for query in the micro-application, provide users with permissions to access and / or operate the page resources, and enable the micro-application to have query permissions.

[0057] Permission data is data used to implement the front-end permissions provided by the micro-application. The permission data may include at least one of the code run to implement the front-end permissions, the route corresponding to the front-end permissions, the page resources corresponding to the front-end permissions, the permission tree, etc. The embodiment of the present application does not limit the permission data.

[0058] The configuration data is the basic data of the micro-application. In some embodiments, the configuration data includes at least one of a micro-application page access address and permission data.

[0059] 202. The configuration device displays a permission management interface, where the permission management interface is used to display permission trees of multiple micro-applications based on permission data of the multiple micro-applications.

[0060] In some embodiments, permissions are hierarchical, for example, tenant management permissions include tenant data query permissions and tenant data editing permissions. Among them, tenant data query permissions and tenant data editing permissions are the next level permissions of tenant management permissions. Therefore, in order to facilitate the management of permissions, the permission tree of multiple micro-applications is displayed in the permission management interface.

[0061] In some embodiments, the permission data includes a permission tree, that is, the configuration device reads the permission tree of the micro-application from the front-end development device and displays the permission tree of the micro-application in the permission management interface. In other embodiments, the permission data is the code that implements the front-end permission, and the configuration data generates the permission tree of the micro-application based on the nested relationship of each permission in the permission data.

[0062] 203. In response to dragging the first node of the permission tree of the first micro-application to the permission tree of the second micro-application in the permission management interface, the configuration device adds the permission data corresponding to the first node to the page data of the second micro-application, so that the second micro-application has the front-end permission corresponding to the first node.

[0063] The nodes in the permission tree correspond one-to-one to the permissions provided by the micro-application, and the first node can be any node in the micro-application. In some embodiments, the permission data corresponding to the first node includes code for implementing the front-end permission corresponding to the first node, and the configuration device adds the permission data to the page data of the second micro-application so that the page of the second micro-application has the front-end permission corresponding to the first node, and the user can use the front-end permission in the page of the second micro-application.

[0064] In other embodiments, the permission data includes a route for front-end permissions, and the configuration device adds the permission data corresponding to the first node to the page data of the second micro-application, including: the configuration device adds the route for the front-end permissions corresponding to the first node to the page data of the second micro-application, so that the front-end permissions corresponding to the first node can be linked to in the page of the second application.

[0065] It should be noted that if the first node has child nodes, when the front-end permissions corresponding to the first node are transplanted to the second micro-application, the front-end permissions corresponding to each child node of the first node will be transplanted to the second micro-application together. For example, the tenant management permission includes the tenant data query permission and the tenant data editing permission. When the first node corresponds to the tenant management permission, the permission data corresponding to the tenant data query permission and the tenant data editing permission will be added to the page data of the second micro-application.

[0066] The permission management method provided in the embodiment of the present application can add the node of the permission tree of the first micro-application to the permission tree of the second micro-application through the permission management interface, so that the permission data corresponding to the first node is added to the page data of the second micro-application. Since the permission data is data used to implement the front-end permissions provided by the micro-application, the second micro-application can also implement the front-end permissions corresponding to the first node without manually modifying the code of the second micro-application, thereby improving development efficiency.

[0067] In a possible implementation, the page data includes a first view component; and adding permission data corresponding to the first node to the page data of the second micro-application so that the second micro-application has the permission corresponding to the first node includes:

[0068] The permission data corresponding to the first node is added to the first view component of the second micro-application program, so that the second micro-application program displays access options corresponding to the permission in the display area corresponding to the first view component, where the permission is the permission corresponding to the first node.

[0069] In a possible implementation, the target view component is a menu view component.

[0070] In one possible implementation, the permission data includes a route of the front-end permission corresponding to the first node, and in response to dragging the first node of the permission tree of the first micro-application to the permission tree of the second micro-application in the permission management interface, the permission data corresponding to the first node is added to the page data of the second micro-application so that the second micro-application has the front-end permission corresponding to the first node, including: in response to dragging the first node of the permission tree of the first micro-application to the permission tree of the second micro-application in the permission management interface, the route in the permission data corresponding to the first node is added to the page data of the second micro-application so that the page of the second micro-application has the function of accessing the front-end permission corresponding to the first node.

[0071] In a possible implementation, after adding the permission data corresponding to the first node to the page data of the second micro-application, the method further includes:

[0072] Updating the page access address of the second micro-application;

[0073] Send the updated page access address and the page data after adding the permission data to the server of the main application so that the server replaces the page access address of the second micro-application with the updated page access address and replaces the page data of the second micro-application with the page data after adding the permission data. The main application includes multiple micro-applications.

[0074] In a possible implementation, the configuration data further includes a page access address of the micro-application; and the method further includes:

[0075] Displaying a menu management interface corresponding to the main application, the menu management interface including a menu of the main application and program identifiers corresponding to multiple micro-applications, the menu of the main application including program identifiers of each micro-application launched in the main application;

[0076] In response to adding the program identifier of the third micro-application to the menu, the program identifier and the page access address of the third micro-application are added to the menu view component of the main application; or, in response to deleting the program identifier of the fourth micro-application from the menu, the program identifier and the page access address of the fourth micro-application are deleted from the menu view component of the main application.

[0077] In a possible implementation, the configuration data further includes a page access address of the micro-application, the page access address includes a timestamp, and different timestamps correspond to different versions of the micro-application; and the method further includes:

[0078] For any micro-application, if the timestamp in the obtained page access address is different from the timestamp in the page access address obtained last time, the configuration data of the micro-application is sent to the server corresponding to the main application so that the server updates the configuration data of the micro-application. The main application includes multiple micro-applications.

[0079] All the above optional technical solutions can be arbitrarily combined to form optional embodiments of the present application, which will not be described one by one here.

[0080] Figure 3 is a flowchart of a permission management method provided in an embodiment of the present application. The embodiment of the present application is illustrated by taking the execution subject as a configuration device as an example. Figure 3 , the method comprising:

[0081] 301. A configuration device obtains configuration data corresponding to a plurality of micro-applications from front-end development devices corresponding to the plurality of micro-applications, wherein the configuration data includes permission data and a page access address.

[0082] In some embodiments, the front-end development devices corresponding to the plurality of micro-applications respectively provide an interface for querying at least one of the permission data and the page access address of the micro-application. Optionally, the permission data includes a permission tree and a route, and the front-end development devices corresponding to the plurality of micro-applications respectively provide an interface for querying the permission tree and the route of the micro-application.

[0083] In some embodiments, after the configuration device is started, it can actively obtain the configuration data corresponding to the multiple micro-applications through the interface. In other embodiments, after the micro-application is released, the front-end development device actively sends the configuration data of the micro-application to the configuration device.

[0084] In the embodiment of the present application, the main application includes the multiple micro-applications, and the main application can be a browser application. The multiple micro-applications are opened by page access. One micro-application corresponds to one page access address, and the user opens the corresponding micro-application by accessing the page access address. The page jump inside the micro-application is realized by routing, that is, when opening different pages inside the micro-application, the page access domain name address remains unchanged, and the routing address changes. Different front-end permissions correspond to different routing addresses.

[0085] 302. The configuration device displays a permission management interface, where the permission management interface is used to display permission trees of the multiple micro-applications based on the permission data of the multiple micro-applications.

[0086] When the computer device displays the permission trees of the multiple micro-applications, the permission trees of the multiple micro-applications may be displayed in an expanded manner or in an overlaid manner, which is not limited in the embodiments of the present application.

[0087] In some embodiments, the permission management interface includes program identifiers of multiple micro-applications, such as a program identifier of a first micro-application and a program identifier of a second micro-application. After the user clicks on the program identifier of any micro-application, the first-level permissions of the micro-application can be expanded and displayed. After clicking on the first-level permissions of the micro-application, the second-level permissions belonging to the first-level permissions can continue to be displayed, and so on.

[0088] 303. In response to dragging the first node of the permission tree of the first micro-application to the permission tree of the second micro-application in the permission management interface, the configuration device adds the permission data corresponding to the first node to the page data of the second micro-application, so that the second micro-application has the front-end permission corresponding to the first node.

[0089] The first micro-application may be any micro-application among the plurality of micro-applications, the second micro-application may be any micro-application among the plurality of micro-applications, and the first micro-application and the second micro-application are two different micro-applications.

[0090] In an embodiment of the present application, if a user drags any node in the permission tree of any micro-application to the permission data of another micro-application, the permission data corresponding to the node is added to the page data of the other micro-application. Since the permission data is data for implementing the front-end permission corresponding to the first node, after the permission data is added to the page data of the other micro-application, the page of the other micro-application can also provide the front-end permission.

[0091] For example, the permission corresponding to the first node is tenant management permission. After adding the data corresponding to the tenant management permission to the page data of the second micro-application, the page of the second micro-application can display the tenant management option. After the user clicks the tenant management option, he can view the tenant data or edit the tenant data, so that the second micro-application has tenant management permission.

[0092] In a possible implementation, considering that other content is to be displayed in the page of the second micro-application, in order to avoid affecting the display of other content in the second micro-application after adding permission data in the page data of the second micro-application, the permission data can be added to an existing view component of the second micro-application, so that the second micro-application displays the access options corresponding to the permission in the display area corresponding to the view component. In some embodiments, the page data includes a first view component; adding the permission data corresponding to the first node to the page data of the second micro-application so that the second micro-application has the permission corresponding to the first node, including: adding the permission data corresponding to the first node to the first view component of the second micro-application so that the second micro-application displays the access options corresponding to the front-end permission in the display area corresponding to the first view component, and the front-end permission is the front-end permission corresponding to the first node.

[0093] The first view component may be any view component. In some embodiments, the first view component is a view component specifically used to display access options of front-end permissions added through the permission management interface. In other embodiments, the first view component may be a component used to display any page resource of the second micro-application.

[0094] Optionally, the first view component is a menu view component, that is, the access option corresponding to the added permission is displayed in the menu of the second micro-application. Since the display rule of the menu view component is to display the objects in the menu data table in sequence, adding the permission data to the menu view component of the second micro-application will not affect the display of other content in the second micro-application.

[0095] It should be noted that since the embodiment of the present application adds the permission data of the first micro-application to the page data of the second micro-application, the page displayed when accessing the permission in the second micro-application is the same as the page displayed when accessing the permission in the first micro-application, which can be regarded as opening the relevant page of the first micro-application in the second micro-application.

[0096] In some embodiments, the permission data corresponding to the first node includes the route of the front-end permission corresponding to the first node. In response to dragging the first node of the permission tree of the first micro-application to the permission tree of the second micro-application in the permission management interface, the configuration device adds the permission data corresponding to the first node to the page data of the second micro-application so that the second micro-application has the front-end permission corresponding to the first node, including: in response to dragging the first node of the permission tree of the first micro-application to the permission tree of the second micro-application in the permission management interface, adding the route in the permission data corresponding to the first node to the page data of the second micro-application so that the page of the second micro-application has the function of accessing the front-end permission corresponding to the first node. By adding the route of the front-end permission corresponding to the first node to the page data of the second micro-application, the user can open the page of the corresponding front-end permission in the first micro-application in the page of the second micro-application.

[0097] Optionally, the page data of the second micro-application includes a first view component, and the configuration device adds the route in the permission data corresponding to the first node to the page data of the second micro-application so that the page of the second micro-application has the function of accessing the front-end permission corresponding to the first node, including: the configuration device adds the route in the permission data corresponding to the first node to the first view component of the second micro-application so that the second micro-application displays the access option corresponding to the front-end permission in the display area corresponding to the first view component. Optionally, the first view component is a menu view component.

[0098] 304. The configuration device updates the page access address of the second micro-application, and sends the updated page access address and the page data after adding the permission data to the server of the main application, so that the server replaces the page access address of the second micro-application with the updated page access address, and replaces the page data of the second micro-application with the page data after adding the permission data, and the main application includes multiple micro-applications.

[0099] Considering that after adding permission data to the page data of the second micro-application, the second micro-application has changed, and the change needs to be synchronized to the client. In order to automatically synchronize the latest data to the server after the micro-application is updated to ensure that the latest content is presented to the client, the embodiment of the present application updates the page access address of the second micro-application after adding permission data to the page data of the second micro-application, and sends the updated page access address and the page data after adding permission data to the server of the main application, so that the server replaces the page access address of the second micro-application with the updated page access address, and replaces the page data of the second micro-application with the page data after adding permission data.

[0100] In some embodiments, the client is provided with a cache mechanism. For some static resources, the client no longer reads from the server, but reads from the local cache. In order to synchronize the second micro-application to the client in time after the update, the page access address of the micro-application includes a timestamp. When the computer device updates the page access address of the second micro-application, it updates the timestamp in the page access address of the second micro-application. When the client requests data from the server, it carries the timestamp in the page access address of the second micro-application. If the timestamp is different from the current timestamp of the page access address of the second micro-application, the server sends the page data of the second micro-application to the client so that the client displays the latest second micro-application.

[0101] It should be noted that the above steps are only illustrative of an example in which a user updates a micro-application through a permission management interface. In another embodiment, a developer can also update the micro-application in a front-end development device, and the front-end development device generates a page access address of the updated micro-application. Optionally, the page access address includes a timestamp, and different timestamps correspond to different versions of the micro-application. Therefore, after the computer device obtains the configuration data of the micro-application, for any micro-application, if the timestamp in the obtained page access address is different from the timestamp in the page access address obtained last time, the configuration data of the micro-application is sent to the server corresponding to the main application, so that the server updates the configuration data of the micro-application.

[0102] In other embodiments, the configuration device also sends the front-end permission verification logic to the server corresponding to the main application. The front-end permission verification logic is a piece of code used to perform front-end permission verification. After each micro-application completes page registration, it can directly use the front-end permission verification logic to perform permission verification on the options / buttons on the front-end permissions in the page.

[0103] 305. The configuration device displays a menu management interface corresponding to the main application, the menu management interface including a menu of the main application and program identifiers corresponding to multiple micro-applications, the menu of the main application including program identifiers of each micro-application launched in the main application.

[0104] In the related art, if any micro-application is launched or unlaunched in the main application, the menu code of the main application needs to be modified to achieve this, which not only increases the workload of developers, reduces development efficiency, but also increases the error rate. In order to solve this problem, a menu management interface corresponding to the main application is provided in the embodiment of the present application. Developers can add any micro-application to the menu through the menu management interface to launch the micro-application, and can also delete any micro-application in the menu to launch the micro-application.

[0105] It should be noted that the permission management interface and the menu management interface are two interfaces provided by the configuration device. The user can open the permission management interface first, or can open the menu management interface first. This embodiment of the present application does not limit this.

[0106] 306. In response to adding the program identifier of the third micro-application to the menu, the configuration device adds the program identifier and the page access address of the third micro-application to the menu view component of the main application; or, in response to deleting the program identifier of the fourth micro-application from the menu, deletes the program identifier and the page access address of the fourth micro-application from the menu view component of the main application.

[0107] In the embodiments of the present application, only deleting the program identifier and the page access address is used as an example for exemplary description. In some embodiments, the menu view component corresponds to a menu data table, and a data item in the menu data table corresponds to an option in the menu. The data item includes the program identifier and the page access address, and may also include other data. Deleting the program identifier and the page access address of the fourth micro-application from the menu view component of the main application includes: deleting the data corresponding to the fourth micro-application from the menu data table.

[0108] 307. The configuration device updates the page access address of the main application, and sends the updated page access address and page data to the main application, so that the server replaces the page access address of the main application with the updated page access address, and replaces the page data of the main application with the updated page data.

[0109] The above step 307 is similar to the above step 304 and will not be described in detail here.

[0110] The permission management method provided in the embodiment of the present application can add the node of the permission tree of the first micro-application to the permission tree of the second micro-application through the permission management interface, so that the permission data corresponding to the first node is added to the page data of the second micro-application. Since the permission data is data used to implement the front-end permissions provided by the micro-application, the second micro-application can also implement the front-end permissions corresponding to the first node without manually modifying the code of the second micro-application, thereby improving development efficiency.

[0111] Furthermore, the embodiment of the present application provides a menu management interface, allowing the user to perform simple program identifier addition or deletion operations in the menu management interface to enable the micro-application to be online and offline without modifying the menu code of the main application, thereby reducing development difficulty and improving development efficiency.

[0112] Furthermore, in an embodiment of the present application, after the computer device determines that the front-end development device updates the micro-application, it can promptly synchronize the relevant data to the server of the main application without modifying the code in the server, thereby improving the update efficiency.

[0113] Figure 4 is a schematic diagram of the structure of a rights management device provided in an embodiment of the present application, such as Figure 4 As shown, the device comprises:

[0114] The acquisition module 401 is used to acquire configuration data corresponding to the plurality of micro-applications from the front-end development devices corresponding to the plurality of micro-applications, wherein the configuration data includes permission data, and the permission data is data used to implement the front-end permissions provided by the micro-applications;

[0115] Display module 402, used to display a permission management interface, the permission management interface is used to display a permission tree of multiple micro-applications based on the permission data of the multiple micro-applications;

[0116] The adding module 403 is used to add the permission data corresponding to the first node to the page data of the second micro-application in response to dragging the first node of the permission tree of the first micro-application to the permission tree of the second micro-application in the permission management interface, so that the second micro-application has the front-end permission corresponding to the first node.

[0117] like Figure 5 As shown, in one possible implementation, the page data includes a first view component; an adding module 403 is used to add the permission data corresponding to the first node to the first view component of the second micro-application, so that the second micro-application displays the access options corresponding to the front-end permissions in the display area corresponding to the first view component, and the front-end permissions are the front-end permissions corresponding to the first node.

[0118] In a possible implementation, the first view component is a menu view component.

[0119] In one possible implementation, the permission data includes a route of the front-end permission corresponding to the first node, and an adding module 403 is used to add the route in the permission data corresponding to the first node to the page data of the second micro-application in response to dragging the first node of the permission tree of the first micro-application to the permission tree of the second micro-application in the permission management interface, so that the page of the second micro-application has the function of accessing the front-end permission corresponding to the first node.

[0120] In a possible implementation, the device further includes:

[0121] An updating module 404, used to update the page access address of the second micro-application program;

[0122] The sending module 405 is used to send the updated page access address and the page data after adding the permission data to the server of the main application, so that the server replaces the page access address of the second micro-application with the updated page access address, and replaces the page data of the second micro-application with the page data after adding the permission data. The main application includes multiple micro-applications.

[0123] In a possible implementation, the configuration data also includes a page access address of the micro-application; the display module 402 is further used to display a menu management interface corresponding to the main application, the menu management interface includes a menu of the main application and program identifiers corresponding to multiple micro-applications, and the menu of the main application includes program identifiers of each micro-application launched in the main application;

[0124] Adding module 403 is also used to add the program identifier of the third micro-application and the page access address in the menu view component of the main application in response to adding the program identifier of the third micro-application to the menu; or, in response to deleting the program identifier of the fourth micro-application from the menu, delete the program identifier of the fourth micro-application and the page access address from the menu view component of the main application.

[0125] In a possible implementation, the configuration data further includes a page access address of the micro-application, the page access address includes a timestamp, and different timestamps correspond to different versions of the micro-application; the device further includes:

[0126] The sending module 405 is used to send the configuration data of the micro-application to the server corresponding to the main application for any micro-application if the timestamp in the page access address obtained is different from the timestamp in the page access address obtained last time, so that the server updates the configuration data of the micro-application. The main application includes multiple micro-applications.

[0127] It should be noted that: the rights management device provided in the above embodiment only uses the division of the above functional modules as an example to illustrate when managing rights. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the computer device is divided into different functional modules to complete all or part of the functions described above. In addition, the rights management device provided in the above embodiment and the rights management method embodiment belong to the same concept. The specific implementation process is detailed in the method embodiment and will not be repeated here.

[0128] Figure 6It is a structural diagram of a configuration device provided in an embodiment of the present application. The configuration device 600 may have relatively large differences due to different configurations or performances, and may include one or more processors (Central Processing Units, CPU) 601 and one or more memories 602, wherein the memory 602 stores at least one program code, and the at least one program code is loaded and executed by the processor 601 to implement the methods provided in the above-mentioned various method embodiments. Of course, the configuration device may also have components such as a wired or wireless network interface, a keyboard, and an input and output interface for input and output, and the configuration device may also include other components for implementing device functions, which will not be described in detail here.

[0129] The configuration device 600 is used to execute the steps executed by the configuration device in the above method embodiment.

[0130] An embodiment of the present application also provides a computer-readable storage medium, in which at least one program code is stored. The at least one program code is loaded and executed by a processor to implement the permission management method as described in any of the above implementation methods.

[0131] An embodiment of the present application also provides a computer program product, which includes at least one program code, and the at least one program code is loaded and executed by a processor to implement the permission management method as described in any of the above implementations.

[0132] In some embodiments, the computer program involved in the embodiments of the present application may be deployed and executed on a computer device, or on multiple computer devices located at one location, or on multiple computer devices distributed at multiple locations and interconnected by a communication network. Multiple computer devices distributed at multiple locations and interconnected by a communication network may constitute a blockchain system.

[0133] The above are only optional embodiments of the present application and are not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application should be included in the protection scope of the present application.

Claims

1. A rights management method, characterized in that: The method comprises: Acquire configuration data corresponding to the plurality of micro-applications from front-end development devices corresponding to the plurality of micro-applications, the configuration data including permission data, which is data for implementing the front-end permissions provided by the micro-applications; Displaying a permission management interface, wherein the permission management interface is used to display a permission tree of the plurality of micro-applications based on the permission data of the plurality of micro-applications; In response to dragging the first node of the permission tree of the first micro-application to the permission tree of the second micro-application in the permission management interface, the permission data corresponding to the first node is added to the page data of the second micro-application so that the second micro-application has the front-end permission corresponding to the first node.

2. The method according to claim 1, characterized in that The page data includes a first view component; and adding the permission data corresponding to the first node to the page data of the second micro-application so that the second micro-application has the front-end permission corresponding to the first node, including: The permission data corresponding to the first node is added to the first view component of the second micro-application so that the second micro-application displays the access options corresponding to the front-end permission in the display area corresponding to the first view component, and the front-end permission is the front-end permission corresponding to the first node.

3. The method according to claim 2, characterized in that The first view component is a menu view component.

4. The method according to claim 1, characterized in that The permission data includes a route of the front-end permission corresponding to the first node, and in response to dragging the first node of the permission tree of the first micro-application to the permission tree of the second micro-application in the permission management interface, adding the permission data corresponding to the first node to the page data of the second micro-application so that the second micro-application has the front-end permission corresponding to the first node, including: In response to dragging the first node of the permission tree of the first micro-application to the permission tree of the second micro-application in the permission management interface, the route in the permission data corresponding to the first node is added to the page data of the second micro-application so that the page of the second micro-application has the function of accessing the front-end permission corresponding to the first node.

5. The method according to claim 1 or 2, characterized in that: After adding the permission data corresponding to the first node to the page data of the second micro-application, the method further includes: Updating the page access address of the second micro-application; Sending an updated page access address and the page data after adding the permission data to the server of the main application, so that the server replaces the page access address of the second micro-application with the updated page access address, and replaces the page data of the second micro-application with the page data after adding the permission data, the main application including the multiple micro-applications.

6. The method according to claim 1, characterized in that The configuration data also includes a page access address of the micro-application; and the method further includes: Displaying a menu management interface corresponding to the main application, the menu management interface including a menu of the main application and program identifiers corresponding to the plurality of micro-applications, the menu of the main application including program identifiers of each micro-application launched in the main application; In response to adding the program identifier of the third micro-application to the menu, the program identifier and page access address of the third micro-application are added to the menu view component of the main application; or, in response to deleting the program identifier of the fourth micro-application from the menu, the program identifier and page access address of the fourth micro-application are deleted from the menu view component of the main application.

7. The method according to claim 1, characterized in that The configuration data also includes a page access address of the micro-application, the page access address includes a timestamp, and different timestamps correspond to different versions of the micro-application; the method also includes: For any micro-application, if the timestamp in the obtained page access address is different from the timestamp in the page access address obtained last time, the configuration data of the micro-application is sent to the server corresponding to the main application so that the server updates the configuration data of the micro-application, and the main application includes the multiple micro-applications.

8. A rights management device, characterized in that: The device comprises: An acquisition module, used to acquire configuration data corresponding to the plurality of micro-applications from front-end development devices corresponding to the plurality of micro-applications, wherein the configuration data includes permission data, and the permission data is data for implementing the front-end permissions provided by the micro-applications; A display module, configured to display a permission management interface, wherein the permission management interface is configured to display a permission tree of the plurality of micro-applications based on the permission data of the plurality of micro-applications; An adding module is used to add permission data corresponding to the first node of the permission tree of the first micro-application to the permission tree of the second micro-application in response to dragging the first node of the permission tree of the first micro-application in the permission management interface, so that the second micro-application has the front-end permission corresponding to the first node.

9. A configuration device, characterized in that: The configuration device includes a processor and a memory, wherein at least one program code is stored in the memory, and the at least one program code is loaded and executed by the processor to implement the permission management method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores at least one program code, and the at least one program code is loaded and executed by the processor to implement the rights management method according to any one of claims 1 to 7.

Images