Login method, electronic device, readable storage medium and program product

Abstract

The invention relates to the technical field of computers, in particular to a login method, electronic equipment, a readable storage medium and a program product, in the method, a client displays a login page, when a user performs degradation login on a login object, a login server classifies the login object for user login in advance, and the login page is displayed on the client; the present invention classifies a login object having a high security requirement as a login object for which degradation login is restricted. Therefore, after the login server determines that the user logs in the client side to fail, if the login server determines that the login object belongs to the login object which limits the degradation login, the degradation login is refused, so that the problem that the login object with relatively large loss to the user is maliciously and illegally logged in under the condition that the login security environment is reduced is prevented.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a login method, electronic device, readable storage medium, and program product. Background Art

[0002] Currently, when a user tries to log in to an application system (such as a shopping mall application system, a developer application system) on a client browser or application (Application, APP) Application systems) may encounter login failures. For example, the login server may be unable to log in due to heavy traffic or due to a code design flaw. In some cases, upon determining a login failure, the login server will provide the client with a downgraded login method. For example, the user may be presented with a downgraded login page that replaces the original authentication information, such as the account number, password, and verification code, with a page that only requires a smaller amount of authentication information, such as the account number and verification code. Only after the login server confirms that the client has passed the login authentication can the client successfully access the application system.

[0003] It is understandable that the login security is greatly reduced for the changed login method. At this time, the application system will be easily subject to malicious and illegal logins, causing losses to users. Summary of the Invention

[0004] In order to solve the above problems, the embodiments of the present application provide a login method, electronic device, readable storage medium and program product, which are used to solve the problem of malicious and illegal login of applications that causes great losses to users when login security is reduced.

[0005] In the first aspect, an embodiment of the present application provides a login method, which is applied to a client, and the method includes: displaying a first login page corresponding to a first login object; receiving a first user operation on the first login page, and sending a first login request corresponding to the first login object; displaying a second login page corresponding to a failed login of the first login request, wherein the login security level of the second login page is lower than the login security level of the first login page; receiving a second user operation on the second login page, and sending a second login request corresponding to the first login object; and displaying first login restriction information for the second login request.

[0006] It is understandable that the client can be any electronic device that can display a login page, for example, the computer described below. In addition, when the client displays the first login page corresponding to the first login object; after receiving the first user operation on the first login page and sending the first login request corresponding to the first login object, there may be a login failure at this time, making it impossible for the user to log in through the first login page. At this time, a second login page corresponding to the failed login request will be displayed, wherein the login security level of the second login page is lower than the login security level of the first login page. For example, the second login page can be the downgraded login page described below. At this time, the security of logging in through the downgraded login page is obviously lower than the security of logging in through the original login page. When the user operates on the second login page, the client will receive the second user operation on the second login page, and then send the second login request corresponding to the first login object. If the current login object is a login object that requires restricted login, the client will display the first login restriction information for the second login request to restrict the user's login. It can be understood that when the user logs in to the client again through the downgraded login page, the login to the first login object is displayed. This can restrict login when the first login object belongs to an application or business with a higher security level requirement, thereby avoiding the problem of malicious and illegal login of the login object that may easily cause greater losses to the user when the login security environment is lowered, thereby avoiding greater losses to the user.

[0007] In a possible implementation of the above-mentioned first aspect, the above-mentioned method also includes: corresponding to the first login page including the following multiple authentication information: user account, user account password, then the authentication information included in the second login page is: user account and / or verification code; corresponding to the first login page including the following multiple authentication information: mobile phone number, SMS password, then the authentication information included in the second login page is: mobile phone number and / or verification code; the first login restriction information includes: prompt information for the first login restriction on the first login object, and / or login failure information for the first login restriction on the first login object.

[0008] It is understandable that when the first login page includes the user account and password, and the second login page only includes the user account and / or verification code, logging in through the second login page is significantly less secure than logging in through the first login page. Furthermore, when the first login page includes the mobile phone number and SMS password, and the second login page only includes the mobile phone number and / or verification code, logging in through the second login page is significantly less secure than logging in through the first login page, and it is significantly easier to successfully log in through the second login page. When logging in using a less secure login method, displaying a prompt message and / or a login failure message can effectively alert the user that the login attempt was unsuccessful.

[0009] In a possible implementation of the first aspect above, the first login page displays a first confirmation login control and receives a first user operation on the first login page, including: receiving first authentication information entered by the user from the first login page, and receiving a click operation on the first confirmation login control by the user; and the second login page displays a second confirmation login control and receives a second user operation on the second login page, including: receiving second authentication information entered by the user from the second login page, and receiving a click operation on the second confirmation login control by the user.

[0010] For example, the first authentication information includes a user account and a password for the user account, and the second authentication information includes a user account and / or a verification code. For another example, the first authentication information includes a mobile phone number and a text message password, and the second authentication information includes a mobile phone number and / or a verification code. It is understandable that the client performs login based on receiving the authentication information entered by the user from the login page, such as the account number, account password, verification code, mobile phone number, text message password, and receiving the user's click operation on the confirmation login control. This login method is fast and convenient.

[0011] In a possible implementation of the first aspect above, it also includes: displaying a third login page corresponding to the second login object, wherein the security requirement of the second login object is lower than the security requirement of the first login object; receiving a third user operation on the third login page, and sending a third login request corresponding to the second login object; displaying a fourth login page corresponding to the third login request in which the login failed, wherein the login security level of the fourth login page is lower than the login security level of the third login page; receiving a fourth user operation on the fourth login page, and sending a fourth login request corresponding to the second login object; and displaying the first successful login page for the fourth login request.

[0012] It is understood that when the client displays the third login page corresponding to the second login object, receives the third user operation on the third login page, and sends the third login request corresponding to the second login object, a login failure may occur, preventing the user from logging in through the third login page. In this case, a fourth login page corresponding to the failed third login request will be displayed. The login security level of the fourth login page is lower than that of the third login page. For example, the fourth login page can be a downgraded login page described below. In this case, the security of logging in through the downgraded login page is significantly lower than that of logging in through the original login page. The user performs an operation on the fourth login page, and the client receives the fourth user operation on the fourth login page. Then, the client sends the fourth login request corresponding to the second login object. If the security requirement of the second login object is lower than that of the first login object, the client will display the first successful login page, indicating that the user has successfully logged in. It is understood that when the user logs in through the downgraded login page, if the security requirement of the login object is lower, the login object can be successfully logged in, thereby improving the user's login efficiency and thereby enhancing the user experience.

[0013] In a possible implementation of the first aspect above, the first login object is an application corresponding to the first login restriction, including at least one of the following: social media applications, email applications, shopping applications, online storage applications, medical applications, and financial applications; and the second login object is an application that does not correspond to the first login restriction, including at least one of the following: learning and listening applications, technical blog applications, and game applications.

[0014] Understandably, social media, email, shopping, online storage, medical, and financial applications contain important data. Therefore, access to these applications will be restricted during downgrade login to avoid significant user losses. Furthermore, access to learning and lecture applications, technical blogs, and gaming applications will not be restricted during downgrade login, facilitating user learning and development.

[0015] In a possible implementation of the first aspect above, the first login object and the second login object belong to the same first application, wherein the first login object is a business corresponding to the first login restriction, including: payment business, transaction business, and online supermarket business; the second login object is a business that does not correspond to the first login restriction, including: mini-game business, query business, and online consultation business.

[0016] Understandably, payment services, transaction services, and online supermarket services are data-intensive. Therefore, restrictions on these services are implemented during downgraded login to avoid significant user losses. Furthermore, mini-game services, search services, and online medical consultation services are not restricted during downgraded login, allowing users to study, live, and develop their interests.

