CN111177612B - Page login authentication method and related device - Google Patents
Page login authentication method and related device Download PDFInfo
- Publication number
- CN111177612B CN111177612B CN201910643352.1A CN201910643352A CN111177612B CN 111177612 B CN111177612 B CN 111177612B CN 201910643352 A CN201910643352 A CN 201910643352A CN 111177612 B CN111177612 B CN 111177612B
- Authority
- CN
- China
- Prior art keywords
- page
- routing module
- login
- target
- client
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Computer Hardware Design (AREA)
- Software Systems (AREA)
- Data Mining & Analysis (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The application provides a page login authentication method and a related device, which can reduce the workload of developers and improve the development efficiency. The method is applied to a front-end framework Vue, the Vue comprising a routing module, the method comprising: receiving a page access request through a routing module, wherein the page access request is used for requesting a login target page; acquiring an operation environment corresponding to a target page according to a page access request through a routing module; if the operation environment corresponding to the target page is the first operation environment, a target application login link is sent to the client through the routing module, so that the client accesses the target application program according to the target application login link, wherein the target application program has a corresponding relation with the first operation environment; receiving callback links sent by a client through a routing module; and authenticating the client through the routing module according to the callback link.
Description
Technical Field
The present application relates to the field of network technologies, and in particular, to a method and related device for page login authentication
Background
When a user accesses a page through a browser, some pages often require the user to log in to continue browsing pages.
In the prior art, a browser generally performs page construction based on a front end framework (Vue), each Vue instance for constructing a page is subjected to an initialization process when being created, in this process, a hook function of some lifecycle is usually operated, and a developer can add codes to the function to set required functions, such as login authentication codes and service rendering codes, so that the browser can render the page for the user after performing login authentication on the user.
Because the login authentication is performed in a hook function of a life cycle in the prior art, the login authentication code and the service code are mutually coupled, and when developing different pages, a developer needs to independently set a set of login authentication code on each page, so that the workload of the developer is large and the development efficiency is low.
Disclosure of Invention
The embodiment of the application provides a page login authentication method and a related device, which can reduce the workload of developers and improve the development efficiency.
An embodiment of the present application provides a method for authenticating page login, where the method is applied to a front end framework Vue, where the Vue includes a routing module, and the method includes:
receiving a page access request through a routing module, wherein the page access request is used for requesting a login target page;
acquiring an operation environment corresponding to the target page according to the page access request through the routing module;
if the operation environment corresponding to the target page is a first operation environment, sending a target application login link to a client through the routing module so that the client accesses a target application program according to the target application login link, wherein the target application program has a corresponding relation with the first operation environment;
receiving a callback link sent by the client through the routing module;
and authenticating the client through the routing module according to the callback link.
A second aspect of the embodiment of the present application provides a page login authentication device, where the page login authentication device includes a front end frame Vue, where the Vue includes a routing module, and the page login authentication device includes:
the first receiving module is used for receiving a page access request through the routing module, wherein the page access request is used for requesting a login target page;
the first acquisition module is used for acquiring an operation environment corresponding to the target page according to the page access request through the routing module;
the sending module is used for sending a target application login link to the client through the routing module if the running environment corresponding to the target page is a first running environment, so that the client accesses a target application program according to the target application login link, wherein the target application program has a corresponding relation with the first running environment;
the second receiving module is used for receiving the callback link sent by the client through the routing module;
and the processing module is used for carrying out authentication processing on the client through the routing module according to the callback link.
Based on the second aspect, the embodiment of the present application further provides a first implementation manner of the second aspect:
the page login authentication device further comprises:
the second acquisition module is used for acquiring the login identification of the tourist from the server through the routing module if the operation environment corresponding to the target page is a second operation environment;
and the storage module is used for storing the visitor login identification through the routing module.
Based on the second aspect, the embodiment of the present application further provides a second implementation manner of the second aspect:
the first obtaining module is further configured to obtain, by using the routing module, an operating environment corresponding to the target page if the routing module does not obtain the user login identifier corresponding to the page access request.
Based on the second aspect, the embodiment of the present application further provides a third implementation manner of the second aspect:
the first obtaining module is further configured to detect a state of a user login identifier if the user login identifier corresponding to the page access request is obtained through the routing module;
and if the user login identification is in an invalid state, acquiring an operation environment corresponding to the target page through the routing module.
Based on the second aspect, or any one of the first implementation manner of the second aspect to the third implementation manner of the second aspect, the present embodiment further provides a fourth implementation manner of the second aspect:
the processing module is also used for storing the user login identification carried by the callback link through the routing module.
A third aspect of an embodiment of the present application provides a client, including: memory, transceiver, processor, and bus system;
wherein the memory is used for storing programs;
the processor is used for executing the program in the memory, and comprises the following steps:
receiving a page access request through a routing module, wherein the page access request is used for requesting a login target page;
acquiring an operation environment corresponding to the target page according to the page access request through the routing module;
if the operation environment corresponding to the target page is a first operation environment, sending a target application login link to a client through the routing module so that the client accesses a target application program according to the target application login link, wherein the target application program has a corresponding relation with the first operation environment;
receiving a callback link sent by the client through the routing module;
authenticating the client through the routing module according to the callback link;
the bus system is used for connecting the memory and the processor so as to enable the memory and the processor to communicate.
A fourth aspect of the embodiments of the application provides a computer readable storage medium comprising instructions which, when run on a computer, cause the computer to perform the method according to the first aspect.
A fifth aspect of an embodiment of the application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method as described in the first aspect.
From the above technical solutions, the embodiment of the present application has the following advantages:
the embodiment of the application provides a page login authentication method and a related device, wherein the method is executed by a routing module additionally added to a Vue framework, when the routing module judges that a target page which a user needs to browse is not logged in by the user, and judges that the target page runs in a first running environment, the target application is accessed in a login link mode, so that the user jumps to the target application to log in, and then jumps to the target page to successfully access, and because the page login authentication steps are executed in the routing module, service codes in a life cycle hook function are executed, the page login authentication steps can be pre-arranged, and when a developer develops different pages, only the login authentication codes are required to be uniformly set in the routing module, so that the login authentication codes are decoupled from the service codes, the workload of the developer is reduced, and the development efficiency is improved.
Drawings
FIG. 1 is a flow chart of a method for page login authentication according to an embodiment of the present application;
FIG. 2 is an application illustration of a page login authentication method according to an embodiment of the present application;
FIG. 3 is a schematic diagram of a page login authentication device according to an embodiment of the present application;
fig. 4 is a block diagram of a part of a structure of a mobile phone related to a client provided in an embodiment of the present application.
Detailed Description
The embodiment of the application provides a page login authentication method and a related device, which can reduce the workload of developers and improve the development efficiency.
The terms "first," "second," "third," "fourth" and the like in the description and in the claims and in the above drawings, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the application described herein may be implemented, for example, in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "includes" and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed or inherent to such process, method, article, or apparatus.
It should be understood that the present application is applied to a network login scenario, and in particular, network login generally refers to a login authentication scenario performed when a user browses a page through a browser on a client.
In the prior art, a browser generally performs page construction based on a front end framework (Vue), each Vue instance for constructing a page is subjected to an initialization process when being created, in this process, a hook function of some lifecycle is usually operated, and a developer can add codes to the function to set required functions, such as login authentication codes and service rendering codes, so that the browser can render the page for the user after performing login authentication on the user.
Because the login authentication is performed in a hook function of a life cycle in the prior art, the login authentication code and the service code are mutually coupled, and when developing different pages, a developer needs to independently set a set of login authentication code on each page, so that the workload of the developer is large and the development efficiency is low.
In order to facilitate understanding, the present application proposes a method for authenticating page login, which is applied to client execution, and the client may include, but is not limited to, a terminal device such as a smart phone, a personal computer, a palm computer, a television set-top box, etc., for outputting an application graphical interface, and sending an operation instruction input by a user through an input device such as a mouse, a keyboard, etc., to a server through a network. It should be understood that, in the embodiment of the present application, a browser is installed on the client, and the browser may be started under different operating environments, such as a WeChat environment and a non-WeChat environment, which are hereinafter referred to as a first operating environment and a second operating environment for convenience of explanation.
The browser usually builds the page based on the Vue, the Vue in the embodiment of the present application includes a routing module, and the routing module executes the page login authentication method in the embodiment of the present application.
The method for page login authentication in the embodiment of the present application is described below from the perspective of the client, and it should be noted that the method for page login authentication in the embodiment of the present application is applied to a front end frame Vue, where Vue includes a routing module. Fig. 1 is a schematic flow chart of a method for page login authentication in an embodiment of the present application, please refer to fig. 1, and an embodiment of a method for page login authentication in an embodiment of the present application includes:
101. receiving a page access request through a routing module, wherein the page access request is used for requesting a login target page;
in this embodiment, when a user needs to access a target page through a browser on a client, a page access request may be input to the client, and after a routing module (for convenience of explanation, the routing module is used to describe the description below) of the client receives the page access request input by the user, a configuration file corresponding to the page access request may be obtained, and it needs to be described that the configuration file may be preset in the client in advance, and the configuration file includes information about whether the target page needs to be logged in. After the routing module determines that the target page needs to be checked for login according to the information of the configuration file, step 102 may be executed.
102. Acquiring an operation environment corresponding to a target page according to a page access request through a routing module;
after receiving the page access request, the routing module needs to determine the operation environment corresponding to the target page. It should be noted that, because the running environments of the browsers are different, the way in which the routing module performs login authentication on the page is also different, specifically, when the routing module obtains the running environment corresponding to the target page and determines that the running environment is the first running environment, step 103 is executed.
103. If the operation environment corresponding to the target page is the first operation environment, a target application login link is sent to the client through the routing module, so that the client accesses the target application program according to the target application login link, wherein the target application program has a corresponding relation with the first operation environment;
when the routing module determines that the running environment is the first running environment, a corresponding target application login link is acquired and sent to the client, and it should be noted that the routing module and the target application in the embodiment may be disposed in the same client, and the target application has a corresponding relationship with the first running environment.
When the client receives the target application login link, the client jumps to the target application program according to the target application login link. At this time, the login authorization page which is displayed on the client and is the target application program can return a callback link to the routing module after receiving the authorization instruction input by the user.
104. Receiving callback links sent by a client through a routing module;
105. and authenticating the client through the routing module according to the callback link.
And the routing module analyzes the callback link after receiving the callback link returned by the target application program in the client so as to authenticate the client according to the callback link. It can be understood that the authentication processing is completed, that is, the page login authentication of the user is completed, which can be regarded as determining that the user login page is successful, until the login authentication step executed by the routing module of the Vue is finished, the user enters the hook function module corresponding to the service code in the Vue, and the client executes the page rendering step to render the complete target page and display the complete target page on the display interface of the client for the user to use.
In the embodiment, the routing module additionally added to the Vue framework is used for executing, when the routing module judges that the target page required to be browsed by the user is not logged in by the user, and judges that the target page is operated in the first operation environment, the target application is accessed in a login link mode, so that the user jumps to the target application to log in, and then jumps to the target page to successfully access, and as the step of page login authentication is executed in the routing module, the step of page login authentication is executed before the step of executing the business code in the life cycle hook function, and when developing different pages, a developer only needs to uniformly set login authentication codes in the routing module, so that the login authentication codes are decoupled from the business code, the workload of the developer is reduced, and the development efficiency is improved.
Optionally, based on the embodiment corresponding to fig. 1, in an optional embodiment of the method for face login authentication in the embodiment of the present application, after obtaining, by the routing module, the running environment corresponding to the target page according to the page access request, the method further includes:
if the operation environment corresponding to the target page is the second operation environment, obtaining a visitor login identification from a server through a routing module;
and storing the login identification of the tourist through the routing module.
In this embodiment, after the routing module determines that the running environment corresponding to the target page is the second running environment, the routing module may request the guest login interface from the server, and after the request is successful, the guest login identifier may be obtained, and the user successfully logs in the page with the guest identity, where the routing module stores the guest login identifier, so far, the login authentication step executed by the routing module of Vue is ended, the hook function module corresponding to the service code in Vue is entered, and the client performs the page rendering step to render the complete target page and display the complete target page on the display interface with the client for the user.
Optionally, based on each embodiment corresponding to fig. 1, in an optional embodiment of the method for face login authentication in the embodiment of the present application, obtaining, by a routing module, an operating environment corresponding to a target page according to a page access request includes:
and if the user login identification corresponding to the page access request is not obtained through the routing module, obtaining the running environment corresponding to the target page through the routing module.
In this embodiment, before the routing module obtains the operating environment corresponding to the target page, the routing module generally obtains the user login identifier corresponding to the page access request sent by the user from the local storage, if the corresponding user login identifier cannot be obtained, it is determined that the user does not log in the target page, login authentication is required, and then the routing module obtains the operating environment corresponding to the target page to execute subsequent login authentication operation.
Optionally, based on each embodiment corresponding to fig. 1, in an optional embodiment of the method for face login authentication in the embodiment of the present application, obtaining, by a routing module, an operating environment corresponding to a target page according to a page access request includes:
if the user login identification corresponding to the page access request is obtained through the routing module, detecting the state of the user login identification;
and if the user login identification is in an invalid state, acquiring an operating environment corresponding to the target page through the routing module.
In this embodiment, before the routing module obtains the running environment corresponding to the target page, the routing module generally obtains the user login identifier corresponding to the page access request sent by the user from the local storage, and if the corresponding user login identifier is obtained, detects the state of the user login identifier.
If the user login identification is judged to be in an invalid state, if the identification is overdue or damaged, the page login authentication needs to be carried out again even if the user logs in the target page, and the routing module can acquire the running environment corresponding to the target page so as to execute the subsequent login authentication operation.
If the user login identification is judged to be in a valid state, ending login authentication operation and executing page rendering operation.
Optionally, based on each embodiment corresponding to fig. 1, in an optional embodiment of the method for face login authentication in the embodiment of the present application, the authentication processing for the client through the routing module according to the callback link specifically includes:
and storing a user login identifier carried by the callback link through the routing module.
In this embodiment, after receiving the callback link, the routing module parses the callback link, and since the callback link includes the user login identifier, after the parsing operation is completed, the routing module may obtain the user login identifier, and store the user login identifier, so as to complete login authentication processing.
For easy understanding, the page login authentication method in the embodiment of the present application will be further described with an application example, and fig. 2 is a schematic view of an application of the page login authentication method in the embodiment of the present application, and please refer to fig. 2, where the application example includes:
201. the routing module receives a page login request input by a user;
202. the routing module judges whether the page needs login verification;
if so, step 203 is performed, and if not, step 208 is performed.
203. The routing module acquires a user login identification to judge whether a user has logged in a page;
if the user login identifier (token) cannot be acquired, executing step 204, if the user login identifier is acquired, judging whether the identifier is valid, if so, executing step 208, and if not, executing step 204;
204. the routing module detects the running environment of the page;
if the first running environment is the first running environment, step 205 is executed, and if the second running environment is the second running environment, step 207 is executed;
205. the routing module acquires an application login link and jumps to a target application;
206. receiving a callback link returned by the target application, and storing a user login identifier;
after the user authorizes login on the target application, the target application sends a callback link to the routing module.
207. The routing module requests a guest login interface and stores a guest login identifier;
208. rendering the page.
The application example is based on the front-end authentication login of vue routing, the login authentication logic is executed in the navigation guard of the routing module, the login authority of the page is uniformly managed, and the login authority and the service code are completely decoupled, so that the workload of developers is reduced, and the login access and maintenance are facilitated. The developer only needs to concentrate on the development of business, and does not need to care about the internal reality of login logic at all.
The above is a detailed description of the method for authenticating the page login in the embodiment of the present application, and the structure and connection relationship of the page login authentication device in the embodiment of the present application will be described below. Fig. 3 is a schematic structural diagram of a page login authentication device according to an embodiment of the present application, please refer to fig. 3, and an embodiment of a page login authentication device according to an embodiment of the present application includes:
a first receiving module 301, configured to receive a page access request through the routing module, where the page access request is used to request a login target page;
the first obtaining module 302 is configured to obtain, by using the routing module, an operating environment corresponding to the target page according to the page access request;
the sending module 303 is configured to send, if the running environment corresponding to the target page is the first running environment, the target application login link to the client through the routing module, so that the client accesses the target application according to the target application login link, where the target application has a corresponding relationship with the first running environment;
a second receiving module 304, configured to receive, through the routing module, a callback link sent by the client;
and the processing module 305 is used for performing authentication processing on the client according to the callback link through the routing module.
Based on the corresponding embodiment of fig. 3, in an alternative embodiment of the page login authentication device in the embodiment of the present application, the page login authentication device further includes:
the second acquisition module is used for acquiring the login identification of the tourist from the server through the routing module if the operation environment corresponding to the target page is the second operation environment;
and the storage module is used for storing the login identification of the tourist through the routing module.
Based on the embodiments corresponding to fig. 3, in an alternative embodiment of the page login authentication device in the embodiment of the present application, the first obtaining module is further configured to obtain, by using the routing module, an operating environment corresponding to the target page if the user login identifier corresponding to the page access request is not obtained by using the routing module.
Based on the embodiments corresponding to fig. 3, in an alternative embodiment of the page login authentication device in the embodiment of the present application, the first obtaining module is further configured to detect a state of the user login identifier if the user login identifier corresponding to the page access request is obtained through the routing module;
and if the user login identification is in an invalid state, acquiring an operating environment corresponding to the target page through the routing module.
Based on the respective embodiments corresponding to fig. 3, in an alternative embodiment of the page login authentication device in the embodiment of the present application, the processing module is further configured to store, by using the routing module, a user login identifier carried by the callback link.
The embodiment of the application also provides a client which comprises the front-end framework Vue, wherein the Vue comprises a routing module. As shown in fig. 4, for convenience of explanation, only the portions related to the embodiments of the present application are shown, and specific technical details are not disclosed, please refer to the method portions of the embodiments of the present application. The client may be any client device including a mobile phone, a tablet computer, a personal digital assistant (personal digital assistant, PDA), a point of sale (POS), a vehicle-mounted computer, and the like, taking the mobile phone as an example of the client:
fig. 4 is a block diagram showing a part of a structure of a mobile phone related to a client provided in an embodiment of the present application. Referring to fig. 4, the mobile phone includes: radio Frequency (RF) circuitry 410, memory 420, input unit 430, display unit 440, sensor 450, audio circuitry 460, wireless fidelity (wireless fidelity, wiFi) module 470, processor 480, and power supply 490. Those skilled in the art will appreciate that the handset configuration shown in fig. 4 is not limiting of the handset and may include more or fewer components than shown, or may combine certain components, or may be arranged in a different arrangement of components.
The following describes the components of the mobile phone in detail with reference to fig. 4:
the RF circuit 410 may be used for receiving and transmitting signals during the process of receiving and transmitting information or communication, in particular, after receiving downlink information of the base station, the downlink information is processed by the processor 480; in addition, the data of the design uplink is sent to the base station. In general, RF circuitry 410 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier (low noise amplifier, LNA), a duplexer, and the like. In addition, the RF circuitry 410 may also communicate with networks and other devices via wireless communications. The wireless communications may use any communication standard or protocol including, but not limited to, global system for mobile communications (global system of mobile communication, GSM), general packet radio service (general packet radio service, GPRS), code division multiple access (code division multiple access, CDMA), wideband code division multiple access (wideband code division multiple access, WCDMA), long term evolution (long term evolution, LTE), email, short message service (short messaging service, SMS), and the like.
The memory 420 may be used to store software programs and modules, and the processor 480 may perform various functional applications and data processing of the cellular phone by executing the software programs and modules stored in the memory 420. The memory 420 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like; the storage data area may store data (such as audio data, phonebook, etc.) created according to the use of the handset, etc. In addition, memory 420 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device.
The input unit 430 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the handset. In particular, the input unit 430 may include a touch panel 431 and other input devices 432. The touch panel 431, also referred to as a touch screen, may collect touch operations thereon or thereabout by a user (e.g., operations of the user on the touch panel 431 or thereabout using any suitable object or accessory such as a finger, a stylus, etc.), and drive the corresponding connection device according to a predetermined program. Alternatively, the touch panel 431 may include two parts of a touch detection device and a touch controller. The touch detection device detects the touch azimuth of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device and converts it into touch point coordinates, which are then sent to the processor 480, and can receive commands from the processor 480 and execute them. In addition, the touch panel 431 may be implemented in various types such as resistive, capacitive, infrared, and surface acoustic wave. The input unit 430 may include other input devices 432 in addition to the touch panel 431. In particular, other input devices 432 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, mouse, joystick, etc.
The display unit 440 may be used to display information input by a user or information provided to the user as well as various menus of the mobile phone. The display unit 440 may include a display panel 441, and optionally, the display panel 441 may be configured in the form of a liquid crystal display (liquid crystal display, LCD), an organic light-emitting diode (OLED), or the like. Further, the touch panel 431 may cover the display panel 441, and when the touch panel 431 detects a touch operation thereon or nearby, the touch operation is transmitted to the processor 480 to determine the type of the touch event, and then the processor 480 provides a corresponding visual output on the display panel 441 according to the type of the touch event. Although in fig. 4, the touch panel 431 and the display panel 441 are two independent components to implement the input and output functions of the mobile phone, in some embodiments, the touch panel 431 and the display panel 441 may be integrated to implement the input and output functions of the mobile phone.
The handset may also include at least one sensor 450, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor, wherein the ambient light sensor may adjust the brightness of the display panel 441 according to the brightness of ambient light, and the proximity sensor may turn off the display panel 441 and/or the backlight when the mobile phone moves to the ear. As one of the motion sensors, the accelerometer sensor can detect the acceleration in all directions (generally three axes), and can detect the gravity and direction when stationary, and can be used for applications of recognizing the gesture of a mobile phone (such as horizontal and vertical screen switching, related games, magnetometer gesture calibration), vibration recognition related functions (such as pedometer and knocking), and the like; other sensors such as gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc. that may also be configured with the handset are not described in detail herein.
Audio circuitry 460, a speaker 461, a microphone 462 can provide an audio interface between the user and the handset. The audio circuit 460 may transmit the received electrical signal after the audio data conversion to the speaker 461, and the electrical signal is converted into a sound signal by the speaker 461 and output; on the other hand, the microphone 462 converts the collected sound signals into electrical signals, which are received by the audio circuit 460 and converted into audio data, which are processed by the audio data output processor 480 and sent to, for example, another cell phone via the RF circuit 410, or which are output to the memory 420 for further processing.
WiFi belongs to a short-distance wireless transmission technology, and a mobile phone can help a user to send and receive e-mails, browse web pages, access streaming media and the like through a WiFi module 470, so that wireless broadband Internet access is provided for the user. Although fig. 4 shows a WiFi module 470, it is understood that it does not belong to the necessary constitution of the mobile phone, and can be omitted entirely as required within the scope of not changing the essence of the application.
The processor 480 is a control center of the mobile phone, connects various parts of the entire mobile phone using various interfaces and lines, and performs various functions and processes data of the mobile phone by running or executing software programs and/or modules stored in the memory 420 and invoking data stored in the memory 420, thereby performing overall monitoring of the mobile phone. Optionally, the processor 480 may include one or more processing units; alternatively, the processor 480 may integrate an application processor that primarily handles operating systems, user interfaces, applications, etc., with a modem processor that primarily handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 480.
The handset further includes a power supply 490 (e.g., a battery) for powering the various components, optionally in logical communication with the processor 480 through a power management system that performs functions such as managing charge, discharge, and power consumption.
Although not shown, the mobile phone may further include a camera, a bluetooth module, etc., which will not be described herein.
In an embodiment of the present application, the processor 480 included in the client further has the following functions:
receiving a page access request through a routing module, wherein the page access request is used for requesting a login target page;
acquiring an operation environment corresponding to a target page according to a page access request through a routing module;
if the operation environment corresponding to the target page is the first operation environment, a target application login link is sent to the client through the routing module, so that the client accesses the target application program according to the target application login link, wherein the target application program has a corresponding relation with the first operation environment;
receiving callback links sent by a client through a routing module;
authentication processing is carried out on the client through the routing module according to the callback link;
the bus system is used to connect the memory and the processor to communicate the memory and the processor.
The embodiment of the application also provides a computer readable storage medium, which comprises instructions, when the computer readable storage medium runs on a computer, the computer is caused to execute the page login authentication method.
A fifth aspect of an embodiment of the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of page login authentication described above.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, which are not repeated herein.
In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in part or all of the technical solution or in part in the form of a software product stored in a storage medium, including instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a read-only memory (ROM), a random access memory (random access memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application.
Claims (10)
1. A method of page login authentication, the method being applied to a front end framework Vue, the Vue comprising a routing module, the method comprising:
receiving a page access request through a routing module, wherein the page access request is used for requesting a login target page;
acquiring an operation environment corresponding to the target page according to the page access request through the routing module;
if the operation environment corresponding to the target page is a first operation environment, sending a target application login link to a client through the routing module so that the client accesses a target application program according to the target application login link, wherein the target application program has a corresponding relation with the first operation environment;
receiving a callback link sent by the client through the routing module;
and authenticating the client through the routing module according to the callback link.
2. The method for authenticating page login according to claim 1, wherein after the routing module obtains the running environment corresponding to the target page according to the page access request, the method further comprises:
if the operation environment corresponding to the target page is a second operation environment, obtaining a visitor login identification from a server through the routing module;
and storing the login identification of the tourist through the routing module.
3. The method for authenticating page login according to claim 1, wherein the obtaining, by the routing module, the operating environment corresponding to the target page according to the page access request includes:
and if the user login identification corresponding to the page access request is not acquired through the routing module, acquiring the running environment corresponding to the target page through the routing module.
4. The method for authenticating page login according to claim 1, wherein the obtaining, by the routing module, the operating environment corresponding to the target page according to the page access request includes:
if the user login identification corresponding to the page access request is obtained through the routing module, detecting the state of the user login identification;
and if the user login identification is in an invalid state, acquiring an operation environment corresponding to the target page through the routing module.
5. A method for authenticating a page login according to any one of claims 1 to 3, wherein the authenticating the client by the routing module according to the callback link specifically comprises:
and storing a user login identifier carried by the callback link through the routing module.
6. A page login authentication device, wherein the page login authentication device comprises a front end frame Vue, the Vue comprises a routing module, and the page login authentication device comprises:
the first receiving module is used for receiving a page access request through the routing module, wherein the page access request is used for requesting a login target page;
the first acquisition module is used for acquiring an operation environment corresponding to the target page according to the page access request through the routing module;
the sending module is used for sending a target application login link to the client through the routing module if the running environment corresponding to the target page is a first running environment, so that the client accesses a target application program according to the target application login link, wherein the target application program has a corresponding relation with the first running environment;
the second receiving module is used for receiving the callback link sent by the client through the routing module;
and the processing module is used for carrying out authentication processing on the client through the routing module according to the callback link.
7. The page log authentication device of claim 6, wherein the page log authentication device further comprises:
the second acquisition module is used for acquiring the login identification of the tourist from the server through the routing module if the operation environment corresponding to the target page is a second operation environment;
and the storage module is used for storing the visitor login identification through the routing module.
8. A client, comprising: memory, transceiver, processor, and bus system;
wherein the memory is used for storing programs;
the processor is used for executing the program in the memory, and comprises the following steps:
receiving a page access request through a routing module, wherein the page access request is used for requesting a login target page;
acquiring an operation environment corresponding to the target page according to the page access request through the routing module;
if the operation environment corresponding to the target page is a first operation environment, sending a target application login link to a client through the routing module so that the client accesses a target application program according to the target application login link, wherein the target application program has a corresponding relation with the first operation environment;
receiving a callback link sent by the client through the routing module;
authenticating the client through the routing module according to the callback link;
the bus system is used for connecting the memory and the processor so as to enable the memory and the processor to communicate.
9. A computer readable storage medium comprising instructions which, when run on a computer, cause the computer to perform the method of any one of claims 1 to 5.
10. A computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of any of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910643352.1A CN111177612B (en) | 2019-07-16 | 2019-07-16 | Page login authentication method and related device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910643352.1A CN111177612B (en) | 2019-07-16 | 2019-07-16 | Page login authentication method and related device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111177612A CN111177612A (en) | 2020-05-19 |
| CN111177612B true CN111177612B (en) | 2023-09-19 |
Family
ID=70655312
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910643352.1A Active CN111177612B (en) | 2019-07-16 | 2019-07-16 | Page login authentication method and related device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111177612B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112187748B (en) * | 2020-09-15 | 2022-11-25 | 中信银行股份有限公司 | Cross-network access control management method and device and electronic equipment |
| CN113472752B (en) * | 2021-06-11 | 2023-12-01 | 北京达佳互联信息技术有限公司 | Authority processing method and device, electronic equipment and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104580074A (en) * | 2013-10-14 | 2015-04-29 | 阿里巴巴集团控股有限公司 | Logging method of client end application and corresponding server of logging method |
| CN105610810A (en) * | 2015-12-23 | 2016-05-25 | 北京奇虎科技有限公司 | Data processing method, client and servers |
| CN105791324A (en) * | 2016-05-12 | 2016-07-20 | 腾讯科技（深圳）有限公司 | Account login method and device |
| CN109669597A (en) * | 2018-10-31 | 2019-04-23 | 武汉艺果互动科技股份有限公司 | Front end authority control method, equipment and storage equipment when user browses web sites |
| CN109784033A (en) * | 2018-12-13 | 2019-05-21 | 平安科技（深圳）有限公司 | Operating right Dynamic Configuration and relevant device based on page menus |
| CN109962908A (en) * | 2019-01-22 | 2019-07-02 | 深圳壹账通智能科技有限公司 | Right management method, device, equipment and storage medium based on token |
-
2019
- 2019-07-16 CN CN201910643352.1A patent/CN111177612B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104580074A (en) * | 2013-10-14 | 2015-04-29 | 阿里巴巴集团控股有限公司 | Logging method of client end application and corresponding server of logging method |
| CN105610810A (en) * | 2015-12-23 | 2016-05-25 | 北京奇虎科技有限公司 | Data processing method, client and servers |
| CN105791324A (en) * | 2016-05-12 | 2016-07-20 | 腾讯科技（深圳）有限公司 | Account login method and device |
| CN109669597A (en) * | 2018-10-31 | 2019-04-23 | 武汉艺果互动科技股份有限公司 | Front end authority control method, equipment and storage equipment when user browses web sites |
| CN109784033A (en) * | 2018-12-13 | 2019-05-21 | 平安科技（深圳）有限公司 | Operating right Dynamic Configuration and relevant device based on page menus |
| CN109962908A (en) * | 2019-01-22 | 2019-07-02 | 深圳壹账通智能科技有限公司 | Right management method, device, equipment and storage medium based on token |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111177612A (en) | 2020-05-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9843616B2 (en) | Method, apparatus and system for sharing webpage | |
| CN107040609B (en) | Network request processing method and device | |
| CN105471931B (en) | Method, device and system for inquiring service data | |
| CN108156508B (en) | Barrage information processing method and device, mobile terminal, server and system | |
| CN105824958A (en) | Method, device and system for inquiring log | |
| CN109905380B (en) | Node control method and related device in distributed system | |
| CN108834132B (en) | Data transmission method and equipment and related medium product | |
| CN107766358B (en) | Page sharing method and related device | |
| CN104298666A (en) | Web page sharing method and web page sharing device | |
| CN103177217B (en) | A kind of file scanning method, system and client and server | |
| CN105530239A (en) | Multimedia data obtaining method and device | |
| CN111177612B (en) | Page login authentication method and related device | |
| CN112749074B (en) | Test case recommending method and device | |
| CN105530222A (en) | Method for establishing connection among terminals, and device and system | |
| CN108270764B (en) | Application login method, server and mobile terminal | |
| CN111273955A (en) | Thermal restoration plug-in optimization method and device, storage medium and electronic equipment | |
| CN110445746B (en) | Cookie obtaining method and device and storage equipment | |
| CN104391629A (en) | Method for sending message in orientation manner, method for displaying message, server and terminal | |
| CN106339402B (en) | Method, device and system for pushing recommended content | |
| CN106709330B (en) | Method and device for recording file execution behaviors | |
| CN110855807A (en) | Method and equipment for adding contact person | |
| CN104601731A (en) | Data push method and device | |
| CN104702643A (en) | A webpage access method, device and system | |
| CN104918130A (en) | Methods for transmitting and playing multimedia information, devices and system | |
| CN105578467A (en) | System, method and device for accessing to wireless access point |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |