A website page access rights management method and system

Abstract

The present invention relates to the field of computer network management technology, and more specifically, to a website page access permission management method and system. The present invention provides a website page access permission management method, comprising the following steps: Step S1, obtaining the corresponding login information of the user logging into the website, generating the user's accessible page permission list and configuration; Step S2, matching the current page that the user needs to access with the user's accessible page permission list and configuration, and determining whether to allow the user to access the current page based on the matching result. The website page access permission management method and system provided by the present invention can efficiently implement the common functions of website page access permissions without manual synchronization by front-end and back-end developers, and is simple to implement and highly versatile.

Description

Technical Field

[0001] The present invention relates to the technical field of computer network management, and more specifically, to a method and system for managing website page access rights. Background Art

[0002] In information management websites such as enterprise CRM (customer relationship management), ERM (enterprise resource management), ERP (enterprise resource planning), there are usually functions to set levels for logged-in users, assign page viewing permissions, and operation button permissions.

[0003] Among them, the CRM (Customer Relationship Management) system refers to an information system that uses software, hardware and network technology to collect, manage, analyze and use customer information for enterprises. With customer data management as the core, it records various interactions between enterprises and customers during the marketing and sales process.

[0004] The ERM (Enterprise Resource Management) system is an information system with management accounting as its core. It identifies and plans enterprise resources, thereby obtaining customer orders, completing processing and delivery, and finally obtaining customer payments. In other words, ERM integrates all internal resources of the enterprise and plans procurement, production, cost, inventory, distribution, transportation, finance, and human resources to achieve the best resource combination and obtain the best benefits.

[0005] ERP (Enterprise Resource Planning) system, an enterprise resource planning system refers to a management platform based on information technology that uses systematic management ideas to provide corporate decision-making and employee decision-making operation means. It is an application system that integrates the management of logistics, financial flow, and information flow, including procurement, sales, inventory, customers, finance and other modules, which are used to optimize enterprise resources and maximize management benefits.

[0006] Generally, the mainstream technical implementation solution is that the front-end developer manually hands over the list of all website pages and the list of all website buttons to the back-end developer, who then returns the list of all website pages and the list of all website buttons through the network interface for enterprise users to configure the login user level, and allocate page viewing permissions and button operation permissions.

[0007] Chinese invention patent CN 200610157777.4 provides a web page permission management method, which verifies and manages the client's permission to access the web page through a configuration file installed in an application server. The method includes the following steps: checking whether the client has logged in to the web page; if the client has not logged in to the web page, importing a login dialog box; receiving an instruction input by the client, and searching for an identity code and an identification code matching the instruction from a database server to determine whether the client has passed the identity authentication; if the client has passed the identity authentication, reading the web page access permission corresponding to the client's identity code from the database server to determine whether the client is within the authorized scope for accessing the web page.

[0008] The inconvenience of the above technical solution is that whenever there are additions, deletions or changes to the website pages, the front-end developers and back-end developers need to manually synchronize the list of all website pages and the list of all website buttons. At the same time, if the website user has set the access rights for a certain page, when a certain page is deleted / replaced due to the iteration of website functions, it will be an invalid / wrong configuration data for the access rights data stored in the database.

[0009] Existing technical solutions are relatively inefficient in development work and may generate invalid / erroneous data causing website malfunctions. Summary of the invention

[0010] The purpose of the present invention is to provide a website page access rights management method and system to solve the problem that the prior art has low efficiency and is prone to errors when the website pages are increased or decreased.

[0011] In order to achieve the above object, the present invention provides a method for managing website page access rights, comprising the following steps:

[0012] Step S1, obtaining the corresponding login information of the user logging into the website, and generating a list of accessible page permissions and configuration for the user;

[0013] Step S2: Match the current page that the user needs to access with the user's accessible page permission list and configuration, and decide whether to allow the user to access the current page based on the matching result.

[0014] In one embodiment, the step S1 further comprises:

