Page access method and device, computer device and storage medium

Abstract

The application relates to a page access method and device, computer equipment and a storage medium. The method comprises the following steps: receiving an access request of a target application for a document page under a target document category in a source application; in response to the access request, obtaining a document permission list corresponding to the source application; from the document permission list, finding a set of operation permissions of the target application for a document under the target document category; rendering an operation entry visual identifier corresponding to an operation permission in the set of operation permissions in the document page under the target document category to obtain rendering data; returning the rendering data to the target application; and the rendering data is used to instruct the target application to display the document page containing the operation entry visual identifier. The method provides a brand-new page access method.

Description

Technical Field

[0001] This application relates to the field of information processing technology, and in particular to a page access method, apparatus, computer device, and storage medium. Background Technology

[0002] With the development of information processing technology, users can access document pages in the source application across applications via external applications, leading to the emergence of page access technology. For example, when a user accesses the document details page corresponding to a document in the source application through an external application, page access technology can control the cross-application access permissions of the external application to prevent the external application from tampering with the document details information on the document details page.

[0003] Traditional page access methods involve user authorization management. When external applications access a document page in the source application, a unified page is displayed, and only authorized users can operate on certain buttons; unauthorized users are unable to do so. This traditional method of user-centric authorization for page access control is limited and cannot achieve effective isolation of operation permissions for documents across different applications. Therefore, there is an urgent need to propose a different page access method. Summary of the Invention

[0004] Therefore, it is necessary to provide a page access method, apparatus, computer device, and storage medium to address the aforementioned technical problems.

[0005] Firstly, this application provides a method for accessing a webpage. The method includes:

[0006] Receive access requests from the target application for document pages under the target document category in the source application;

[0007] In response to the access request, obtain the document permission list corresponding to the source application;

[0008] From the document permission list, find the set of operation permissions that the target application has for documents under the target document category;

[0009] In the document page under the target document category, render the visual identifier of the operation entry corresponding to the operation permission in the set of operation permissions to obtain the rendered data;

[0010] The rendered data is returned to the target application; the rendered data is used to instruct the display of the document page containing the visual identifier of the operation entry point in the target application.

[0011] In one embodiment, the method further includes:

[0012] From the document permission list, find the identifiers of the document categories for which the target application has operation permissions, and obtain the set of permission document categories;

[0013] If the identifier of the target document category matches the identifier in the set of authorized document categories, then

[0014] Perform the step of searching the document permission list for the set of operation permissions that the target application has for documents under the target document category.

[0015] In one embodiment, the set of operation permissions is a second set of operation permissions; the access request carries a target application identifier and an identifier of the target document category; searching the document permission list for the set of operation permissions that the target application has for documents under the target document category includes:

[0016] From the document permission list, find the first set of operation permissions corresponding to the identifier of the target document category; the first set of operation permissions refers to the set of operation permissions that all external applications have for documents under the target document category;

[0017] From the first set of operation permissions, find the operation permissions corresponding to the target application identifier to obtain the second set of operation permissions.

[0018] In one embodiment, the step of rendering a visual identifier for the operation entry corresponding to the operation permission in the set of operation permissions on the document page under the target document category, and obtaining the rendered data includes:

[0019] From the second set of operation permissions, find the set of entry permissions corresponding to each operation entry visual identifier;

[0020] In the document page under the target document category, according to the entry permission set, render the visual identifiers of each operation entry point to obtain rendered data.

[0021] In one embodiment, the set of operation permissions includes identifiers of operations for which the target application has operation permissions for documents under the target document category; the method further includes:

[0022] The target application receives an operation request for a target document in the source application based on the operation entry visualization identifier; the operation request carries the identifier of the target operation.

[0023] In response to the operation request, the identifier of the target operation is matched with the identifier in the set of operation permissions;

[0024] Return permission matching results to the target application to instruct the target application to process the operation request accordingly based on the permission matching results.

[0025] In one embodiment, returning a permission matching result to the target application to instruct the target application to process the operation request accordingly based on the permission matching result includes:

[0026] If the permission matching result is successful, the target application is instructed to call the target operation plugin corresponding to the identifier of the target operation to execute the operation corresponding to the operation request;

[0027] If the permission matching result is unsuccessful, the target application will be prompted that it does not have the permission to perform the operation corresponding to the operation request.

[0028] In one embodiment, the source application is a native application that provides document pages under the target document category; the target application is an external application other than the source application; the document permission list records the operation permissions that different target applications have for documents under each document category; the operation entry visualization includes operation buttons.

[0029] Secondly, this application provides a method for accessing a webpage. The method includes:

[0030] In response to an access operation targeting a document page under the target document category in the source application, an access request is initiated based on the target application.

[0031] Receive rendering data returned in response to the access request; the rendering data includes data for displaying a visual identifier for the operation entry point; the visual identifier for the operation entry point corresponds to the operation permissions in the set of operation permissions; the set of operation permissions includes the operation permissions that the target application has for documents under the target document category, which are in the document permission list corresponding to the source application;

[0032] Based on the rendered data, the document page containing the visual identifier of the operation entry is displayed in the target application.

[0033] Thirdly, this application also provides a page access device. The device includes:

[0034] The receiving module is used to receive access requests from the target application for document pages under the target document category in the source application;

[0035] The lookup module is used to respond to the access request, obtain the document permission list corresponding to the source application, and search the document permission list for the set of operation permissions that the target application has for documents under the target document category.

