Browser-based login processing method and system

Abstract

The invention provides a method and system for login processing based on a browser. The method comprises the steps that a request, with the information that token login is allowed by the browser, for website visiting is sent by the browser and received by a website server; a token is generated through the relevance of the browser and the characteristic information of a website; when the fact that token login is allowed by the website is judged by the website server, the corresponding token is obtained from the browser; validity verification is conducted on the obtained token and if verification is successful, login of the website is allowed. According to the method and system for login processing based on the browser, seamless single sign on can be achieved, the procedure that a user logs in the website is simple and safe, and the user experience is improved.

Description

technical field [0001] The present invention relates to the technical field of mobile communication, and more specifically, to a browser-based login processing method and system. Background technique [0002] The popularity of the Internet enables people to enjoy more and more abundant application services through websites. Since different users have different needs, it is necessary to create a user account for the website they use, and use different user accounts to meet the service needs of different users. For example, when a user wants to enter a website to enjoy a certain service provided by the website, the user first creates a user account, including a user name and password. When entering the website, the website needs to confirm the corresponding identity of the user name and password entered by the user. , before providing it with the desired service. [0003] Before users use the services of a website, the website needs to verify their identity first. That is t...

AI Technical Summary

Problems solved by technology

[0005] 1. The access party (that is, the application service) needs to realize the docking with multiple manufacturers. If the access party does not realize the docking with the manufacturer, the user will need to jump to the authentication page of the authentication center for authentication before logging in, so that Affect the user experience

[0006] 2. Since different application services may be accessed through different manufacturers, and the authentication between each manufacturer cannot be used universally, users still need to provide different authentication accounts when accessing application services on different websites

For example, application A (picture online storage service) uses the access of vendor A, while application B (picture online printing service) uses the access of vendor B. When application B requests to print the pictures stored in application A, it needs to Realize through their respective authentication accounts, which will also make users feel that it is cumbersome to memorize and input account information, which will affect the user experience.

[0007] 3. Since there may be multiple implementation methods for the access of the same application service, when the application developer uses it irregularly, the user still needs to remember the accounts of multiple authentication centers, and it is also impossible to make the user simple and safe. Purpose of logging into the site

[0008] Therefore, the login method of the prior art is still somewhat complicated and inconvenient to use

Images