[0015] Step S11, obtaining the corresponding login information of the user logging into the website, and returning the list and configuration of accessible pages corresponding to the permission level of the user;

[0016] Step S12: performing intersection processing on the list and configuration of all permission pages of the website and the list and configuration of accessible pages of the corresponding permission level of the user, searching and generating the list and configuration of permission pages accessible to the user;

[0017] Step S13: merge the list and configuration of all public pages of the website with the list and configuration of permission pages accessible to the user to generate the list and configuration of permission pages accessible to the user.

[0018] In one embodiment, in step S2, determining whether to allow the user to access the current page according to the matching result further includes:

[0019] When the current page is in the user's accessible page permission list and configuration, the user is allowed to open and access the current page normally;

[0020] When the current page is not in the user's accessible page permission list and configuration, opening and accessing the current page is prohibited, and the page is redirected to the no-authority prompt page.

[0021] In one embodiment, the list of all permission pages and configurations of the website is a collection of all pages and configurations in the website that require permission to access;

[0022] The list of pages and configurations accessible to the user at the corresponding permission level is a collection of pages and configurations accessible to the logged-in user at the corresponding permission level.

[0023] In one embodiment, the list of accessible pages and configurations for the user's corresponding permission level is a subset of the list of all permission pages and configurations of the website.

[0024] In one embodiment, the list of accessible pages and the configuration of the user's corresponding permission level in step S11 are configured by the following steps:

[0025] Step S111, read the page file to automatically generate a list and configuration of all authorized pages of the website and a list and configuration of all public pages of the website;

[0026] Step S112, automatically converting to a permission configuration page according to the list and configuration of all permission pages of the website and the list and configuration of all public pages of the website;

[0027] Step S113: Select and configure page access permissions at different permission levels, save the page list, and form a list of accessible pages and configurations at different permission levels.

[0028] In one embodiment, the step S111 further includes:

[0029] By reading the execution command script of all local page files of the website project, a list of all permission pages and public pages of the website and the corresponding configurations are generated.

[0030] In one embodiment, the permission configuration page is a permission check page.

[0031] In order to achieve the above object, the present invention provides a website page access rights management system, comprising:

[0032] a memory for storing instructions executable by a processor;

[0033] A processor is used to execute the instructions to implement any of the methods described above.

[0034] In order to achieve the above object, the present invention provides a computer storage medium on which computer instructions are stored, wherein when the computer instructions are executed by a processor, any of the above methods is executed.

[0035] The present invention provides a website page access permission management method and system, which do not require manual synchronization by front-end and back-end developers, and efficiently implement common functions of website page access permission, are simple to implement and have strong versatility. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] The above and other features, properties and advantages of the present invention will become more apparent through the following description in conjunction with the accompanying drawings and embodiments, in which the same reference numerals always represent the same features, wherein:

[0037] Figure 1 A flow chart of a method for managing website page access rights according to an embodiment of the present invention is disclosed;

[0038] Figure 2 A flowchart of the authority management of a user logging into a website according to an embodiment of the present invention is disclosed;

[0039] Figure 3 A flow chart of a user accessing a website page according to an embodiment of the present invention is disclosed;

[0040] Figure 4 A flowchart of permission page configuration according to an embodiment of the present invention is disclosed;

[0041] Figure 5 A principle block diagram of a website page access authority management system according to an embodiment of the present invention is disclosed. DETAILED DESCRIPTION

[0042] In order to make the purpose, technical solution and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the invention and are not used to limit the invention.

[0043] The present invention proposes a website page access permission management method and system, which involve browsers, web page access, service management and permission control, and specifically includes a page access permission management and interception technology for users of an enterprise management website.

[0044] Figure 1 A flow chart of a method for managing website page access rights according to an embodiment of the present invention is disclosed. Figure 1 As shown, the website page access permission management method proposed by the present invention includes the following steps:

[0045] Step S1, obtaining the corresponding login information of the user logging into the website, and generating a list of accessible page permissions and configuration for the user;