[0036] The configuration module is used to render a visual identifier for the operation entry corresponding to the operation permission in the set of operation permissions on the document page under the target document category, thereby obtaining rendering data; and to return the rendering data to the target application; the rendering data is used to instruct the display of the document page containing the visual identifier for the operation entry in the target application.

[0037] Fourthly, this application also provides a page access device. The device includes:

[0038] The acquisition module is used to respond to an access operation on a document page under a target document category in the source application by initiating an access request based on the target application; receiving rendering data returned in response to the access request; the rendering data includes data for displaying a visual identifier for the operation entry; the visual identifier for the operation entry corresponds to the operation permissions in the set of operation permissions; the set of operation permissions includes the operation permissions that the target application has for documents under the target document category, which are in the document permission list corresponding to the source application;

[0039] The display module is used to display the document page containing the visual identifier of the operation entry point in the target application according to the rendered data.

[0040] Fifthly, this application also provides a computer device. The computer device includes a memory and a processor, the memory storing a computer program, which, when executed by the processor, causes the processor to perform the steps of the methods described in the embodiments of this application.

[0041] Sixthly, this application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program thereon, which, when executed by a processor, causes the processor to perform the steps of the methods described in the embodiments of this application.

[0042] In a seventh aspect, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, causes the processor to perform the steps of the methods described in the embodiments of this application.

[0043] The aforementioned page access method, apparatus, computer equipment, and storage medium receive access requests from target applications for document pages under target document categories in source applications; respond to the access requests by obtaining a document permission list corresponding to the source application; from the document permission list, search for the set of operation permissions that the target application possesses for documents under the target document category, enabling targeted control of operation permissions for each target application and achieving permission isolation between different target applications. In the document page under the target document category, render the visual identifiers of the operation entry points corresponding to the operation permissions in the set of operation permissions, obtaining rendered data; return the rendered data to the target application; the rendered data is used to instruct the target application to display document pages containing the visual identifiers of operation entry points. The server can, based on the document permission list and the set of operation permissions corresponding to the target application, visually render the operation entry points that the target application has operation permissions for, while restricting the display of operation entry points that the target application does not have operation permissions for, thereby enabling targeted page access permission control for different target applications. Unlike traditional solutions that uniformly display pages and manage user authorization, this achieves isolation of operation permissions for documents under different target applications. Attached Figure Description

[0044] Figure 1 This is an application environment diagram of a page access method in one embodiment;

[0045] Figure 2 This is a flowchart illustrating a page access method in one embodiment;

[0046] Figure 3a This is a schematic diagram of a document page containing a visual identifier for an operation entry point in one embodiment;

[0047] Figure 3b This is a schematic diagram of a document page containing a visual identifier for an operation entry point, as shown in another embodiment.

[0048] Figure 4a This is a schematic diagram of a document page where the target application performs an operation in one embodiment.

[0049] Figure 4b This is a schematic diagram of a document page where the target application performs an operation in another embodiment;

[0050] Figure 5 This is a sequence diagram of page access in one embodiment;

[0051] Figure 6 This is a structural block diagram of a page access device in one embodiment;

[0052] Figure 7 This is a structural block diagram of a page access device in one embodiment;

[0053] Figure 8This is an internal structural diagram of a computer device in one embodiment;

[0054] Figure 9 This is a diagram of the internal structure of a computer device in another embodiment. Detailed Implementation

[0055] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0056] The page access method provided in this application embodiment can be applied to, for example, Figure 1 In the application environment shown, terminal 102 communicates with server 104 via a network. A data storage system can store the data that server 104 needs to process. The data storage system can be integrated onto server 104 or placed on a cloud or other network server. Server 104 can receive access requests from the target application for document pages under the target document category in the source application via terminal 102; server 104 can respond to the access request by obtaining the document permission list corresponding to the source application; server 104 can find the set of operation permissions that the target application has for documents under the target document category from the document permission list; server 104 can render the visual identifier of the operation entry corresponding to the operation permission in the set of operation permissions on the document page under the target document category, obtaining rendered data; server 104 can return the rendered data to the target application via terminal 102. Terminal 102 can be, but is not limited to, various personal computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices can be smart speakers, smart TVs, smart air conditioners, smart in-vehicle devices, etc. Portable wearable devices can be smartwatches, smart bracelets, head-mounted devices, etc. Server 104 can be implemented using a standalone server or a server cluster consisting of multiple servers.

[0057] In one embodiment, such as Figure 2 As shown, a page access method is provided, which can be applied to... Figure 1 Taking the server in the example, the following steps are included:

[0058] S202, Receive the access request from the target application for the document page under the target document category in the source application; In response to the access request, obtain the document permission list corresponding to the source application.

[0059] In this context, a document refers to a written document obtained or prepared during business processing, detailing the actual circumstances of a transaction or event. It can be understood that a document serves as a basis for processing the delivery of goods and payment for goods. An access request is a request to access the document page under the target document category in the source application. A document permission list is a list of permissions used to control the target application's access to document pages. It can be understood that the document permission list includes permission information for each target application to access the document page under the target document category in the source application.

[0060] Specifically, a target application can send an access request to the server for a document page under a target document category in the source application, and the server can receive the access request. In response to the access request, the server can look up the document permission list corresponding to the source application based on the identifier of the source application carried in the access request.

