Client zero-storage single sign-on method

Abstract

The invention discloses a client zero-storage single sign-on method. The method is that sign-on pages of all application systems are provided by a sign-on authorization center; the information of user signing on the system is stored by the sign-on authorization center and synchronized to a server of each application system at the same time, so that the user information and session ID (or bills) are not stored in the client. By adopting the client zero-storage single sign-on method, the user information can be stored, transmitted and synchronized in the sign-on authorization center and application service, thus that unnecessary information is transmitted to other sides from the client can be avoided, and moreover, the risk that the session ID (or bill) is embezzled can be prevented; the development process of a single sign-on application system is simplified, and the safety performance of the system is improved.

Description

technical field [0001] The present invention is applicable to the field of software, especially the software of BS structure is more suitable to adopt this method to realize the single sign-on of the system. Background technique [0002] Existing single sign-on methods mostly use technologies such as the following: 1. Insert authentication media into the USB port of the client's computer; 2. The client stores the user information after login; plugin. [0003] Among the above four solutions, if the USB of the client computer is inserted into the USB authentication medium, the number of users must be limited, and the distribution and management process of the medium is very troublesome; the client stores the user information after login is suitable for rich client applications; Installing plug-ins on the client side will bring about a decline in user experience. [0004] The client stores the single sign-on session ID (or ticket), which is the mode that stores the least info...

AI Technical Summary

Problems solved by technology

[0005] The way the client stores the session ID (or ticket) has the following deficiencies: 1. The session ID (or ticket) is useless information for the system and must be converted into a user ID before it can be used by the system; 2. The session ID (or ticket) ) It is useless to store on the client side, because the reading of data is done on the server side; 3. It is inconvenient for the client side to store tickets, unlike the server side, which only stores one copy in the Session, which needs to be repeated back and forth to pass between pages

Images