[0046] Step S2: Match the current page that the user needs to access with the user's accessible page permission list and configuration, and decide whether to allow the user to access the current page based on the matching result.

[0047] Figure 2 A flowchart of the rights management of a user logging into a website according to an embodiment of the present invention is disclosed. Figure 2 As shown, when a user logs into the website's permission management, the user's page access permissions are generated.

[0048] The step S1 further comprises the following steps:

[0049] Step S11, obtaining the corresponding login information of the user logging into the website, and returning the list and configuration of accessible pages corresponding to the permission level of the user;

[0050] After the user logs in to the website correctly, when the user visits a page, the backend service returns a list of accessible pages for the user's permission level.

[0051] Step S12: performing intersection processing on the list and configuration of all permission pages of the website and the list and configuration of accessible pages of the corresponding permission level of the user, searching and generating the list and configuration of permission pages accessible to the user;

[0052] The list of all permission pages and configurations of the website is a collection of all pages and configurations on the website that require permission to access;

[0053] The list of pages and configurations that are accessible to the user at the corresponding permission level is a collection of pages and configurations that are accessible to the logged-in user at the corresponding permission level.

[0054] Furthermore, the list of accessible pages and configurations for the user's corresponding permission level is a subset of the list of all permission pages and configurations of the website.

[0055] Step S13: merge the list and configuration of all public pages of the website with the list and configuration of permission pages accessible to the user to generate the list and configuration of permission pages accessible to the user.

[0056] Figure 3 A flow chart of a user accessing a website page according to an embodiment of the present invention is disclosed. Figure 3 As shown, in the step S2, determining whether to allow the user to access the current page according to the matching result further includes:

[0057] When the current page is in the user's accessible page permission list and configuration, the user is allowed to open and access the current page normally;

[0058] When the current page is not in the user's accessible page permission list and configuration, opening and accessing the current page is prohibited, and the page is redirected to the no-authority prompt page.

[0059] Match the current page accessed by the user with the user's accessible page permission list and configuration. If it is in the accessible page permission list, the page will be opened normally; if it is not in the accessible page permission list, the website will jump to the 401 no permission prompt page.

[0060] For example, when a user is about to visit page A, the relevant code first intercepts and obtains the path of the page the user is about to visit as a. At this time, a is searched and compared with the accessible page permission list corresponding to the user. If found, it is allowed to jump to page A. If the web page is not found, it is forced to jump to the 401 no permission prompt page.

[0061] Figure 4 A flowchart of configuring a permission page according to an embodiment of the present invention is disclosed. Figure 4 The illustrated embodiment discloses how the front-end page provides the website administrator with a permission configuration page and how the front-end development delivers the permission page list to the back-end development.

[0062] The permission configuration page is automatically generated based on the page list configuration, and the website administrator configures user-level page access permissions.

[0063] The list of accessible pages and configuration of the user's corresponding permission level in step S11 are configured through the following steps:

[0064] Step S111, read the page file to automatically generate a list and configuration of all authorized pages of the website and a list and configuration of all public pages of the website;

[0065] The front-end developer reads the page files in the website project and automatically generates a list of all permission pages and a list of all public pages for the website.

[0066] Furthermore, by reading the execution command script of all local page files of the website project, a list of all permission pages and a list of public pages of the website and corresponding configurations are generated.

[0067] Step S112, automatically converting to a permission configuration page according to the list and configuration of all permission pages of the website and the list and configuration of all public pages of the website;

[0068] When the website administrator enters the permission configuration page, the page is automatically converted into a permission configuration page based on the configuration of the list of all permission pages on the website and the list of all public pages on the website.

[0069] Furthermore, the permission configuration page is a permission check page.

[0070] Step S113: Select and configure page access permissions at different permission levels, save the page list, and form a list of accessible pages and configurations at different permission levels.

[0071] The website administrator configures page access permissions for a certain user level and saves the page list to the database.

[0072] For example, the list of all public pages of the website includes public pages X, Y, and Z, and the list of all permission pages of the website includes permission pages A, B, C, D, and E.