[0061] In one embodiment, the server can retrieve a list of document permissions from a metadata database. The metadata database may include at least one of metadata, such as data describing the information displayed on the document page and data describing access information to the document page. Metadata refers to data that describes data, descriptive information about data and information resources. It can be understood that the document page access information may include permission information for each target application to access the document page.

[0062] In one embodiment, a user can log in to the target application via a terminal to access document pages. In response to the user's access to document pages, the target application can initiate an access request for document pages under the target document category in the source application.

[0063] In one embodiment, a document page may include at least one of a document details page, a document editing page, and a document list page.

[0064] In one embodiment, document categories may include at least one of the following: accounts payable, payment invoices, accounts receivable, and receipts.

[0065] S204. From the document permission list, find the set of operation permissions that the target application has for documents under the target document category.

[0066] Operation permissions refer to the permissions that a target application has to perform operations on documents under a target document category.

[0067] Specifically, the server can search the document permission list to find the set of operation permissions that the target application has for documents under the target document category, based on the identifier of the target document category carried in the access request.

[0068] In one embodiment, operation permissions may include at least one of the following: add, delete, submit, review, adjust, link query, accounts receivable settlement, push-down invoicing, generate vouchers, refresh, and exit.

[0069] S206, in the document page under the target document category, visualize the operation entry corresponding to the operation permission in the set of rendering and operation permissions, obtain the rendering data; return the rendering data to the target application.

[0070] The rendered data is used to instruct the target application to display document pages containing visual identifiers for operation entry points. These visual identifiers are elements that represent operation entry points and are used to visually display them. In essence, triggering an operation entry visual identifier can instruct the target application to perform the corresponding operation. For example, the "Add Document" button is the visual identifier for the "Add Document" operation; clicking it will trigger the target application to perform the operation to add a new document.

[0071] Specifically, the server can render the visual identifiers of the operation entry points corresponding to the operation permissions in the set of operation permissions on the document page under the target document category, thus obtaining rendered data. The server can return the rendered data to the target application, and the target application can display the document page containing the visual identifiers of the operation entry points after receiving the rendered data. It can be understood that the target application only displays the visual identifiers of the operation entry points corresponding to the operation permissions that the target application has.

[0072] In one embodiment, the visual identifier for the operation entry point may include at least one form such as a button, hyperlink, and drop-down menu. It is understood that this application embodiment does not limit the form of the visual identifier for the operation entry point, as long as it can represent the operation entry point for triggering the corresponding operation.

[0073] In one embodiment, Figure 3a This is a schematic diagram of a document page containing visual identifiers for operation entry points. Application 1 can respond to a user's access to the financial accounts receivable list page by sending an access request for the financial accounts receivable list page in the source application to the server. The server can find the set of operation permissions corresponding to Application 1, render the visual identifiers for the operation entry points corresponding to the operation permissions in the set, and obtain the rendered data. The server can send the rendered data to Application 1, and Application 1, based on the rendered data, displays the financial accounts receivable list page including operation buttons such as Add, Delete, Submit, Link Query, More, Refresh, and Exit. It can be understood that the second set of operation permissions corresponding to Application 1 includes operation permissions such as Add, Delete, Submit, Link Query, More, Refresh, and Exit.

[0074] In another embodiment, Figure 3b This is a schematic diagram of a document page containing visual identifiers for operation entry points. Application 2 can respond to a user's access to the financial accounts receivable list page by sending an access request for the financial accounts receivable list page in the source application to the server. The server can find the set of operation permissions corresponding to Application 2, render the visual identifiers for the operation entry points corresponding to the operation permissions in the set of operation permissions, and obtain the rendered data. The server can send the rendered data to Application 2, and Application 2, based on the rendered data, displays the financial accounts receivable list page including operation buttons such as Add, Delete, Submit, Review, Adjust, Accounts Receivable Settlement, Push-down Invoicing, Linked Query, Generate Voucher, More, Refresh, and Exit. It can be understood that the set of operation permissions corresponding to Application 2 includes the operation permissions of Add, Delete, Submit, Review, Adjust, Accounts Receivable Settlement, Push-down Invoicing, Linked Query, Generate Voucher, More, Refresh, and Exit.

[0075] Understandable. Figure 3a and Figure 3b The images show document pages with visual icons for operation entry points displayed by different target applications. Application 1 and Application 2 have different sets of operation permissions for documents under the target document category. Application 1's set of operation permissions does not include approval, adjustment, accounts receivable settlement, invoicing, and voucher generation permissions; therefore, the document pages in Application 1 do not display the corresponding operation buttons. Application 2, on the other hand, includes these operation permissions, and thus the document pages displayed in Application 2 also include the corresponding operation buttons. Clearly, the pages displayed by Application 1 and Application 2 are rendered by the server specifically according to the respective sets of operation permissions for Application 1 and Application 2.