[0017] In a possible implementation of the first aspect above, it also includes: receiving a fifth user operation corresponding to a third login object, sending a fifth login request corresponding to the third login object, wherein the user account of the third login object is the same as the user account of the second login object; and displaying the second login restriction information for the fifth login request.

[0018] It is understood that after the second login object successfully logs in, the client receives the fifth user operation corresponding to the third login object and sends a fifth login request corresponding to the third login object, i.e., performing single sign-on for the third login object. For example, the user account of the third login object is the same as the user account of the second login object, and the user no longer needs to enter verification information through the login page to perform the login request. It is understandable that because the second login object logs in through a degraded login page, the login security is relatively low. When performing single sign-on in a less secure login environment, restricting the third login object by displaying the second login restriction information for the fifth login request can prevent malicious and illegal logins to the third login object, thereby preventing user losses.

[0019] In a possible implementation of the first aspect above, the second login restriction information includes: prompt information for performing the second login restriction on the third login object, and / or login failure information for performing the second login restriction on the third login object.

[0020] It is understandable that when logging in with a less secure login method, the user can be effectively reminded that the login failure can be achieved by displaying a prompt message and / or displaying a login failure message.

[0021] In a possible implementation of the first aspect above, it also includes: receiving a sixth user operation corresponding to a fourth login object, sending a sixth login request corresponding to the fourth login object, wherein the user account of the fourth login object is the same as the user account of the second login object; and displaying a second successful login page for the sixth login request.

[0022] It is understood that after the second login object successfully logs in, the client receives a sixth user operation corresponding to the fourth login object and sends a sixth login request corresponding to the fourth login object. The user account of the fourth login object is the same as the user account of the second login object. Therefore, single sign-on can be performed for the fourth login object when the user account of the fourth login object is the same as the user account of the second login object. At this point, the user no longer needs to enter verification information on the login page to send the login request. Furthermore, the client can display the second successful login page for the sixth login request, thereby improving the efficiency of logging in to the fourth login object.

[0023] In a possible implementation of the first aspect above, the third login object is an application corresponding to the second login restriction, including at least one of the following: payment applications, medical applications, social applications, cloud storage applications, and government service applications; the fourth login object is an application that does not correspond to the second login restriction, including at least one of the following: learning and listening applications, technical blog applications, and game applications.

[0024] In a possible implementation of the first aspect above, the third login object and the fourth login object belong to the same second application, wherein the third login object is a business corresponding to the second login restriction, including at least one of the following: payment business, transaction business, online supermarket business; the fourth login object is a business that does not correspond to the second login restriction, including at least one of the following: mini-game business, query business, and online consultation business.

[0025] In a second aspect, an embodiment of the present application provides a login method, which is applied to a server, and the method includes: receiving a first login request corresponding to a first login object, wherein the first login request is obtained based on a first login page; in response to the first login request, sending a second login page content corresponding to the first login request that failed to log in; receiving a second login request corresponding to the first login object, wherein the second login request is obtained based on the second login page content, and the login security level of the second login page is lower than the login security level of the first login page; sending a first login failure message based on the second login request not meeting the first login condition, wherein the first login condition includes: the login object is an object that is not restricted from logging in.

[0026] It is understandable that the above-mentioned server may be the login server described below. The server receives a first login request corresponding to a first login object, determines that there is a login failure, and then sends the content of a second login page corresponding to the first login request for which the login failed. For example, the second login page is a degraded login page described below. The user can then log in on the second login page, causing the server to receive a second login request corresponding to the first login object. The server will judge the first login object in the second login request. If the first login object is an object that requires login restriction, a first login failure message will be sent to restrict login to the first login object, thereby preventing the problem of malicious and illegal login to login objects that cause greater losses to users when the login security environment is reduced, thereby avoiding causing greater losses to users.

[0027] In a possible implementation of the second aspect above, it also includes: receiving a third login request corresponding to the second login object, the security requirement of the second login object is lower than the security requirement of the first login object, wherein the third login request is obtained based on the third login page; in response to the third login request, sending the fourth login page content corresponding to the failed login of the third login request; receiving a fourth login request corresponding to the second login object, wherein the fourth login request is obtained based on the fourth login page content, and the login security level of the fourth login page is lower than the login security level of the third login page; based on the fourth login request satisfying the first login condition, sending a first login success message.

[0028] It is understandable that when the server displays the third login page corresponding to the second login object and receives the third login request for the third login page, a login failure may occur at this time. Then, the server sends the content of the fourth login page corresponding to the failed login request for the third login request, for example, the fourth login page is the downgraded login page described below. The user can then log in on the fourth login page, causing the server to receive the fourth login request corresponding to the second login object. The server will determine the second login object in the fourth login request. If the second login object is an object that is not restricted from login, the server will send the first login success message. When the user logs in through the downgraded login page, the login object can successfully log in if the security requirements for the login object are low, thereby improving the user's login efficiency and thus improving the user experience.

[0029] In a possible implementation of the second aspect above, it also includes: receiving a fifth login request corresponding to a third login object, wherein the user account of the third login object is the same as the user account of the second login object; based on the fifth login request not meeting the second login condition, sending a second login failure message, wherein the second login condition includes: the login object is an object that is not restricted from login.

[0030] As will be appreciated, after the server successfully allows the second login subject to log in, it may receive a fifth login request corresponding to a third login subject, where the user account of the third login subject is the same as the user account of the second login subject, i.e., single sign-on is now being performed. Based on the fifth login request, the server determines whether the third login subject, which is being logged in through single sign-on, is a subject that requires login restrictions. If so, the server restricts the login, thereby improving security.

[0031] In a third aspect, an embodiment of the present application provides an electronic device comprising: a memory for storing instructions, and one or more processors. When the instructions are executed by one or more processors, the processor executes any login method as described in the first aspect and any of the various implementations of the first aspect, or executes any login method as described in the second aspect and any of the various implementations of the second aspect.

[0032] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which instructions are stored, which cause an electronic device to execute a login method such as the first aspect and any one of the various implementations of the first aspect, or to execute a login method such as the second aspect and any one of the various implementations of the second aspect.

[0033] In a fifth aspect, an embodiment of the present application provides a computer program product, which includes: computer program code, which, when the computer program code runs on a computer, enables the computer to execute any login method such as the first aspect and any one of the various implementations of the first aspect, or execute any login method such as the second aspect and any one of the various implementations of the second aspect.

[0034] Among them, the beneficial effects of the third to fifth aspects can refer to the relevant beneficial effects of the first and second aspects, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] Figure 1 According to some embodiments of the present application, a schematic diagram of a login scenario is shown;

[0036] Figure 2A According to some embodiments of the present application, a shopping mall page 001 is shown;

[0037] Figure 2B According to some embodiments of the present application, a login page 002 is shown;

[0038] Figure 2C According to some embodiments of the present application, a downgraded login page 003 is shown;

[0039] Figure 3According to some embodiments of the present application, a login framework 500 is shown;

[0040] Figure 4 According to some embodiments of the present application, an interactive schematic diagram of a login method is shown;

[0041] Figure 5A According to some embodiments of the present application, a login failure page 004 is shown;

[0042] Figure 5B According to some embodiments of the present application, a page 005 after a successful login is shown;

[0043] Figure 5C According to some embodiments of the present application, a login failure page 006 is shown;

[0044] Figure 5D According to some embodiments of the present application, a page 007 after a successful login is shown;

[0045] Figure 6 According to some embodiments of the present application, a schematic diagram of a login method interaction is shown, taking application 1 as a developer alliance application and application 2 as a cloud space application as an example;

[0046] Figure 7A According to some embodiments of the present application, a developer alliance login page 008 is shown;

[0047] Figure 7B According to some embodiments of the present application, a downgraded login page 009 is shown;

[0048] Figure 8 According to some embodiments of the present application, a schematic diagram of a device is shown. DETAILED DESCRIPTION

[0049] The illustrative embodiments of the present application include, but are not limited to, a login method, an electronic device, a readable storage medium, and a program product.

[0050] The following describes the embodiments of the present application in conjunction with the accompanying drawings.

[0051] Figure 1According to some embodiments of the present application, a schematic diagram of a login scenario is shown. In this scenario, multiple application systems belonging to the same cloud vendor can use the same login server for login due to the mutual trust relationship. In addition, each application system can have the same account number, account number, password and other information, so that single sign-on (SSO) can be performed between multiple application systems. That is, in multiple application systems, the user only needs to log in once, and then, based on the authentication information of the application system that has been successfully logged in, when logging in to other application systems, no login authentication is required.

[0052] like Figure 1 As shown, user K can log in to application system Y1 and application system Y2 belonging to the same cloud vendor on the browser of computer 100, and application system Y1 corresponds to application server 300, and application system Y2 corresponds to application server 400. When computer 100 wants to access application server 300 corresponding to application system Y1, or application server 400 corresponding to application system Y2, it needs to go through login server 200 for login authentication. That is, multiple application systems under the cloud vendor trust each other and share the same set of login authentication servers. At this time, each application system can share the same set of user data. The login authentication process of any application ultimately needs to use a unified login server 200 to complete the login authentication. It can be understood that only after the login authentication of the login server 200 is passed, can the computer 100 successfully log in to the application system to be logged in.

[0053] In some cases, upon receiving a login request, the login server 200 may detect a failure in the main login process. In this case, a downgraded login method may be used. For example, the downgraded login method may receive less authentication information than before the downgrade and provide the computer 100 with a downgraded login page, allowing the computer 100 to log in using the downgraded login method. Compared to the original login page, the downgraded login page requires the user to enter less authentication information, and the computer 100 will receive less valid information for login authentication than before. In this case, the login server 200 will perform login authentication based on the reduced authentication information and, if the authentication information is correct, pass the login authentication. When the computer 100 successfully logs in to the application system using the downgraded login page, in some cases, the user may experience limitations when using certain application system functions or performing operations on certain data, such as being unable to access the user's password or using the beauty function on photos. In other cases, the user may not experience any limitations when using application system functions or performing operations on certain data, and may still use all functions and access all data. However, after logging in through the downgraded login method, regardless of whether the application imposes restrictions on the user's operations, there will be a problem that the application system is easily maliciously and illegally logged in due to the small amount of authentication information verified by the login server 200 and the low login security level of logging in through the downgraded login page, resulting in a large amount of user data being leaked, thereby causing irreparable losses.

[0054] For example, reference Figure 2A The shopping mall page 001 shown in FIG. 1 is introduced by taking the application system Y1 as a specific shopping mall application A1 as an example. User K clicks the "Login" control K101 in the shopping mall page 001, and the shopping mall page 001 will jump to the following Figure 2B The login page 002 shown in FIG. User K can enter the user account "888xxx" in the input box K201 on the login page 002, enter the user account password "123xxx" in the input box K202, and enter the verification code "XLGP" in the input box K203A, which is the same as the letters on the verification image K203B. Then the user clicks the "Confirm" control K204, which can be used as a login confirmation control to confirm the login. At this time, the computer 100 will send a message to the user. Figure 1 The application server 300 in the login request sends a login request, which includes authentication information such as the user account, the user account password and the verification code. The application server 300 will forward the login request to the Figure 1The login server 200 in the login server 200, when confirming that the main login process fails, for example, when the login server 200 fails to log in due to high concurrency or code design defects, it will adopt a downgrade login solution, that is, provide a downgrade login page to the computer 100. Figure 2C The downgrade login page 003 shown in FIG. 1 only provides an account input box K301 and a verification code input box K302A. At this time, the computer 100 only needs to enter the account and verification code (with Figure 2B Compared with the login page in , the login password is reduced), and then the login server 200 only needs to confirm that the account exists and the verification code is entered correctly, that is, the computer 100 is allowed to access the application server 300 based on less authentication information.

[0055] However, when the login server 200 adopts the downgraded login method, the authentication information only includes the account number and the verification code, the authentication information is relatively simple and easy to obtain, so the security level corresponding to the downgraded login method is lower than the security level of the original login page. At this time, the application system can easily be maliciously and illegally logged in, causing a large amount of user data to be leaked, resulting in irreparable losses.

[0056] Currently, some existing technologies only ensure user login security when the application system login process is normal. For example, user-related authentication information is added during login to confirm the user's identity, specifically the user's frequently logged-in locations, frequently used IP addresses, and historical behavior data corresponding to the user's login account. However, these methods can only ensure user login security when the application system login process is normal. For downgraded login methods, because the valid authentication information is reduced during downgraded login, user-related authentication information alone cannot guarantee user login security.

[0057] In addition, continue to refer to Figure 1 After successfully logging into application system Y1, user K can use single-sign-on to log into application system Y2, which uses the same login account and password as application system Y1. For example, application system Y2 could be cloud space B1, which has a trusted relationship with shopping mall A1. Computer 100 then sends a login request to application server 400, which forwards it to login server 200. Based on the authentication information from application system Y1's successful login, login server 200 approves computer 100's login to application system Y2, allowing computer 100 to access application server 400.

[0058] However, since the login method used by computer 100 to log in to application system Y1 is relatively risky, when computer 100 uses single sign-on to log in to application system Y2, the risk of login is also relatively high when re-login authentication is not performed through the login page. At this time, the logged-in application system will also be easily subject to malicious and illegal login, especially when the logged-in application system Y2 has a lot of sensitive data, resulting in huge losses to users.

[0059] Therefore, in order to solve the above problems, the present application proposes a login method. In this method, a login server classifies the login objects targeted by the user login in advance (for example, different application systems, or different services belonging to the same application system), and classifies the login objects with high security requirements as login objects that are restricted from performing downgraded login. In this way, after determining that a failure has occurred in the user login client, if the login server detects that the user has logged in to the client again, it determines whether the login object executed after the user logs in again is a login object that is restricted from performing downgraded login. If it is a login object that is restricted from performing downgraded login, the downgraded login is rejected, thereby preventing the problem of malicious and illegal login of login objects that cause greater losses to the user when the login security environment is reduced, thereby avoiding causing greater losses to the user.

[0060] It is understood that when the login object is an application, applications with high security requirements may include social media applications, email applications, shopping applications, online storage applications, medical applications, financial applications, etc. It is understandable that social media applications, email applications, shopping applications, online storage applications (such as cloud storage), financial applications, etc. usually store users' personal information, photos, videos, financial information, transactions and other private data. If this data is leaked, it will cause significant losses to users.

[0061] Applications with low security requirements may be learning and listening applications, technical blog applications, game applications, etc., which involve less user privacy information.

[0062] When different businesses also require independent identity authentication and authorization, the login objects are different businesses belonging to the same application system. In this case, businesses with high security requirements may include payment services, transaction services, online supermarket services, etc. Businesses with low security requirements may include small games, query services, online medical consultation services, etc., which are not required here.