[0073] Set the user with permission level 1 to access pages A, B, and C;

[0074] Set the user with permission level 2 to access pages A, B, C, D, and E.

[0075] When any user with permission level 1 logs in to the website, the backend service returns a list of accessible pages for that user level, that is, the pages that the user can access include permission pages A, B, C and public pages X, Y, Z.

[0076] Although the above methods are illustrated and described as a series of actions for simplicity of explanation, it should be understood and appreciated that these methods are not limited by the order of the actions, because according to one or more embodiments, some actions may occur in a different order and / or concurrently with other actions from those illustrated and described herein or not illustrated and described herein but understandable to those skilled in the art.

[0077] Figure 5 The principle block diagram of a website page access permission management system according to an embodiment of the present invention is disclosed. The website page access permission management system may include an internal communication bus 501, a processor (processor) 502, a read-only memory (ROM) 503, a random access memory (RAM) 504, a communication port 505, and a hard disk 507. The internal communication bus 501 can realize data communication between components of the website page access permission management system. The processor 502 can make judgments and issue prompts. In some embodiments, the processor 502 can be composed of one or more processors.

[0078] The communication port 505 can realize data transmission and communication between the website page access permission management system and external input / output devices. In some embodiments, the website page access permission management system can send and receive information and data from the network through the communication port 505. In some embodiments, the website page access permission management system can transmit and communicate data with external input / output devices in a wired form through the input / output terminal 506.

[0079] The website page access permission management system may also include different forms of program storage units and data storage units, such as a hard disk 507, a read-only memory (ROM) 503 and a random access memory (RAM) 504, which can store various data files used for computer processing and / or communication, and possible program instructions executed by the processor 502. The processor 502 executes these instructions to implement the main part of the method. The results processed by the processor 502 are transmitted to an external output device through a communication port 505 and displayed on a user interface of the output device.

[0080] For example, the implementation process file of the above-mentioned website page access rights management prediction method can be a computer program, which is stored in the hard disk 507 and can be recorded in the processor 502 for execution to implement the method of the present application.

[0081] When the implementation process file of the website page access permission management method is a computer program, it can also be stored in a computer-readable storage medium as a product. For example, a computer-readable storage medium may include, but is not limited to, a magnetic storage device (e.g., a hard disk, a floppy disk, a magnetic strip), an optical disk (e.g., a compact disk (CD), a digital versatile disk (DVD)), a smart card, and a flash memory device (e.g., an electrically erasable programmable read-only memory (EPROM), a card, a stick, a key drive). In addition, the various storage media described herein can represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media (and / or storage media) that can store, contain and / or carry code and / or instructions and / or data.

[0082] The present invention provides a website page access rights management method and system, which specifically has the following beneficial effects:

[0083] 1) When the functions of website pages are increased or decreased, there is no need for front-end developers to synchronize page configurations with back-end developers. Website administrators can directly enter the permission configuration page to make additional allocations, which greatly reduces the workload of front-end developers and back-end developers;

[0084] 2) When compiling a project, a page list and corresponding configuration are generated by reading the execution command script of all local page files of the website project. Compared with the past manual and clumsy registration and writing of configurations according to page files one by one, automated script generation frees developers from manual work and is more convenient and accurate.

[0085] Those skilled in the art will appreciate that information, signals, and data may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips cited throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0086] Those skilled in the art will further appreciate that the various illustrative logic blocks, modules, circuits, and algorithm steps described in conjunction with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or a combination of the two. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps are generally described above in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. The technician may implement the described functionality in different ways for each specific application, but such implementation decisions should not be interpreted as resulting in a departure from the scope of the present invention.

[0087] The various illustrative logic modules and circuits described in conjunction with the embodiments disclosed herein may be implemented or executed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in cooperation with a DSP core, or any other such configuration.

