A cross-site server login authentication method

Abstract

The invention discloses a login authentication method of a cross-website server. The login authentication method includes the following steps;S1, generating a secret key file pair; S2, transforming an entry address of a website B into an intra-domain address of a website A, and verifying identity of a user by the website A; S3, when the user is not a user of the website A, returning the entry address of the website B to a user browser, and asking for redirection; S4, when the user is a user of the website, generating an identifier UUID (universally unique identifier) according to a session ID, wherein the UUID and a user login account form a user information character string; S5, utilizing a private key file to encrypt the user information character string, and redirecting the browser to the entry address of the website B; S6, extracting the UUID in a request and judging validity of the UUID by the website B; S7, if the UUID is valid, using a public key file to decrypt an encrypted message to acquire the session ID and the login account; S8, if the UUID is invalid, processing the current user as a common non-logged-in user by the website B. By the login authentication method, sharing of user login information among different website servers in a safe and economical manner is realized.

Description

Technical field [0001] The invention belongs to the field of website design and development, and is a technology for identifying and marking user sessions by a server. Background technique [0002] With the popularization of web2.0 technology, a large number of enterprises put their own business and work flow on the website to achieve efficient and standardized office capabilities. With the development of enterprises, the enterprise-level architecture of this business system will become more and more complex, and the development of different subsystems may be led by different departments. The design and implementation of these subsystems often have big differences, and the implementation technology, development language and even the geographic location of the server are not the same. This difference makes the standardization and sharing of data between various website subsystems a difficult problem. The most troublesome problem for enterprises and developers is that when users j...

AI Technical Summary

Problems solved by technology

However, there are also some problems in the single sign-on system. First, the authentication server needs to be deployed separately. For a website system with a slightly simpler structure, this increases the economic budget and maintenance costs; second, if it is not in The entire enterprise-level system was designed with the single-sign-on mechanism in mind at the beginning, but it was added in the integration process of the existing subsystems. It is necessary to refactor the subsystems in the existing production environment and rewrite the user authentication module. , it takes a lot of energy to do so, and there is a risk of system upgrade

Images