[0076] The above page access method receives an access request from a target application for a document page under a target document category in the source application; responds to the access request by obtaining the document permission list corresponding to the source application; from the document permission list, it searches for the set of operation permissions that the target application has for documents under the target document category, enabling targeted control of the operation permissions of each target application and achieving permission isolation between different target applications. On the document page under the target document category, it renders the visual identifiers of the operation entry points corresponding to the operation permissions in the set of operation permissions, obtaining rendered data; it returns the rendered data to the target application; the rendered data is used to instruct the target application to display document pages containing the visual identifiers of the operation entry points. Based on the set of operation permissions corresponding to the target application in the document permission list, it can visually render the operation entry points that the target application has operation permissions for, restricting the display of operation entry points that the target application does not have operation permissions for, making these operation entry points invisible to the user. This effectively avoids the problem of users being misled by displayed operation entry points that cannot be operated due to lack of authorization, thus improving the user experience. Furthermore, by implementing permission isolation between different target applications, it enables targeted page access control for different target applications, unlike the traditional approach of uniformly displaying pages and managing user authorization.

[0077] Furthermore, implementing page access control through metadata is simpler, reduces development costs, and does not require excessive intervention in the normal business logic of the documents, resulting in low coupling with business code.

[0078] In one embodiment, the method further includes: searching for the identifier of the document category to which the target application has operation permissions from the document permission list to obtain a set of permission document categories; if the identifier of the target document category matches the identifier in the set of permission document categories, then performing the step of searching for the set of operation permissions that the target application has for documents under the target document category from the document permission list.

[0079] The set of permission document categories refers to the set of document categories for which the target application has the authority to operate.

[0080] Specifically, the server can look up the identifiers of document categories that the target application has the right to operate on from the document permission list, obtain a set of permission document categories, and match the identifier of the target document category carried in the access request with the identifiers in the set of permission document categories. If the identifier of the target document category matches the identifiers in the set of permission document categories, then the server will execute the step of looking up the set of operation permissions that the target application has for documents under the target document category from the document permission list.

[0081] In one embodiment, the server can use the target application's identifier carried in the access request to search the document permission list for the identifiers of document categories that the target application has operation permissions for, thus obtaining a set of permissioned document categories. It can be understood that the set of permissioned document categories in the document permission list corresponds one-to-one with the identifiers of the target application.

[0082] In this embodiment, the server can search for the identifier of the document category that the target application has operation permissions from the document permission list to obtain the permission document category set. If the identifier of the target document category matches the identifier in the permission document category set, the server will execute the step of searching for the set of operation permissions that the target application has for documents under the target document category from the document permission list. This can obtain the permission document category set of each target application, realize permission isolation between target applications, and ensure the stability of page access control.

[0083] In one embodiment, the set of operation permissions is a second set of operation permissions; the access request carries the target application identifier and the identifier of the target document category; searching the document permission list for the set of operation permissions that the target application has for documents under the target document category includes: searching the document permission list for the first set of operation permissions corresponding to the identifier of the target document category; the first set of operation permissions refers to the set of operation permissions that all external applications have for documents under the target document category; searching the first set of operation permissions for the operation permissions corresponding to the target application identifier to obtain the second set of operation permissions.

[0084] Specifically, the server can retrieve the first set of operation permissions corresponding to the target document category identifier from the document permission list, and retrieve the operation permissions corresponding to the target application identifier from the first set of operation permissions, thus obtaining the second set of operation permissions. It can be understood that there is a one-to-one correspondence between the target document category identifier and the first set of operation permissions, and a one-to-one correspondence between the target application identifier and the second set of operation permissions.

[0085] In one embodiment, the server can render the visual identifier of the operation entry corresponding to the operation permission in the second set of operation permissions on the document page under the target document category to obtain the rendered data.

[0086] In this embodiment, the server can search for a first set of operation permissions corresponding to the identifier of the target document category from the document permission list; from the first set of operation permissions, it can search for operation permissions corresponding to the identifier of the target application to obtain a second set of operation permissions. This allows the server to find the operation permissions that the target application has for the target document category. Subsequently, the server can return rendering data and permission matching results to the target application based on the operation permissions in the second set of operation permissions to perform page access control on the target application.

[0087] In one embodiment, the set of operation permissions includes identifiers of operations that the target application has operation permissions for documents under the target document category; the method further includes: receiving an operation request from the target application for a target document in the source application based on an operation entry visualization identifier; the operation request carries an identifier of the target operation; in response to the operation request, matching the identifier of the target operation with identifiers in the set of operation permissions; and returning a permission matching result to the target application to instruct the target application to process the operation request accordingly based on the permission matching result.

[0088] Specifically, the server can receive operation requests from the target application for a target document in the source application based on a visual identifier for the operation entry point. In response to the operation request, the server can match the identifier of the target operation with identifiers in the set of operation permissions and return the permission matching result to the target application. Upon receiving the permission matching result, the target application processes the operation request accordingly. It can be understood that if the permission match is successful, the target application can execute the target operation; otherwise, the target application cannot execute the target operation.

[0089] In one embodiment, the target application can display a document page to the user after receiving the rendered data. In response to a user's click on a visual identifier for an action entry point, the target application can initiate an action request to the server for the target document in the source application.

[0090] In one embodiment, the operation request may carry at least one of a source application identifier, a target application identifier, a target document category identifier, and a target document identifier. It is understood that after receiving the operation request, the server can search the database for the document permission list corresponding to the source application based on the source application identifier. The server can search the document permission list for a set of permission document categories based on the target application identifier. The server can search the document permission list for a first set of operation permissions based on the target document category identifier. The server can search the first set of operation permissions for a second set of operation permissions based on the target application identifier. It is understood that performing targeted permission searches based on identifiers in the document permission list can effectively control operations involving high concurrency and large data volumes.