[0088] In one or more exemplary embodiments, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented as a computer program product in software, each function may be stored on or transmitted by a computer-readable medium as one or more instructions or codes. Computer-readable media include both computer storage media and communication media, including any medium that facilitates the transfer of a computer program from one place to another. Storage media may be any available medium that can be accessed by a computer. As an example and not limitation, such a computer-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of an instruction or data structure and can be accessed by a computer. Any connection is also properly referred to as a computer-readable medium. For example, if the software is transmitted from a website, a server, or other remote source using a coaxial cable, a fiber optic cable, a twisted pair, a digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwaves, the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwaves are included in the definition of the medium. Disk and disc as used herein include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, wherein disk often reproduces data magnetically, while disc reproduces data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0089] As shown in this application and claims, unless the context clearly indicates an exception, the words "a", "an", "an" and / or "the" do not refer to the singular and may also include the plural. Generally speaking, the terms "include" and "comprise" only indicate the inclusion of the steps and elements that have been clearly identified, and these steps and elements do not constitute an exclusive list. The method or device may also include other steps or elements.

[0090] The above embodiments are provided for persons familiar with the art to implement or use the present invention. Personnel familiar with the art can make various modifications or changes to the above embodiments without departing from the inventive concept of the present invention. Therefore, the protection scope of the present invention is not limited to the above embodiments, but should be the maximum scope of the innovative features mentioned in the claims.

Claims

1. A method for managing access rights to website pages, characterized in that: The following steps are involved: Step S1, obtaining the corresponding login information of the user logging into the website, and generating a list of accessible page permissions and configuration for the user; Step S2: matching the current page that the user needs to access with the user's accessible page permission list and configuration, and determining whether to allow the user to access the current page based on the matching result; Wherein, the step S1 further comprises: Step S11, obtaining the corresponding login information of the user logging into the website, and returning the list and configuration of accessible pages corresponding to the permission level of the user; Step S12: performing intersection processing on the list and configuration of all permission pages of the website and the list and configuration of accessible pages of the corresponding permission level of the user, searching and generating the list and configuration of permission pages accessible to the user; Step S13: merge the list and configuration of all public pages of the website with the list and configuration of the permission pages accessible to the user to generate the list and configuration of the permission pages accessible to the user; The list of accessible pages and configuration of the user's corresponding permission level in step S11 are configured through the following steps: Step S111, read the page file to automatically generate a list and configuration of all authorized pages of the website and a list and configuration of all public pages of the website; Step S112, automatically converting to a permission configuration page according to the list and configuration of all permission pages of the website and the list and configuration of all public pages of the website; Step S113, select and configure page access permissions at different permission levels, save the page list, and form a list of accessible pages at different permission levels and configuration; The list of all permission pages and configurations of the website is a collection of all pages and configurations on the website that require permission to access; The list of pages and configurations accessible to the user at the corresponding permission level is a collection of pages and configurations accessible to the logged-in user at the corresponding permission level.

2. The website page access rights management method according to claim 1, characterized in that: In step S2, determining whether to allow the user to access the current page according to the matching result further includes: When the current page is in the user's accessible page permission list and configuration, the user is allowed to open and access the current page normally; When the current page is not in the user's accessible page permission list and configuration, opening and accessing the current page is prohibited, and the page is redirected to the no-authority prompt page.

3. The website page access rights management method according to claim 1, characterized in that: The list of pages and configurations accessible to the user at the corresponding permission level is a subset of the list of pages and configurations of all permissions on the website.

4. The website page access rights management method according to claim 1, characterized in that: The step S111 further comprises: By reading the execution command script of all local page files of the website project, a list of all permission pages and public pages of the website and the corresponding configurations are generated.

5. The website page access rights management method according to claim 1, characterized in that: The permission configuration page is a permission selection page.

6. A website page access rights management system, comprising: a memory for storing instructions executable by a processor; A processor, configured to execute the instructions to implement the method according to any one of claims 1 to 5.

7. A computer storage medium having computer instructions stored thereon, wherein when the computer instructions are executed by a processor, the method according to any one of claims 1 to 5 is executed.

Images