[0063] In addition, for single sign-on, when a new login object is logged in successfully based on the previous login object, the login server still restricts the new login object. The login server will reclassify the login objects for single sign-on in advance, and classify login objects with sensitive information (such as user privacy information) as login objects with restricted single sign-on. In this way, if it is determined that the login object is a login object with restricted single sign-on, the single sign-on will be rejected, thereby preventing the login object using single sign-on from being maliciously and illegally logged in when the login security environment is reduced, thereby avoiding causing significant losses to users.

[0064] For example, when single sign-on is performed between different application systems, the applications that need to be restricted include: payment applications, medical applications, social applications, cloud storage applications, government service applications, etc.

[0065] For another example, when single sign-on is allowed between different services of the same application, the services that need to be restricted include: payment services, transaction services, online supermarket services, access to cloud space services, etc.

[0066] Understandably, applications such as payment, shopping, healthcare, social networking, cloud storage, and public security involve large amounts of personal identity information, financial information, transaction records, medical records, and sometimes public service and national security information. Leakage of this data could result in severe financial losses and the disclosure of personal privacy.

[0067] It is understandable that since single sign-on restrictions are imposed on login objects with important sensitive data, key sensitive businesses are effectively prevented from performing single sign-on based on other login objects with low security requirements, effectively ensuring the login security of new login objects.

[0068] It is understandable that the application systems with a trust relationship may be application systems developed by the same company, or application systems of different companies may establish a trust relationship through communication connections, or may be trust relationships established in other ways, which will not be elaborated here.

[0069] When performing a downgraded login, the number of authentication information in the downgraded login can be changed from multiple to 1, or from K to O, where K is less than O.

[0070] It is understood that the aforementioned computer can be a client. Clients include, but are not limited to, mobile phones, tablet computers, in-vehicle devices, augmented reality (AR) / virtual reality (VR) devices, ultra-mobile personal computers (UMPCs), netbooks, personal digital assistants (PDAs), smart homes, patrol robots, and the like, and this application does not impose any restrictions thereon. The login server or application server can have different architectures, such as server clusters or distributed server architectures, and is not limited thereto.

[0071] It is understood that in some embodiments, the login server and the application server corresponding to the application system can be the same server. That is, the login server's function of performing login authentication for multiple applications or different services of the same application can be deployed on an application server that has at least one application server function. For example, the login server 200 and the application server 300 can be the same server. In addition, the application servers corresponding to different applications can also be the same server. For example, the login server 200, application server 300, and application server 400 can be the same server. Modules for different application systems and modules for login authentication can be deployed on the same server. The specific deployment method is not limited here.

[0072] In order to more clearly understand the login method of the embodiment of the present application, the following is explained by taking the example that each application system corresponds to a different application server, and the application server and the login server are not the same server.

[0073] Figure 3 According to some embodiments of the present application, a schematic diagram of a login framework 500 is shown. Figure 3 As shown, the login framework 500 includes a computer 100 , a login server 200 , an application server 300 , and an application server 400 .

[0074] Specifically, computer 100 is configured to receive a login operation from user K on a browser or app for a specific login object, generate a login request, and send it to the corresponding application server. In some implementations, computer 100 includes a user login interface interaction module that can respond to content sent by the application server by displaying a page; it can also receive user input and generate a login request.

[0075] Login server 200 is configured to determine whether to allow login requests corresponding to login objects. In some implementations, login server 200 includes an HTTPS request processing module and a configuration data storage module. The HTTPS request processing module is configured to respond to received login requests. The configuration data storage module is configured to store a database containing data used to verify whether the login request meets login conditions, thereby determining the request.

[0076] The application server 300 forwards the login request received from the computer 100 to the unified login server 200. It is also configured to receive the downgraded login page content or login result sent by the login server 200. Furthermore, upon receiving the downgraded login page content from the login server 200, the application server 300 forwards the downgraded login page content to the computer 100. Furthermore, based on the login result received from the login server 200, the application server 300 provides different login content to the computer 100. Specifically, in some embodiments, when the application server 300 receives a login result from the login server 200 indicating that login is permitted, it can send the application page content after a successful login to the computer 100. When the application server 300 receives a login result from the login server 200 indicating that login failed, it can send a login failure message to the computer 100. It should be understood that the application server 400 can perform the same operations as the application server 300, and this will not be described in detail here.

[0077] It is understood that the login request forwarded by the application server can be a login request for login or a single sign-on request for single sign-on. It is understood that in some implementations, the application server 300 and the application server 400 both include a request processing module (e.g., an https request processing module) to process the login request sent by the computer 100.

[0078] To understand more clearly, Figure 4 According to some embodiments of the present application, an interactive diagram of a login method is shown. The interactive diagram is illustrated by taking the login object as an application as an example. The interactive diagram shows the login interaction process between the computer 100, the login server 200, and the application server 300 and the application server 400. When each device performs the login interaction, the execution subject can be each electronic device, or the processor or chip of the electronic device. However, the present application does not limit the execution subject of the interaction process. The specific steps are as follows:

[0079] S401 , the computer 100 displays a login page D1 for application 1 .

[0080] In some embodiments, the user can open a browser on the computer 100 and enter the login page D1 of the application 1 through the browser.

[0081] In other embodiments, a user operates APP1 on computer 100 and enters the login page D1 of application 1 through APP1. For example, the user double-clicks APP1 on computer 100 and then selects the login control on APP1, causing computer 100 to display the login page D1 for application 1. It is understood that the computer 100 may display the login page D1 in different ways for different applications, and this is not required here.

[0082] For example, taking Application 1 as a shopping mall application, you can refer to the above Figure 2B The browser of the computer 100 shown displays the shopping mall page 002 . At this time, the login page D1 is the shopping mall page 002 .

[0083] S402, the computer 100 detects a user login operation and generates a login request Q1 for login.

[0084] In some embodiments, a user can perform a login input operation on login page D1 to enable login authentication. Computer 100 detects the user login input, obtains the input authentication information, and then generates a login request Q1 based on the authentication information. Login request Q1 includes the authentication information and application information. For example, the application information may include an application identifier corresponding to application 1.

[0085] It can be understood that the authentication information may include the following authentication factors: user account, user account password, verification code, security environment parameters, mobile phone number, SMS password, user device IP, user device login location, biometrics, device login time and other authentication factors.

[0086] For example, refer to the above Figure 2B The following figure shows a description of login page 002. User K enters the user account "888xxx" in input box K201, the user account password "123xxx" in input box K202, and the verification code "XLGP" in input box K203A, which matches the letters in verification image K203B. The user then clicks the "Confirm" control K204. Computer 100 then receives authentication information, including the user account, password, and verification code. Based on the authentication information, computer 100 generates a login request Q1, which includes the user account, password, verification code, and the application identifier corresponding to the shopping mall.

[0087] For another example, the user can enter the mobile phone number and SMS password on the login page, and then click the confirmation control. At this time, the computer 100 will receive the authentication information including the mobile phone number and SMS password to generate a login request Q1.

[0088] S403 , the computer 100 sends a login request Q1 to the application server 300 .

[0089] S404 , the application server 300 forwards the login request Q1 for the application 1 to the login server 200 .

[0090] S405: The login server 200 confirms that a failure occurs in the main login process and adopts a downgraded login solution.

[0091] In some embodiments, the login server 200 confirms that a failure has occurred in the main login process and that the login has failed according to the login request Q1. For example, the login server 200 fails to log in due to high concurrency or a code design defect. In this case, a downgraded login solution is adopted, that is, a downgraded login page is provided to the computer 100. In this case, the login server 200 sends the downgraded login page content to the computer 100 through the application server 200.