[0091] In one embodiment, after receiving an operation request, the server may perform a first match between the target document category identifier and the identifiers in the set of permission document categories. If the first match succeeds, the server may perform a second match between the identifier of the target operation and the identifiers in the second set of operation permissions, and return the permission matching result of the second match to the target application. If the first match fails, the server may return the permission matching result of the first match to the target application.

[0092] In this embodiment, the server can receive an operation request from the target application for a target document in the source application based on the operation entry visual identifier; the operation request carries the identifier of the target operation; in response to the operation request, the identifier of the target operation is matched with the identifier in the set of operation permissions; the permission matching result is returned to the target application to instruct the target application to process the operation request accordingly based on the permission matching result. This can re-verify the operation permissions of the target application when it performs the operation, and further ensure the security of page access control.

[0093] In one embodiment, on the document page under the target document category, rendering the operation entry visualization identifier corresponding to the operation permission in the set of operation permissions to obtain the rendering data includes: searching for the entry permission set corresponding to each operation entry visualization identifier from the second set of operation permissions; and rendering each operation entry visualization identifier according to the entry permission set on the document page under the target document category to obtain the rendering data.

[0094] The entry permission set refers to the set of operation permissions corresponding to each operation entry visual identifier. It can be understood that multiple operation entry visual identifiers can be nested within a single operation entry visual identifier, such as a drop-down menu.

[0095] Specifically, the server can look up the set of entry permissions corresponding to each operation entry visual identifier from the second set of operation permissions. It can be understood that one operation entry visual identifier can correspond to multiple operation permissions, and multiple operations can be performed through a single operation entry visual identifier. For example, multiple operations can be performed through a dropdown menu; that is, the dropdown menu contains multiple different operation entry visual identifiers, and each operation entry visual identifier in the dropdown menu corresponds one-to-one with the operation permissions in the corresponding entry permission set. The server can then render each operation entry visual identifier according to the entry permission set on the document page under the target document category, obtaining the rendered data.

[0096] In one embodiment, the same visual identifier for an operation entry point can correspond to different operations. For example, the "Add" button on the document page in different target applications corresponds to different "Add" operations. Application A can add multiple types of documents, such as accounts receivable documents, while application B can only add accounts payable documents. The server can store the identifiers of the entry permission sets corresponding to the visual identifiers of the operation entry points that the target applications can display in one set, and store the different operations that the target applications can perform through the visual identifiers of the operation entry points, i.e., the entry permission sets corresponding to the visual identifiers of the entry points, in another set. It can be understood that the server can first look up the identifiers of the entry permission sets corresponding to each visual identifier in the second set of operation permissions, and then look up the entry permission sets according to the identifiers of the entry permission sets.

[0097] In this embodiment, the entry permission set corresponding to each operation entry visual identifier is searched from the second operation permission set; on the document page under the target document category, each operation entry visual identifier is rendered according to the entry permission set to obtain rendered data, which can further control the operation permissions corresponding to each operation entry visual identifier, ensuring the diversity and stability of page access control.

[0098] In one embodiment, returning a permission matching result to the target application to instruct the target application to process the operation request accordingly based on the permission matching result includes: if the permission matching result is successful, instructing the target application to call the target operation plugin corresponding to the identifier of the target operation to execute the operation corresponding to the operation request; if the permission matching result is unsuccessful, prompting the target application that it does not have the permission to execute the operation corresponding to the operation request.

[0099] In this context, a plugin refers to a program written according to a specific application programming interface (API). It can only run on the system platform specified by the program (and may support multiple platforms simultaneously), and cannot run independently of the designated platform. A target operation plugin is a plugin used to perform a target operation.

[0100] Specifically, if the permission matching result is successful, the server allows the target application to call the target operation plugin corresponding to the identifier of the target operation to execute the operation corresponding to the operation request; if the permission matching result is unsuccessful, the server can prompt the user that the target application does not have the permission to execute the operation corresponding to the operation request.

[0101] In one embodiment, after receiving the permission matching result, if the permission matching result indicates that the application fails, the application will display a prompt message to the user indicating that it does not have the permission to perform the target operation.

[0102] In one embodiment, the server can perform unified access control on document operation plugins. It can be understood that there is a one-to-one correspondence between the identifier of the target operation and the target operation plugin; that is, there is a one-to-one correspondence between the operation plugin and the operation permission. If the permission matching result is successful, the target application has the operation permission for the target operation, and the target application can call the target operation plugin to execute the target operation.

[0103] In one embodiment, the server can directly invoke the target operation plugin to execute the target operation after the permission matching result is passed.

[0104] In one embodiment, Figure 4aThis is a diagram illustrating a document page where an operation is performed for the target application. In response to a user clicking the "Approve" button, Application 1 sends an operation request for the target document in the source application to the server. The server can find the second set of operation permissions corresponding to Application 1, match the target operation identifier carried in the operation request with the identifier in the second set of operation permissions, and return a failed permission matching result to the target application. Upon receiving this permission matching result, Application 1 prompts the user that the user does not have this operation permission. It is understandable that some malicious users can develop additional operation buttons in external applications. Although the external application can display these modified operation buttons, since the document permission list does not contain the corresponding operation permission, even if the server can receive the corresponding operation request, the permission matching result returned to the external application will inevitably be a failure. In this case, the external application cannot call the operation plugin to execute the operation corresponding to the modified operation button, effectively ensuring the security of page access control.

[0105] In another embodiment, Figure 4b This is a diagram illustrating a document page where an operation is performed for the target application. In response to the user clicking the "Approve" button, Application 2 sends an operation request for the target document in the source application to the server. The server can find the second set of operation permissions corresponding to Application 2, match the target operation identifier carried in the operation request with the identifiers in the second set of operation permissions, and return the matching result to the target application. After receiving this matching result, Application 2 invokes the operation plugin to perform the approval operation and notifies the user that the approval is complete upon completion.

[0106] Understandable. Figure 4a and Figure 4b This is a diagram illustrating a document page where operations are performed for different target applications. Clearly, external applications without the necessary permissions, even if they can display the corresponding operation buttons, cannot invoke the operation plugin to perform the operation.

[0107] In this embodiment, if the permission matching result is successful, the target application is instructed to call the target operation plugin corresponding to the identifier of the target operation to execute the operation corresponding to the operation request; if the permission matching result is unsuccessful, the target application is prompted that it does not have the permission to execute the operation corresponding to the operation request, thus realizing permission verification processing during user operations. Furthermore, the plugin itself is composed of a series of small functional structures and provides its own services to the outside world through an interface, so it has greater reusability and is easier to port. Based on the operation plugin, controlling the target application's operations on the document page can improve the stability of page access control.

[0108] In one embodiment, the source application is a native application that provides document pages under the target document category; the target application is an external application other than the source application; the document permission list records the operation permissions that different target applications have for documents under each document category; the operation entry visual identifier includes operation buttons.

[0109] Specifically, target applications can access document pages under target document categories within the source application across applications. The server can control page access for each target application based on the different operation permissions for each document category recorded in the document permission list. After receiving the rendered data from the server, the target application can display operation buttons. Users can click on these buttons to trigger the corresponding actions.

[0110] In this embodiment, the server can control page access for different target applications based on the operation permissions they possess for documents under each document category, as recorded in the document permission list, ensuring the security of external applications accessing document pages. Furthermore, target applications can display more intuitive identifiers such as operation buttons to users, enhancing the user experience.

[0111] In one embodiment, such as Figure 5 The diagram shows the sequence of events for the page access method. Users can log into the target application on their terminal. They can then open document pages in the source application based on the target application, triggering an access request sent to the server for document pages under the target document category in the source application. Upon receiving the access request, the server retrieves the document permission list corresponding to the source application from the database based on the source application identifier carried in the access request. The server then searches the document permission list for the target application's corresponding permission document category set based on the target application identifier carried in the access request, and matches the identifier of the target document category carried in the access request with the identifier in the permission document category set.

[0112] If the match is successful, the server can search for the first set of operation permissions in the document permission list according to the identifier of the target document category carried in the access request, and then search for the second set of operation permissions in the first set of operation permissions according to the identifier of the target application. The server can render the operation entry visual identifier corresponding to the operation permission in the second set of operation permissions, obtain the rendered data, and return the rendered data to the target application. If the match is unsuccessful, it indicates that the target application does not have access permissions, and the server can directly return the rendered data, instructing the target application not to display the operation entry visual identifier, that is, the operation button is restricted to visibility. After receiving the rendered data, the target application displays the document page containing the operation entry visual identifier.

[0113] The target application can display a document page with a visual identifier for an operation entry point to the user. The user can click on the visual identifier to trigger the target application to perform the corresponding operation. In response to the user clicking the visual identifier, the target application can send an operation request to the server, based on the visual identifier, for a target document in the source application. Upon receiving the operation request, the server retrieves the document permission list corresponding to the source application from the database according to the source application identifier carried in the operation request. Then, according to the target application identifier carried in the operation request, the server searches the document permission list for the set of permission document categories corresponding to the target application and performs a first match between the identifier of the target document category carried in the operation request and the identifier in the set of permission document categories.

[0114] If the first match succeeds, the server can search for the first set of operation permissions in the document permission list according to the identifier of the target document category carried in the operation request, and then search for the second set of operation permissions in the first set according to the identifier of the target application. The server can perform a second match between the identifier of the target operation carried in the operation request and the identifiers in the second set of operation permissions to obtain the permission matching result, and return the permission matching result to the target application. If the first match fails, it indicates that the target application does not have any permissions for the target document category, and the server can directly return the permission matching result, prompting the target application that it does not have the operation permission, that is, it cannot execute the operation. The target application receives the permission matching result. If the permission matching result is successful, it calls the target operation plugin to execute the target operation; if the permission matching result is unsuccessful, it prompts the user that it does not have the operation permission.

[0115] In one embodiment, a user can modify the action buttons on a document page within the target application.

[0116] In one embodiment, a user can modify the document permission list corresponding to the source application, and add or delete operation permissions and permission document categories corresponding to each target application.

[0117] In one embodiment, when the source application receives a request from the target application, it can forward the request to the server.

[0118] In one embodiment, the source application may respond to a request initiated by the target application by sending a permission verification request to the server. This permission verification request carries information about the request initiated by the target application. The permission verification request instructs the server to verify the relevant permissions of the target application based on the request initiated by the target application.

[0119] In one embodiment, developers can implement low-code access control for external applications that access documents through non-source application entry points, achieving low coupling with business logic. This means that each permission set shares a common development logic, allowing for access control with minimal code.

