A page login method, system and related device

Abstract

The present application provides a page login method, which includes: receiving a token returned by the backend; saving the token to local storage, and adding the token to header information; The instruction is sent to the backend; the user page permission information is obtained according to the user information returned by the backend and sent to the routing permission table; when the user initiates a page update request, it is judged whether the page update request is valid according to the routing permission table; Displays the target page corresponding to the page update request. This application implements page-level authority management, ensures control of unauthorized access, effectively intercepts unauthorized access, and improves network security protection capabilities. It makes the management of user page permissions more time-effective. The present application also provides a page login system, a computer-readable storage medium and a user login device, which have the above beneficial effects.

Description

technical field [0001] The present application relates to the field of network security, and in particular, to a page login method, system and related device. Background technique [0002] The previous permission control system was dynamically generated by the back-end based on the user's permissions. If the system adds modules or adjusts the back-end configuration routing and permissions of sub-pages in the later stage, the front-end and back-end are finally separated, and the front-end is dominated by the back-end. And the later maintenance cost is high. [0003] In the prior art, the front end sends a request to obtain user permission information after successful login and when the page is refreshed. Therefore, when the administrator modifies the user permission information, it cannot take effect immediately, and the route can be re-acquired only when the user logs in next time. It is difficult to modify the permissions of different user pages, which is not conducive to ...

AI Technical Summary

Problems solved by technology

[0002] The previous permission control system was dynamically generated by the backend according to the user's permissions. If the system added modules or adjusted the subpage backend configuration routing and permissions in the later stage, it was hard to separate the frontend and backend, and returned to the state where the frontend was dominated by the backend. And later maintenance costs are high

[0003] In the existing technology, the front end mainly uses the front-end to send requests to obtain user permission information after successful login and when the page is refreshed. Therefore, when the administrator modifies the user permission information, it cannot take effect immediately, and the route can only be obtained again when the user logs in next time. information, it is difficult to modify the page permissions for different users, which is not conducive to the maintenance of network information security

Images