[0092] S406 , the login server 200 sends the degraded login page content to the application server 300 .

[0093] In some embodiments, the login server 200 sends a code representing the degraded login page content to the application server 300 .

[0094] S407 , the application server 300 sends the downgraded login page content to the computer 100 .

[0095] In some embodiments, the login server 200 forwards a code indicating the downgraded login page content to the computer 100 .

[0096] S408, the computer 100 displays a downgrade login page.

[0097] In some embodiments, the computer 100 displays the downgraded login page according to the received downgraded login page content.

[0098] For example, you can refer to Figure 2C The downgraded login page 003 shown only provides an account input box K301 and a verification code input box K302A, and clicks the "Confirm" control K303 to log in.

[0099] It is understandable that in order to ensure the user's access experience, the login server 200 provides the computer 100 with a downgraded login page, which requires the user to authenticate less authentication information. Therefore, the security level of the downgraded login page is lower than the security level of the previous login page.

[0100] S409, the computer 100 receives the user login operation again and generates a login request Q2.

[0101] In some embodiments, the computer 100 receives a user login input operation on the downgraded login page, obtains the input authentication information, which is the authentication information of the downgraded login, and then generates a login request Q2 again based on the authentication information of the downgraded login. The login request Q2 includes the authentication information of the downgraded login and application information.

[0102] For example, referring to the above Figure 2C , the user enters the account number "888xxx" and the verification code "XLGP" in the downgrade login page 003 of the computer 100, thereby generating a login request Q2.

[0103] For another example, the user may enter a mobile phone number and / or a verification code on the login page, thereby generating a login request Q2.

[0104] S410 , the computer 100 sends a login request Q2 to the login server 200 .

[0105] S411, the login server 200 determines whether the first login condition is met according to the login request Q2.

[0106] If the first login condition is not met, proceed to S412; otherwise, proceed to S414.

[0107] In some embodiments, the first login condition includes that the authentication information is correct and the logged-in application 1 is an application with lower security requirements, that is, an application that is not restricted from logging in. If, based on the login request Q2, it is determined that the first login condition is met, for example, the authentication information is correct and the logged-in application 1 is an application with lower security requirements, then the process goes to S414 and sends a login permission message, that is, a login success message; otherwise, the process goes to S412 and sends a login failure message. It can be understood that application login is restricted according to the security requirements of the application, so that in the case of a poor login security environment, when a downgraded login is used after a login failure, application servers with higher security requirements cannot be accessed independently, thereby ensuring the login security and reliability of the entire application ecosystem.

[0108] Specifically, in some implementations, the login server 200 compares the authentication information with information stored in a database or other authentication source to confirm the user's identity. Furthermore, the server 200 needs to determine the security category of the application to determine whether the logged-in application 1 is an application with low security requirements, thereby restricting applications with higher security requirements.

[0109] As will be appreciated, the database will pre-store the security category identifiers corresponding to each application. For example, the security category identifier corresponding to applications with lower security requirements may be configured as identifier 1, and the security category identifier corresponding to applications with higher security requirements may be configured as identifier 2. After the login server 200 determines that the authentication information is correct and, based on the application information, indexes the application in the database and obtains the security category identifier corresponding to the application as identifier 1, which indicates a lower security requirement, it deems that the first login condition is met and proceeds to S414 to allow the login. Otherwise, the process proceeds to S412 and sends a login failure message to the application server 300. As will be appreciated, the login failure message may include the reason for the login failure, such as failure to authenticate a particular authentication factor in the authentication information or application limitations.

[0110] For example, if application 1 is a shopping mall application, the login server 200 indexes application 1 from the database and obtains identifier 2 corresponding to application 1. The login server 200 then deems that the first login condition is not met and proceeds to S412 to send a login failure message to the application server 300. The login failure message includes login restriction information corresponding to the application.

[0111] For another example, taking application 1 as an application belonging to the blog technology category, the login server 200 indexes the application 1 from the database, and obtains the corresponding identifier 1 of application 1, and determines that the authentication information is correct, then it is considered that the first login condition is met, and it will enter S414 to allow login.

[0112] S412 , the login server 200 sends a login failure message to the application server 300 .

[0113] In some implementations, the login server 200 sends a login failure message to the application server 300 , and the login failure message includes information corresponding to the application 1 being restricted from logging in.

[0114] S413, the application server 300 sends a login failure message to the computer 100.

[0115] In some implementations, the application server 300 sends a login failure message to the computer 100 , and the login failure message includes information corresponding to the restricted login of the application 1 . At this time, the computer 100 will display the restricted login information.

[0116] For example, since application 1 is a shopping mall application with high security requirements, the application server 300 sends a login failure message to the computer 100, and the login failure message includes information corresponding to the restricted login of application 1. Therefore, after the computer 100 receives the message corresponding to the restricted login of application 1, a prompt box will pop up to prompt that the login failed. Figure 5A The login failure page 004 of the shopping mall application is shown. At this time, a prompt box K401 will pop up on the login page 004, and the prompt box K401 displays "Prompt: Login failed". It is understandable that the login page 004 can also be displayed in other ways, which is not required here.

[0117] S414 , the login server 200 sends a login permission message to the application server 300 .

[0118] It is understandable that the login message is allowed to include correct authentication information, such as account information, so that the application server 300 can subsequently send application page content for application 1 to the computer 100.

[0119] S415 , the application server 300 sends the application page content for application 1 to the computer 100 .

[0120] In some embodiments, in response to the login permission message, the application server 300 sends the application page content for application 1 to the computer 100. In this case, in the case of a poor login security environment, when a login failure is followed by a downgraded login, the application server with a lower security level can be independently accessed without affecting the user's application experience.

[0121] For example, since application 1 is a technical blog application with low security requirements, the application server 300 sends the application page content for application 1 to the computer 100. Therefore, the computer 100 displays the application page content for application 1 according to the received application page content. Figure 5B As shown in the page 005 after successful login, at this time, the computer 100 displays the application page after successfully accessing the application server 300, so that the user can perform application operations.

[0122] In addition, optionally, after successfully logging in, the user can also perform single sign-on on application 2 that has a trust relationship with application 1 based on the successful login of application 1, thereby performing the following steps S416-S423.

[0123] S416 , the computer 100 receives a user login operation for single sign-on for application 2 and generates a login request P1 .

[0124] As will be appreciated, after a successful login on computer 100, the login server typically stores the user's successful login information in the form of a cookie on computer 100. This allows a user to access multiple application servers with only one login. Furthermore, by storing authentication information in a cookie, the client automatically sends the cookie along with the request to the corresponding server when subsequently accessing other trusted application systems.

[0125] In some embodiments, the application page of application 1 includes an entry for accessing application 2. The user can select the entry to implement a single sign-on operation for application 2. After receiving the user's selection of the entry, computer 100 generates a login request P1, where login request P1 includes application information corresponding to application 2 and also includes stored authentication information from a previous successful login.

[0126] In other embodiments, when application 1 is opened in a browser, the user can also re-enter the URL in the browser to implement a single sign-on user login operation for application 2. For details, please refer to the following Figure 6 At this time, a login request P1 may also be generated.

[0127] S417 , the computer 100 sends a login request P1 to the application server 400 .

[0128] S418 , the application server 400 sends a login request P1 to the login server 200 .

[0129] S419: The login server 200 determines whether the second login condition is met based on the login request P1.

[0130] If the second login condition is not met, the process proceeds to S420 and sends a login failure message to the application server 400 ; otherwise, the process proceeds to S422 and sends a login permission message to the application server 400 .