[0120] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0121] Based on the same inventive concept, this application also provides a page access device for implementing the page access method described above. The solution provided by this device is similar to the implementation described in the above method; therefore, the specific limitations in one or more page access device embodiments provided below can be found in the limitations of the page access method described above, and will not be repeated here.

[0122] In one embodiment, such as Figure 6 As shown, a page access device 600 is provided, including: a receiving module 602, a searching module 604, and a configuration module 606, wherein:

[0123] The receiving module 602 is used to receive access requests from the target application for document pages under the target document category in the source application;

[0124] The lookup module 604 is used to respond to the access request, obtain the document permission list corresponding to the source application, and from the document permission list, find the set of operation permissions that the target application has for documents under the target document category;

[0125] The configuration module 606 is used to render the visual identifier of the operation entry corresponding to the operation permission in the set of operation permissions on the document page under the target document category, and obtain the rendered data; return the rendered data to the target application; the rendered data is used to instruct the display of the document page containing the visual identifier of the operation entry in the target application.

[0126] In one embodiment, the lookup module 604 is further configured to look up the identifier of the document category for which the target application has operation permissions from the document permission list, and obtain a set of permission document categories; if the identifier of the target document category matches the identifier in the set of permission document categories, then the step of looking up the set of operation permissions that the target application has for documents under the target document category from the document permission list is executed.

[0127] In one embodiment, the set of operation permissions is a second set of operation permissions; the access request carries the target application identifier and the identifier of the target document category; the lookup module 604 is further configured to look up the first set of operation permissions corresponding to the identifier of the target document category from the document permission list; the first set of operation permissions refers to the set of operation permissions that all external applications have for documents under the target document category; the second set of operation permissions is obtained by looking up the operation permissions corresponding to the target application identifier from the first set of operation permissions.

[0128] In one embodiment, the set of operation permissions includes identifiers of operations that the target application has operation permissions for documents under the target document category; the receiving module 602 is further configured to receive an operation request from the target application for a target document in the source application based on the operation entry visualization identifier; the operation request carries the identifier of the target operation; the searching module 604 is further configured to, in response to the operation request, match the identifier of the target operation with the identifiers in the set of operation permissions; and return the permission matching result to the target application to instruct the target application to process the operation request accordingly based on the permission matching result.

[0129] In one embodiment, the lookup module 604 is further configured to, if the permission matching result is successful, instruct the target application to call the target operation plugin corresponding to the identifier of the target operation to execute the operation corresponding to the operation request; if the permission matching result is unsuccessful, prompt the target application that it does not have the permission to execute the operation corresponding to the operation request.

[0130] In one embodiment, a page access method is provided, in which the method is applied to Figure 1 Taking the terminal in the example, the process includes: responding to an access operation on a document page under the target document category in the source application, initiating an access request based on the target application; receiving rendering data returned in response to the access request; the rendering data includes data used to display the visual identifier of the operation entry point; the visual identifier of the operation entry point corresponds to the operation permissions in the set of operation permissions; the set of operation permissions includes the operation permissions that the target application has for documents under the target document category, which are in the document permission list corresponding to the source application; and displaying the document page containing the visual identifier of the operation entry point in the target application according to the rendering data.

[0131] Specifically, users can log in to the target application via a terminal and access document pages under the target document category in the source application. The terminal can respond to this access operation by sending an access request to the server. Based on the received access request, the server can obtain the document permission list corresponding to the source application and then search for the set of operation permissions that the target application has for documents under the target document category. The server can render the visual identifiers of the operation entry points corresponding to the operation permissions in the set of operation permissions, obtain rendered data, and send the rendered data to the terminal. The terminal can receive the rendered data returned in response to the access request and display the visual identifiers of the operation entry points according to the rendered data, thus displaying document pages containing the visual identifiers of the operation entry points in the target application.

[0132] In this embodiment, the terminal can send an access request from the target application to the document page under the target document category in the source application, and receive the rendering data sent by the server. This allows the terminal to display a visual identifier of the operation entry point with the target application's operating permissions to the user, thereby improving the user experience and ensuring the stability of page access control.

[0133] Based on the same inventive concept, this application also provides a page access device for implementing the page access method described above. The solution provided by this device is similar to the implementation described in the above method; therefore, the specific limitations in one or more page access device embodiments provided below can be found in the limitations of the page access method described above, and will not be repeated here.

[0134] In one embodiment, such as Figure 7 As shown, a page access device 700 is provided, including: an acquisition module 702 and a display module 704, wherein:

[0135] The acquisition module 702 is used to respond to an access operation on a document page under the target document category in the source application, and to initiate an access request based on the target application; receive rendering data returned in response to the access request; the rendering data includes data for displaying the operation entry visual identifier; the operation entry visual identifier corresponds to the operation permissions in the set of operation permissions; the set of operation permissions includes the operation permissions in the document permission list corresponding to the source application and the operation permissions that the target application has for documents under the target document category;

[0136] Display module 704 is used to display a document page with a visual identifier for operation entry in the target application according to the rendered data.

[0137] The aforementioned page access device and its modules can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can invoke and execute the operations corresponding to each module.

[0138] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 8 As shown, the computer device includes a processor, memory, and a network interface connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The database stores page access-related data. The network interface communicates with external terminals via a network connection. When executed by the processor, the computer program implements a page access method.

