CN111435382A - Login verification method of page and terminal - Google Patents
Login verification method of page and terminal Download PDFInfo
- Publication number
- CN111435382A CN111435382A CN201910031227.5A CN201910031227A CN111435382A CN 111435382 A CN111435382 A CN 111435382A CN 201910031227 A CN201910031227 A CN 201910031227A CN 111435382 A CN111435382 A CN 111435382A
- Authority
- CN
- China
- Prior art keywords
- login
- page
- target page
- event message
- target
- 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.)
- Granted
Links
Images
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
The invention provides a page login verification method and a terminal, which are characterized in that a page login attribute of a target page is obtained by receiving a request of jumping to the target page, whether login is needed or not is judged according to the page login attribute of the target page, if the login is needed, the login state of a user is continuously judged, if the login state is not needed, a login request is packaged into an event message, and the event message is sent to a login component; the login mechanism can be automatically triggered when a user accesses certain pages, the user can normally access other pages without login, the method is more humanized, the user viscosity is increased, and the user experience is improved.
Description
Technical Field
The invention relates to the field of network operation and management, in particular to a login verification method and a terminal for a page.
Background
With the development of the information age, mobile applications enable lives of people to be more and more convenient, and when pages of the mobile applications are browsed, all pages of some mobile applications can be browsed randomly under the condition of a tourist mode, so that users of the mobile applications are low in stickiness, and users who register and log in are few; still other mobile applications require the user to log in upon entering the application home page, which may initially be annoying to the user, possibly causing the user to forgo using the mobile application.
Disclosure of Invention
The technical problem to be solved by the invention is as follows: the page login verification method and the terminal can realize that a user can automatically trigger a login mechanism when accessing certain pages, and improve user experience.
In order to solve the technical problems, the invention adopts a technical scheme that:
a login verification method for a page comprises the following steps:
s1, receiving a request for jumping to a target page, acquiring a page login attribute of the target page, judging whether login is needed according to the page login attribute of the target page, and if so, executing S2;
s2, judging whether the current login state is logged in;
if not, the login request is encapsulated into the event message, and the event message is sent to the login component.
In order to solve the technical problem, the invention adopts another technical scheme as follows:
a login verification terminal for a page comprises a memory, a processor and a computer program which is stored on the memory and can run on the processor, wherein the processor executes the computer program to realize the following steps:
s1, receiving a request for jumping to a target page, acquiring a page login attribute of the target page, judging whether login is needed according to the page login attribute of the target page, and if so, executing S2;
s2, judging whether the current login state is logged in;
if not, the login request is encapsulated into the event message, and the event message is sent to the login component.
The invention has the beneficial effects that: acquiring a page login attribute of a target page by receiving a request for jumping to the target page, judging whether login is needed according to the page login attribute of the target page, if so, continuing to judge the login state of a user, if not, packaging a login request into an event message, and sending the event message to a login component; the login mechanism can be automatically triggered when a user accesses certain pages, the user can normally access other pages without login, the method is more humanized, the user viscosity is increased, and the user experience is improved.
Drawings
FIG. 1 is a flowchart of a login verification method for a page according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of a login verification structure of a page according to an embodiment of the present invention;
FIG. 3 is a flowchart of component interaction of a login verification method of a page according to an embodiment of the present invention;
fig. 4 is a flowchart illustrating component interaction of an Android system of a login verification method for a page according to an embodiment of the present invention;
FIG. 5 is a flowchart of the IOS system component interaction of the login verification method of a page according to an embodiment of the present invention;
FIG. 6 is a flowchart illustrating whether a boot page is configured in the page login verification method according to an embodiment of the present invention;
FIG. 7 is a flowchart of a first open container home page of a login verification method for a page according to an embodiment of the present invention;
FIG. 8 is a flowchart of a method for checking page login according to an embodiment of the present invention;
description of reference numerals:
1. a login verification terminal of a page; 2. a memory; 3. a processor.
Detailed Description
In order to explain technical contents, achieved objects, and effects of the present invention in detail, the following description is made with reference to the accompanying drawings in combination with the embodiments.
The most key concept of the invention is as follows: when a user accesses certain pages, a login mechanism is automatically triggered, and user experience is improved.
Referring to fig. 1, a method for checking login of a page includes the steps of:
s1, receiving a request for jumping to a target page, acquiring a page login attribute of the target page, judging whether login is needed according to the page login attribute of the target page, and if so, executing S2;
s2, judging whether the current login state is logged in;
if not, the login request is encapsulated into the event message, and the event message is sent to the login component.
From the above description, the beneficial effects of the present invention are: acquiring a page login attribute of a target page by receiving a request for jumping to the target page, judging whether login is needed according to the page login attribute of the target page, if so, continuing to judge the login state of a user, if not, packaging a login request into an event message, and sending the event message to a login component; the login mechanism can be automatically triggered when a user accesses certain pages, the user can normally access other pages without login, the method is more humanized, the user viscosity is increased, and the user experience is improved.
Further, the step S2 further includes: and if so, directly jumping to the target page.
From the above description, the user can browse any page in the logged-on state without packaging the login request into the event message, thereby accelerating the processing speed of the page.
Further, the method also comprises the following steps: s3, acquiring and displaying a login interface returned by the login component according to the event message, and judging whether login is completed;
if yes, calling a command in the event message, and executing and jumping to the target page according to the command.
As can be seen from the above description, after the user logs in, the user can jump to the target page according to the command in the event message, so as to meet the browsing expectation of the user.
Further, at S3, the method further includes:
judging whether the page is integrated in a Tab container page or not;
if yes, receiving and displaying a false page before jumping to the target page according to the command execution;
the executing the jump to the target page according to the command comprises:
and replacing the false page with a real page.
As can be seen from the above description, the false page is displayed during login verification, which saves resources and memory overhead.
Further, the receiving the request to jump to the target page in S1 includes:
acquiring the type of an operating system currently used;
and if the type of the currently used operating system is the IOS operating system, creating an instance of the target page.
From the above description, when the type of the operating system used is the IOS operating system, an instance of the target page can be created after receiving the request to jump to the page, which accelerates the page jump speed of the user after completing login and improves the fluency of page jump.
Referring to fig. 2, a login verification terminal for a page includes a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor executes the computer program to implement the following steps:
s1, receiving a request for jumping to a target page, acquiring a page login attribute of the target page, judging whether login is needed according to the page login attribute of the target page, and if so, executing S2;
s2, judging whether the current login state is logged in;
if not, the login request is encapsulated into the event message, and the event message is sent to the login component.
From the above description, the beneficial effects of the present invention are: acquiring a page login attribute of a target page by receiving a request for jumping to the target page, judging whether login is needed according to the page login attribute of the target page, if so, continuing to judge the login state of a user, if not, packaging a login request into an event message, and sending the event message to a login component; the login mechanism can be automatically triggered when a user accesses certain pages, the user can normally access other pages without login, the method is more humanized, the user viscosity is increased, and the user experience is improved.
Further, the step S2 further includes: and if so, directly jumping to the target page.
From the above description, the user can browse any page in the logged-on state without packaging the login request into the event message, thereby accelerating the processing speed of the page.
Further, the method also comprises the following steps: s3, acquiring and displaying a login interface returned by the login component according to the event message, and judging whether login is completed;
if yes, calling a command in the event message, and executing and jumping to the target page according to the command.
As can be seen from the above description, after the user logs in, the user can jump to the target page according to the command in the event message, so as to meet the browsing expectation of the user.
Further, at S3, the method further includes:
judging whether the page is integrated in a Tab container page or not;
if yes, receiving and displaying a false page before jumping to the target page according to the command execution;
the executing the jump to the target page according to the command comprises:
and replacing the false page with a real page.
As can be seen from the above description, the false page is displayed during login verification, which saves resources and memory overhead.
Further, the receiving the request to jump to the target page in S1 includes:
acquiring the type of an operating system currently used;
and if the type of the currently used operating system is the IOS operating system, creating an instance of the target page.
From the above description, when the type of the operating system used is the IOS operating system, an instance of the target page can be created after receiving the request to jump to the page, which accelerates the page jump speed of the user after completing login and improves the fluency of page jump.
Example one
Referring to fig. 1 and fig. 3 to 8, a method for checking login of a page includes the steps of:
s1, receiving a request for jumping to a target page, and acquiring the type of the currently used operating system;
as shown in fig. 5, if the currently used operating system type is an IOS operating system, an instance of the target page is already created when the request is received (i.e., when the getPage is parsed for the target page), as shown in fig. 4, if the currently used operating system type is an Android operating system, only relevant information of one target page is returned when the getPage is, an instance of the target page is not created immediately, but an instance of the target page is actually created when the target page is switched;
acquiring the page login attribute of the target page, judging whether login is needed according to the page login attribute of the target page, and if so, executing S2;
the developer can analyze the definition of each component when the service component configures whether the page needs to be logged in, namely, the page login attribute "allow _ guest" of the configured page is defaulted as "false" which is not needed to be logged in, and the server "jenkins" can analyze the definition of each component when constructing the application of an application factory (the server can be determined according to the actual situation, and is selected as the "jenkins" server here), and if the page attribute definition of the component contains the attribute in the "output attribute list", the content is output; the output attribute list is stored in a content service, and the content service is used for storing attributes of each component in the application, such as names, types, events, pages and other attributes;
the above scheme is applied to specific application scenarios, for example:
accessing a list of output attributes stored on the content service, such as accessing: http:// app-native-storage. web. sdp.101.com/v0.8/define/1f5474c0-df26-4aa7-9ee3-541a2e9f915 a;
traversing all nodes in the data/namespace: bizName/pages, namely traversing the page configuration attribute of the service component, and when the page login attribute exists in a node, outputting the content configured with the page login attribute to app/assets/app _ factor/app/page _ attributes.
S2, judging whether the current login state is logged in;
if not, packaging the login request into an event message, and sending the event message to a login component;
if yes, directly jumping to the target page;
as shown in fig. 3, the application framework performs the check judgment when a page jump (goPage, getPage, goPageForResult) is triggered, wherein an application factory judges the login authority of a target page and the login state of a current user, encapsulates relevant information into an event message and sends the event message to a login component, and the login component performs further check on the user after receiving the event message in order to improve security and consider information sensitivity;
the login component is a component packaged and provided by an application factory of the shared platform and used for managing user login, login and user account information and the like;
s3, acquiring and displaying a login interface returned by the login component according to the event message, and judging whether login is completed;
if yes, calling a command in the event message, and executing and skipping to the target page according to the command;
wherein the S3 further includes:
judging whether the page is integrated in a Tab container page or not;
if yes, receiving and displaying a false page before jumping to the target page according to the command execution;
the executing the jump to the target page according to the command comprises:
replacing the false page with a real page;
the false page is a Tab container page which is not loaded with actual content and is used for saving resources and memory expenditure, the login page is covered on the top layer at the moment, and the execution command is to replace the false page with a real page;
as shown in fig. 6, when the login component processes the event message, it may be determined whether a guide page before login is configured, and if so, the guide page is displayed before the login page is displayed; the guiding page is configured before the application is constructed, simple explanation and guidance can be made on user login before a login interface, and a login component can jump to a target page after login is successful according to an event message, on the premise that related information of the jump to the target page is packaged in the event message, or according to actual requirements, the event message of the previous page is returned without jumping to the target page after login is successful is packaged in the event message, and the previous page is returned after login is successful according to the event message; when the type of the used operating system is the IOS operating system, an instance of the target page can be created after the request of jumping to the page is received, the page jumping speed of the user after the login is finished is increased, and the page jumping fluency is improved.
Under the default condition, a Tab container home page is a type of lower Tab distribution, each Tab can be clicked and jumps to a target page on the Tab container home page, that is, a plurality of pages can be presented on one Tab container home page, as shown in fig. 7, fig. 7 shows whether the Tab container home page triggers a login check process, when the Tab container home page cannot acquire an available page, a jump is made to a login page for forced login, as shown in fig. 8, fig. 8 shows whether the login check process is triggered when one Tab container page in an application jumps to the target page in the non-login state on the basis of fig. 7, and if the login check is triggered and the login is completed, the target page is displayed; and if the login verification is not needed, directly displaying the target page.
Example two
Referring to fig. 2, a login verification terminal 1 for a page includes a memory 2, a processor 3, and a computer program stored in the memory 2 and capable of running on the processor 3, where the processor 3 implements the steps in the first embodiment when executing the computer program.
In summary, according to the page login verification method and the terminal provided by the present invention, a request for jumping to a target page is received, a page login attribute of the target page is obtained, whether login is required is determined according to the page login attribute of the target page, if login is required, a login state of a user is continuously determined, and if the login state is not required, a login request is encapsulated into an event message, and the event message is sent to a login component; the login mechanism can be automatically triggered when a user accesses certain pages, and the user can normally access other pages without login, so that the method is more humanized, the user viscosity is increased, and the user experience is improved; and a false page is displayed during login verification, so that the resource and memory overhead is saved.
The above description is only an embodiment of the present invention, and not intended to limit the scope of the present invention, and all equivalent changes made by using the contents of the present specification and the drawings, or applied directly or indirectly to the related technical fields, are included in the scope of the present invention.
Claims (10)
1. A login verification method for a page is characterized by comprising the following steps:
s1, receiving a request for jumping to a target page, acquiring a page login attribute of the target page, judging whether login is needed according to the page login attribute of the target page, and if so, executing S2;
s2, judging whether the current login state is logged in;
if not, the login request is encapsulated into the event message, and the event message is sent to the login component.
2. The method for checking login of a page according to claim 1, wherein said step S2 further comprises:
and if so, directly jumping to the target page.
3. The method for checking page login according to claim 1, further comprising:
s3, acquiring and displaying a login interface returned by the login component according to the event message, and judging whether login is completed;
if yes, calling a command in the event message, and executing and jumping to the target page according to the command.
4. The method for verifying login of a page according to claim 3, wherein said step of S3 further comprises:
judging whether the page is integrated in a Tab container page or not;
if yes, receiving and displaying a false page before jumping to the target page according to the command execution;
the executing the jump to the target page according to the command comprises:
and replacing the false page with a real page.
5. The method for checking login of page as claimed in claim 1, wherein said receiving a request to jump to a target page in said S1 comprises:
acquiring the type of an operating system currently used;
and if the type of the currently used operating system is the IOS operating system, creating an instance of the target page.
6. A login verification terminal for a page, comprising a memory, a processor and a computer program stored on the memory and operable on the processor, wherein the processor implements the following steps when executing the computer program:
s1, receiving a request for jumping to a target page, acquiring a page login attribute of the target page, judging whether login is needed according to the page login attribute of the target page, and if so, executing S2;
s2, judging whether the current login state is logged in;
if not, the login request is encapsulated into the event message, and the event message is sent to the login component.
7. The login verification terminal for pages of claim 6, wherein said step S2 further comprises:
and if so, directly jumping to the target page.
8. The login verification terminal for a page of claim 6, further comprising:
s3, acquiring and displaying a login interface returned by the login component according to the event message, and judging whether login is completed;
if yes, calling a command in the event message, and executing and jumping to the target page according to the command.
9. The login verification terminal for pages of claim 8, further comprising at said S3:
judging whether the page is integrated in a Tab container page or not;
if yes, receiving and displaying a false page before jumping to the target page according to the command execution;
the executing the jump to the target page according to the command comprises:
and replacing the false page with a real page.
10. The login verification terminal for pages of claim 6, wherein after said receiving the request to jump to the target page in said S1, comprises:
acquiring the type of an operating system currently used;
and if the type of the currently used operating system is the IOS operating system, creating an instance of the target page.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910031227.5A CN111435382B (en) | 2019-01-14 | 2019-01-14 | Login checking method of page and terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910031227.5A CN111435382B (en) | 2019-01-14 | 2019-01-14 | Login checking method of page and terminal |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111435382A true CN111435382A (en) | 2020-07-21 |
| CN111435382B CN111435382B (en) | 2022-10-18 |
Family
ID=71579851
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910031227.5A Active CN111435382B (en) | 2019-01-14 | 2019-01-14 | Login checking method of page and terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111435382B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112069476A (en) * | 2020-09-16 | 2020-12-11 | 杭州安恒信息技术股份有限公司 | Login state detection method, device, equipment and readable storage medium |
| CN112333184A (en) * | 2020-10-30 | 2021-02-05 | 广东科徕尼智能科技有限公司 | Method, terminal and storage device for limiting user to directly access main page |
| CN113343153A (en) * | 2021-06-25 | 2021-09-03 | 山石网科通信技术股份有限公司 | Webpage login method and device, storage medium and processor |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102591889A (en) * | 2011-01-17 | 2012-07-18 | 腾讯科技（深圳）有限公司 | Method and device for assisting user input based on browser of mobile terminal |
| US20160173481A1 (en) * | 2014-12-10 | 2016-06-16 | Infovine Co., Ltd. | Convenient Login Method, Apparatus and System for Automatically Detecting and Filling in Login Field within Web Environment or Application |
| CN107040543A (en) * | 2017-04-26 | 2017-08-11 | 努比亚技术有限公司 | Single-point logging method, terminal and storage medium |
-
2019
- 2019-01-14 CN CN201910031227.5A patent/CN111435382B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102591889A (en) * | 2011-01-17 | 2012-07-18 | 腾讯科技（深圳）有限公司 | Method and device for assisting user input based on browser of mobile terminal |
| US20160173481A1 (en) * | 2014-12-10 | 2016-06-16 | Infovine Co., Ltd. | Convenient Login Method, Apparatus and System for Automatically Detecting and Filling in Login Field within Web Environment or Application |
| CN107040543A (en) * | 2017-04-26 | 2017-08-11 | 努比亚技术有限公司 | Single-point logging method, terminal and storage medium |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112069476A (en) * | 2020-09-16 | 2020-12-11 | 杭州安恒信息技术股份有限公司 | Login state detection method, device, equipment and readable storage medium |
| CN112069476B (en) * | 2020-09-16 | 2022-07-12 | 杭州安恒信息技术股份有限公司 | Login state detection method, device, equipment and readable storage medium |
| CN112333184A (en) * | 2020-10-30 | 2021-02-05 | 广东科徕尼智能科技有限公司 | Method, terminal and storage device for limiting user to directly access main page |
| CN113343153A (en) * | 2021-06-25 | 2021-09-03 | 山石网科通信技术股份有限公司 | Webpage login method and device, storage medium and processor |
| CN113343153B (en) * | 2021-06-25 | 2022-09-09 | 山石网科通信技术股份有限公司 | Webpage login method and device, storage medium and processor |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111435382B (en) | 2022-10-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110363026B (en) | File operation method, device, equipment, system and computer readable storage medium | |
| US8423651B1 (en) | Cross-domain communications with a shared worker application | |
| US8060932B2 (en) | Modular enterprise authorization solution | |
| US10303748B2 (en) | Method and device for providing webpage browsing based on web browser engine kernel | |
| CN102347941B (en) | A kind of safety applications control method based on open platform | |
| CN111435382B (en) | Login checking method of page and terminal | |
| US20230036980A1 (en) | Micro-frontend system, sub-application loading method, electronic device, computer program product, and computer-readable storage medium | |
| US9020973B2 (en) | User interface model driven data access control | |
| US20150089474A1 (en) | Runtime generation and injection of java annotations | |
| CN111143207B (en) | Method for checking model training notice and training log at mobile terminal | |
| US10831892B2 (en) | Web browser script monitoring | |
| CN110188296B (en) | Application program embedded page processing method, browser, equipment and storage medium | |
| KR20220167388A (en) | Data processing methods, apparatus, computer devices, and storage media | |
| CN110213105A (en) | It is a kind of cross-platform micro- using creation method | |
| CN108319474B (en) | Page information generation method, device and equipment | |
| US7630988B2 (en) | Computer product and session management method | |
| CN113849199A (en) | Method and device for cross-system installation of application, electronic equipment and storage medium | |
| CN108509228B (en) | Page loading method, terminal equipment and computer readable storage medium | |
| CN111563215B (en) | Method and device for controlling front-end operation authority and related equipment | |
| WO2021093672A1 (en) | Method for embedding external system, workflow system, device and computer readable storage medium | |
| CN112836186A (en) | Page control method and device | |
| CN112287349A (en) | Security vulnerability detection method and server | |
| CN113626001A (en) | API dynamic editing method and device based on script | |
| CN114741628A (en) | Webpage loading method and related device | |
| CN108881344B (en) | Service processing method and device, storage equipment and processing server |
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 |