[0131] In some embodiments, since application 1 successfully logged in, it can be determined that the authentication information is correct. Therefore, the second login condition at least includes that application 2 is not a critical or sensitive application, that is, an application that is not restricted from logging in. In addition, the second login condition may also include that the authentication information is correct to prevent the authentication information from being tampered with.

[0132] If, based on login request P1, the second login condition is determined to be met, the process proceeds to S422 and sends a login permission message; otherwise, the process proceeds to S420 and sends a login failure message. It is understood that by restricting application login based on the presence of sensitive information in an application, in the event of a poor login security environment, the application server containing sensitive information cannot be accessed when a degraded login is used after a login failure, thereby ensuring the login security and reliability of the entire application ecosystem.

[0133] In some implementations, the database may pre-store sensitive category identifiers corresponding to various applications. For example, the sensitive category identifier corresponding to important sensitive applications may be configured as identifier 3, and the sensitive category identifier corresponding to non-important sensitive applications may be configured as identifier 4. After the login server 200 determines that the authentication information is correct and indexes application 2 in the database based on its application information, it may determine whether application 2 is an important sensitive application based on the sensitive category identifier corresponding to the indexed application 2. If it is determined that the application is not an important sensitive application, it is considered that the first login condition is met, and the process proceeds to S414 to allow login. Otherwise, the process proceeds to S412 to send a login failure message to the application server 300. It is understood that the login failure message may carry the reason for the login failure, such as whether a certain authentication factor in the authentication information failed to authenticate, or whether there are application restrictions.

[0134] S420 , the login server 200 sends a login failure message to the application server 400 .

[0135] In some implementations, the login server 200 sends a login failure message to the application server 400 , and the login failure message includes information corresponding to the restricted login of the application 2 .

[0136] S421, the application server 400 sends a user login failure message to the computer 100.

[0137] In some implementations, the application server 400 sends a login failure message to the computer 100 , and the login failure message includes information corresponding to the restricted login of the application 2 . At this time, the computer 100 will display the restricted login information.

[0138] For example, reference Figure 5C The login failure page 006 of application 2 is shown. At this time, a prompt box K601 will pop up on the login page 006, and the prompt box K601 displays "Prompt: Login failed". It is understandable that the login page 006 can also be displayed in other ways, which is not required here.

[0139] S422 , the login server 200 sends a login permission message to the application server 400 .

[0140] S423 , the application server 400 sends the application page content for application 2 to the computer 100 .

[0141] In some embodiments, the application server 400 sends application page content for application 2 to the computer 100 in response to the login permission message.

[0142] In some embodiments, the application server 300 responds to the login permission message by sending the application page content for application 2 to the computer 100. In this case, when the login security environment is poor, it can ensure the security of single sign-on when a downgraded login is used after a login failure without affecting the user's application experience.

[0143] For example, reference Figure 5D The page 007 after the application 2 is successfully logged in is shown. At this time, the computer 100 displays the application page after successfully accessing the application server 400, so that the user can perform application operations.

[0144] It is understood that the execution order of steps 401 to S423 described above is merely an example. In other embodiments, other execution orders may be employed, and some steps may be split or combined. This is not a time limit. For example, in step S406 described above, if the login server 200 discovers a failure in the main login process, in addition to sending a downgraded login page to the application server 300, which then forwards the page to the computer 100, the downgraded login page may also be sent directly to the computer 100. This is not a requirement.

[0145] It is understandable that when using downgraded login, applications with high security requirements are restricted, and when using single sign-on, important sensitive applications are restricted. This ensures that in the case of a poor login security environment, when using downgraded login after a login failure, applications with high security requirements are prevented from illegal and malicious logins, and ensures that mutually trusted applications can log in conveniently without the need for re-login authentication, without affecting the user's application experience.

[0146] In order to more clearly understand the login method of the embodiment of this application, Figure 6 According to some embodiments of the present application, a login method interaction diagram is shown, taking Application 1 as a Developer Alliance application and Application 2 as a cloud space application as an example. Accordingly, the server corresponding to the Developer Alliance application is Developer Alliance server 300A, and the server corresponding to the cloud space application is cloud space server 400A. The user logs in to the Developer Alliance application through browser 100A and performs login authentication through login server 200A. The specific interaction process is as follows:

[0147] S601: A user accesses the Developer Alliance website through a browser.

[0148] In some embodiments, a user uses a computer to open a browser and prepares to visit a developer alliance website of a cloud vendor. The user enters the developer alliance website address in the browser 100A: "https: / / www.developer.xxx.com / index.html". After the browser sends a request, it will resolve the domain name www.developer.xxx.com to the developer alliance server 300A and ask the developer alliance server 300A for the content to be displayed on this page. After receiving this request, the developer alliance server 300A will jump to the login page if the user is not logged in. For example, if you jump to Figure 7A The Developer Alliance login page 008 is shown.

[0149] S602 , the browser 100A receives a user login operation from the login page of the developer alliance application and generates a login request Q1a .

[0150] For example, the user Figure 7A The developer alliance login page 008 shown receives the user login input. Figure 7A , the user input includes user account, user account password, verification code, etc. It can be understood that the content of the login page is the same as the above Figure 2B The page content is the same as in the above. For detailed description, please refer to the above Figure 2B It is understandable that the generated login request Q1a includes the application information corresponding to the developer alliance (for example, application identification), as well as the user account, user account password, verification code and other authentication information.

[0151] S603 , the browser 100A sends a login request Q1a for the developer alliance application to the developer alliance server 300A.

[0152] S604: The developer alliance server 300A sends a login request Q1a to the login server 200A.

[0153] For example, after receiving the request, the developer alliance server 300A forwards it to the login server 200A for unified login authentication for login authentication.

[0154] S605: The login server 200A confirms that a failure occurs in the main login process and adopts a downgraded login solution.

[0155] For example, login server 200A receives login request Q1a. Due to a failure in the current main login process, the normal user login authentication process cannot be completed, resulting in a large number of user login failures. Login server 200A urgently initiates a downgrade solution, downgrading the security level of the login page to a level where users only need their account number and verification code to log in.

[0156] S606: The login server 200A sends the downgraded login page content to the developer alliance server 300A.

[0157] For example, the login server 200 returns a downgraded login page to the browser of the developer alliance server 300A, and the user only needs an account number and a verification code to log in.

[0158] S607: The developer alliance server 300A sends the downgraded login page content to the browser 100A.

[0159] S608: The browser 100A receives a user login operation from the downgraded login page.

[0160] For example, the browser 100A displays the following information based on the received downgrade login page: Figure 7B The downgrade login page 009 is shown. After the user sees the downgrade login page 009, he enters his account number and verification code, clicks login, and tries to log in again. The specific user enters his account number and verification code in the downgrade login page 008. It can be understood that the content of this login page is different from the above Figure 2C The page content is the same as in , and the specific way to receive user input can refer to the above Figure 2C The description is not repeated here.

[0161] S609 , the browser 100A sends a login request Q2a for the developer alliance application to the login server 200A.

[0162] For example, the login request Q2a includes application information corresponding to the developer alliance, as well as an account number and a verification code.

[0163] S610: The login server 200A determines that the developer alliance application meets the first login condition and can be independently logged in.

[0164] It is understandable that after the login server 200A is downgraded, it receives a user's login request. Since the user login is in a low-security environment after the downgrade, the login security cannot be effectively guaranteed. The login server 200 needs to restrict application logins, allowing only applications with low security requirements to log in and prohibiting applications with high security requirements from logging in.