[0139] In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 9 As shown, the computer device includes a processor, memory, communication interface, display screen, and input devices connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements a page access method. The display screen can be an LCD screen or an e-ink screen. The input devices can be a touch layer covering the display screen, buttons, a trackball, or a touchpad located on the computer device's casing, or an external keyboard, touchpad, or mouse.

[0140] Those skilled in the art will understand that Figure 8 and Figure 9The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0141] In one embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above-described method embodiments.

[0142] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps in the above method embodiments.

[0143] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0144] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0145] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments described above. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0146] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0147] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A method for accessing a webpage, characterized in that, The method includes: Receive access requests from the target application for document pages under the target document category in the source application; In response to the access request, obtain the document permission list corresponding to the source application; the document permission list records the operation permissions that different target applications have for documents under each document category; From the document permission list, find the set of operation permissions that the target application has to perform operations on documents under the target document category; In the document page under the target document category, render the visual identifier of the operation entry corresponding to the operation permission in the set of operation permissions to obtain the rendered data; The rendered data is returned to the target application; the rendered data is used to instruct the display of the document page containing the visual identifier of the operation entry point in the target application.

2. The method according to claim 1, characterized in that, The method further includes: From the document permission list, find the identifiers of the document categories for which the target application has operation permissions, and obtain the set of permission document categories; If the identifier of the target document category matches the identifier in the set of authorized document categories, then Perform the step of searching the document permission list for the set of operation permissions that the target application has for performing operations on documents under the target document category.

3. The method according to claim 1, characterized in that, The set of operation permissions is a second set of operation permissions; the access request carries the target application identifier and the identifier of the target document category; The step of searching the document permission list for the set of operation permissions that the target application has to perform operations on documents under the target document category includes: From the document permission list, find the first set of operation permissions corresponding to the identifier of the target document category; the first set of operation permissions refers to the set of operation permissions that all external applications have to perform operations on documents under the target document category. From the first set of operation permissions, find the operation permissions corresponding to the target application identifier to obtain the second set of operation permissions.

4. The method according to claim 3, characterized in that, In the document page under the target document category, the visual identifier of the operation entry corresponding to the operation permission in the set of operation permissions is rendered, and the rendered data includes: From the second set of operation permissions, find the set of entry permissions corresponding to each operation entry visual identifier; In the document page under the target document category, according to the entry permission set, render the visual identifiers of each operation entry point to obtain rendered data.

5. The method according to claim 1, characterized in that, The set of operation permissions includes identifiers of operations for which the target application has operation permissions for documents under the target document category; the method further includes: The target application receives an operation request for a target document in the source application based on the operation entry visualization identifier; the operation request carries the identifier of the target operation. In response to the operation request, the identifier of the target operation is matched with the identifier in the set of operation permissions; Return permission matching results to the target application to instruct the target application to process the operation request accordingly based on the permission matching results.

6. The method according to claim 5, characterized in that, The step of returning a permission matching result to the target application to instruct the target application to process the operation request accordingly based on the permission matching result includes: If the permission matching result is successful, the target application is instructed to call the target operation plugin corresponding to the identifier of the target operation to execute the operation corresponding to the operation request; If the permission matching result is unsuccessful, the target application will be prompted that it does not have the permission to perform the operation corresponding to the operation request.

7. The method according to any one of claims 1 to 6, characterized in that, The source application is the native application that provides the document page under the target document category; the target application is an external application other than the source application; the operation entry visual identifier includes operation buttons.

8. A method for accessing a page, characterized in that, The method includes: In response to an access operation targeting a document page under the target document category in the source application, an access request is initiated based on the target application. The system receives rendering data returned in response to the access request; the rendering data includes data for displaying a visual identifier for the operation entry point; the visual identifier for the operation entry point corresponds to the operation permissions in the set of operation permissions; the set of operation permissions includes the operation permissions in the document permission list corresponding to the source application, and the operation permissions that the target application has for performing operations on documents under the target document category; the document permission list records the operation permissions that different target applications have for documents under each document category. Based on the rendered data, the document page containing the visual identifier of the operation entry is displayed in the target application.

9. A page access device, characterized in that, The device includes: The receiving module is used to receive access requests from the target application for document pages under the target document category in the source application; The lookup module is used to respond to the access request, obtain the document permission list corresponding to the source application; from the document permission list, find the set of operation permissions that the target application has to perform operations on documents under the target document category; the document permission list records the operation permissions that different target applications have for documents under each document category. The configuration module is used to render a visual identifier for the operation entry corresponding to the operation permission in the set of operation permissions on the document page under the target document category, thereby obtaining rendering data; and to return the rendering data to the target application; the rendering data is used to instruct the display of the document page containing the visual identifier for the operation entry in the target application.

10. A page access device, characterized in that, The device includes: The acquisition module is used to respond to an access operation on a document page under a target document category in the source application by initiating an access request based on the target application; receiving rendering data returned in response to the access request; the rendering data includes data for displaying a visual identifier for the operation entry; the visual identifier for the operation entry corresponds to the operation permissions in the set of operation permissions; the set of operation permissions includes the operation permissions in the document permission list corresponding to the source application, and the operation permissions that the target application has for performing operations on documents under the target document category; the document permission list records the operation permissions that different target applications have for documents under each document category. The display module is used to display the document page containing the visual identifier of the operation entry point in the target application according to the rendered data.

11. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 8.

12. 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 method according to any one of claims 1 to 8.

13. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 8.

Images