Front-end page login state adaptation method

Abstract

The invention discloses a front-end page login state adaptation method, which comprises the following steps of setting a login module based on an application system corresponding to a front-end page, and connecting the login module with each stage of subsystem of the application system; enabling the subsystems of all levels to confirm the access authority through the login module; on the basis of the access permission, verifying the legality of the access permission through the login module to obtain a verification result; feeding a verification result back to the first event triggering party through the front-end page or the subsystems at all levels, and enabling the first event triggering party to carry out next operation according to the verification result through flow guidance of the front-end page or the subsystems at all levels. In the method provided by the invention, the automatic triggering mode can be adapted to a third-party application to directly access a login state limiting page of the application, so that the development cost is reduced; a development engineer does not need to care about login state synchronization between different pages, so that the abnormal risk is reduced; and the user does not need to frequently switch and click, so that the user experience is improved.

Description

technical field [0001] The invention relates to the field of vector magnetometer calibration, in particular to a front-end page login state adaptation method. Background technique [0002] In the development process of large-scale front-end applications, cooperation and mutual drainage with third-party applications are very common, and they need to be embedded in various applications. However, the user system is often inconsistent, and each application needs to handle the login status separately. For example, when applications in multiple industrial sectors are redirected to application A, or traffic diverted by third-party application activities is redirected to application A, the following situations often occur: [0003] Situation 1: The target page of the application A has restrictions that require login status to access, such as the personal center page, etc. Usually, the solution to this situation is that the A application itself judges the login status before the jum...

AI Technical Summary

Problems solved by technology

[0006] 1. Development engineers need to pay attention to the synchronization of login status between different pages. For example, if the login is successful or failed on the login page, it cannot be carried when returning to the upper-level page. It needs to be processed separately. The logic is complex and the development volume big and risky

[0007] 2. The cost of directly connecting the third application to this application is very high, and the login logic needs to be adapted separately. The adaptation logic of different applications is different, resulting in the need to issue multiple compatible solutions

[0008] 3. After the user logs in successfully, the user needs to re-trigger the next action before continuing to visit, which leads to poor user experience

Images