[0165] For example, the login server 200A determines that the authentication information is correct, and determines that the developer alliance application is an application with low security requirements, which meets the first login condition and can perform independent login.

[0166] S611: The login server 200A sends a login permission message to the developer alliance server 300A.

[0167] S612: The developer alliance server 300A sends the developer alliance website page to the browser 100A.

[0168] S613 , the browser 100A receives the cloud space login operation and generates a login request P1a.

[0169] For example, a user successfully logs in to the Developer Alliance website after a login downgrade, and then wants to open a new browser page based on this login. Since the cloud application and the Developer Alliance are mutually trusted applications, the user can enter the cloud address: https: / / www.cloudapace.com / index.html to log in to the cloud application through single sign-on. Specifically, based on the cloud address entered by the user and the authentication information of the corresponding Developer Alliance application stored in browser 100A, a login request P1a is generated. Login request P1a includes the corresponding cloud application information, the user account stored in the browser, and a verification code.

[0170] S614 : The browser 100A sends a login request P1a for single sign-on for the cloud application to the cloud server 400A.

[0171] S615 , the cloud space server 400A forwards the login request P1a to the login server 200A.

[0172] For example, the cloud space server 400A receives a single sign-on request and forwards the request to the login server 200 for single sign-on.

[0173] S616: The login server 200A determines that the cloud space application does not meet the second login condition and login is not possible.

[0174] For example, login server 200A receives a login request P1a corresponding to a cloud space application. Since it is currently in a downgraded login scheme, in a low-security environment, to protect the user's personal privacy data, login server 200A will restrict single sign-on (SSO), allowing only non-critical sensitive applications to perform SSO, and not allowing SSO for critical sensitive services. Furthermore, since cloud space stores a large amount of personal data, such as user photo albums, user address books, call logs, and other user privacy data, which are critical sensitive services, login server 200A determines that the cloud space application is a critical sensitive application and does not meet the second login condition. Login server 200A returns an error code, prohibiting the user from logging into the cloud space application through SSO, and returns a message to cloud space server 400A informing it of the failure of SSO. Login is not possible.

[0175] S617: The login server 200 sends a single sign-on failure message to the cloud space server 400A.

[0176] S618 , the cloud space server 400A notifies the browser 100A that the user login has failed.

[0177] It can be understood that the execution order of the above steps S601 to S618 is only an example. In other embodiments, other execution orders may be adopted, and some steps may be split or merged. There is no time limit here.

[0178] Understandably, the above Figure 4 as well as Figure 6 The following description takes the application server and login server as different servers as an example.

[0179] In other embodiments, as described above, when the login server and the application server corresponding to a certain application are the same server, for example, the login server 200 and the application server 300 may be the same server 500, then for Figure 4 The operations performed by the application server and the login server are performed by the module corresponding to the function of the application server on the server 500. Figure 4 The operations performed by the login server in the example are performed by the module corresponding to the login server function on the server 500. At this point, the interaction between the computer 100, login server 200, application server 300, and application server 400 can be transformed into the interaction between the computer 100, application server 400, and server 500. The specific process is not repeated here.

[0180] In addition, in some embodiments, as described above, the login server and all application servers corresponding to the same account are the same server, that is, the login server's function of performing login authentication for multiple applications or different services of the same application, as well as the function of the application server corresponding to all applications are deployed on the same server. For example, in this case, the login server 200, the application server 300, and the application server 400 are the same server 600. Figure 4 The operations performed by each application server in the example are performed by modules on the server 600 corresponding to the functions of each application server. Figure 4 The operations performed by the login server in the example are performed by a module corresponding to the function of the login server on the server 600. At this time, the computer 100 only needs to interact with the server 600.

[0181] Figure 8 A schematic structural diagram of a device is shown according to an embodiment of the present application.

[0182] It can be understood that the device 800 can be any electronic device that runs a cloud platform, for example, it can include but is not limited to mobile phones, tablet computers, vehicle-mounted equipment, augmented reality (AR) / virtual reality (VR) devices, ultra-mobile personal computers (UMPC), netbooks, personal digital assistants (PDA), servers, server clusters, etc., without limitation here.

[0183] like Figure 8 As shown, device 800 may include one or more processors 801, also referred to as processing units, which may implement certain control functions. Processor 801 may be a general-purpose processor or a dedicated processor. For example, it may be a baseband processor or a central processing unit. A baseband processor may be used to process communication protocols and communication data, while a central processing unit may be used to control communication devices, such as base stations, baseband chips, terminals, and terminal chips, execute software programs, and process data in software programs.

[0184] In an optional design, the processor 801 may also store instructions and / or data 803, and the instructions and / or data 803 can be executed by the processor so that the device 800 performs the method described in the above method embodiment.

[0185] In another alternative design, processor 801 may include a transceiver unit for implementing receiving and transmitting functions. For example, the transceiver unit may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing the receiving and transmitting functions may be separate or integrated. The transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or may be used for transmitting or delivering signals.

[0186] In another possible design, the apparatus 800 may include a circuit that can implement the login function in the aforementioned method embodiment.

[0187] Optionally, the device 800 may include one or more memories 802, on which instructions / data 804 may be stored. The instructions may be executed on a processor, causing the device 800 to perform the method described in the above method embodiment. Optionally, the memory may also store data. Optionally, the processor may also store instructions and / or data. The processor and memory may be provided separately or integrated. For example, the corresponding relationship described in the above method embodiment may be stored in the memory or in the processor.

[0188] Optionally, the apparatus 800 may further include a transceiver 805 and / or an antenna 806. The processor 801 may be referred to as a processing unit, and controls the apparatus 800. The transceiver 805 may be referred to as a transceiver unit, a transceiver, a transceiver circuit, a transceiver device, an interface, an interface circuit, or a transceiver module, and is configured to implement transceiver functions.

[0189] Optionally, the apparatus 800 in the embodiment of the present application may be used to execute the embodiment of the present application. Figure 4 、 Figure 6 The login method described in .

[0190] According to the method provided in the embodiments of the present application, the present application also provides a computer program product, which includes: computer program code, when the computer program code is run on a computer, enables the computer to implement the steps performed by the device 800 in any one of the above embodiments.

[0191] According to the method provided in the embodiments of the present application, the present application also provides a computer-readable medium, which stores program code. When the program code runs on a computer, the computer implements the steps performed by the device 800 in any of the above embodiments.

[0192] The various embodiments disclosed in this application can be implemented in hardware, software, firmware, or a combination of these implementation methods. The embodiments of the present application can be implemented as a computer program or program code executed on a programmable system, which includes at least one processor, a storage system (including volatile and non-volatile memory and / or storage elements), at least one input device, and at least one output device.

[0193] Program code can be applied to input instructions to perform the functions described herein and generate output information. The output information can be applied to one or more output devices in a known manner. For purposes of this application, a processing system includes any system having a processor such as, for example, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), or a microprocessor.

[0194] Program code can be implemented with a high-level programming language or an object-oriented programming language to communicate with the processing system. Where necessary, program code can also be implemented in assembly language or machine language. In fact, the mechanism described in this application is not limited to the scope of any particular programming language. In either case, the language can be a compiled language or an interpreted language.

