Front-end management method, computer device, readable storage medium and program product
By identifying and configuring preset group permissions for the front end, and utilizing sandbox containers and encrypted transmission technology, the problem of unreasonable front end management platform design is solved, achieving efficient and secure cross-platform front end management.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- CHINA ASSET MANAGEMENT CO LTD
- Filing Date
- 2026-02-02
- Publication Date
- 2026-06-16
AI Technical Summary
Existing technologies have poorly designed front-end management platforms, resulting in complex management processes and a lack of security.
By identifying the preset group of the front-end to be embedded as the target group, configuring group permissions, and embedding the front-end into the target platform according to the baseline information, the sandbox container is used for security isolation and permission monitoring, realizing cross-domain data transmission encryption, and performing fine-grained permission management and multi-terminal platform adaptation.
It improves the configuration efficiency and security of front-end management, ensuring the stable operation of the front-end on different platforms and the security of data transmission.
Smart Images
Figure CN122219989A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of Internet technology, and in particular to a front-end management method, computer device, computer-readable storage medium, and computer program product. Background Technology
[0002] With the rapid development of Internet technology, various platforms for displaying pages have emerged, such as web pages, mobile applications, and mini-programs. In practical applications, pages of the same application may need to be embedded in different platforms. However, due to the unreasonable design of embedding multiple platforms, there are problems such as the complexity of the front-end management platform and security concerns. Summary of the Invention
[0003] This application provides a front-end management method, a computer device, a computer-readable storage medium, and a computer program product to at least solve the problems of complex and insecure front-end management in related technologies.
[0004] This application provides a front-end management method, which includes: obtaining a front-end embedding request; wherein the front-end embedding request includes a target platform; identifying a preset group to which the front-end to be embedded belongs as the target group; wherein the front-end information associated with the preset group is used as the basis information for generating front-ends embedded on different platforms; configuring the group permissions of the target group on the front-end to be embedded, and embedding the front-end to be embedded into the target platform according to the basis information.
[0005] In one embodiment of this application, configuring the group permissions of the target group to the front-end to be embedded includes: obtaining the pre-configured functional permissions and accessible platform resources of the target platform; requesting the corresponding platform resources from the target platform according to the functional permissions, so as to obtain the corresponding platform resources of the target platform as embedding resources; embedding the front-end to be embedded into the target platform using the embedding resources, and granting the group permissions of the target group to the front-end to be embedded.
[0006] In one embodiment of this application, after granting the group permissions of the target group to the front-end to be embedded, the method further includes: monitoring permission usage; wherein, permission usage includes at least one of the permissions used by the front-end to be embedded when it is embedded in the target platform and the permissions used by the front-end to be embedded when it is running on the target platform; evaluating whether the permission usage complies with the target permissions; wherein, the target permissions include functional permissions and / or group permissions; and terminating permission usage that exceeds the target permissions in response to non-compliance with the target permissions.
[0007] In one embodiment of this application, embedding the front-end to be embedded into the target platform includes: obtaining the front-end functions of the front-end to be embedded; verifying whether the target platform supports the front-end functions; and, in response to the target platform not supporting the front-end functions, replacing the front-end functions with the basic functions of the front-end functions on the target platform, or deleting the front-end functions on the target platform.
[0008] In one embodiment of this application, embedding the front-end to be embedded into the target platform according to the reference information includes: obtaining a sandbox container; wherein, the target group forms a group main front-end within the sandbox container; adapting to the display size of the target platform, elastically loading the layout and / or style of the group sub-front-end through the front-end tag of the target group to form the front-end to be embedded, and controlling the communication between the front-end to be embedded and the group main front-end through the front-end message processing interface.
[0009] In one embodiment of this application, identifying the preset group to which the front-end to be embedded belongs as the target group includes: obtaining the front-end to be embedded; querying whether the front-end to be embedded is being embedded into the target platform for the first time; in response to the front-end to be embedded being embedded into the target platform for the first time, verifying whether the front-end to be embedded belongs to the preset group; in response to the front-end to be embedded belonging to the preset group, determining to embed the front-end to be embedded into the target platform, and taking the preset group to which it belongs as the target group.
[0010] In one embodiment of this application, after embedding the front-end to be embedded into the target platform according to the reference information, the method further includes: obtaining a cross-domain data request sent by the target platform; verifying the verification signature carried by the cross-domain data request; and in response to the verification signature passing the verification, executing the cross-domain data request to obtain data from the target data platform.
[0011] This application also provides a computer device, which includes a memory and a processor. The memory is used to store a computer program, and the processor is used to execute the computer program to implement the steps of any of the above-described front-end management methods.
[0012] This application also provides a computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the steps of any of the above-described front-end management methods.
[0013] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of any of the aforementioned front-end management methods.
[0014] This application enables the use of preset groups with the same baseline information applied during page construction as a foundation. During front-end management, the preset group to which the front-end to be embedded belongs is used as the target group. The front-end to be embedded is configured according to the permissions of the target group, and the front-end to be embedded into the target platform can be quickly constructed based on the baseline information. This significantly improves the configuration efficiency and security of the front-end to be embedded. Therefore, it solves the technical problems of complex and insecure front-end management, achieving the technical effect of improving front-end management efficiency and reliability. Attached Figure Description
[0015] To more clearly illustrate the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0016] Figure 1 This is a schematic diagram of the structure of an embodiment of the front-end management system of this application; Figure 2 This is a flowchart illustrating an embodiment of the front-end management method of this application; Figure 3 This is a flowchart illustrating another embodiment of the front-end management method of this application; Figure 4 A flowchart illustrating an embodiment of the service interaction for this application; Figure 5 This is a flowchart illustrating an embodiment of embedding the front end of this application; Figure 6 This is a schematic diagram of the structure of a computer device according to an embodiment of this application. Detailed Implementation
[0017] 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 protection scope of this application.
[0018] It should be noted that, in the description of this application, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. The terms "first," "second," etc., in this application are used to distinguish similar objects and are not used to describe a specific order or sequence.
[0019] To enable those skilled in the art to better understand the present application, the present application will be further described in detail below with reference to the accompanying drawings and specific embodiments.
[0020] The specific application environment architecture or specific hardware architecture on which the execution of the front-end management method depends is described here.
[0021] Please see Figure 1 , Figure 1 This is a flowchart illustrating an embodiment of the front-end management system described in this application.
[0022] In this embodiment, the front-end management system may include a preset platform 10, a preset group 20, and a front-end management device 30.
[0023] The number of preset platforms 10 can be one or more.
[0024] The number of preset groups 20 can also be one or more.
[0025] For a description of the features in the embodiment corresponding to the front-end management device, please refer to the relevant description of the embodiment corresponding to the front-end management method, which will not be repeated here.
[0026] The embodiments of this application provide a front-end management method, and the front-end management method is described in detail in conjunction with the execution flow of the front-end management method.
[0027] Please see Figure 2 , Figure 2 This is a flowchart illustrating an embodiment of the front-end management method of this application.
[0028] S101: Obtain the front-end embedding request; where the front-end embedding request includes the target platform.
[0029] In this embodiment, the front-end management device obtains a front-end embedding request. The target platform information contained in the front-end embedding request is used to clarify the specific platform on which the page needs to be embedded, so that the front-end management device can perform front-end management according to the target platform.
[0030] S102: Identify the preset group to which the front-end to be embedded belongs as the target group; wherein, the front-end information associated with the preset group serves as the reference information for generating front-ends embedded on different platforms.
[0031] In this embodiment, after receiving a front-end embedding request, the front-end management device identifies the preset group to which the front-end to be embedded belongs and uses it as the target group. The preset groups are pre-defined groups based on factors such as front-end functionality and adaptation requirements, or they can be categorized by enterprise, group, etc. In this embodiment, related pages with the same enterprise identifier can be considered to belong to the preset group. The front-end information associated with the preset group can provide unified benchmark information for the generation of embedded pages on different platforms, thereby ensuring the standardization of the generated embedded pages corresponding to the preset group, which is beneficial for improving the consistency and adaptation efficiency of front-end management.
[0032] S103: Configure the group permissions of the target group on the front-end to be embedded, and embed the front-end to be embedded into the target platform according to the baseline information.
[0033] In this embodiment, after determining the target group, the front-end management device configures the group permissions of the target group on the front-end to be embedded. The group permission configuration can ensure that the front-end to be embedded has reasonable operation permissions in the target platform, reducing usage problems caused by improper permissions. At the same time, the front-end management device embeds the front-end to be embedded into the target platform according to the preset group association benchmark information. The benchmark information can provide a clear basis for the front-end management process, ensure the compatibility between the front-end to be embedded and the target platform, and help to achieve stable operation of the page in the target platform, thereby improving the user experience.
[0034] This embodiment can use a preset group with the same baseline information applied when building a page as a basis. When managing the front-end, the preset group to which the front-end to be embedded belongs is used as the target group. The front-end to be embedded is configured according to the permissions of the target group, and the front-end to be embedded into the target platform can be quickly built according to the baseline information. This can significantly improve the configuration efficiency and security of the front-end to be embedded, thereby improving the efficiency and reliability of front-end management.
[0035] Please see Figure 3 , Figure 3 This is a flowchart illustrating another embodiment of the front-end management method of this application.
[0036] S201: Get the front-end embedding request.
[0037] In this embodiment, the front-end embedding request includes the target platform.
[0038] The front-end management device obtains a front-end embedding request carrying target platform information. The target platform information can clearly define the embedding direction of the front-end to be embedded, i.e., the platform to be embedded.
[0039] S202: Identify the preset group to which the front-end to be embedded belongs as the target group.
[0040] In this embodiment, the front-end information associated with the preset group is used as the base information for generating front-ends embedded in different platforms.
[0041] Specifically, it can obtain the front-end to be embedded.
[0042] Checking whether the front-end to be embedded is being embedded into the target platform for the first time can reduce duplicate group checks in non-first-time embedding scenarios, which helps improve processing efficiency.
[0043] In response to the frontend being embedded for the first time on the target platform, the system verifies whether the frontend belongs to a preset group. If the frontend belongs to a preset group, the system determines that the frontend will be embedded on the target platform, and its preset group will be used as the target group. This verification process ensures that the frontend meets the basic requirements for cross-platform embedding. The frontend management device determines that the frontend will be embedded on the target platform and uses its preset group as the target group, providing a group basis for subsequent permission configuration and page generation.
[0044] S203: Obtain pre-configured functional permissions and accessible platform resources of the target platform.
[0045] In this embodiment, the front-end management device can obtain the pre-configured functional permissions and accessible platform resources of the target platform. The functional permissions can define the scope of operations that the front-end to be embedded can perform on the target platform, and the accessible platform resources are used for front-end management and operation. This can clarify the permission boundaries and resource supply capabilities of the target platform, which is beneficial for providing accurate reference for subsequent resource requests and permission adaptation, and can also reduce the situation of embedding failure due to unclear permissions or resources.
[0046] S204: Request the corresponding platform resources from the target platform based on the function permissions, so as to obtain the corresponding platform resources of the target platform as embedding resources.
[0047] In this embodiment, the front-end management device can request corresponding platform resources from the target platform based on the acquired functional permissions of the target platform. There is a preset correspondence between functional permissions and platform resources. Requesting resources based on this correspondence ensures that the acquired resources match the functional requirements of the front-end to be embedded. Acquiring the corresponding platform resources of the target platform as embedding resources helps maintain the embedding and stable operation of the front-end on the target platform, and also helps improve the success rate and smoothness of front-end management.
[0048] S205: Use embedding resources to embed the front-end to be embedded into the target platform.
[0049] In this embodiment, the front-end functionality to be embedded can be obtained. It is then verified whether the target platform supports the front-end functionality. If the target platform does not support the front-end functionality, the front-end functionality is replaced with its basic functionality on the target platform, or the front-end functionality is removed from the target platform. This verification action can pre-check for compatibility risks. If the target platform does not support the front-end functionality, the front-end management device replaces the advanced original front-end functionality with its basic functionality on the target platform, or removes the front-end functionality from the target platform. This reduces the risk of page malfunctions caused by functional incompatibility, ensuring that the front-end to be embedded can be used normally on the target platform, and improving the flexibility of cross-platform adaptation.
[0050] S206: Grant the target group's group permissions to the front-end to be embedded.
[0051] In this embodiment, group permissions for the target group can be assigned to the front-end to be embedded, thereby configuring the group permissions for the target group on the front-end. Group permissions can be considered a relatively uniform standard of operation permissions based on preset groups. Assigning group permissions to the front-end to be embedded can improve the efficiency of permission assignment, thus improving front-end management efficiency. Furthermore, it can ensure that the front-end to be embedded has an operation scope that matches its group attributes, reducing the functional limitations caused by missing permissions or security risks caused by permission overreach, which is beneficial to ensuring the security and reliability of page operation.
[0052] S207: Embed the front-end to be embedded into the target platform according to the baseline information.
[0053] In this embodiment, a sandbox container can be obtained. Within the sandbox container, the target group forms a main front-end. Adapting to the display size of the target platform, the layout and / or style of the sub-front-ends of the group are flexibly loaded via the target group's front-end tag to form the front-end to be embedded. Communication between the front-end to be embedded and the main front-end of the group is controlled through a front-end message processing interface.
[0054] In other words, the front-end management device can acquire a sandbox container, which provides an independent operating environment for the front-end to be embedded, reducing conflicts between the front-end and the original functions of the target platform and ensuring the stability of the target platform. Within the sandbox container, the target group forms a main front-end, which provides a unified operating platform and interaction basis for the sub-front-ends within the same group. The front-end management device adapts to the display size of the target platform and flexibly loads the layout and / or style of the sub-front-ends of the group through the front-end tags of the target group to form the front-end to be embedded. This flexible loading method can adapt to the display specifications of different target platforms, ensuring that the display effect of the front-end to be embedded meets the user's visual needs. Simultaneously, the front-end management device controls the communication between the front-end to be embedded and the main front-end of the group through a front-end message processing interface. This communication method enables data interaction and command transmission between the two, ensuring the normal functioning of the front-end to be embedded.
[0055] S208: Monitor and manage permission usage in the front-end to be embedded.
[0056] In this embodiment, permission usage can be monitored. Permission usage includes at least one of the permissions used when the front-end to be embedded is embedded into the target platform, and the permissions used when the front-end to be embedded is running on the target platform.
[0057] Assess whether the usage of permissions conforms to the target permissions. The target permissions include functional permissions and / or group permissions.
[0058] Responding to situations where permissions are not met, terminating the use of permissions beyond the target permissions can further reduce the security risks posed by unauthorized operations to the target platform or the front-end to be embedded, and ensure the reliable operation of front-end management.
[0059] Optionally, it is also possible to obtain cross-domain data requests sent by the target platform.
[0060] Verify the verification signature carried in cross-domain data requests.
[0061] In response to the successful verification of the signature, a cross-domain data request is executed to obtain data from the target data platform.
[0062] Alternatively, data with a certain level of privacy can be encrypted, which helps to ensure the security of data transmission.
[0063] Alternatively, it can obtain cross-domain data requests sent by the target platform; verify the verification signature carried in the cross-domain data request; in response to the verification signature passing the verification, decrypt the cross-domain data request, execute the decrypted cross-domain data request to obtain the encrypted data fed back by the target data platform, decrypt the encrypted data and re-encrypt it before feeding it back to the target platform.
[0064] In layman's terms, this embodiment can construct a secure container for the front-end module, establish a secure data interaction channel, achieve fine-grained permission management, and handle multi-platform adaptation and compatibility.
[0065] Specifically, building a sandbox environment can create an isolated and secure front-end module container. This container uses a sandbox mechanism to restrict the runtime environment of front-end modules, achieving security isolation, environment isolation, and risk control. The sandbox forms an independent DOM (Document Object Model) space and JavaScript execution environment, reducing the likelihood of malicious modifications to the DOM structure and global variables of the target platform by front-end modules. For example, a strongly isolated iframe sandbox can be used, where the iframe is a browser-native isolated environment whose internal window and document are completely independent of the parent page for reliable isolation. Child front-ends can be loaded via iframes, possessing independent DOM trees, JavaScript contexts, and BOM (Browser Object Model) objects; the parent page and child front-ends communicate via postMessage (a message handling mechanism) to reliably control data exchange.
[0066] The security detection mechanism can integrate a real-time code behavior analysis engine to monitor abnormal behaviors such as unusual API (Application Programming Interface) calls, abnormal data transmission, and malicious code patterns. During abnormal API call detection, all API calls can be recorded and verified through API call interceptors. During abnormal data transmission detection, anomalies such as packet size, frequency, and target address can be monitored. For malicious code pattern recognition, pattern matching can be performed based on a predefined malicious code signature library.
[0067] Containers can also integrate resource access control to implement whitelist-based resource access control, allowing access only to pre-authorized system resources. They can also establish a resource access logging mechanism to record all resource access behaviors for security verification.
[0068] Establishing a secure data exchange channel enables encrypted data transmission, data verification mechanisms, and cross-domain request handling. Specifically, data exchange between the front-end module and multiple target platforms can be encrypted using asymmetric encryption algorithms. The front-end module and the target platform each hold a public and private key pair. The sender uses the receiver's public key to encrypt the data, and the receiver uses its own private key to decrypt it, ensuring that the data is not stolen or tampered with during transmission. During data exchange, both parties need to verify the integrity and authenticity of the data. For cross-domain data requests, a token-based verification method, i.e., signature verification, is used. When sending a cross-domain request, the front-end module needs to include a token authenticated by the target platform in the request header. The target platform verifies the token, and only after successful verification is the request allowed to continue processing.
[0069] Fine-grained permission management allows for permission definition, request and approval, and dynamic control. Specifically, a pre-defined permission list can be defined for the multi-platform resources and functions accessible to the front-end module. Permission levels are categorized into basic, extended, and advanced permissions. Basic permissions include basic page display and simple data retrieval; extended permissions include partial data modification and specific function calls; advanced permissions include access to core resources and control of critical functions. When embedded in the target platform, the front-end module can request corresponding permissions based on its functional requirements. The target platform administrator reviews the permission requests, determining whether to grant permissions and the level of permission granted based on factors such as the front-end module's trustworthiness and purpose. The target platform can also monitor the front-end module's permission usage in real time, immediately revoking permissions and issuing a warning if the module exceeds its authorized scope. Furthermore, the platform supports dynamically adjusting permissions based on the front-end module's operational status and security level.
[0070] Multi-platform adaptation and compatibility handling can abstract the target platform interface layer, style and layout adaptation, and function degradation handling.
[0071] Specifically, an abstract target platform interface layer can be constructed to encapsulate and unify the underlying APIs of different multi-platform target platforms. The front-end module interacts with the target platform by calling methods of the abstract interface layer, without needing to concern itself with the API differences of specific target platforms. The abstract interface layer automatically maps to the corresponding native API of the target platform based on the currently running target platform type. Employing flexible layout and adaptive design, the front-end module can automatically adjust page styles and layouts according to the screen size and resolution of different target platforms. Furthermore, to address style compatibility issues across different target platform browsers or applications, compatibility stylesheets can be predefined to ensure consistent display across all target platforms. For advanced features not supported on some target platforms, a feature degradation strategy can be set. When it is detected that a target platform does not support a feature, it automatically switches to an alternative basic feature, ensuring the basic usability of the front-end module.
[0072] The following section elaborates on the detailed working principle of the front-end management method of this application, using specific applications as examples. It should be noted that the following description uses the front-end management system as the executing entity of the front-end management method. The front-end management system can be considered as a secure container capable of managing and scheduling processes such as front-end embedding and execution.
[0073] A front-end management system can include a management platform, gateway services, and business services. The management platform can connect to the target platform to enable interaction, while the gateway service and business services implement specific front-end management, which will be described in detail below.
[0074] Please see Figure 4 , Figure 4 This is a flowchart illustrating an embodiment of the service interaction for this application.
[0075] In one embodiment, the management platform sends a screenshot to the gateway service to send a data request. The data request includes a front-end signature and encrypted content to help ensure the security and integrity of the request during transmission and reduce the risk of illegal tampering or theft.
[0076] Upon receiving a request, the gateway service can perform signature verification and decryption operations. It verifies the signature validity using a preset key and decrypts the encrypted content to obtain the original request information, thereby confirming the request's reliability. The gateway service can also record access logs and perform traffic monitoring. Access logs can preserve request traceability for later tracking, while traffic monitoring helps manage the load on the front-end management system, ensuring stable service operation. The gateway service can also verify access permissions, checking whether the entity corresponding to the request has the necessary authorization to access the target service, reducing the risk of unauthorized access.
[0077] Upon successful authorization verification, the gateway service can forward the data request to the business service. The business service processes the request, generates return data, and passes it to the gateway service. Upon receiving the return data, the gateway service adds a gateway signature and encrypts it before transmitting the processed data to the management platform. This ensures the security of the return data during transmission, thus completing the data interaction process.
[0078] Please see Figure 5 , Figure 5 This is a flowchart illustrating an embodiment of front-end embedding in this application.
[0079] In one embodiment, a secure container embedding scenario is taken as an example, embedding a business page into a multi-platform system, including mobile apps, mini-programs, and PC management systems. A preset group can initiate a transition page request (i.e., a front-end embedding request) to the management platform. This request includes an encrypted platform identifier and a signature. The platform identifier identifies the target platform to be embedded into, and the signature can be generated based on an agreed-upon key between the preset group and the management platform. Encryption prevents unauthorized modification of the request content, thus ensuring request security. Upon receiving the request, the management platform encapsulates the target group information, which may include the cross-platform adaptation specifications and basic interaction rules for the target group's page. A front-end embedding request carrying the group's permission configuration is generated and then transmitted to the corresponding business service via a gateway service. The gateway service filters and routes the request, ensuring that it is only transmitted to the matching business service, preventing invalid requests from interfering with system operation.
[0080] The business service can perform multi-dimensional security checks on frontend embedding requests, verifying the target group identifier, checking if it is within the business service's preset group list, completing signature verification, confirming the validity of the signature through an agreed key, and then decrypting the data to obtain the original embedding requirements. After successful verification, the business service obtains the identifier of the frontend to be embedded, processes the corresponding page data, and retrieves the target platform's allowed access permission list to clarify the functional scope of the page to be embedded. If so, the business service can return the data of the frontend to be embedded and the access permission list to the management platform via the gateway service. Upon receiving the information, the management platform processes the secure container, i.e., the sandbox container. The sandbox container provides an independent operating environment for the page to be embedded, isolating the page from the target platform's original code and reducing code conflicts and data interference between pages. Subsequently, the management platform encapsulates the frontend page adapted to the target platform and finally responds to the preset group with the configured page to be embedded, achieving secure and stable embedding of the business page on the target platform, while the secure container ensures data security and environmental isolation during page operation.
[0081] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms, or of course by hardware.
[0082] Embodiments of this application also provide a computer device.
[0083] Please see Figure 6 , Figure 6 This is a schematic diagram of the structure of a computer device according to an embodiment of this application.
[0084] In one embodiment, the computer device includes a memory 41 and a processor 42.
[0085] The memory 41 stores a computer program, and the processor 42 is configured to run the computer program to perform the steps in any of the above-described front-end management method embodiments.
[0086] Embodiments of this application also provide a computer-readable storage medium storing a computer program, wherein the computer program is configured to execute the steps in any of the above-described front-end management method embodiments at runtime.
[0087] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.
[0088] Embodiments of this application also provide a computer program product, which includes a computer program that, when executed by a processor, implements the steps in any of the above-described front-end management method embodiments.
[0089] Embodiments of this application also provide another computer program product, including a non-volatile computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps in any of the above-described front-end management method embodiments.
[0090] Those skilled in the art will further 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 implementation should not be considered beyond the scope of this application.
[0091] The foregoing has provided a detailed description of a front-end management method, computer device, computer-readable storage medium, and computer program product provided in this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the embodiments above are only intended to help understand the method and core ideas of this application. It should be noted that those skilled in the art can make various improvements and modifications to this application without departing from its principles, and these improvements and modifications also fall within the protection scope of this application.
Claims
1. A front-end management method, characterized in that, The front-end management method includes: Obtain the front-end embedding request; wherein, the front-end embedding request includes the target platform; Identify the preset group to which the front-end to be embedded belongs as the target group; wherein, the front-end information associated with the preset group serves as the reference information for generating front-ends embedded on different platforms; Configure the group permissions of the target group on the front end to be embedded, and embed the front end to be embedded into the target platform according to the baseline information.
2. The front-end management method according to claim 1, characterized in that, The step of configuring the group permissions of the target group in the front end to be embedded includes: Obtain the pre-configured functional permissions and accessible platform resources of the target platform; Based on the aforementioned functional permissions, request the corresponding platform resources from the target platform to obtain the corresponding platform resources of the target platform as embedding resources; The embedding resources are used to embed the front-end to be embedded into the target platform, and the group permissions of the target group are granted to the front-end to be embedded.
3. The front-end management method according to claim 2, characterized in that, After granting the target group's group permissions to the front-end to be embedded, the process also includes: Monitor permission usage; wherein, the permission usage includes at least one of the permissions used when the front-end to be embedded is embedded into the target platform, and the permissions used when the front-end to be embedded is running on the target platform; Evaluate whether the usage of the permissions conforms to the target permissions; wherein, the target permissions include the functional permissions and / or the group permissions; In response to non-compliance with the target permissions, terminate the use of permissions that exceed the target permissions.
4. The front-end management method according to claim 1, characterized in that, The step of embedding the front-end to be embedded into the target platform includes: Obtain the front-end functionality to be embedded in the front-end; Verify whether the target platform supports the front-end function; In response to the target platform not supporting the front-end function, the front-end function is replaced on the target platform using the basic functions of the front-end function, or the front-end function is removed from the target platform.
5. The front-end management method according to claim 1 or 4, characterized in that, The step of embedding the front-end to be embedded into the target platform according to the reference information includes: Obtain a sandbox container; wherein the target group forms a group main front end within the sandbox container; Adapting to the display size of the target platform, the layout and / or style of the sub-frontend of the group are flexibly loaded through the front-end tag of the target group to form the front-end to be embedded, and the communication between the front-end to be embedded and the main front-end of the group is controlled through the front-end message processing interface.
6. The front-end management method according to claim 1, characterized in that, The step of identifying the preset group to which the front-end to be embedded belongs as the target group includes: Obtain the front-end to be embedded; Check whether the front-end to be embedded is being embedded into the target platform for the first time; In response to the fact that the front-end to be embedded is being embedded into the target platform for the first time, it is verified whether the front-end to be embedded belongs to the preset group; in response to the fact that the front-end to be embedded belongs to the preset group, it is determined to embed the front-end to be embedded into the target platform, and the preset group to which it belongs is taken as the target group.
7. The front-end management method according to claim 1, characterized in that, After embedding the front-end to be embedded into the target platform according to the benchmark information, the process further includes: Obtain cross-domain data requests sent via the target platform; Verify the verification signature carried in the cross-domain data request; In response to the verification signature passing the verification, the cross-domain data request is decrypted, the decrypted cross-domain data request is executed to obtain the encrypted data fed back by the target data platform, the encrypted data is decrypted and re-encrypted and fed back to the target platform.
8. A computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the front-end management method according to any one of claims 1 to 7.
9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the front-end management method according to any one of claims 1 to 7.
10. A computer program product, comprising a computer program, characterized in that, When executed by a processor, the computer program implements the steps of the front-end management method according to any one of claims 1 to 7.