[0195] In some cases, the disclosed embodiments may be implemented in hardware, firmware, software, or any combination thereof. The disclosed embodiments may be implemented as instructions carried or stored on one or more temporary or non-temporary machine-readable (e.g., computer-readable) storage media, which may be read and executed by one or more processors. For example, instructions may be distributed over a network or through other computer-readable media. Therefore, a machine-readable medium may include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer), including but not limited to a floppy disk, an optical disk, an optical disk, a magneto-optical disk, a read-only memory (ROM), a random access memory (RAM), an erasable programmable read-only memory, an electrically erasable programmable read-only memory, a magnetic card or an optical card, a flash memory, or a tangible machine-readable memory for transmitting information (e.g., a carrier wave, an infrared signal, a digital signal, etc.) using the Internet in an electrical, optical, acoustic, or other form of propagation signal. Therefore, a machine-readable medium includes any type of machine-readable medium suitable for storing or transmitting electronic instructions or information in a form readable by a machine (e.g., a computer).

[0196] In the accompanying drawings, some structural or method features are shown in a particular arrangement and / or order. However, it should be understood that such a particular arrangement and / or order may not be required. Rather, in some embodiments, these features may be arranged in a manner and / or order different from that shown in the illustrative drawings. In addition, the inclusion of a structural or method feature in a particular figure does not imply that such feature is required in all embodiments, and in some embodiments, such features may not be included or may be combined with other features.

[0197] It should be noted that the units / modules mentioned in the various device embodiments of the present application are all logical units / modules. Physically, a logical unit / module can be a physical unit / module, or a part of a physical unit / module, or can be implemented as a combination of multiple physical units / modules. The physical implementation of these logical units / modules themselves is not the most important. The combination of functions implemented by these logical units / modules is the key to solving the technical problems raised by this application. In addition, in order to highlight the innovative part of this application, the above-mentioned device embodiments of this application do not introduce units / modules that are not closely related to solving the technical problems raised by this application. This does not mean that other units / modules do not exist in the above-mentioned device embodiments.

[0198] It should be noted that in the examples and description of this patent, relational terms such as first and second are merely used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. Without further restriction, an element defined by the phrase "comprising a" does not exclude the presence of other identical elements in the process, method, article or device comprising the element. Although the present application has been illustrated and described with reference to certain preferred embodiments of the present application, it should be understood by those skilled in the art that various changes can be made thereto in form and detail without departing from the scope of the present application.

Claims

1. A login method, characterized in that: Applied to a client, the method includes: Displaying a first login page corresponding to the first login object; receiving a first user operation on a first login page, and sending a first login request corresponding to a first login object; Displaying a second login page corresponding to the failed login of the first login request, wherein the login security level of the second login page is lower than the login security level of the first login page; receiving a second user operation on the second login page, and sending a second login request corresponding to the first login object; The first login restriction information for the second login request is displayed.

2. The method according to claim 1, characterized in that Also includes: If the first login page includes the following authentication information: user account and password of the user account, the second login page includes the following authentication information: user account and / or verification code; If the first login page includes the following authentication information: mobile phone number, SMS password, then the second login page includes the following authentication information: mobile phone number and / or verification code; The first login restriction information includes: prompt information for performing the first login restriction on the first login object, and / or login failure information for performing the first login restriction on the first login object.

3. The method according to claim 2, characterized in that The first login page displays a first login confirmation control, and the receiving a first user operation on the first login page includes: Receiving first authentication information input by a user from the first login page, and receiving a click operation of the user on the first confirmation login control; and, The second login page displays a second confirmation login control, and receiving a second user operation on the second login page includes: receiving second authentication information input by the user from the second login page, and receiving a click operation on the second confirmation login control by the user.

4. The method according to any one of claims 1 to 3, characterized in that Also includes: displaying a third login page corresponding to a second login object, wherein the security requirement of the second login object is lower than the security requirement of the first login object; receiving a third user operation on a third login page, and sending a third login request corresponding to the second login object; Displaying a fourth login page corresponding to the failed third login request, wherein the login security level of the fourth login page is lower than the login security level of the third login page; receiving a fourth user operation on a fourth login page, and sending a fourth login request corresponding to the second login object; A first successful login page for the fourth login request is displayed.

5. The method according to claim 4, characterized in that The first login object is an application corresponding to the first login restriction, including at least one of the following: Social media applications, email applications, shopping applications, online storage applications, medical applications, and financial applications; and, The second login object is an application that does not correspond to the first login restriction, including at least one of the following: a learning and lecture application, a technical blog application, and a game application.

6. The method according to claim 4, characterized in that The first login object and the second login object belong to the same first application, Among them, the first login object is the business corresponding to the first login restriction, including: payment business, transaction business, and online supermarket business; the second login object is the business that does not correspond to the first login restriction, including: mini-game business, inquiry business, and online consultation business.

7. The method according to claim 6, characterized in that Also includes: receiving a fifth user operation corresponding to a third login object, and sending a fifth login request corresponding to the third login object, wherein the user account of the third login object is the same as the user account of the second login object; Second login restriction information for the fifth login request is displayed.

8. The method according to claim 7, characterized in that The second login restriction information includes: prompt information for performing the second login restriction on the third login object, and / or login failure information for performing the second login restriction on the third login object.

9. The method according to claim 8, characterized in that Also includes: receiving a sixth user operation corresponding to a fourth login object, and sending a sixth login request corresponding to the fourth login object, wherein the user account of the fourth login object is the same as the user account of the second login object; A second successful login page for the sixth login request is displayed.

10. The method according to claim 9, characterized in that The third login object is an application corresponding to the second login restriction, including at least one of the following: Payment applications, medical applications, social applications, cloud storage applications, and government service applications; The fourth login object is an application that does not correspond to the second login restriction, including at least one of the following: a learning and lecture application, a technical blog application, and a game application.

11. The method according to claim 10, characterized in that The third login object and the fourth login object belong to the same second application, Among them, the third login object is a business corresponding to the second login restriction, including at least one of the following: payment business, transaction business, and online supermarket business; the fourth login object is a business that does not correspond to the second login restriction, including at least one of the following: mini-game business, query business, and online consultation business.

12. A login method, characterized in that: Applied to a server, the method includes: receiving a first login request corresponding to a first login object, wherein the first login request is obtained based on a first login page; In response to the first login request, sending a second login page content corresponding to a failed login of the first login request; receiving a second login request corresponding to the first login object, wherein the second login request is obtained based on content of the second login page, and a login security level of the second login page is lower than a login security level of the first login page; Based on the second login request not satisfying a first login condition, a first login failure message is sent, wherein the first login condition includes: the login object is an object that is not restricted from login.

13. The method according to claim 12, characterized in that Also includes: receiving a third login request corresponding to a second login object, the security requirement of the second login object being lower than the security requirement of the first login object, wherein the third login request is obtained based on a third login page; In response to the third login request, sending a fourth login page content corresponding to the failed login of the third login request; receiving a fourth login request corresponding to the second login object, wherein the fourth login request is obtained based on content of the fourth login page, and a login security level of the fourth login page is lower than a login security level of the third login page; Based on the fourth login request satisfying the first login condition, a first login success message is sent.

14. The method according to claim 13, characterized in that Also includes: receiving a fifth login request corresponding to a third login object, wherein a user account of the third login object is the same as a user account of the second login object; Based on the fifth login request not satisfying a second login condition, a second login failure message is sent, wherein the second login condition includes: the login object is an object that is not restricted from login.

15. An electronic device, characterized in that: The device comprises: a memory for storing instructions; A processor, configured to execute the instructions to implement the login method according to any one of claims 1 to 14.

16. A readable storage medium, characterized in that The readable medium stores instructions, which, when executed on an electronic device, enable the electronic device to execute the login method according to any one of claims 1 to 14.

17. A computer program product, characterized in that The computer program product comprises: a computer program code, and when the computer program code is run on a computer, the computer is caused to execute the login method according to any one of claims 1 to 14.

Images